Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Pool is a container of 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 following:

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

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

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

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

Is Anonymously Accessible ?
Check this option to allow 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 tasksroles and routes from graphical designer.

Pool also contains following properties:

Open Script

Script to be executed for every new instances just before first task. This script may be useful to assign dynamically changing default values. (ex: assign current date to form value) Please refer to scripting section for more detail.

Closing Script

Script to be executed for every normally closed (by user action or deadline) instances. This script may be useful for export process data to any external system. Please refer to scripting section for more detail.

Terminating Script

Script to be executed for terminated (forced by administrative or system) instances. Please refer to scripting section for more detail.

Templates

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

Variables

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

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

 

  • No labels