Histórico da Página
HTML |
---|
<div id="main-content" class="wiki-content group">
<h1 id="EventosFinaisdeprocesso-Eventofinaldeprocessocomum">
<img class="confluence-embedded-image"
src="http://tdn.totvs.com/download/attachments/126714950/17.png?version=1&modificationDate=1393445981000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/126714950/17.png?version=1&modificationDate=1393445981000&api=v2">Common
process final event
</h1>
<p>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). </p>
<h1 id="EventosFinaisdeprocesso-Eventofinalcomerro">
<img class="confluence-embedded-image"
src="http://tdn.totvs.com/download/attachments/126714950/18.png?version=1&modificationDate=1393445990000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/126714950/18.png?version=1&modificationDate=1393445990000&api=v2">Final
event with error
</h1>
<p>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.</p>
<h1 id="EventosFinaisdeprocesso-Eventofinaldecancelamento">
<img class="confluence-embedded-image"
src="http://tdn.totvs.com/download/attachments/126714950/19.png?version=1&modificationDate=1393446001000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/126714950/19.png?version=1&modificationDate=1393446001000&api=v2"> Final
cancellation event
</h1>
<p>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.</p>
<h1 id="EventosFinaisdeprocesso-EventofinaldeSinal">
<img class="confluence-embedded-image"
src="http://tdn.totvs.com/download/attachments/126714950/20.png?version=1&modificationDate=1393446010000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/126714950/20.png?version=1&modificationDate=1393446010000&api=v2"> Signal
final event
</h1>
<p>When finishing the request, a signal will be issued and it will
be captured by signal reception activities in other processes.</p>
<div>
<h1 id="EventosFinaisdeprocesso-Eventofinalmúltiplo.">
<img class="confluence-embedded-image"
src="http://tdn.totvs.com/download/attachments/126714950/21.png?version=1&modificationDate=1393446017000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/126714950/21.png?version=1&modificationDate=1393446017000&api=v2"> Multiple
final event.
</h1>
<p>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.</p>
<h1 id="EventosFinaisdeprocesso-Eventofinalterminal">
<img class="confluence-embedded-image"
src="http://tdn.totvs.com/download/attachments/126714950/22.png?version=1&modificationDate=1393446023000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/126714950/22.png?version=1&modificationDate=1393446023000&api=v2"> Terminal
final event
</h1>
<p>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.</p>
</div>
<p> </p>
</div> |
Import HTML Content
Visão Geral
Conteúdo das Ferramentas