Veritran Docs

We added the next render screen navigation block to lambda processes. This block replaces the next render sequence block and allows the user to select screens with a predictive input that concatenates its identifying attributes. The next render sequence block is now removed from the Next section but will still work to ensure compatibility.

We added a new set of blocks to lambda processes that allows the user to filter and search for elements within arrays under specific conditions. These blocks combine logical rules and apply transformations to the columns values. By adding these blocks, the building logic is simplified and the process legibility is improved.

We added the possibility to use original colors of an image in SVG format for the Icon component. With this improvement, we eliminate the restriction that makes it use a single color.

We added the ¿replace in text [text] the regex [text] with [text]¿ block to lambda processes. This new block allows the user to replace text using regular expressions (also known as regex).

We added the parse VT notation [text] to number block to lambda processes. This block allows the user to convert values in Veritran notation to decimal numbers. It simplifies the handling of arrays and reduces the complexity in building logic.

We improved the rendering of shadows in components. Now, their appearance matches the designs made in Figma.

We added the a new feature for packages building from Studio. This feature automatically compiles the configuration and configurable transactions in use and creates a business application package (BAP). This facilitates and simplifies deployment and guarantees that a package is complete from the Studio side. By using this feature, users won't need to use the smart release configuration parameter. You can read Business Application Package documentation to learn more.

We added a new text editor in the lambda processes blocks, which increases productivity and agility when the user changes text type values.

We added the possibility to configure visual statuses to the Button, Text Label, Text Input and Flex Container components. We also added the possibility to add, replace or eliminate styles applied to components through the CSS_CLASS_ADD, CSS_CLASS_REPLACE y CSS_CLASS_REMOVE events.

We added the possibility for a device to automatically reconnect Devtools upon lost connection if the device screen blocks or the app is minimized.

We added the scroll attribute to the Flex Container component.

We increased security in Devtools by adding the Single Sign On mechanism to access the tool.

We improved the Themes section by fixing issues related to saving changes, and editing styles and variables in the Custom tab.

We improved the Themes section by configuring a more organized UI that allows the user to better understand the information.

We fixed an error that did not solve the tokens when the user attempted to execute the Quick run or Quick Publish features in their respective editors. This error caused the token value to be replaced by its value before the new configuration was sent.

We fixed an error that did not allow clicks in Flex Container components to propagate correctly due to the Statuses feature. Now, the status Pressed requires an OnClick event to be set.

We fixed an error in the Parallel component that did not show the H84 error if an error in the request occurred.

We fixed issues in lambda processes that resulted in lack of stability and unpredictable behavior in the lambda processes editor.