Using text fields with more than 255 characters in the dataset

It is now possible to create a dataset that uses text fields with more than 255 characters and associate it with the form field of the text (255) type.

If the return is larger than 255, the system automatically crops it, and it is no longer necessary to perform Cast (value transformation) in the SQL command.

This change grants higher flexibility and speed in the creation of integrations via database.

 

Record in the audit trail when there is an error in the countersign of the form signature field

From now onwards, when the user enters the wrong countersign in the form signature field, the event is recorded in the audit trail, enabling the tracking of failed attempts. In this version, this is only applicable to normal (non-responsive) forms.

 

New feature in the responsive form to search for the workflow action being executed

It is now possible to create a rule in the save event of the form that checks which action is being executed.

To do that, simply create the rule using the new "Action name" feature made available in the instance data.

Thus, it is possible, for example, to validate only some fields in a certain workflow action.

 

Display confirmation alert when deleting items from the responsive form

Now, a confirmation alert is displayed when deleting items, variables, expressions, and functions in the responsive form modeling.

In the execution, when trying to delete a record from the table field, the alert requesting the confirmation is also displayed.

 

Blocking duplicated records in the responsive form grid

From this version onwards, the responsive form respects the "Do not allow adding duplicated information to the grid" flag.

By enabling this option, in the table field data, it will not be possible to add duplicated information to the grid of the form in the same instance.

 

Previous versions

View also the improvements made to this component in previous versions: