Veritran Docs

We modified the way transactions are published in an app. Previously, only the transactions and processes in use were analyzed and published. Now, all transactions with the “pending publication” status from the selected branch in “Dependencies” are included, regardless of whether they’re linked to a process or not.

We aligned transaction keys with those in the middleware to ensure consistency. A transaction key now consists of the transaction code and the product code: “TRX_CODE+PRODUCT_CODE”.

We added the Last publication column to the transaction list, showing the last publication date and the user who performed it. This improves visibility into publication history and complements audit tracking.

We improved the dependencies graph to visually identify the relation between different app dependencies.

We optimized performance to prevent long load times or frozen browser tabs when viewing merge request details with large changesets. This also affects the low-code changes viewer for Screens (when the feature flag is enabled).

We improved the UX by ensuring that once a merge request is successfully merged, its details and displayed changes are refreshed to reflect its actual status.

We improved the merge request UI by disabling “Merge” and “Resolve and Merge” buttons when the target branch is protected, preventing confusion from unusable options.

We changed how Translations are saved. They used to be branch-specific and are now global to the app.

We fixed an issue in the merge request process where users were not notified if the target branch was protected, resulting in an unclear error. Now, when the target branch is protected, a tag indicating so appears on the merge request detail screen.

We fixed an issue where merge requests without changes were shown as having conflicts in Studio, but couldn’t be resolved. We’ve now introduced a new merge request status (without changes) and display a message indicating that there are no changes in the empty state, in the toolbar, and as a new chip in the merge request list.

We resolved a performance issue in Low-Code Test where the list of components in a Test’s Steps would sometimes fail to load randomly and show an error message.

We corrected false positives in the Broken connections rule in Diagnostics. This rule no longer flags connection errors on Screens using component-type interfaces, preventing confusion and ensuring a more accurate app evaluation.

We disabled the creation of legacy processes to support the adoption of lambda processes. Legacy processes remain visible by default but can only be created, duplicated, or imported if the account is configured with the corresponding feature flag.

We disabled the creation of native transactions, promoting the use of configurable transactions. Native transactions remain visible by default but can no longer be created or duplicated without the corresponding feature flag.

We removed the Generate and publish option from the Export & Generate section. Generation is now only available from the top menu or the Overview.

We removed the Export option from the top menu of apps, which previously opened a modal for exporting branches.

We removed the Package extension option from modules.