Histórico da Página

You can only edit activities and flows of a process that is in edit mode. 

Start is the initial activity of a process and it indicates where its flow starts. When a new process request is started, it will be the first activity to be run. 

When preparing the instructions of an activity, it is common to need to search for information of other files or sites.

The platform has the concept of hyperlink that allows you to add accesses to platform documents and also to Internet addresses through external documents; thus, avoiding information replication and making browsing easy. So you need to enter the [WD:999999] tag, where 999999 should be substituted by the document code in the platform.

It will only display the types of allocation mechanism that can be used in Start type activities.

When an assignment mechanism is selected for a Start activity, only users returned by the mechanism can start a process request.

When using an assignment mechanism, you need to detail the information to be considered in it for its correct functioning. For more details, check the Assignment Mechanisms feature. 

If it is already checked in the process configuration, this option will come disabled. When advancing from the activity that has password confirmation, the password of the user who is running the task will be requested. If the password is invalid, the user running the activity can try as many times as required. The process movement will only happen when the running user enters the password correctly. In the process history screen, it will contain an indication that the user confirmed the password in the activity movement in the request.
Important: The activities checked for password confirmation use cannot be automatized by WebServices. 

The Consensus % field is only used when it is a joint activity. 

The available options are:

• Always: When checked, it defines that you always need to select for which user this activity should be assigned.
• When there is more than one option: When selected, it defines that only when there is more than one user listed, you need to select to which one of them the activity should be assigned.
• Never (valid for joint activity only): When selected, it determines this activity will be assigned to all users listed by the assignment mechanism.

Important: When the Never option is selected (valid for joint activity only), the Joint Activity field is checked automatically and the Consensus % should also be entered.

If this option is checked, the request requisitor will be notified by email about the activity start. 

If this option is checked, the person responsible for the activity in question will be notified by email that the activity in question is in arrears.
The value entered in the Tolerance field will be the time that platform will wait after the activity deadline expiration to start to send the in arrears notification e-mail, and the value entered in the Frequency field will be the time range between each in arrears notification e-mail send. 

If this option is checked, the request requisitor will be notified by email that the activity in question is in arrears. The value entered in the Tolerance field will be the time that platform will wait after the activity deadline expiration to start to send the in arrears notification e-mail, and the value entered in the Frequency field will be the time range between each in arrears notification e-mail send. 

The available options are:

• Do not control effort: When selected, it determines that the effort should not be controlled. In this situation, it will not be possible to use indicators in CAP that consider the activity effort and cost.
• Based on Estimated Effort: When it is selected, it determines the effort estimated for the calculation will be considered. This value is coming from the Expected Effort field.
• Based on the Annotations of Hours: When it is selected, it determines the effort entered in the annotation of hours will be considered. In this situation, the user must enter the quantity of hours worked in the activity to finish the task.
• Based on End Time: When it is selected, it determines the end time as activity effort will be considered. It considers as end time the time when the activity has remained with the user, considering the working hours and holidays.

For more details of CAP resource use, check the Process Analysis Center feature.

To click the Property option, you need to move the mouse over the element so the options will be visible. 

When preparing the instructions of an activity, it is common to need to search for information of other files or sites.

The platform has the concept of hyperlink that allows you to add accesses to platform documents and also to Internet addresses through external documents; thus, avoiding information replication and making browsing easy. So you need to enter the [WD:999999] tag, where 999999 should be substituted by the document code in the platform.

It will only display the types of allocation mechanism that can be used in common activities. 

The value in hours is considered, along with the working hours selected, to calculate the conclusion deadline limit of the activity. This deadline is considered from the activity receipt. 

If it is already checked in the process configuration, this option will come disabled. When advancing from the activity that has password confirmation, the password of the user who is running the task will be requested. If the password is invalid, the user running the activity can try as many times as required. The process movements can only occur when the executor user enters the password correctly. In the process history screen, it will contain an indication that the user has confirmed the password in the activity movement in the request. Important: The activities checked for password confirmation use cannot be automatized by WebServices. 

That way the activity will only be considered closed and the request moved when the % of consensus provided is reached. 

If this option is checked, the person responsible for the activity in question will be notified by email about the activity start. 

If this option is checked, the request requisitor will be notified by email about the activity start. 

If this option is checked, the person responsible for the activity in question will be notified by email that the activity in question is in arrears. The value entered in the Tolerance field will be the time that platform will wait after the activity deadline due date to start to send the arrears notification e-mail and the value entered in the Frequency field will be the interval of time between the sends of each arrears notification e-mail. 

If this option is checked, the process manager will be notified by email that the activity in question is in arrears. The value entered in the Tolerance field will be the time that platform will wait after the activity deadline due date to start to send the arrears notification e-mail and the value entered in the Frequency field will be the interval of time between the sends of each arrears notification e-mail.

The available options are:

• Do not control effort: When selected, it determines that the effort should not be controlled. In this situation, it will not be possible to use indicators in CAP that consider the activity effort and cost.
• Based on Estimated Effort: When it is selected, it determines the effort estimated for the calculation will be considered. This value is coming from the Expected Effort field.
• Based on the Annotations of Hours: When it is selected, it determines the effort entered in the annotation of hours will be considered. In this situation, the user must enter the quantity of hours worked in the activity to finish the task.
• Based on End Time: When it is selected, it determines the end time as activity effort will be considered. It considers as end time the time when the activity has remained with the user, considering the working hours and holidays.

For more details of CAP resource use, check the Process Analysis Center feature.

The End element indicates the process flow end. All process must have at least one End.

If this option is selected, the requisitor will be notified by email about the end of the request.

If this option is checked, the process manager will be notified by email about the request end.

The automatic activity is a mechanism that, depending of the result obtained, determines to what activity, among the possible ones, the process flow should be forwarded.

It is also possible to edit an existing condition by pressing the Edit button or remove an existing condition by pressing the Remove button.
Important: the platform will obey the addition order of the conditions to execute them, so the request will be moved to the activity defined in the first true condition found.

The target activity will be activity for the request that will be moved when the condition in the question is true.

When using an assignment mechanism, you need to detail the information to be considered in it for its correct functioning. For more details, check the Assignment Mechanisms feature.

To click the Property option, you need to move the mouse over the element so the options will be visible.

Any process added to platform can be used as a Subprocess. When the request is moved for the Subprocess, the main process request is ended and a new Subprocess request is created. If the movement flow allows return, when the main process request is moved to the subprocess, a new request for the subprocess is created and the main process request will be blocked until the end of the subprocess request. As soon the subprocess request ends, the main process request is moved to the activity previous to the subprocess and its execution can continue.

Fork represents the start of parallel activities, all activities and flows that are after Fork and before Join will be executed in parallel.

The Note element is used to provide additional information in the process diagram.

When the note is added to the design area, a text box is displayed where it is also possible to enter the note.

To click the Property option, you need to move the mouse over the element so the options will be visible.

To select a document, the magnifying glass icon must be pressed and browse the folders and documents in the screen displayed. When you find the desired document, select it and click the Select button.

Flows are mechanisms that define to which activity the process may follow. To click the Flow option, you need to move the mouse over the element so the options will be visible. Important: The Subprocess and End elements can only be used as target activity. When this procedure is done in the Document and Note elements, a flow will not be created, but an association will, since they are not considered process activities.

To click the Property option, you need to move the mouse over the element so the option will be visible.

When selected, it determines the activity will be moved automatically to the target activity when its end deadline is overdue. For this to happen, it is necessary to configure a schedule of Automatic Flow type. For more details about how to configure a schedule, check the Task Scheduler feature.

When selected, it determines the target activity can perform a return action to the source activity.

The entered text is presented as an action option to the user at the moment of the target activity execution. It is optional and if it is not entered, the source activity name will be used.