Here you can specify which documents to route to a process step. This is required when you branch the process flow, if you want to prevent documents from being routed along multiple branches of your process.
You do this by specifying one or more expressions (conditions) that determine if the process rule applies to the current document. Click
to specify such an expression.An expression consists of these parts:
column | The logical operation that links the expressions (used when you specify more than one expression or if you specify a sub-expression). |
column | The document property
to be evaluated. ( |
column | The operator that is applied to the document
property. ( |
column | The value to associate with the operator. Depending on the operand, select a value from a list or type a value. |
Optional: Click add design comments to a process rule.
toUse these settings to:
How long (in days, hours, minutes, and/or seconds) to delay processing. | |
Applies the process rule to only root documents. | |
Applies the process rule to sub-documents, too. Then select one of these routing options:
If canceled documents are to be ignored when applying the rule, select .Note: Quick access values are only added to root documents meaning that the rule only applies to those documents even though Rule applies to root and sub-documents is selected. | |
Changes the priority of all documents processed in this rule. Documents with a higher priority value are prioritized. Select and specify one of these options:
Tip: You can also change the priority in the Process Monitor. |
These settings are used to add field values to documents that pass through the process rule.
column | The name of the field. |
column | The field value. |
column | If selected, creates the field recursively for every sub-document of the root document. |
These settings are used to add quick access values (match codes) to tasks that
pass through the process rule. These can be used to find documents more
quickly in the Process Monitor (click in the area). The values can also be edited there.
Developer tip: You can also use the GetNextDocument method that is available in the XBOUND API to find documents by their match codes. (See Customizing XBOUND using the API.)
Note: Existing values, if any, are overwritten when a process rule sets a quick access value (match code).
The first match code to add (or change) in each task that passes the process rule. Enter max. 200 characters. | |
A second match code to add (or change) in each task that passes the process rule. |