Configuring the User Task
After starting the construction of a workflow it is necessary to understand how to configure a user task so that your experience at the time of building is as practical as when the end-user uses the workflow.
Before getting started
At the very least, you will need to have a flow being recorded as it is not possible to save the flow if it does not have an input and an output event. For this to happen, it is necessary that the two events have a task so that it is possible for the user to interact with the flow in some way.
Procedures for configuring the User Task
- Open or build a Flow;
- Click on the "Diagram" tab;
- To create a User Task, click on Activities to open activity options;
- Select User Task by clicking and dragging to the drawing area;
Double-clicking on the activity will open the following properties:
- Identification
- Name: of the user task;
- Description: detail the user task;
- Identifier: it is a unique acronym for the task and it is used to code Rhino and for Builder forms;
- Counts SLA: it sets "Yes" or "No" ( the "Suspend SLA" status will appear in the ticket management interface);
- Execution percentage: informative field about the percentage of this task in the entire workflow;
- Is it an approval task?: set "Yes" or "No";
- Assignment
- Recipient Type: select whether it will be for a specific group or user;
- Assignment Type: define whether the assignment will be for execution or monitoring;
- Group/User: select the group/user;
- Or Expression: search for an expression already registered;
- User actions
- Select the registration action: it searches for the action already registered (e.g.: approval action, that is, an expression for this purpose);
- Clean button - allows you to delete what was written;
- Build button - allows you to build a new action or expression;
- Input action
- Build expression: it defines an expression directly;
- Select registration action: it searches for an action already registered
- Output action
- Build expression: it defines an expression directly;
- Select registration action: it searches for an action already registered
- Interface
- Interaction type: it is the way in which a Questionnaire or a Builder Form will be applied in the ticket management interface, in a given workflow status. The configuration of items that will be visible can be defined in the portfolio, or configured directly in the User Activity element (of the workflow):
- Defined in the portfolio: it is possible for a ticket template (questionnaire or form) to appear punctually in a workflow status, using what has been configured in the service attribute "Activity" (request/incident) - fields: “CREATION Template” and “Monitoring Template”. This option is advantageous when you have generic workflows used by several services.
- Standard form: default from system
- Builder Form: it has an identifier to call for the workflow triggered by this form
- Knowledge Base
- Link knowledge base: choose the knowledge you want to link to the user task.
- To make a connection with another element of the flow, click once on the item you want to connect, four square dots will appear in the orange color around the item, select the direction you want and drag the orange dot to the item you want the connection to be made;
- To use the connection in the best way it is necessary to configure it. For this, use the symbol "+" that is in the color orange on the connection line and with a double click open the following properties:
- Name - for identification on the connection line;
- Condition - uses a function that gives proper condition to the line;
- Action - uses a specific action for the purpose of the line;
- State - is an expression that generates a status for the activity.