Índice |
---|
outline | true |
---|
exclude | .*ndex |
---|
style | none |
---|
|
In this configuration of activities and flows, you define the main information to be considered during a process request. So you need to define the information with attention; thus, guaranteeing correct process functioning.
...
It is also possible to export the process documentation, generating a document with information referring to the process and its activities or the process flow image.
...
01. Drag the Start element from the side menu to a location in the process flow modeling area
...
13. After finishing configuring the start settings, click Confirm.
...
01. Drag the End element from the side menu to the desired place in the process design area.
...
Painel |
---|
Required information: Name Name to be assigned to the end of the process. Notify requisitioner When checked, the requisitioner of the request will be notified of the end of the request by e-mail. Notify manager When checked, the manager of the activity will be notified of the end of the request by e-mail. |
04. Click Confirm.
...
01. Drag the Activity element from the side menu to a location in the process flow modeling area.
...
Painel |
---|
To delete the element from the process diagram, simply click Delete, represented by a bin. |
Painel |
---|
Required information: Description Description of the activity to comprise the process. Instructions Instructions that make it easy to understand the activity in the process. When preparing the instructions of an activity, it is common to need to search for information from other files or websites. There is the concept of hyperlinks, which allow adding access to both TOTVS Fluig Platform documents and Internet addresses via external documents, avoiding replication of information and making it easier to browse. To do this, add the tag [WD:999999], replacing 999999 by the document code in document browsing. Working Hours Working hours to which the activity will be associated. Working hours are registered on the platform and are used for calculation of deadlines and delays for process activities. For example, if the working hours were configured as being from Monday to Friday, from 8:00 a.m. to 6:00 p.m., and there is an activity that lasts 1 hour and was created at 5:30 p.m. on Tuesday, its completion deadline will be Wednesday at 8:30 a.m., due to the working hours. Assignment mechanism The way how users will be selected to perform the activity. It only displays the types of assignment mechanism that can be used in regular activities. Available mechanisms: - Assignment by association: when selected, the users that can perform this activity (the ones returned from the combination of several assignment mechanisms) are displayed for selection;
- Assignment by form field: when selected, the activity is assigned to the user that is entered in a field on the form associated to the process;
- Assignment by activity performer: when selected, the activity is assigned to the performer of a previous activity of the process;
- Assignment by group: when selected, the users that can perform this activity (all users belonging to a group) are displayed for selection;
- Assignment by collaborator group: when selected, the users that can perform this activity (the ones belonging to the same groups as the authenticated user or the user who started the request, as configured in the mechanism) are displayed for selection;
- Assignment by role: when selected, the users that can perform this activity (all users belonging to a role) are displayed for selection;
- Assignment for a group: when selected, the activity is assigned to a pool of resources, containing the users belonging to the group. In this case, any user from the group can be assigned the activity;
- Assignment to a role: when selected, the activity is assigned to a pool of resources, containing the users belonging to the role. In this case, any user assigned to the role can be assigned the activity;
- Assignment by user: when selected, the activity is assigned to a specific user.
Completion deadline - By fixed value: Deadline to complete a task. The hourly value is considered, along with the selected working hours, to calculate the deadline for finishing the activity. This deadline is counted as of the activity’s receipt.
- By form field: When selected, allows choosing a form field that will define a deadline for the task whose property is being changed.
Painel |
---|
Values valid for the field: - 999:99 = Standard format.
It will follow the same logic of the fixed value, considering the working hours and holidays applicable to the user in charge. For the other values, use the following formats: - 9999-99-99 = year, month and day;
- 9999-99-99 99:99 = year, month, day, hour and minute;
- 99/99/9999 = year, month and day;
- 99/99/9999 99:99 = year, month, day, hour and minute;
- 9999999999 = date in milliseconds.
Working hours and holidays will not be considered, exactly as specified Nota |
---|
| When you enter a date without the time, the last time of day is 23:59. |
|
Request digital signature When checked, such activity must be digitally signed by its performer user. In this case, upon completion of the activity, it displays a window where the performer user needs to add their digital signature and, only then, can the request be sent to the next activity. Confirm password When checked, the user needs to enter their password to finish the activity. If this option is already checked in the process configuration, it will come disabled. When sending the activity that requires password confirmation to the next one, the user who is performing the task has to enter their password. If the password is invalid, the activity performer can try as many times as necessary. The process will only be moved when the performer user enters their password correctly. The process history will indicate that the user has confirmed their password when moving the activity in the request. Please note: the activities checked for password confirmation use cannot be automated by WebServices. Inhibits Transfer option When checked, the activity cannot be transferred for another user to perform it. Joint activity When checked, the activity should be performed by more than one user. By doing so, the activity will only be considered completed and the request moved when % of the entered consensus is reached. % Consensus Percentage of consensus required to consider the activity as completed. This field is enabled only when the option Joint activity is checked. Selects collaborators Frequency at which it is necessary to select the user to assign this activity when moving the request. Available options: - Always: when checked, it is always necessary to select the user to be assigned this activity when moving the request;
- When there is more than one option: when selected, only when there is more than one user listed is itnecessary to select which user must be assigned the activity when moving the request;
Never (valid for joint activities only): when selected, this activity will be assigned to all users listed by the defined assignment mechanism. When selecting this option, the Joint activity field is automatically checked, and you are also required to enter the % Consensus. |
...
Painel |
---|
For information on assignment mechanism settings, see Configure assignment mechanism. |
Painel |
---|
Attachment rules are events that will occur in the created activity whe moving to the next activity. These events only occur in normal activities or in the start activity of a process. |
...
Painel |
---|
Required fields: Title Set a name for the request title, or choose a form field. Default: Description of the process. Highlight Set a form field to fill it. The field should be the highlight and should not be too long. Default: Activity name. Description Set a text for a preview description of the request and/or choose form fields. The information that exceeds the limit is available in the request. Default: Instruction about the activity and process + Identifier.
Available actions: Decline Select ‘Disable’ or ‘Problem solved’. Approve Select ‘Disable’ or ‘Problem solved’. |
11. Define the required information
Painel |
---|
Required information: Notify person in charge When checked, the person in charge of the activity will be notified of its start by e-mail. Notify requisitioner When checked, the requisitioner of the request will be notified of the start of that activity by e-mail. Notify manager When checked, the manager of the process will be notified of the start of that activity by e-mail. |
13. Define the required information
Painel |
---|
Required information: Notify person in charge When checked, the person in charge of the activity will be notified by e-mail if it is late. Tolerance Time during which the platform will wait, after the deadline for the activity expires, to start sending the e-mail notifying the person in charge, requisitioner or manager of the delay, according to the checked options. Frequency Time interval between the e-mails that are sent to notify the person in charge, requisitioner or manager of the delay, according to the checked options. Expiration notification Time prior to the expiration of the task when the e-mail will be sent to notify the person in charge, requisitioner or manager (according to the checked options) that the task is about to expire. Notify requisitioner When checked, the requisitioner of the request will be notified by e-mail when that activity is late. Notify manager When checked, the manager of the process will be notified by e-mail when that activity is late. |
15. Define the required information
...
16. After finishing configuring the activity, click Confirm.
...
The default flow indicates an automatic activity action, which happens when none of the defined conditions is met. For more details, go to Flows.
...
09. Add as many conditions as you wish, configure them and click Confirm.
Configure Service
...
01. Drag the Service element from the side menu to the desired location in the process flow modeling area.
...
Painel |
---|
- Service
Select a service type Soap, already registered through the Services item, located in the Control Panel, General tab.
Painel |
---|
To learn how to create a service, access the documentation here. |
- Operation
Selecting the magnifying glass icon will allow you to select one of the available operations. The operations will be listed by Name and PortType (ColleagueService).
- To set up
In the settings of the selected operation, the Properties and SOAP Headers can be configured.
Painel |
---|
Properties - Basic Authentication - Select whether or not to authenticate. You can define a user and password.
- SSL - enable when soap service requires use of ssl.
- Disable Chunking - disable sending the entire soap envelope.
- List SOAP messages - enable to show the sending and receiving messages in the log.
- Response time - enable to display the time the request waits for the response.
SOAP Headers Allows you to add a header. Trigger Save to complete the configuration. |
- Parameters
Fill in the parameters as required:- Assignment
- Value, Form, Variable or Null (When selecting Null, the Value field is automatically dispensed. For the Form option to be displayed, it is necessary to have a form attached to the process). - Value
- Will be displayed when the assignment field is selected as Variable. They are: WKCompany, WKUser, WKCardId, WKCurrentState, WKDef, WKFormId, WKNextState, WKNumProcess, WKNumState, and WKUserComment.
- Return
Fill in the returns as requested:- Assignment
- In the Form option, you can search for and include a form in the Value field, and in the Note option, you can add a note message by tapping Edit object as icon in the Value field).
|
05. Activate Confirm.
...
01. Drag the Document element from the side menu to a location in the process flow modeling area.
...
Painel |
---|
To select a document, simply click the magnifying glass icon below the Document field. In the pop-up window, find the document, select it and click Select. |
04. Click Confirm.
...
01. Drag the Note element from the side menu to a location in the process flow modeling area.
...
Painel |
---|
Name Name of the note. Document Text that corresponds to the note. |
04. Click Confirm.
...
01. Drag the Swimlane element from the side menu to a location in the process flow modeling area.
...
Painel |
---|
Name Name of the Swimlane to represent a participating entity in the process flow. Color Choose a color for the swimlane. |
04. Click Confirm.
...
01. Drag the Subprocess element from the side menu to a location in the process flow modeling area.
...
Painel |
---|
This tab allows the user to configure the submission of values in form fields between a process and a subprocess. Thus establishing the fields that come from the parent process and go to the child process, and from the child process going to the parent process. Both parent and child processes should have a created form so that the sending of values and their respective directions can be set. This allows the user to transfer information between parent and child processes in a simple and transparent way. Here is an example of the directions that indicate source and destination of the information: 1st transfer the value from the parent field (source) to the child field (destination): Name-> User name. 2nd transfer the value from the child field (source) to the parent field (destination): Name<- User name. 3rd transfer and return the value of the field (both transfer the value from one to the other): Name<-> User name. Information from the columns: Process fields Fields to be used from the form created in the parent process. Select a field from the parent form to relate the fields. Direction Direction that indicates the information flow between the process and sub-process fields. When clicking it, it changes the source and destination of the relationship with the fields. Subprocess fields Fields to be used from the form created in the child process. Select a field from the child form to relate the fields. Status Indicates the confirmation that the new relationship between the process and subprocess fields was created. The New button allows adding new sending of values between process and subprocess. It is also possible to Edit or Delete a field relationship via the icons located in the right corner of the tab. The system does not allow relating two process fields with the same direction |
05. Click Confirm.
...
01. Drag the Fork element from the side menu to a location in the process flow modeling area.
...
03. Enter a name (optional).
04. Click Confirm.
...
01. Drag the Join element from the side menu to a location in the process flow modeling area.
...
03. Enter a name (optional).
04. Click Confirm.
...
01. Place the mouse on the source element of the flow.
...
Painel |
---|
To delete the element from the process diagram, simply click Delete, represented by a bin. |
05. Enter the required information in the General tab.
Painel |
---|
Name Name to be assigned to the flow. Flow activ. Text to be used to identify the advance action from the source activity to the target activity in the process flow. The entered text is displayed to the user as an action option when performing the source activity. That is optional and, if it is not entered, the target activity name will be used. Automatic flow When it is checked, the activity will be moved automatically to the target activity when its deadline expires. For this to happen, configure an Automatic Flow scheduling. For more details on how to configure scheduling, see Task Scheduler. Allows return When checked, it is possible to return the request from the target activity to the source activity. Return activ Text to be used to identify the advance action from the target activity to the source activity in the process flow. The entered text is displayed to the user as an action option when performing the target activity. That is optional and, if it is not entered, the source activity name will be used. This field is enabled only when the Allow return option is checked. |
07. A process start and transaction message can be defined in the Transaction message tab.
...