Skip to main content

Veritran Docs

3.0.4.14 to 3.0.4.20

Release date: January 2024

New Features and Improvements
  • We enabled the use of the PROCESSING_TITLE constant during the execution of a transaction in lambda processes. This constant allows you to obtain the value configured in the Processing Message field of that transaction.

  • We improved the text that describes the weight and size specifications shown when the user uploads a thumbnail to a theme in Studio.

  • In the Themes section, we introduced the following improvements:

    • We added the Flex component to the Styles list.

    • We removed the limit in variables creation, such as colors and fonts.

    • We eliminated the limit in styles creation.

    • We added the tertiary variable by default for colors.

    • We added the margin and padding variables.

    • We added the option to configure the margin and padding settings for each style.

    • We added the opacity field to color variables.

  • To improve performance when generating and publishing an app, we added the possibility to use the cache to obtain processes and resources already generated. In those cases where the cache is not necessary and the user prefers to generate and publish using the former process, we added a toggle in the Generate & Publish modal that includes this option.

  • We enabled a new Function block in lambda processes that allows the user to decrypt static and custom tokens.

  • We added a new block in lambda processes that allows the user to manage errors in transactions and customize the logic executed in the case of each error.

  • We added detailed information of the transactions invoked in lambda processes.

  • We added a new function type block that emulates the behavior of an #R expression. This block reads the 157 token that contains a JSON with a predefined structure.

  • We added a block in the MATH section that receives a numeric value as input and returns such value in Veritran notation.

  • We added the download of search matches for screens and processes in App Flow's Used In feature.

  • We added the download of search matches for tokens and arrays in App Flow's Used In feature.

  • We added an improvement in Diagnostics that provides greater detail in searches by including entities invoked by dynamic tokens in orphan entities.

  • We added a unified search panel for the Flow Search and Used In features in App Flow that results in an improvement in the user experience.

Fixes
  • We fixed a problem that prevented lists in the cache to load when they were previously deleted by the user, which caused an error when opening a screen.

  • We fixed an error that, when the user used the "Ctrl+S" shortcut outside the screens editor, caused the associated screen to block and to show the Studio re-connection message.

  • We fixed an error in lambda processes that caused the Length of array block not to obtain the number of rows.

  • We fixed an error in lambda processes that occurred when the user invoked a transaction if a RgisterString was changed to a RgisterNumber in the Code tab.

  • We fixed an error that occurred when saving a screen of a module that contained only one screen and interface.

  • We fixed an error in App Flow that did not make it possible to correctly update the list of tokens and arrays when changing the search chip.

  • We modified the App Flow interface. Now, the empty state only appears when no results can be found during a search.

  • We fixed an error that occurred when importing or deleting a lambda process that invoked a transaction that did not exist in the environment.

  • We fixed an error that prevented all the elements to remain within the floating panel.

  • We fixed an error that prevented the correct visualization of images configured in the Background Image and Simulator Background Image attributes for panel components.

  • We fixed an error that affected the font size used by default in label components.

Deprecations
  • We eliminated the ActionsTLC attribute from the right panel of the screens editor.

  • We eliminated the message parameter in the execute async transaction block of lambda processes.