Dynamic Sequential Approval

UserDefinedProperties

Opens the Following Window:

User Defined Properties Window

Purpose of this Window:

Specifies ClientData values that are associated with the AgileShape's associated tasks at runtime. This is a way for you to specify a set of variable-like name/value pairs that are passed to your web page via a WorkItem object. This is an alternative to passing data via URL parameters. On your web page you can retrieve this data via the ClientData property of the WorkItem and use it however you want.

Approvers

Definition:

Specifies the custom attribute that contains the user names of the participants. The user names in the custom attribute must be separated by a semicolon.

This property works as a part of the loop to specify the participants (who are the approvers) required to complete the activity. The task is assigned to each user one-by-one through each iteration of the loop.

During each iteration, the AgileShape assigns the task to the first user name specified by the Approvers property. Then, the custom attribute associated with this property is modified - the first user name is removed from the list, and the next user name is assigned to the task for the next iteration of the loop until all the approvers complete the task.

Allowed Values:

A custom attribute.

Note: The value of this property must be the name of a custom attribute. The value of the custom attribute must be initialized elsewhere using an Update Custom Attributes AgileShape.

If the value of the custom attribute is not updated in the loop, it ends up in an infinite loop.

Default Value:

$Approvers

Custom Attributes:

Yes

LoopCondition

Definition:

The custom attribute that specifies the status of the sequential loop as a Boolean value.

The value of the custom attribute is updated each time the AgileShape exits an iteration of the loop to determine whether more participants are remaining to complete the task.

The value of the specified custom attribute must be checked using a Single Condition AgileShape to determine when the process needs to exit from the loop to move to another activity.

Allowed Values:

A custom attribute.

Note: The value of this property must be the name of a custom attribute. The value of the custom attribute must be initialized elsewhere using an Update Custom Attributes AgileShape.

Default Value:

$HasMoreApprover

Custom Attributes:

Yes

EnabledExchangeServer

Definition:

Integrates the AgileShape with Microsoft Exchange Server. The AgileShape's associated tasks are visible in the Microsoft Outlook's task list to the assigned participants.

Allowed Values:

• False - The AgileShape in not integrated with Microsoft Exchange Server.
• True - The AgileShape is integrated with Microsoft Exchange Server that enables the participants to view the assigned tasks in Microsoft Outlook.

Default Value:

False

ExchangeServer

Opens the Following Window:

Exchange Server Configuration Window

Purpose of this Window:

Integrates an AgileShape with Microsoft Exchange Server. When this connection is properly configured, the AgileShape will then insert, update, and remove tasks for the assigned participants, so that the tasks can be viewed directly from Microsoft Outlook.