Tasks properties

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Process wizard > Model Process > Modeling for execution >

Tasks properties

 

ELEMENT

CONSIDERATIONS

PROPERTIES

Task

User Activities display content to end users as a Case (an instance) flows through a Process. The user interface to be displayed is designed in the Forms modeler.

 

Every task has a Performer. To define who will execute each task, an Assignation Rule must be defined.

Basic Properties

 

Display Name: This is the display name of the Activity that is shown in the Work Portal.

 

Name: This is the name of the Activity in the database.

 

Description: Displays additional information for the Task.

 

Runtime Properties

 

Help text: In this option, the user can configure a help text for the Activity.

 

Url Help: In this option, the user can configure a URL that contains help text for the Activity.

 

Cost: Indicates the cost of Tasks

 

Duration: Determines the maximum time that a Task can be active (unfinished) to consider that it is still on time. It is defined in hours and minutes. The maximum values are:

o35791393 (Hours)

o59 (Minutes)

 

Priority: Indicates the order on which Bizagi will activate or execute Tasks.

 

Reassign: If enabled, the Task can be reassigned by the user during the process. By default, the property is disabled. For more information about this option, refer to Work Reassignment.

 

Notify: When enabled, this property notifies about the assignation to all users that have been assigned to a Task. By default, the property is disabled.

 

Is Singleton: Enables the assignment of special characteristics to the Activity, so that if more than one transition or sequence line enters it, it will not be duplicated if there is already an active instance.

 

Allow to release: If enabled, the Task can be released by the user during the process. By default, the property is disabled. For more information about this option, refer to Work Reassignment.
 

Timer Event Duration: This property is used when a Timer Intermediate Event is attached to the Task.

 

Mobile Access: Enables the task to be executed from mobile devices.

 

Message when activity is completed: Defines the message shown when the task is finished and the end user has no more pending activities in the case. If no message is defined, the Process will show the Global Form.

Service task

Service Tasks are automated tasks that the system executes without any interaction with the end user.

Basic Properties

 

Display Name: This is the display name of the Activity that is shown in the Work Portal.

 

Name: This is the name of the Activity in the database.

 

Description: Displays additional information for the Task.

 

Runtime Properties

 

Cost: Indicates the cost of the Task.

 

Priority: Indicates the order on which Bizagi will activate or execute Tasks.

 

Is Asynchronous: Correspond to automatic Tasks of the process flow, which have been designed especially to call external interfaces. These interfaces are used for integration with customer’s proprietary systems.

 

Retries: Determines the number of times that the asynchronous Task must be executed automatically if an error is thrown.

 

Retry Interval: An interval of time in minutes that must be fulfilled before retrying the automatic execution of asynchronous Task in case of error.

 

Show Feedback: The system will execute immediately and a wait page will be displayed while the request is processed; if this option is disabled, then the asynchronous Task is executed later in the Bizagi scheduler and the user is sent to the Inbox if there are no pending Activities in the Case.

 

Timeout: Allows defining a maximum interval in seconds, in which the execution of the asynchronous Task is possible; the system automatically cancels the operation when the time is reached.

 

Show on Timeline diagram: When checked, this activity will be shown amongst the other activities in the cases Timeline. Read more about the Timeline here.

Receive task

 

Send task

If a Process is waiting for a message, it will be paused until the message arrives or it will change the flow for exception handling.

 

In order to use a throw Message, there has to be a corresponding catch Message that catches the message. It can be a Message Intermediate Event, a Message Start or a receive Task.

 

The Send Task should be configured to identify the target Process and the target shape.

 

The catch and throw messages must have the exact same name and they must be in different Processes.

Basic Properties

 

Display Name: This is the display name of the Activity that is shown in the Work Portal.

 

Name: This is the name of the Activity in database.

 

Description: Displays additional information for the Task.

Script task

Script Tasks are automatic tasks used in Bizagi to send custom notifications (emails).

Basic Properties

 

Display Name: This is the display name of the Activity that is shown in the Work Portal.

 

Name: This is the name of the Activity in database.

 

Description: Displays additional information for the Task.

Manual task

This is a Task that is expected to be performed without the aid of any application. An example of this could be secretary filing physical documents.  Manual Tasks display content to end users as a Case (an instance) flows through a Process.

 

Every task has a Performer. To define who will execute each task, an Assignation Rule must be defined.

Basic Properties

 

Display Name: This is the display name of the Activity that is shown in the Work Portal.

 

Name: This is the name of the Activity in database. It cannot be modified.

 

Description: Displays additional information for the Task.

Conditional task

Conditional activities are an extension to BPMN 2.0. They are turned on or off depending on the data flowing through a case.

 

A Boolean expression must be defined in order to activate this task. If no expression is defined it will behave as a regular Task.

 

If the condition set becomes true, the activity will be enabled and allocated.

 

If the condition becomes false, the activity will be turned off.

 

It does not require an incoming sequence flow.

 

Every task has a Performer. To define who will execute each task, an Assignation Rule must be defined.

 

This task displays content to end users. The user interface to be displayed is designed in the Forms modeler.

Basic Properties

 

Display Name: This is the display name of the Activity that is shown in the Work Portal.

 

Name: This is the name of the Activity in the database.

 

Description: Displays additional information for the Task.

 

Runtime Properties

 

Help text: In this option, the user can configure a help text for the Activity.

 

Url Help: In this option, the user can configure a URL that contains help text for the Activity.

 

Cost: Indicates the cost of Tasks

 

Duration: Determines the maximum time that a Task can be active (unfinished) to consider that it is still on time.

 

Priority: Indicates the order on which Bizagi will activate or execute Tasks.

 

Reassign: If enabled, the Task can be reassigned by the user during the process. By default, the property is disabled. For more information about this option, refer to Work Reassignment.

 

Notify: When enabled, this property notifies about the assignation to all users that have been assigned to a Task. By default, the property is disabled.

 

Allow to release: If enabled, the Task can be released by the user during the process. By default, the property is disabled. For more information about this option, refer to Work Reassignment.
 

Timer Event Duration: This property is used when a Timer Intermediate Event is attached to the Task.

 

Mobile Access: Enables the task to be executed from mobile devices.

 

Message when activity is completed: Defines the message shown when the task is finished and the end user has no more pending activities in the case. If no message is defined, the Process will show the Global Form.