Skip to main content

Veritran Docs

3.3.1

Release date: December 2024

New Features and Improvements
  • We improved the loading time of module branches in the dependencies list to avoid delays and prevent the user from losing the screen settings when saving.

  • We improved the information loading for the entities that make up an app, ensuring that the correct data related to the user that modified the entity and the date/time the entity was modified.

  • We added a checkbox in the Settings page to select a branch as the active branch for adoption metrics. Only one branch can be selected per app or module. Enabling one branch will disable the others.

  • We added the possibility to search for transactions pending publication in the app modules and publish them.

  • We added a feature to list the names of breakpoints with changes, matching the names they have in the screens editor.

  • We added the possibility to compare attributes listed by breakpoints in web apps to match the experience in mobile apps. The names are displayed as listed in the screens editor.

  • We added filters to search for resources by their configuration type in the Studio publication. The filters available include: Only if I use it, Never and Always.

  • We updated the extensions for lambda processes in the environments.

  • We added warning messages when generating and publishing an app to alert about errors that do not affect the configuration publication (e.g., an error when refreshing Webfly to detect changes or when publishing transactions).

  • We implemented a regular expression validation to prevent creating variable names with numeric characters only. This caused runtime errors as JavaScript does not allow this behavior.

Fixes
  • We fixed issues when opening screens in the screens editor, thus shortening loading times and avoiding errors.

  • We fixed an error in the processes editor that caused issues when trying to open processes with the Description field empty.

  • We fixed a persistence issue of the financial institutions in Configurable Transactions, both when building in Studio and when executing on the host (runtime).

  • We fixed an issue the prevented the creation of site parameters after they had been deleted.

  • We corrected the hint text placement in the “Default site value” dropdown menu so it is displayed correctly and not cut off by the component’s edge.

  • In the legacy processes editor, we fixed an error where the transaction invocation did not respect the processing message set in the transaction.

  • We fixed the import of lambda processes that use previously imported transactions.

  • We fixed an issue in the Used in field for transactions that failed to correctly capture values from certain lambda processes blocks that called a transaction.

  • We fixed input and output configuration in backend lambda processes.

  • We fixed the import of apps and modules so that they can be imported without changing the siteID in the XML file. Now, when a module is deleted and re-imported with the same name as before, the connections to the previously created module will work correctly.

  • We fixed the disabling of the edit and delete options for non-native Studio components, as well as their incorrect classification. Native components will still have the edit and delete options disabled.

  • We fixed a problem in the legacy process diagrammer where, if the next step of a process was empty, it did not automatically infer the next step where to connect.

  • We fixed the saving of creation dates for configurable transactions.

  • We fixed the site parameters table to display the correct error toaster (red) when there is an error, instead of the success toaster.

  • We modified the field validation in JIRA so that commits can now be associated with JIRA tickets using keys of any value.

  • We fixed an issue in Used In where entity suggestions were not filtered by the selected type.

  • We fixed an issue when starting Studio by allowing the MB product ID to be configured through a property in each environment. This occurred as in some cases the MB product did not match the default ID.

  • We fixed the behavior and display of tags for a resource or theme, adding horizontal scrolling to navigate the applied themes without breaking the uniqueness of the modal.

  • We corrected an issue where the last collapsible component in a container component was not displayed correctly.

  • We fixed the size of the treeview to display components before rendering.

  • We fixed an issue where the dates of the branches did not show the correct date.