2023.2.8
Rollback
We introduced a new functionality which allows you to rollback, i.e. withdraw, Journals which were generated and posted from previously imported Business Events.
For more details, refer to Rollback.
Data Deduplication
The data deduplication functionality has been enhanced. Now, when a duplicate error is detected, an error will be logged and you will be able to view it in the Error log file.
Journal Line Definition
Journal Line Definition has been enhanced with a Unique ID that will allow you to easily identify records, e.g. in the Error log.
For more details, refer to Journal Line Definition.
Please note that Journal ID and Journal Line ID by default constitute the Primary Keys for Journals and Journal Lines, respectively. If you are upgrading with an existing Journal Line Definition these fields will automatically become Primary Keys, however the Unique ID will not reflect this on the screen, i.e. they will still have the “NO” flag.
If you want to create a Primary Key for an existing Journal Line Definition, please remember that this will constitute changes to the Journal Line Definition and will affect your processing and may cause loss of transactional data.
Error Management
Error management was enhanced to facilitate better tracking of connections between failed Journals and the Business Events they were originated from. Now, when a Journal fails, the error log will report the Primary Key of the failed Journal and the Primary Key of the Business Event it was generated from.
Resolved Issues
Fynapse Outbound J1 - Activity Amount incorrectly using Enriched Value (ASD-24607)
The issue was fixed. Now, the J1_Activity Amount field is correctly populated with the expected amount sent not with the enriched activity amount (deferral amount).
Fynapse Outbound J1 - Business Date incorrectly using Enriched Value (ASD-24606)
The issue was fixed. Now, the J1_Business Date field is correctly populated with the expected date not with the enriched business date (deferral date).
