This release brings an enhancement to reference data tables and adds to data prep the same change management controls that you're used to in our reconciliation processes.
- New support for reference tables - update or add new rows to an existing reference data table without having to resubmit the entire dataset
- Data prep enhancements - we’ve added staging copy and the ability to promote processes between environments
Update data in reference data tables
It’s now more efficient to update your large reference tables when there are only a small proportion of changes.
You can now send files that contain just the changed and new rows with Duco identifying which rows to update or create based on the columns you set as ‘tracking columns’ in the settings.
You can still choose to replace the entire population of rows when data is submitted by either manual upload or SFTP routing.
Data prep enhancements
4-eye control for configuration changes
Managing changes to your data prep processes at ease with the same level of governance you have been accustomed to when using Duco.
You can now use staging copies to change and test your changes in data prep processes, in the same way that you do for recon. When you are ready, raise a change request and go through a 4-eye review and approval process to roll out to production.
Seamlessly rollout changes through development environments
When you are using our development environments feature, you can now promote data prep process configurations between them.
Together with the enhancement from last release, you can now promote your data prep processes and the corresponding reconciliation process that uses it as input to another environment:
- Export your data prep process to the target environment, and apply that import request. It will create a new staging copy to the data prep process.
- When ready, raise a change request to roll it out to production.
- Export the reconciliation process to the same target environment and apply the import request. Choose the data prep process that is now in the target environment in the mapping step.
- Test the whole flow in the staging copy created.
Bug fixes
Issues addressed |
Description |
Issue with updating the Cash accounts list |
An error occurs after an attempt to upload data to the Cash accounts list and it is not possible to re-upload the file again. |
Unclear error message while uploading MT940/ MT950 messages |
While uploading the MT940/ MT950 messages to a Cash process, the error message was not indicating which lines of the messages caused the issue. |
Cash transactions are left in the 'unprocessed' state after submission |
After the cash submission some transactions are left in 'unprocessed' state, but can be processed afterwards by matching on 'unfinished accounts'. |
Global cash accounts overview export is failing in some cases |
Cannot export global account overview when sub accounts have different latest statement end dates. |
Loading error after using Alpha prediction |
In some scenarios, the process page does not load and error is shown after match field or roll-up rule prediction. |
NRL rule using a reference data table does not work properly in Data Prep |
In Data Prep an NRL rule fails to find non-string values in reference data tables. |
Not possible to delete an output field in a Data Prep process |
In a Data Prep process a deleted output field was reappearing after the screen refresh making it impossible to remove the field completely. |
Data Prep snapshot is not available to be used in a run |
In some edge cases Data Prep snapshot information was not properly replicated to be used in a Duco reconciliation process. |
Duco shows an empty Data Prep snapshot after the output fields update |
In Data Prep after the output schema changes the snapshots created prior to the change will show as empty. |