1.15.3
Release date: January 2026
Increased the number of registers that can be visualized when creating a release candidate from 20 to 1000.
Fixed an issue affecting transactions with descriptions longer than 30 characters.
Release date: November 2025
Improved how dependencies are managed during a transaction import process. Now, the system identifies the transaction that failed and, upon the first error, it executes a rollback on the whole bundle so that there are no incomplete transactions. If the system identifies a broken dependency,the whole bundle fails. This new functionality will be enabled by default.
Blue-Green can now be used with configurable transactions.This allows to execute controlled tests in production without affecting final users through the use of experiments. This makes validating and comparing versions easier. Some of the main characteristics include:
Branch versioning in development environments: Now it's possible to publish several versions of a same transaction (same code and product) by having them in different branches.
Blue-Green experiments in PROD: Not it is possible to define groups of users that can access an alternate version of an app (green) while the rest of the users use the same stable version (blue).
Controlled experiments promotion: Once the experiment is validated, it can be easily promoted to PROD. This updates transactions and configurations.
Smart import: The system detects which transactions have been updated and updates them.
Fixed an issue that did not allow to select the auth party after editing a transaction. Now, the import process associates auth parties using the code instead of the ID. For this to work correctly, we suggest to keep the same auth party codes across environments.
Fixed the error message that showed when trying to create an app from the XML import.