Task execution using mobile forms

 

 

Disable manual execution of the Workflow action

Starting in this version, it is possible to create actions and choose to display the action button to the user in the execution of the activity or use only the execution via system. Example: Create an action that must be clicked only in the automatic execution of the activity. The user must not have access to this option.

 

 

Create sequential load balancing

Now it is possible to perform the load balancing in a group by following the user queue. Up to now, it was allowed distributing the tasks automatically to the users of a group with the lowest number of activities or the lowest number of estimated hours of the activities. With this new option, it is also possible to follow a sequence. First user A receives a task, then user B, and so on.

 

 

Display document in the workflow general data

When the workflow association is configured in the category data, the system automatically starts a process instance. Now it is possible to view the document that originated the workflow in the instance data.

 

 

Requester role

Starting in this version, the Requester role was created. This new information is displayed next to the instance data starter and on the task execution screen. This field may be used to treat requests arising from demands, tickets, among others. In that case, the task executor creates the record referencing the actual requester of the status. This functionality is optional and may be enabled in the template process data. It is also possible to check an option in the activity allowing the executor to edit the requester.

 

 

An option to define the comment as restricted was also created. That way, the requester may not view the comment. New functions were also created in the SE Form formulas to search for the login, user ID, name, department, and position of the requester. With that, for example, it is possible to hide the fields according to the requester department.