How a workflow operates

Workflows have several dependencies and working parts that need to be configured in order to function properly. Typically, a workflow operates in the following fashion:

  1. A workflow instance is started when a client application triggers an event listener, or a user manually starts a workflow.
  2. The event listener or the manual entry signals the initiation of the workflow process.
  3. The workflow's primary action is invoked and the process begins.
  4. The primary action instance invokes one or more subsequent actions.
  5. Each action has attributes assigned that govern how it should operate. The action in turn invokes one or more actions according to its configuration.
  6. One of the components of a workflow can be requiring approvals from designated approvers of actions (changes, requests, and so on). When the workflow encounters an approval action, the process is temporarily paused, and resumes once the approval has been received.
  7. The sequential or parallel routing continues until each thread reaches a termination point.

When you include an action that involves more than one approver, you can decide whether to require all approvers to OK the request or whether only one approval is required. If you specify All must approve, you can also indicate a percentage, in order to allow something less than 100% (percentages are always rounded up).  If you specify Any may approve, the process will continue as soon as a single approval has been received.

If you include a group, Process Manager treats the entire group as an individual approver. Once an approval or denial is recorded by any member of the group, the approval is treated as a group decision and other group members can no longer approve or deny.

Required components of workflows

You need to configure the following components to successfully run a workflow:

Optional components of workflows

You can also apply optional components to your workflows: