Release Notes

Change on Data Structure Definition Screen

To improve the integrity of data structure definition we removed the ability to upload single Entities on the Data Structure Definition screen. Entities can now be uploaded exclusively in the Configuration Data JSON file on the Configuration Data screen.

Enhancements on Flows Screen

We implemented two changes on the Flows screen:

1. Delete action - the name of the Archive action has been changed to Delete. The result of the action is unchanged, i.e. deleted Flows are no longer visible in the grid and cannot be filtered in the Status column.
2. Deleting Flows in Draft status - previously, when you deleted a Flow in Draft status the Flow in Active status that was the source of the Draft was also deleted. Now, when you delete a Flow in Draft status, only this Flow is deleted.

Enhancement on Processing Summary Screen

We enhanced the Processing Summary screen to include Business Events generated by Flows. Now, the grid will also show the processing journey of Business Events generated as the result of Flow transformations and then processed in the Accounting Engine step.

Changes to Journal Import via File Ingestion Screen, Adjustment Portal Screen and Flow Journal Input Step

We implemented a change for importing Journals into Fynapse. Now, when you input Journals via the File Ingestion screen, the Adjustment Portal screen or through the Journal Import step in a custom Flow, and the ingested Journals have the Reversing Journal Type, both base and reversing Journals will be created.

Video preview:

Data Structure Definition - Changes in Support for Complex Attributes

We implemented the following changes in rules for defining complex attributes in Entities:

• InLine type complex attribute can only be defined as a nested attribute of a List type attribute; you cannot define InLine type attribute as a standalone attribute
• It is not possible to define a List type attribute as nested attribute of another List type attribute

Ingestion Configuration Screen

We implemented a new Ingestion Configuration screen that allows you to edit the headers used in the ingestion CSV files for Entities. It also allows you to sort data in Entities with complex attributes, e.g. InLine attribute.

Video preview:

Bulk Operations - Balances and Extracts with Balances

We enhanced the bulk download feature to include Balance Queries and Extracts with Balances in Configuration Data JSON file.

"balanceQueries": {
      "savedQueries": [
        {
          "type": "balance",
          "query": {
            "limit": -1,
            "balanceDate": {
              "type": "specificDate",
              "date": "2055-02-03"
            },
            "fields": [
              "customAccountingConfigName"
            ]
          },
          "name": "TestBalance1"
        },
        {
          "type": "balanceMovement",
          "query": {
            "limit": -1,
            "balanceDate": {
              "type": "currentDate"
            },
            "fields": [
              "customTransactionCurrencyName"
            ],
            "openingDate": {
              "type": "daily"
            }
          },
          "name": "TestBalanceMovement1"
        }

{
        "extractConfigurationName": "balance extract",
        "balanceQueryName": "TestBalanceMovement1",
        "startDate": "2055-02-11T23:00:00Z",
        "extractType": "CSV",
        "uploadSpace": "CLOUD_STORAGE",
        "incremental": false,
        "query": {
          "namespace": "fynapse",
          "entity": "Balances",
          "queryFilter": {}
        },
        "scheduler": {
          "type": "DISABLED"
        },
        "splitBy": {
          "isSplitByAttributeEnabled": false
        }
      },
      {
        "extractConfigurationName": "balance movement extract",
        "balanceQueryName": "TestBalanceMovement1",
        "startDate": "2055-02-18T23:00:00Z",
        "extractType": "CSV",
        "uploadSpace": "CLOUD_STORAGE",
        "incremental": false,
        "query": {
          "namespace": "fynapse",
          "entity": "Balances",
          "queryFilter": {}
        },
        "scheduler": {
          "type": "DISABLED"
        },
        "splitBy": {
          "isSplitByAttributeEnabled": false
        }
      }

For detailed description of the properties, refer to Configuration Data.

Dynamic Date Filtering in Extracts

We enhanced the extraction functionality by implementing a new dynamic filter for date attributes in the Query criteria panel. Previously, you could use only static date filters (for example, 1.1.2026-13.1.2026) that would always return the same data sets unless you manually update the dates. Now you can define dynamic date filters that allow you to extract data for a selected number of days, months, and years based on the following time anchors: the current day, previous day, previous period end, and previous year end. As a result, you no longer need to update date filters manually to ensure the extraction uses the correct time frame. For example, when the date filter is set to “11 days” and the anchor is set to the “previous day”, the extracted date range will adjust automatically based on the run date:

• 15.12.2025-25.12.2025 (inclusive) when the extraction is executed on 26.12.2025
• 15.01.2026-25.01.2026 (inclusive) when the extraction is executed on 26.01.2026

In each case, Fynapse recalculates the date range dynamically backwards each time the extraction is triggered to get the most recent 11 days.

Additionally, we added a new column to the Extraction Logs grid - Error message. This new column will contain errors thrown during the extraction process regarding the usage of invalid Fiscal Calendars. Dynamic Date Attributes Filtering.

Video preview:

Extracts - Advanced Journal Aggregation

We enhanced the Journal aggregation option in Extracts. Previously, you could only aggregate Journals based on defined Dimension Sets. Now, you can configure advanced Journal aggregation which allows you to define hierarchical aggregation Journals based on the selected grouping and ordering attributes and partitioning attributes:

• Grouping and ordering attributes - are used for aggregation. Once you select the attributes, you can order them in the way you want data to be sorted and displayed by dragging attributes.

Partitioning attributes - are used to to partition Journal Lines into independent data sets.

This option is available only when FDS is selected as a target name and Journal or Unposted Journal as a data source.

Video preview: