Veritran Docs

We upgraded the Log4J to version 2.5.1.

We removed the double error message when setting the user password.

We added new variables to configure OpenTelemetry.

We updated dependencies to increase the component's security.

We added new variables to configure OpenTelemetry.

We improved the component to support special characters and ANSI and UTF-8 coding files.

We improved error handling by importing points of interest exceeding the maximum number of characters accepted.

We fixed an error that occurred when loading points of interest with specific special characters.

We fixed an error that occurred when importing points of interest, which showed an incorrect file size.

We added the possibility to generate libraries to reuse code in actions.

We updated dependencies to increase the component's security.

We updated dependencies to provide a more secure component.

We 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:

We 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.

We fixed the error message that showed when trying to create an app from the XML import.

We improved the Tamper Detection configuration by modifying the forms and enabling tamper detection tools specific per platform (iOS, Android and Harmony). This improvement allows the users to handle tamper detection tools in a more efficient manner, while reducing human error and ensuring the correct application of critical security configurations.

We added a the Static Resources Branch feature that allows user to enable, through specific permissions, the configuration of customized branches in apps and builds. As a result, this provides more flexibility for teams to test or adjust branches without depending on a single static branch from the repository.

We added the Scope setting to the Application configuration, which allows users to hide internal Platform testing and debugging apps. This configuration contains the Public and Internal options, and reduces visual and operational burden.

We fixed an error in the file upload section.

We fixed an error that occurred in the minimum version validation logic.

We fixed the filters in the drop-down menus that appear in the Notification > Messages section, which caused options to appear behind the list header.

We fixed how tokens are handled in timeout flows. We modified the getUserForTimerData() function in the Device Handler so that it uses the flag "0", preserving the tokens original case.

We added a new banner that appears when a session loss is identified in Workspace and Studio is active. This banner indicates that the session was lost. The user must click the Try again button to open a browser tab and log in again. Once logged in, the user must click the Try again button again and continue working without impact.

We added a color palette specific to the top menu and Overview of each workspace (Apps, Modules and Transactions repositories). Apps appear in blue, transactions appear in orange and modules appear in violet.

We added business parameters to the Business Application Packages (BAPs), including the parameters identified in use in configurable transactions and those marked as as Include in BAP.

We added transactions marked as Include in BAP to the Business Application Packages (BAPs).

We added a new way to manage dependencies. Now, users can isolate them per workspace, which eliminates the cross-repository tree structure. Now, each app branch independently manages its dependencies at all levels, and modules manage their dependencies first level only. When the app is generated, the app overrides the modules dependencies and controls the structure to be generated without modifying the module relation. This improvement simplifies building, improves versioning and avoids undesired impact between repositories, while providing control, traceability and flexibility when configuring or updating dependencies.

We added the date data type to lambda processes. Now, users have blocks to perform conversions, comparisons, transformations and calculations using dates. This functionality requires binaries from 7.15 version for mobile devices and 2.11 version for WebFly devices.

We updated Studio to VTUI 3.6.0 version.

We added a new version of the API REST node. This allows the user to dinamically configure URLs, headers and bodies to integrate external services with more flexibility. This improvement optimizes REST integrations building and maintenance experience. This feature is controlled through a feature flag and is deactivated by default.

We added the possibility to force the inclusion of transactions and business parameters in BAPs. Now, the user can configure the Include in BAP attribute to define which business parameters and business transactions must be included in a BAP. This improvement provides more control and traceability, and avoids manual work or incorrect invoking, and ensures that all required elements are included in the package generation.

We modified the behavior of action libraries to ensure the correct update of transactions using them. Now, any changes made to an action library (either in its configuration, logic or contract) appear automatically in related transactions, that will have the Pending Publication status to ensure coherence before they are published.

We improved Run Transaction response times. This optimizes the publication of configurable transactions.

We added a parameter to the parse number to VT notation block in lambda processes, that allows the user to define a fixed number of decimals. This parameter is optional and does not require an update of mobile or Webfly versions.

We added an attribute to define the size of icons in button components in the screens editor. This is available for both mobile and web apps.

We implemented a mechanism that allows the user to configure a delay between On Click actions in a component (at the global and local level).

We added the preview of .SVG files and filters to the Assets section.

We fixed an error that caused inconsistencies when showing data in the previous themes editor (if the feature flag for the new themes editor was activated).

We fixed an error that caused an incorrect display of a react component when it was included within a data grid component.

We fixed an error that closed the app when an incorrect configuration was defined in a flex container component.

We fixed an error that failed to show the correct color defined for the ExtendtoStatusBar attribute in a component in the screens editor.

We fixed an issue that caused duplicated transactions when the last update of the entity had been performed by the user migration-tools.

We fixed an error that occurred when a merge was executed from Studio and the merge request processing time in GitLab was longer than expected. This error caused a timeout in the backend and showed an error message, even in those cases where the merge request was successful. To fix this error, we increased the waiting time in Studio to 3 minutes, which ensures greater stability in merge requests resolution.

We added the possibility to filter by node in the transaction log.

We implemented pagination in the back-end. This allows to fix a timeout issue that occurred when there were many resources to paginate.

We added the Smart Import feature. This feature automates the transactions and business parameters import process between environments, reducing manual error and improving changes tracking.

We added the possibility to see the BAP version (Business Application Package) in the Configurations page in Middleware.

We updated the Traefik version to modify the balancing algorithm and provide a more robust and secure product.

We added new variables to configure OpenTelemetry.

We updated the system core architecture to Spring Boot 2.7.x. This solves instability issues in dependencies management, thus ensuring an experience without interruptions and significantly faster response times. In addition, we updated security protocols and eliminated obsolete configurations, by reinforcing sensitive data protection and ensuring a secure environment against modern threats.

We updated the lambda processes execution motor in the backend by replacing it with GraalJS. We also added a pool of interpreters. This improves lambda processes performance and data throughput, while providing faster responses and a greater processing capacity.

We updated the Veridas SDK version to 6.1.1.

We updated the BlinkId SDK version to 7.4.3.

We updated the FaceTec SDK version to 10.0.15.

We added the Bootstrap 5.3.8 version that applies security patches and covers vulnerabilities that appeared in previous versions. This improves frontend security and reliability, while reducing potential risks in the app and its users.

We improved the handling of tree dictionaries in contexts that share the same library. Now, each tree goes through a one-time analysis and is stored per library. This improvement reduces the execution of redundant code in equivalent trees of different instances in the same context, while improving efficiency and overall system performance.

We standardized frontend coding styles and documentation by: adding an .editorconfig, file, suggesting file extensions, improving the settings.code-workspace configuration and updating the README description. This improvement facilitates collaboration between developers, ensures more consistency in the code and improves accessibility to the project documentation.

We fixed a configurable component bug in the Input component that occurred when configuring an id for the submitButton attribute in the screens editor. This error only occurred when several configurable components appeared in the same view.

We fixed an error that caused a double escape sequence by removing the properties of HTML escape characters sequence from configurable component's interface before it is created. This ensures that values are correctly stored in the configurable component. Now, data is adequately saved and the user can benefit from a consistent and trustworthy interface.