Attachment sending by the message event

In this version, the possibility of sending an email with attachments has been implemented in the process message event. In addition to that, it is possible to configure the sending of form files and also the attachments of a determined activity.

 

 

Improvement in the usability in the access to multiple sub-processes from the instance data

From this version, the system displays the title of each sub-process instance in the options of the "Lower instance" button of the ribbon.

 

 

Display the documents associated in the lower instances on the Instance/Activity screen

Now it is possible to view the documents from SE Document associated in the sub-process instances. That way, it is no longer necessary to individually access the lower instances to access the associated documents.

 

Executor change notification

From this version, when changing the executor through the instance management, the system will send a notification to the current and the new executors alerting about the change.

 

Improvement in the usability when filtering tasks per process

Now the task filters display the process templates containing the number of tasks in each template. That way it is possible to easily filter and identify which processes have tasks.

 

 

Requirement improvement

Aiming to optimize the filling of requirements in the tasks, a resource that allows the addition of attachments and documents directly in the requirement fields has been implemented.

 

 

 

 

Performance improvement in the instance view

From this version, the search by keyword and Workflow management filters use the indexing tool similar to the one that already exists in the general view.

 

 

Process SLA control

Aiming to configure dynamic deadlines, adopting SLA concepts, rules that use process attributes, form fields, and process priority have been implemented. It is also possible to define time pause controls according to the process status. For example: If the contract field is equal to "Platinum", the SLA must be defined with 08:00, otherwise, the 48:00 SLA should be used. That way, the deadline of the instances is dynamic and varies according to the defined rules.

 

 

Execution of mobile activity

The objective is to allow the execution of the activity via smart phone, encompassing the task list. It is possible to view a summary of the data of each task and execute an action.