Required information: Description
Description of the activity to comprise the process. Instructions
Instructions that make it easy to understand the activity in the process. When preparing the instructions of an activity, it is common to need to search for information from other files or websites. There is the concept of hyperlinks, which allow adding access to both TOTVS Fluig Platform documents and Internet addresses via external documents, avoiding replication of information and making it easier to browse. To do this, add the tag [WD:999999], replacing 999999 by the document code in document browsing. Working Hours
Working hours to which the activity will be associated. Working hours are registered on the platform and are used for calculation of deadlines and delays for process activities. For example, if the working hours were configured as being from Monday to Friday, from 8:00 a.m. to 6:00 p.m., and there is an activity that lasts 1 hour and was created at 5:30 p.m. on Tuesday, its completion deadline will be Wednesday at 8:30 a.m., due to the working hours. Assignment mechanism
The way how users will be selected to perform the activity. It only displays the types of assignment mechanism that can be used in regular activities. Available mechanisms: - Assignment by association: when selected, the users that can perform this activity (the ones returned from the combination of several assignment mechanisms) are displayed for selection;
- Assignment by form field: when selected, the activity is assigned to the user that is entered in a field on the form associated to the process;
- Assignment by activity performer: when selected, the activity is assigned to the performer of a previous activity of the process;
- Assignment by group: when selected, the users that can perform this activity (all users belonging to a group) are displayed for selection;
- Assignment by collaborator group: when selected, the users that can perform this activity (the ones belonging to the same groups as the authenticated user or the user who started the request, as configured in the mechanism) are displayed for selection;
- Assignment by role: when selected, the users that can perform this activity (all users belonging to a role) are displayed for selection;
- Assignment for a group: when selected, the activity is assigned to a pool of resources, containing the users belonging to the group. In this case, any user from the group can be assigned the activity;
- Assignment to a role: when selected, the activity is assigned to a pool of resources, containing the users belonging to the role. In this case, any user assigned to the role can be assigned the activity;
- Assignment by user: when selected, the activity is assigned to a specific user.
Completion deadline - By fixed value: Deadline to complete a task. The hourly value is considered, along with the selected working hours, to calculate the deadline for finishing the activity. This deadline is counted as of the activity’s receipt.
- By form field: When selected, allows choosing a form field that will define a deadline for the task whose property is being changed.
| Painel |
|---|
Values valid for the field: - 999:99 = Standard format.
It will follow the same logic of the fixed value, considering the working hours and holidays applicable to the user in charge. For the other values, use the following formats: - 9999-99-99 = year, month and day;
- 9999-99-99 99:99 = year, month, day, hour and minute;
- 99/99/9999 = year, month and day;
- 99/99/9999 99:99 = year, month, day, hour and minute;
- 9999999999 = date in milliseconds.
Working hours and holidays will not be considered, exactly as specified | Nota |
|---|
| When you enter a date without the time, the last time of day is 23:59. |
|
Request digital signature When checked, such activity must be digitally signed by its performer user. In this case, upon completion of the activity, it displays a window where the performer user needs to add their digital signature and, only then, can the request be sent to the next activity. Confirm password
When checked, the user needs to enter their password to finish the activity. If this option is already checked in the process configuration, it will come disabled. When sending the activity that requires password confirmation to the next one, the user who is performing the task has to enter their password. If the password is invalid, the activity performer can try as many times as necessary. The process will only be moved when the performer user enters their password correctly. The process history will indicate that the user has confirmed their password when moving the activity in the request. Please note: the activities checked for password confirmation use cannot be automated by WebServices. Inhibits Transfer option
When checked, the activity cannot be transferred for another user to perform it. Joint activity
When checked, the activity should be performed by more than one user. By doing so, the activity will only be considered completed and the request moved when % of the entered consensus is reached. % Consensus
Percentage of consensus required to consider the activity as completed. This field is enabled only when the option Joint activity is checked. Selects collaborators
Frequency at which it is necessary to select the user to assign this activity when moving the request. Available options: - Always: when checked, it is always necessary to select the user to be assigned this activity when moving the request;
- When there is more than one option: when selected, only when there is more than one user listed is itnecessary to select which user must be assigned the activity when moving the request;
Never (valid for joint activities only): when selected, this activity will be assigned to all users listed by the defined assignment mechanism. When selecting this option, the Joint activity field is automatically checked, and you are also required to enter the % Consensus. |