Pools

Pool is a container of a diagram. Most of the business processes require more than one diagram for different operations. For example advance request and expense payment diagrams can be defined in one process. 

For a pool, you can configure the following:

Name
Identifies the pool. This information is used only by process designers and is not visible for users.

Default Form
Default selected form to show users if task does not specify any form.

Data Root
Root data element is used from data model. Different pools may share the same root element if it is needed.

Is Administrative ?
Check this option if the pool is used only for administrative operations. When checked, the pool can only be accessed by the user that has "write" permission on the process, or if the user is an admin. For example; You may need to create an Options diagram to set process preferences.

Is Anonymously Accessible ?
Check this option to allow the access for the anonymous (non-logged in) users. This option also requires anonymous access permission on domain preferences.

Documentation URL
Documentation URL address is used to link process documentation.

Support URL
Support URL address is used to link support site.

After pool is created you can configure the tasks, roles and routes from graphical designer.

Pool also contains following properties:

Open Script

Please refer to the Instance Opening Script for more details.

Closing Script

Please refer to the Instance Closing Script for more details.

Terminating Script

Please refer to the Instance Termination Script for more details.

Templates

List of the message templates to be used for mail notifications. More information can be found at the Templates section.

Variables

List of the variables which will be used in a scripting environment. Variables are used to define and easily update static values for rule validations, formulas etc. Defined variables can be accessed with $ sign prefix. Example: $ExpenseLimit

Variable values can be overriden with Task definitions to update the value only in a task scope. Example: $AllowPriceChange can be set to false in pool definition and can be set to true for administrative type tasks to disable the rule validation.