In addition to the major changes in governance and control (see here for details), this April release includes improvements across the platform, with new features, usability enhancements and performance improvements.
You can also see a list of defects addressed here.
Usability
Export breaks only
Often users export run results to spreadsheets for further analysis and processing. If you only want to analyse unmatched or partially matched data, you have to spend time filtering the data within the spreadsheets. In addition, when you have a lot of data in your process run, exporting the full data set can take a long time.
In this release, you can now choose to export breaks only, which will only export unmatched and partially matched data to the spreadsheet, therefore reducing the time it takes to export and also save your time from manually filtering afterwards. We have also improved the general performance of spreadsheet generation to give you results quicker.
The same option is available in our API by using the breaks_only parameter. See our API documents for more detail.
Bookmarking your views
By dynamically generating URLs since the February release, you can already bookmark particular result filters to reuse them, or share them with your team members. This release we have refined the feature so that it can always load the data from the latest run. Simply go to your current latest run, apply your filters and bookmark the URL.
Bulk delete match fields
Clients who have utilised the match field prediction by Duco Alpha have seen significant time savings when configuring new reconciliation processes. Occasionally, you may find the match fields predicted by Duco Alpha are not suitable, such as cases when you need to apply filter rules. You can now quickly remove them on the UI.
CASH
Upfront search
Finding particular transactions needed to conduct reconciliation, investigation and resolution activities is an essential part of an efficient operating model. You can now discover a particular subset of data quickly by applying all the filtering criteria at once, using the new Search function in cash reconciliations. In addition the search button provides visibility of how many fields have filter criteria applied.
Ignore account
Clear and transparent control over which Accounts are to be reconciled within any process is vital to remove unnecessary work and obtain compliance. This can now be achieved through setting Account statuses to ‘Ignore’, which will block balance and transaction related to those Accounts from feeding into the reconciliation.
System performance
Matching runs
Matching runs are a core part of Duco data processing, matching 300 million records everyday and efficiently identifying breaks and issues in your data. We have identified and improved various areas in the processing which cut down the time taken to complete a run, including the core data matching algorithm, how we load data and save matching results, and how calculated results and workflow rules are executed. In preliminary tests using real-life data, we have observed more than 50% of time saving in some cases.
Result display
Quickly displaying results is the next most important step after the data has been processed. We have replaced the user interface component in the result table, to make it much faster to display these results. In processes with more than 100 columns, we have observed display time being halved.
Export results to spreadsheet
We have completely rewritten how we load data from the database to generate the result spreadsheet, so that you can extract your results much more quickly for your post processing. The performance improvements are more obvious if you have a large amount of roll-ups in your run.
New look in Settings, continued
Continuing our effort to revamp our user interface, in this release you will see the new look applied to more Setting screens.
Bug Fixes
General platform
| Issue addressed | Description |
| Partial match score cannot be set to 0% | Cannot set the partial match score to 0% in Results Control |
| Issues with adding users to run notifications | Cannot add more than one user to Run Notifications when using search |
| Duco UI vs PDF configuration discrepancy | Percentage tolerance rule in PDF configuration file is not in line with Duco UI |
| Issues with accessing Reference data tables | Unable to access some Reference data tables from UI in some scenarios |
| Filtering values with underscore in results | Cannot filter records by the values containing an underscore |
| Deleting columns in Reference table | Cannot delete empty columns from a Reference data table used by an import request. |
| Closing multiple exceptions at once | Cannot close multiple exceptions at once when at least one of them is in 'Pending' status |
| Unable to access run results | Unable to view the run results of a connected process which ran prior to conversion of data types in the match fields |
| Performance issue of User Entitlements API | Getting timeout response when querying high volumes from User Entitlements API |
Data platform
| Issue addressed | Description |
| Missing run data | Some run data in Duco is missing in Data Platform caused by incorrect timestamps. |
| Breaking fields not updated | For some runs, the breaking fields data are missing in Data Platform, due to incorrect update logic. |
| Duplicate runs when user has changed email address | If a user's email address is changed, all runs triggered by her appear duplicated in Data Platform. |