When designing the process flow of your process, you can add work to be carried out by the end-user. This behavior is implemented through the Human Activity process activity, which you can drag onto your canvas from the Process Flow Toolbox.
The Human Activity allows you to specify and assign a work to be carried out by the end-users in your application. Once the process flow execution reaches a Human Activity the end-user or end-users are informed (in their Taskbox) of the work that has to be carried out. Then, one of them executes the activity and signals that it has been done in the Taskbox, and the Human Activity execution finishes and the process flow execution continues to the next process activity in the flow path.
A Human Activity can have input parameters, output parameters, and callback actions.
If no configuration is done, the Human Activity is assigned to all end-users, that is, it is displayed in the Taskbox of each end-user until it is executed by one of them. However, to force the assignment of a Human Activity to a specific end-user, simply set the User property to the desired end-user. For advanced cases, you may set an expression that returns the user that handles the activity, using the expression editor.
If the execution of the human activity is to be automatically ended after an event occurs over an entity, the kind of event must be set in the Close On property with one of the following entity actions: Create<Entity> or Update<Entity>.
Once you select the kind of event in the On Close property, a list of entity attributes is displayed for you to set the condition to automatically end the human activity: a primary key for a specific record and/or reference attributes for a specific value on an attribute.
For example, if the human activity is designed for a user to carry on an interview but interviews can be cancelled, then the Close On property must be set with the UpdateInterview entity action and the interview status attribute with the cancelled code.
You may add security to your Human Activities to be sure that only authorized end-users can execute the activity, which is especially useful for critical or high responsibility activities. For this, simply check the roles allowed to execute the Human Activity. Learn more about security.
Service Studio provides you with mechanisms to access Human Activity process activities among eSpaces. You can expose your Human Activity process activities to other eSpaces or use Human Activity process activities defined in another eSpace.
Changing the Close On property to listen to events from another entity only has effect on Human Activity instances that are created after the change. All instances that were already executing will continue listening to events from the previous entity. Therefore, you should only make this change when there are no more Human Activity instances listening to the previous entity.
Human Activity Properties | Process Business Rules Actions | About Roles | Expose a Process Activity | Use Process Activity References | Process Flow Toolbox