2023.2.6
Journal Line Definition
The Journal Line Definition has been enhanced with five new Systemic Fields:
- Ingestion ID
- Journal ID
- Journal Line ID
- Reversing
- Reversed by
For more details, refer to Journal Line Definition.
Upgrading from an existing configuration
If you already have created a Journal Line Definition, then after the upgrade the Journal ID, Journal Line ID, Reversing, and Reversed by field will be automatically added. However, the Ingestion ID field has to be added manually. To do this:
- Download your current configuration via the Configuration Data screen in Bulk Operations section.
- The four fields listed above will be automatically added to the journalDefinition section of the JSON file.
- Add the Ingestion ID as the last attribute in the journalDefinition:
- Upload the JSON file.
Bulk Operations
Starting from this release it is possible to edit the Entities, including Journal Line Definition Protected Entity, via the Configuration Data JSON file without loss of transactional data already in the system.
In order to change an Entity, upload a JSON file with the changes via the Configuration Data screen. If the changes are not supported by the system, a dialog will appear informing you of possible data loss and ask you for confirmation. If you choose to upload unsupported changes, all transactional data will be lost.
The supported changes are:
- Adding an attribute that is not mandatory
- Dropping an attribute that is not part of a Primary Key nor is part of any hint
- Reordering attributes
The unsupported changes are:
- Changing Entity temporality type
- Changing attribute types
- Changing the mandatory setting of an attribute
- Changing an attribute’s Primary Key
- Changing Entity hints
Accounting Rules Navigator Traceability
The View History section of the Accounting Rules Navigator screen has been enhanced. It now allows you to view the details of what changed the accounting rules in a particular version.
For more details, refer to Accounting Rules Navigator.
Extraction
Manifest Receipt File
We implemented a mechanism that automatically generates an additional file for each extract file placed on Amazon S3 and generated for the Journal data source. You can use the manifest receipt file to identify data inaccuracy and incompleteness after data processing.
For more details, refer to Manifest Receipt File.
Deferred Payments
The validation scenario in which the Transaction Amount = Deferral Amount would cause an error to be thrown has been removed. Now, when the Transaction Amount and Deferral Amount are equal, both permanent and reversing Journals will be generated.
Resolved Issues
Fynapse Extraction Stuck (ASD-23860)
The issue, when an extract file is stuck in the pending status endlessly due to its size, was fixed. Now large extract files will be handled properly.