2023.2.3

Data Deduplication

We implemented a deduplication mechanism for Business Events which verifies the ID of incoming data upon ingestion. This verification occurs based on the Primary Key setup for the data. If incoming data is recognized as already having been ingested into Fynapse it is rejected right after ingestion and not processed.

For more details, refer to Data Input File Ingestion.

Automatic Reprocessing of Journals

The reprocessing functionality was enhanced to include Journals. Now, failed Journals will be handled the same way as failed Business Events. They will be automatically resubmitted for reprocessing.

For more details, refer to Error Management and Data in the Accounting Engine.

Security

The first version of security has been implemented. From this release access to Fynapse functionalities is controlled by user roles built on sets of permissions. Two basic roles have been defined - Editor and Reader. 

For more details, refer to Roles and Permissions.

Resolved Issues

Large Amount of Time out Errors when Reprocessing (ASD-23361)

The issue was fixed. The time out errors were caused by insufficient resources on the Subledger configuration. The resources have been increased to eliminate the issue.

Reprocessed Journals Being Dropped from Error and Journal Lines Reports (ASD-23348)

The issue was fixed. The underlying logic for handling connectivity issues with the database, was changed. Now, when such a system error occurs, e.g. a time out, reprocessing is stopped and the failed Business Events will wait for the next auto-reprocessing.