2023.1.2
Resubmission
This release comes with automated daily resubmission of failed Business Events.
All failed Business Events are automatically resubmitted for processing once a day.
Currently automatic resubmission occurs once a day at the time specified by the Fynapse team. By default this is set to 1 am in the location of the Kubernetes cluster hosting Fynapse. Please contact the DevOps team via Aptitude Support regarding changes to this setting.
For more details, refer to Business Event Definition, How Do I Know a Business Event Is Failed? section.
Automated daily resubmission affects the working of Posting Date override. Previously, enabling Posting Date override would cause all Business Events on the level of a given Subledger Node to be resubmitted regardless of their status. Now, only failed Business Event will be resubmitted.
Fiscal Calendars
A new View History section was added to the Fiscal Calendars screen. It allows you to check who and when changed a given Fiscal Calendar.
For more details, refer to Fiscal Calendars.
Business Event Definition
A new feature was added to Business Event Definition to identify unique records. Now, when creating a Business Event Definition, you have to select an attribute or several fields which will constitute a unique ID and be later used to identify the Business Event, e.g. in validation errors.
For more details, refer to Business Event Definition.
Error Management
This release introduces a new Error Management service. Error Management allows you to export a log with processing errors.
For more details, refer to Error Management.
Resolved Issues
Accounting Engine - Journal Mapping override: Workflow order
The issue was fixed. Previously, when processing deferral entries, the reversal of the future period deferrals were not reflected in the custom field attribute. Rather than showing the reversal, the same debits and credits as the reversing entry were reflected.
Now, if a deferral event is posted and in the configuration the transaction amount is mapped (1:1 mapping) to a custom attribute, the custom attribute will match the transaction amount.
Business Event Definition - “sourceSystem” and “sourceSystemId” Fields
The “sourceSystem” and “sourceSystemId” fields are no longer mandatory for the Business Event Definition.
Business Event Definition - Event Type Systemic Field
The issue was fixed. Previously, the fieldName of the Event Type Systemic Field had to be set to “Event Code”, otherwise the Accounting Engine would reject the definition configuration. Now the Event Type Systemic Field can have any name, per your requirements.
Hotfixes
Error log not populating (ASD-22193)
The issue was fixed. Previously, in some cases no Journals would be produced even though the input file was successfully ingested. The records would remain in the processing queue indefinitely and no errors would appear in the Error log. Now, the backend logic was fixed and the Journals and Errors are produced correctly.
