From this version onwards, it is possible to define a data source for the responsive form grid/table. Thus, it is possible to import external data to a form grid/table. The system also allows a configuration to open a screen displaying the records for the user to choose which ones should be added.
From this version onwards, it is possible to apply enabling and disabling properties, among others, to all elements within a group, such as panel and section. This improvement allows simplifying rule creation and making it faster.
It is now possible to obtain starter and requester data such as: login, user ID, name, e-mail, and ID #/department name/default position of the requester. If the requester is of the customer type, it is possible to search for their company, name, and e-mail. Such information is important to display in the form or use in other rules, making the form even more dynamic.
From this version onwards, it is possible to enter a comment to the instance history using a value filled out in the form. It is also possible to change the priority and the status of the instance. With these actions, it is easy to manage important information and to improve the meeting of process demands.
With the action to execute a URL, it is possible to open an external URL dynamically retrieving data from the form. The action to execute an activity allows it to be executed from a form button. These actions require the rule to be executed in the interface.
It is now possible to create a totalizer of the responsive form grid/table. Thus, it is possible to apply a counter, sum, minimum, and maximum to a grid/table field. This action allows validation rules to be created, avoiding the creation of inconsistent records.
This action allows creating rules so that, in an activity, only the add button is enabled, and only the edit button in another. Thus, it is possible to control the actions in the grid/table according to necessity, improving usability for the end user.
It is now possible to create rules with conditions and, according to each condition, change the value of a variable. This avoids the need to create hidden control fields in the responsive form, keeping the layout clean and improving loading performance.
From this version onwards, it is possible to obtain the value of a table field in an advanced list. This function allows, for example, searching for the company federal EIN # in a supplier list from the responsive form rules.
It is now possible to duplicate an action for "IF" conditionals, as well as the conditions within this action. It is also possible to duplicate the full rule, allowing a faster, more precise rule creation and editing.
From this version onwards, it is possible to change the name of the table field in the item properties in the responsive form, enabling a better management of pivot tables.
It is now possible to round values considering decimal places. By default, the system removes the decimal places after crossing the established floating-point number. With this new function, it is possible to round values considering also the decimal places.
Now, the form name can also be localized for several languages. Thus, it is possible to view the name according to the logged user language in the listings and in the activity execution data screen.
From this version onwards, the (unresponsive) form report displays the default system header and footer, with an image of the company logo, date and time, user, and page number.
From this version onwards, it is possible to edit a record from a pivot table using the editTableRecord method available for SOAP web services.
Previous versions
View also the improvements made to this component in previous versions: