Welcome > Process Designer module > Design a basic process map > Activity > Configure the properties of an activity > Configure the advanced properties of an activity > Preconditions > Set up activity preconditions

Set up activity preconditions

See Preconditions.

  1. Select the activity for which to set preconditions.
  2. On the Extended Properties page, click the Advanced tab.
  3. In the Preconditions box, use either option:

    • Use a static value. For example, if an activity should become pending when three instances of the event called PROCESSEVENT1 have been raised, create a precondition, PROCESSEVENT1=3.

      Note

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

      • Reuse a precondition by pasting into another precondition.

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

    • Consume a numeric variable, existing process event, document set or a document type.

      Note 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 value of VAR1=5, the event will fire five times to fulfill the precondition.

  4. To set the preconditions for a document set:
    1. Click the Document Set button next to the Preconditions box.
    2. Consume Document sets. At runtime, the precondition only evaluates to true when all the document type rules in the specified document sets are met.
      Alternatively, consume specific document types. At runtime, the precondition only evaluates to true when the rules defined against the specified document types are met.
  5. Click Save.