Add preconditions

To specify a static value so that activity should become pending when three instances of the event called PROCESSEVENT1 have been raised, create a precondition, PROCESSEVENT1=3.

• Use static values to create multiple conditions within a precondition. For example, ((EVT1 >=5) OR (EVT2 = 6 and EVT3 = 4))

• You can reuse a precondition by pasting it into another precondition.

• You can use null check-in condition text. For example, [nullstr] = null and [nulldate] =null. You cannot use "Null" or "NULL".

To use a dynamic value, right-click on the rule editor and select a numeric variable (process or server), existing process event, or a document type.

• If a numeric variable is used in the precondition such as PROCESSEVENT1=VAR1, the precondition will evaluate the number of times the event is fired based on the value of the variable. For example, if the value of VAR1=5, the event will fire five times to fulfill the precondition. If the required process variable is not available for preconditions, you can create a new variable directly from the activity properties panel. See Create a process variable while configuring activity properties.

• If specific document types are used, the precondition only evaluates to true when the rules defined against the specified document types are met.

• If a document set is used in the process, you can use the Valid (set to Bool variable) and Count (set to Short variable) properties of the document set. You can use document set properties without events. For example, create two process variables: a Bool variable and set the value to false, and a Short variable and set its value to 1. Add the activity preconditions by setting the Valid property of the document set to Bool variable and the Count property to Short variable. At runtime, when the document is uploaded, based on the document set the values of Count and Valid are updated and the activity becomes pending only if the preconditions are satisfied.