2025.2.1

Release notes for Fynapse 2025.2.1

FX Revaluation

We enhanced the FX revaluation functionality to allow you to configure multiple FX revaluation configurations.

For more details, refer to: Multiple Currencies Configuration.

Security - Data Permissions

We added a new feature to the Security functionality that allows users with the Fynapse Security Administrator role to grant access to defined data sets to selected user groups. As a result, they can define granular access rules to reduce the chances of unauthorized data exposure. The current implementation allows users with the Fynapse Security Administrator role to configure data permission rules for transactional data on the Subledger Node level. The results of the configured data permission rules will be visible while using the Journals, Balances, and Period Locking screens, where user groups entitled to access these screens will view only data sets defined by particular rules. The data permissions feature is made of two separate screens available from the Security menu:

  • Data Permissions that allows to define data permission rules to grant selected user groups access to data. The screen also allows to edit, clone, and delete selected data permission rules.
  • Security Settings that allows to turn on and off the feature. Without turning it on, created data permission rules will not affect data access.

The data permissions feature can be enabled and disabled but you need to remember that turning it on and off changes the logic how restricting data access works, i.e.:

  • Once enabled, user groups will be able to view only specific data included in the data permission rule to which they are assigned. This means that these user groups cannot view all available data, and unassigned user groups lose access to all available data.
  • Once disabled, Fynapse will revert to the previous logic for granting access to data, i.e., all user groups can view all available data.

For more details, refer to Data Permissions.

Error management

Reprocessing

We implemented a new functionality that enables users with the Fynapse System Administrator role to easily configure when and how often automatic reprocessing of failed events should be triggered. Additionally, they can set a maximum number of reprocessing retries. Both settings will be configurable via the Reprocessing screen. Previously, it was impossible to define these settings via the Fynapse GUI.

Currently, automatic resubmission occurs by default once a day at 8:00 UTC and the number of retries is set to 30 unless it is defined differently by a user with the Fynapse System Administrator role.

For more details, refer to Reprocessing.

Changing the Way of Exporting Errors to a File

Released under Feature Flag

We removed the possibility of exporting errors to a file from the Errors screen via the Export results as CSV button. Instead, we developed a possibility to download results to a file from the Extraction logs screen. To start downloading, you will have to just click a proper extract file name.

Please remember that you need to have an extract configuration for errors created and run before you can download any results from the Extraction logs screen and the Target status for this file must be Sent.

For more details, refer to Extraction logs and Errors.

Extraction Logs - New Statuses

We added two new statuses for the Extraction status in Extraction logs:

  • Pending - it informs you that Fynapse collects data that will be extracted, but the extraction process itself has not started yet. At this point, it is not recommended to run the same extract configuration again, and it is impossible for the incremental extraction.
  • Duplicated - it informs that a user triggered the extraction process again for an incremental extract already in the Pending status. It will also indicate that such extraction will not be performed at this point and it will not be possible to run it automatically or manually until it reaches at least the In progress status.

For more details, refer to Extraction logs.

Documentation

A new article about configuring SSO was added to the Developer Resources section.