Creating a Condition Event

Use the Set Conditions step to specify the conditions that must be satisfied for the starting event to run.

  1. In the Event type menu, select the type of event in the repository for the starting event to run. (More information below)
  2. In the Repository menu, select the repository you want to monitor for the selected event type.
  3. Under Event Options, if you want the event to be activated by workflow or business process actions within the repository, select the Allow workflows and business processes to satisfy the following conditions. option. (More information below.)
  4. In the box below, set the conditions that must be matched for the starting event to run. You can have up to 16 conditions per starting event.

Example: You want to start a workflow when a document containing three pages is created in a specific repository. You can do this by selecting Entry Created as the event type and Document: Page Count equals 3 as the condition.

Selecting an Event Type

You can select from the following types of event types:

Event Type Options
Event Type Description
Entry Created An entry is created in the repository.
Entry Moved An entry is moved in the repository.
Entry Copied An entry is copied from within the repository.
Entry Changed An entry undergoes some type of change in the repository.
Entry Deleted An entry is deleted from the repository.
Entry Restored An entry is restored after being deleted from the repository.
Document Signed An entry is signed in the repository.

About Allowing Workflows and Business Processes to Satisfy Conditions

When the Allow workflows and business processes to satisfy the following conditions. option is enabled, business processes and workflows can satisfy the event conditions and invoke workflow instances running under the ProcessAutomationUser account. For example, a starting event can activate when an entry is created, and start a workflow that can create entries. This will create a loop of the workflow activating the starting event potentially unexpectedly. These invocations will contribute to your Workflow service limits.