In Duco we are committed to continuously improving the experience of our customers on the platform and helping solve their most complex data challenges.
Cash
Improved statements handling
Currently in the Cash module submissions are already being split automatically by account and currency. With this release we are introducing better support to our customers with their ongoing ISO20022 migrations.
A single submission often contains multiple statements which may be required to be split further. To enable this, we will allow a unique statement identifier to be configured (in one or more input fields). For example, with a SWIFT file, this would be represented as the Statement/ Sequence combination.
This new capability will help to:
- avoid the need to break the statements down into multiple separate submissions
- Improve control over your statement integrity
- have greater general flexibility in combining the statements
- make it easier to identify issues in specific statements
You can also use Data Prep to aggregate multiple statements and submit them in a batch while still ensuring statement-level visibility.
Feature deprecation
Cases
In the previous release we have removed the ability to create cases, but the open cases were still visible in the environment to allow you to complete the exceptions investigation and to adopt the Exceptions Workflow.
With this April release we are fully removing the Cases capability. In order to be able to investigate breaks more effectively, you might want to enable the Exceptions Workflow.
Check this page for detailed instructions on how the Exception Workflow is working.
Run details API change
With this release we are introducing changes to the response schema of Run details API, version 3.
We will be removing 3 fields ‘expired_a_count’, ‘expired_b_count’ and ‘expired_count’.
If there are any systems dependent on these fields, you might need to update the settings.
Notice on the upcoming changes
Record Tracking lookback change
In our May release we will be implementing new functionality that will have a significant positive impact on run performance, especially for those high volume complex processes.
The change consists in a toggle option to enable limiting the number of runs included as part of record tracking, which can be found under the Record Tracking settings.
- All existing processes with record tracking enabled will have this feature switched off, i.e. there will be no limit on the record tracking for existing processes.
- For new processes created after the release with record tracking enabled, the limit feature will be switched on automatically.
Nevertheless, users with relevant permissions will still be able to un-toggle the new setting under the Record Tracking settings page and thus set the number of runs for record tracking to unlimited.
NOTE: If no record tracking is set on an individual process, you can still raise requests with our Support team to limit the runs for all processes to a set value as you currently do, however if the record tracking limit is also toggled then this will take precedence and only the previous run will be considered for record tracking purposes.
More details will be shared in the next Release Notification email.
Sunsetting the Labels gadget on Dashboards
We are working hard on creating a new set of dashboards that will allow our users across many functions to have access to their mission critical information in a consolidated location.
This means that current Dashboards will be changing and we are starting with the Labels gadget.
With the next release this gadget will be removed from the gadgets creation menu and in 6 months all the existing Labels usage gadgets will be removed.
If you are relying on this information being available on the Dashboard and have concerns about the removal of this feature please inform your Customer Success Manager or contact our Support team.
Please note that you will still be able to use the labels as usual and they will also be available in the Data Platform for reporting.
Fixed bugs
Issue Addressed | Description |
Issue with manually submitting files to the reconciliations via the new user interface. | The users were shown a "Service Unavailable" error when trying to submit files to a reconciliation process in a new user interface. |
Not able to open linked transactions in a Cash process. | The users were getting redirected to the All Transactions page when opening the linked transaction in a new tab in a Cash process. |
Issues with setting up Accounts for a Cash process. | The users were getting errors when uploading a ".csv" account configuration file to setup a Cash process and the process configuration was not getting validated. |
Not possible to download a PDF configuration file in Data Prep | In some cases when results are in pending status, the PDF config file was not generated properly. |