Common
process final event
It indicates the end of the workflow process This task is not assigned to any user as it is only an indication that the workflow request was completed. No post-processing will happen after the end of the workflow request. (However, it is possible to perform post-processing through customization).
Final
event with error
This indicates that the workflow request was completed with an error from the organization’s business point of view. At an execution level, Fluig will behave in the same way as if executing a common end. The only objective of this notation is to clarify the business point of view that the workflow request did not follow as expected.
Final
cancellation event
It allows to cancel a workflow request through its navigation. If the workflow request is moved to this activity, it will be canceled. This is the same effect as the one obtained by canceling open requests through my requests option in the Task Central.
Signal
final event
When finishing the request, a signal will be issued and it will be captured by signal reception activities in other processes.
Multiple
final event.
This event allows you to send multiple signals and execute several conditional scripts. In this case, conditional scripts will only be executed and their return will not be validated. This component is recommended in cases where it is necessary to send different signals after the end of the process. This activity has no scheduling and will not prevent the end of the request. The request will be closed and the script execution and signal sending will be as a post-processing at the end of the workflow request.
Terminal
final event
This event behaves similarly to the common process end. The notation indicates that the process has been terminated and that no type of compensation or post-processing will occur.
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas