From this version, it is possible to determine an exception route for the process to follow if a webservice execution fails. Information about the call is recorded in the process history. A new filter to list instances with inconsistencies has been made available in the instance management.
Accessing SE Suite via mobile device can now start a process instance. The system automatically shows the execution screen, allowing to start and execute the first activity quickly and practically.
From this release, selecting a template process in the workflow task menu, allows you to view the form fields (entity attributes) of this process. In this way, it is possible to sort the listing by fields, such as customer, value, etc.
It is now possible to view the associated documents in the "upper level" process in the document association listing in subprocess activities. This functionality allows the executors of subprocess activities to access complete documentation more quickly and easily.
Now, it is possible to use the attachments resource also on mobile devices. This feature allows you to quickly add files in the task.
With this API you can create a link (URL) that allows you to access the task execution screen. This way you can use the link in Analytics portals, message events, etc. It is also possible to use the URL outside SE Suite, such as a customer center, for example. When accessing the URL, if the user is not logged in the system, you will be prompted to log in before opening the data screen.
With this API you can create a link (URL) that allows you to access the data screen of the instance. In this way, it is possible to e-mail the URL, which when accessed will open the data screen. It is also possible to use the URL outside SE Suite, such as a customer center, for example. When accessing the URL, if the user is not logged in the system, you will be prompted to log in before opening the data screen.
By hovering over an activity or clicking on it in the instance flowchart, some important information such as executor, dates, etc., will be shown. The information in the summary and caption/tooltip of the task was standardized to improve your understanding. It is also shown in this set of information whether the activity was performed automatically. This information is important for audits and traceability.
Now when you open the flowchart of a blocked instance for editing, the HTML5 modeler will be used. This improvement is intended to improve usability and make it faster to edit the instance flowchart.
Now load balancing is applied when the executor is determined via formula. In this way, you can create rules for dynamic executor and still apply load balancing.
From this version, when performing an activity in which the filling in of the comments is mandatory, the system opens a screen to enter the content and finish it. In this way, the other action buttons remain disabled, avoiding inconsistency when clicking the wrong button.