Veritran Docs

We fixed an issue related to Rego policies.

We added the possibility to run commands in all nodes, grouped by Blue or Green.

We fixed the search bar in the Configuration Management page, which was not filtering entries after entering a text.

We added the possibility to enable the deletion of old configurations. This improvement allows to specify thenumber of days a configuration will be retained, and after that period, it will be automatically deleted.

We fixed an issue that, after obtaining the debug log file from the console with a certain log level specified on a variable, the log level reverted to 6 instead of applying the level configured in the configuration file.

We fixed an issue that occured when there were two transactions with the same transaction code but different products. When trying to publish one of them from Studio, instead of publishing the selected transaction, the system published the transaction with the same code but different product code.

We modified messaging when there is a dependency not configured in the environment, since it was previously marked as a dependency issue.

In the Certificates section, in the Public Key option, we added the PUBKEY_PEM data type.

We fixed an issue when importing transactions that occured due to Auth Parties IDs being different in source and target environments. Now, if the imported transaction is native, the ID on the database will be DFLT, and if it's configurable, it will be IRIS.

We fixed the transaction log's UI so that columns and fields data does not overlap the details on the log.

We fixed a visual bug on the Configuration's History table, in the Configuration Management section.

We added the previous and next options to the transactions log details.

We fixed an issue in the transaction log Transactions Response Codes section that showed a different message in the summary than in the details.

We fixed an issue when importing transactions that did not allow importing native transactions as it searched by transaction type instead of searching by auth party code. Now, when importing a native transaction, the auth party code is assigned by default.

We fixed an issue in the transaction log filters that did not allow using special caracters.

We fixed an issue when exporting the transaction log to PDF that did not show the transactions' variable data section. Jaspers should also be updated as the fix included changes in the repository.

We fixed an issue that overwrote the transaction Auth Party value when uploading a JSON.

We fixed an issue that transformed the data obtained by the server from the data base and displayed it incorrectly.

We fixed an error that changed the transaction Auth Party when importing it from another environment.