|
Use the following options to execute or perform other operations with the activity:
A
|
The activity actions allow you to execute the current activity and send the flow to another element of the process. When you perform an activity action, the system may automatically perform some operations such as executing an external application, sending an e-mail notification, or enabling a timer event, among others. Each action refers to an output flow of the activity that is being executed.
Before clicking on this option make sure all the required fields of the activity data screen, have been properly filled out. Depending on the configurations made in the activity action data during the process modeling (SE Process), filling out some fields or associating some objects may be required for the activity to be executed successfully.
|
|
B
|
The Previous step action allows the process flow to return to the previous activity without the need for return action modeling. To perform this action, first, fill in the Comments field with an explanation and then click on the corresponding option. At this time, the previous activity will be enabled for the party responsible to execute it again.
▪This action will only be displayed if the "Disable action for sending record back to previous activity" option has not been checked in the activity data (Configuration  Instance) during process modeling. If the option is unchecked, this action might not be displayed when the activity under execution is the first activity of the instance or a sub-activity, or when there is a sub-process or a gateway in the return path between the activity under execution and the previous activity. ▪This action will not be displayed if in the previous activity there are actions that change the status of the action plan. |
|
C
|
When an activity is returned, the executor can perform the following actions:
▪Undo execution: This action cancels the execution of the subsequent activities of the activity in question, allowing a new execution to take place. That is, when executing this action, the activity screen is reloaded with the action options that appear when the activity is enabled for the first time. Remember that when performing this operation, it is necessary to provide an explanation in the Comments section. ▪Resend: Enables to send the activity to the same point of the flow where it was before, undoing execution is not necessary.
|
D
|
This action enables responsible user to Delegate the execution of the activity to another user. First of all, it is necessary to fill out the Comments field with a reason and then click on the corresponding option. At this point, a screen to select the user who will take the responsibility for the execution of the activity will be displayed. When saving the selection made, the activity will be enabled for the new party responsible to execute.
This action will only be displayed if the "Allow activity to be assigned to another user" option has been checked in the activity data (Configuration Instance) during the process modeling.
|
Remember that the activity delegation may be limited to users that have the same functional role as the current activity executor, to users of a specific functional role or to users of a specific team. This configuration is set on the activity data screen (Configurations  Instance), during the process modeling. If no restriction has been configured, then the activity can be delegated to any user.
|
|
E
|
This action allows you to finish a sub-activity execution.
|
|
