The upcoming release will bring you a series of enhancements across cash reconciliation and Data Prep functionalities:
- Data Prep enhancements - seeing items filtered out by rules for auditability, capture change details and justification when making process setting changes, and more
- Further performance and usability improvements on your Cash reconciliations with improved speed on actions and better error messages when uploading Accounts
Data Prep enhancements
Capture change details when updating process settings
You can now capture the details and justification of configuration changes as part of the change management process. Add comments when you raise, close, approve or reject a change request to a staging copy.
Option to maintain full auditability for filtered out records
Items filtered out by active filter rules can now be seen in the results, making it easier for troubleshooting your configurations and providing full data audit. You can toggle this through the new Results control in settings.
This will be disabled for all existing Data Prep processes that have already been setup before the release, which you can enable it if you’d like those data reported. For all new processes, this option will be enabled by default.
If filtered items are being reported, they will be counted towards your chargeable volume. Items filtered in submissions before the release will remain unreported.
More information on statuses of your submissions
We are now showing more detailed statuses for your submissions, so that you can track more closely what has been done to the files you’ve submitted to a Data Prep process. You will now see:
Submission status |
Description |
New |
File has been received and in queue for processing |
Processing |
File is been processed and transformed |
Processed |
File has been successfully processed, with results now available. There may be errors for individual lines, see the Error tab. |
Failed |
Processing failed completely for this file. User should check the cause and corresponding corrective action e.g. update configuration and submit again, or contact Duco Support. |
Vol limit exceeded |
Volume limit has been exceeded or will be if this file was processed, so the file has not been processed. Depending on your limit, you can submit it the next day for example, or contact your Duco Customer Success Manager |
Deleted |
This submission has now been deleted. |
Aborted |
Processing was interrupted by the system. You can resubmit the data if necessary. |
Not processed |
The submitted data is not mapped to anything. You can update configuration and resubmit. |
Cash enhancements
Quicker responses when actioning transaction with constituents
Continuing our effort to improve the performance of your Cash reconciliations, this release sees quicker responses when commenting, adding labels, removing labels, splitting, manual netting and breaking apart transactions that have many constituents.
Improved feedback when uploading Accounts
Error messages will now be shown when there are any format or column value validations issues when importing Accounts into Cash reconciliations, making it much easier to correct and re-import as necessary.
Bug fixes
Issue addressed | Description |
Balances from MT940/ MT950 messages are not fed from a Data Prep to a Cash process. | In a Data Prep process, if an MT940/ MT950 message contained account id with a comma in it, Duco extracted both transactions and balances correctly, but failed to feed the balances to the downstream Cash process. |
Data Prep snapshot was not created automatically in some circumstances | In some cases in Data Prep a snapshot was not being created automatically as per the process setup. |
The filter rules are interactive on the Changes page in the staging copy | In a Data Prep process, a user could still interact and update filters from the staging copy Changes page, although the changes wouldn't be saved. Instead, all information there had to be read-only. |
Not all the file processing completion messages are shown | Data Prep process was missing notifications for process completion in some scenarios when multiple files were submitted. |
Issues with updating results page view settings in a two-sided process which uses a Data Prep process as input. | Hiding a Data Prep process name column on the results page in a two-sided process did not hide the values of the column and shifted all the other columns. |
XML run results export fails after some specific manual actions | In some specific cases when there were records with exception workflow actions in the run, the XML run results export was not capturing the actions properly and was failing |
Process export to other environments fails after some specific configuration changes | During export of a two-sided matching process a process importer could see the error 'Generation failed'. This was happening when an input field used in a match field was deleted and then replaced with another input field leaving traces of the deleted one. |
Filtering by the workflow and match statuses does not work in custom view excel export for cash | In a cash process excel exports using current view was not taking into consideration applied filters on the workflow and match statuses. |
Incorrectly specified file name pattern was blocking SFTP file submissions | In some cases when a file name pattern was written with errors, it was blocking processing of newly submitted files. |