Histórico da Página
...
Flows are the mechanisms that define to which activity the request should followgo. They determine the path that the request will take as the stages or activities are completed.
Flows are represented by arrows that indicate the direction of movement, which can be either a one-way path – from the source activity to the destination target activity – or a return – from the destination target activity back to the source activity.
...
The common flow is the standard flow for moving the request between activities. It is the flow used most used flowoften, allowing the request to be moved move from one activity to another without the possibility of returning to the previous activity.
The common flow is represented by an arrow that indicates the direction in which the request will be movedmove.
Automatic flow
...
The automatic flow moves the request automatically to the destination target activity when after reaching the deadline of the source activity has been reached , and it has is not yet been completed, fulfilled; that is, the request has not yet been moved to the next step.
The automatic flow is represented by a A clock in the middle of the arrow that indicates pointing the direction in to which the request will be movedmove represents the automatic flow.
For the automatic flow to work correctly, it is necessary required that:
- the source activity has have a defined deadline;
- there is a scheduling of the type Automatic flow exist in the Task scheduler, determining a time interval from which requests that are stalled in activities with automatic flow are checked and moved.
| Informações | ||
|---|---|---|
| ||
→ Since the automatic flow only moves the request after the deadline of the source activity has been is reached, it is you must also necessary to configure a common flow in the source activity to allow conventional movement, ; that is, to allow the request to be moved move before reaching the deadline for completion of the source activity. → During the execution of While running an automatic flow, there is no authenticated user is performing the movement. Therefore, events that use the authenticated user through APIs must consider this fact to avoid inconsistencies in execution. |
| Painel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Return flow
...
The return flow allows the request to go back to the originating source activity.
When the request is moved moves from the originating source activity to the destination target activity through a flow that allows return, upon completing the destination target activity, it will be possible to you can return the request to the previous activity, ; that is, the originating one.
The person responsible for receiving the request will be is the same person who previously completed the originating source activity, ; that is, who moved it to the destination target activity last.
The return flow is represented by an arrow starting from the destination target activity and pointing to the originating source activity.
Automatic flows You can also be configured configure automatic flows to allow returnreturns. In this case, its representation will also have a clock in the middle of the arrow, as follows: 
.
| Informações | ||
|---|---|---|
| ||
The You can only use the return flow can only be used in the version of the process in which the request is located during the movement. Therefore, if you convert the request is converted to another version of the process, in its first movement after the conversion, it cannot return to the previous activity, since there will be a movement that represents the conversion and, therefore, it will lose the possibility of immediate return. |
| Painel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
Flows have predefined messages that are displayed at the moment of moving the when you move the request from the originating source activity to the destination target activity. However, you can customize these messages can be customized according to in accordance with the process or stage.
| Painel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
| Painel | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||
Flow type
Common flow title
Return flow Return flow title
|
03. Click on the Flow Message tab to customize the message displayed when the request goes through this flow.
| Painel | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The flow message is displayed upon completing the movement of the request from the source activity to the destination target activity. These messages already exist by default; however, they you can be customized customize them if desired.
Title
Description
Request link text
|
04. Click on Save draft – located on the right side of the top bar – to save the settings made in the Flow component.
05. In the displayed message, click on Ok, I understand.
| Informações | ||
|---|---|---|
| ||
This documentation is valid from the Voyager update (2.0) update onwards. If you are using a previous update, it may contain information different from what you see on your platform. |
| HTML |
|---|
<!-- Hotjar Tracking Code for http://tdn.totvs.com/display/fb -->
<script>
(function(h,o,t,j,a,r){
h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)};
h._hjSettings={hjid:1280165,hjsv:6};
a=o.getElementsByTagName('head')[0];
r=o.createElement('script');r.async=1;
r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv;
a.appendChild(r);
})(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv=');
</script> |
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas