2024.3.1

Release notes for Fynapse 2024.3.1

Flow

Released under a Feature Flag

We implemented a new Flow feature, which allows you to compose your own integrated Fynapse processes, i.e. Flows, comprising of lookups, calculation rules, native Fynapse processes such as the Accounting Engine processing and Journal processing, etc.

Each Flow is comprised of a series of user-defined processing “steps” represented by blocks. These steps are chained together via a visual flow diagram that has a defined start and an end. Each step performs some form of data processing or performs some logic that determines the next action in the Flow.

For more details, refer to Flow.

Operations Dashboard

We implemented a new Operations Dashboard screen, which allows you to view the progress of operations on data from a given ingestion file with Business Events.

For more details, refer to Operations Dashboard.

Authorization Workflow

We implemented the Authorization workflow functionality, which allows you to set up a mechanism that does not allow to apply any changes to the configuration without reviewing and consequently approving or rejecting them. This means that any changes done to configuration will be applied and visible in Fynapse only after approving them by users with proper permissions. At each point you can see a status of a particular request. Additionally, if you are the requestor of a request you can withdraw it if it still has the Pending approval status.

This functionality can be used only for the Accounting Rules Navigator and must be enabled by the user with the proper permission.

For more details, refer to Authorization Workflow.

Error Management - Failed Data Screen

Released under a Feature Flag

The reason we made the decision to release under an ‘invisible’ feature flag is from a control perspective. In order to prevent data loss when enabling the functionality, we need to perform checks to ensure we do not lose any data that is currently processing. If you want to test this feature please raise an ASD support ticket with Aptitude Software Support.

We completed the development of a new Error Management that contains two screens - Errors (already released) and Failed Data available in this release. The new Failed Data screen presents Entities with details of the underlying failed data. It also allows you to perform the failed data reprocessing on demand without waiting for the scheduled reprocessing. The screen includes a flexible search option that enables you to quickly filter failed data using selected attributes and to even save your queries to use them instantly in the future. Once you find data that you are interested in, you can download it to a CSV file with only one click.

Balances - Changes in the Saved Criteria Panel

We made some changes to the Saved criteria panel on the Balances screen. Previously, you were able to edit, override, and delete saved query criteria. Now there is no possibility to edit and delete query criteria once saved. You can still use the saved query criteria to create a new query.

For more details, refer to Balance Queries.

Extraction - Balances

We implemented a possibility to extract Balances using the Fynapse Extraction screen. This functionality allows you to create extract configurations on the basis of saved query criteria configured on the Balances screen to define which Balances should be extracted. Still the extract configuration can be run manually or automatically (using the scheduler capability). Previously, you were able to extract Journals, Unposted Journals, Errors, and user defined Entities.

For more details, refer to Data Extraction.

Extraction - User Defined Transaction Entities

We implemented a possibility to extract user defined transaction type Entities using the Fynapse Extraction screen. This functionality allows you to create extract configurations to define which user defined transaction type Entities should be extracted and run the extraction process manually or automatically (using the scheduler capability). Previously, you were able to extract only user defined reference type Entities.

For more details, refer to Data Extraction.

Bulk Operations - User Defined Transaction Entities Extract Configurations

Released under Feature Flag

To ensure consistency with existing Fynapse configuration, we extended the Bulk Configuration feature to include user defined transaction type Entities’ extract configurations. Going forward you will be able to download the bulk configuration inclusive of extract configurations for user defined transaction type Entities and upload them to another environment.

For more details, refer to Configuration Data.

Business Event Definition - Enrichment

We have enhanced the Business Event Definition screen to include information about references created for Business Event Entity and Enriching Attributes. Now, in the Business Event Definition grid you can see the information about the source of data for the given field (input file or reference) and the name of the Enriching Attribute, i.e. the field from a referenced Entity that will populate data into this field.

Moreover, you can view the list of defined references by scrolling down to the new References section, which is below the Fields section on the Business Event Definition screen.

For Entities other than the Business Event Entity the “source” attribute will appear for all defined fields when you download the Configuration Data JSON file. However, for these Entities this attribute is non-mandatory and you do not need it to upload your Configuration Data JSON file.

For more details, refer to Business Event Definition.

Ingestion of gzip Files via Backend

We implemented the possibility to ingest via backend data files in the gzip format, which allows you to upload more data in one file. Such files are decompressed just after uploading to the dedicated cloud storage to check if they meet the same requirements as files in the CSV format and to undergo the same validation and deduplication processes to be finally ingested. Details of ingested files are as well available in the Ingest file grid.

For more details, refer to Data Input File Ingestion and Data Ingestion Using Backend.