Bizagi Extended Attributes

Bizagi allow to add extended attributes to Tasks. There are special attributes thar are used in Bpm Flow.

Extended Attribute [seasideComponent]
If it is present the BpmFlow engine will use a SeasideComponent to render the task. And the name of the component is the value of the attribute.
If it is absent the BpmFlow engine will use an Orbeon Form to render the task. The form's name is the task's name.

Extended Attribute [previousFields]
This option is used when a form need to show a value of a previous form in the process. Previous fields are separated by blank space (name surname id). Adding these fields will make the Bpm Flow to send their values in token interchange. In the host form these fields must be read only.

Extended Attribute [executionTime]
Each task can be set with the expected execution time. There are three supported type of expected execution time:

• In Days
• In Hours
• In Minutes

When a task instance is created and it has a expected execution time then a warning will be displayed to the user.
Expected Execution Time it takes three arguments from Bizagi field:

• Type (days, hours, minutes) + Value
• Warning Threshold
• Calendar name.

The warning will be show when [Warning Threshold] is reached by counting time from task creation. To count time a [Calendar] is used.

Possible configurations:
5d,70%,Default
This will set a In Days (count) with 5 days as value and with a threshold of 70% (a warning will be show after the 70% of time to finish the task is consumed). The calendar named 'Default' will be used to count days.

8h,50%,Default
This will set a In Hours (count) with 80 hours as value and with a threshold of 50% (a warning will be show after the 50% of time to finish the task is consumed). The calendar named 'Default' will be used to count hours.

Assignation Policy [assignationPolicy]

Each Bpm Process Definition can have an assignation policy to automatically assign tasks to users. The assignation policy can be set in Backoffice application or can be set inside Bizagi®. By default all Bpm Process Definitions have a none assignation policy so users must peek available task to them. To set assigantion policy in Bizagi® create a extended attribute named "assignationPolicy" which can have the following values:

• BpmNoneAssignationPolicy (default no need to be set)
• BpmFairAssignationPolicy
• BpmRoundRobinRoleAssignationPolicy
• BpmRoundRobinTaskAssignationPolicy