Setting

Definition

Node

A short description that will be used to describe the process point in the History log and elsewhere.  If the workflow was laid out using a standard workflow template, use the node number assigned to each step in the workflow.

Description

Long description for the process point.

Workflow to which this process point belongs

Each process point must be assigned to a top-level workflow.

This process point is locked by

Allows a process point definition to be locked by an individual.

Owner

Name of individual who "owns" this process point (if applicable)

Type

Type of process point.  Different settings will be available based on this choice.

Action to be performed

Depends on type.  Defines the action to be performed first.  When an action is chosen, several other parameters may be available to be selected to completely define how the action will proceed.

Conditionally move to next process point

You may optionally select one or two conditions, which if true, will cause the workflow thread to advance to the next process point.  One condition may be chosen to cause, if true, progression to the process point defined for Approved.  A second condition may be chosen to cause, if true, progression to the process point defined for Denied.  Conditional progression is only available for Process-then-Decision process points, and then only for those with an action that causes a wait (such as sending an email for an approval).

Note, if you specify both a condition for the Approved path as well as a condition for the Denied path, the Approved path condition will be evaluated first.  If both conditions evaluate to true, the Approved path will be taken.

The condition(s) specified must be set against the main table of the thread, for the record whose primary key value is carried in VKEY of the thread.  As an example, if the workflow is designed to handle approvals for the software request portal, then the thread table will be the software orders table.

Work item gets forwarded to this process point if approved

If the process point type is Process, then Decision and the request is approved, this will be the next process point.  If the process point type is Process, then Forward, this will also be the next process point.

Otherwise, move to this process point

If the process point type is Process, then Decision and the request is denied, this will be the next process point.  This setting does not apply to Process, then Forward types.

If an error occurred, move to this process point

This section allows the definition of up to four different branches depending on various error codes that may be returned by the current process point.  The error conditions are tested in order, and the first match that occurs will cause the workflow to branch to the process point defined to handle that error. Error codes may be entered as a list, separated by commas.  If any error code in the list is matched, the specified process point will be next.  Error codes may also be entered with the wildcard matching character (asterisk - *).  For example, entering 110* will cause any error returned by function 110 to be matched.

Time limit for a work item at this process point

Defines the time, in hours, that a request can be outstanding before an approval reply will be ignored.  The request will expire when this time has passed.  A setting of 0 means there is no time limit.

When max time expires, move to this process point

When the time limit expires, the workflow engine will move to the process point specified.

Time at this process point before first escalation
(not yet implemented)

Amount of time, in hours, after the first notice is sent before the notice is sent again.  Applies to approvals (or any process point that is waiting for a reply)

Time at this process point before second escalation
(not yet implemented)

Amount of time, in hours, after 2nd notice is sent before the notice is sent again.

Time at this process point before third escalation
(not yet implemented)

Amount of time, in hours, after 3rd notice is sent before the notice is sent again.

Minimum % of approvals required to approve

This only applies to approval requests that are sent to a Group for approval.  CAB approval percentage is taken from the CAB settings.  This setting defines the minimum percentage of approvals received back from the group to constitute an overall request approval.  For Groups, a 100% quorum is required (a reply must be received from every member to which a request was sent before the minimum approval number will be applied to determine if approval was achieved.