Wait for Entry Change

Wait for Entry Change activity

This activity pauses the workflow until a specified condition is satisfied. Learn about tokens this activity produces

To set up this activity:

  1. Drag the activity from the toolbox pane and drop it in the Designer pane.
  2. In the properties pane, type a name and description of the activity.
    The name and description editors
  3. In the Connection Profile property box, select the repository you want the activity to use.
  4. In the Entry to Wait for property box, select the entry you want the activity to act on. Learn more about selecting an entry
  5. In the Wait Condition property box, click Edit conditions....
  6. Configure the conditions.
  7. Click OK.

You may want to disable activities if you only want to test specific sections of your workflow. To disable activities:

  1. Select an activity in the designer pane to highlight it.
  2. In the Description property box, clear Enable.

Tokens for Wait for Entry Change Activity

This activity produces the following tokens:

Tokens
Name Description Sample Syntax
Initially Satisfied The token returns "True" if the wait condition was initially satisfied. %(WaitforEntryChange_Initially Satisfied)
Duration How long it took the wait condition to be satisfied. %(WaitforEntryChange_Duration)
Event Id The event ID number for the wait condition being satisfied. %(WaitforEntryChange_Event ID)
User Name The user who satisfied the wait condition.* %(WaitforEntryChange_User)
User SID The SID (Security Identifier) of the user who satisfied the activity's wait condition.* %(WaitforEntryChange_User SID)

The "WaitforEntryChange" portion of the syntax changes to match the activity's name.

Note: All non-alphanumeric characters, except underscores, are removed from the name. For example, if you rename the activity "Wait for (Approval)", the syntax for the Event Id token will be "%(WaitforApproval_Event Id)".

*When a wait condition is satisfied, two tokens are created that indicate who satisfied the condition (User Name and User SID). However, in the unlikely event that two users make changes to the entry within a short time period, the tokens indicate the user who made the changes that caused the wait condition to be evaluated, not necessarily the user who made the changes that caused the wait condition to be satisfied.