Veritran Docs

We fixed an error in the identification of the navigation trace used for passing input values in screen-type modules on Web. This issue caused input tokens passed as parameters to appear empty in the interface, even when they had assigned values in the browser. This fix ensures proper and secure synchronization of attributes when executing heavy processes or lambdas, improving data consistency and delivering a more reliable user experience.

We fixed an issue with the identification of message-type events (modules) that prevented the correct synchronization of output attributes during the execution of heavy processes or lambdas. This affected the user experience in screen-type modules on Web, where token values passed as parameters appeared empty despite being correctly assigned. This improvement ensures safe and reliable data synchronization between events, enhancing the consistency of visible information for the end user.

We resolved an issue that occurred when an input/output/message was defined in the component but not in the interface, which caused navigation to break.

We corrected the execution order of use cases when synchronizing states between the frontend and backend. This improvement ensures proper application state consistency, avoiding desynchronization and providing a more predictable and stable user experience.

We fixed an issue caused by the lack of state in certain service classes that needed to be shared across contexts.

We fixed an error in the _GETFILE function that prevented files from being downloaded from contexts other than the main one. The request is now performed globally, ensuring successful downloads regardless of context.

We introduced a new feature in process execution that simulates on Web the array behavior observed on Mobile. To achieve this, we added an extra column to the array via a toggle feature that replicates the Mobile structure {index, "a", "b", "c"}. This resolves the issue where updating a row with values like “a|b|c” in Web failed because the index was not part of the array.

We fixed errors that occurred when the site parameter CONCATENATION_STYLE was set as a string instead of a boolean. It is now accepted in either format (boolean or string).