In this release we are bringing better visibility into your Duco platform usage, as well as a set of usability improvements for faster process creation and exceptions investigation.
Solutions
Improved pre-configured solutions page navigation
The preconfigurated template page got much easier to view and navigate with the new search field. You can now search for specific regulatory template with a search box visible on the top left side.
Additionally, the list view got enhanced with smaller cards so you can see more templates in the screen and navigate through them more easily.
Ingestion
Latest submissions status - processing overview
We have enhanced the processes page with additional details for Data Prep processes. Now you can easily find the number and status of those submissions from the main processes view.
By clicking on the process status name you can see details of submissions for the last 7 days with status split: failed, not processed or successful.
Reconciliation
Easier navigation to rollup constituents
In generic recon processes, you can now navigate to see the individual records that made up a rollup easily, through the right hand side Details view. And that page has now got a new look.
This provides a more direct way to see the underlyers, compared to the existing navigation from the item details page. Also the rest of information available in the item details page are now all available through the right hand side menu, and it will soon be removed as part of the new UI design.
Quickly find the table column you want to use in rules
When you want to use a reference data table in your NRL rule (e.g. use a look up table to map a field value, such as internal security ID to ISIN), it is often hard to find the exact columns you want to use in cases when there are many of them. Now you can quickly search for the column you want to use by typing its name.
Governance
Tracking platform usage in one view
You can now easily check the overall usage statistics of your Duco instance in one view. You will be able to see the total volume usage across all processes in the Duco instance, breakdown by process types, and the total number of active processes.
As we migrate the existing Dashboard feature to a new improved version, the first dashboard we’ve brought to you is the Volume Dashboard. This default version is in preview mode, giving you the first glance of what the new dashboard will look like.
In the coming releases you will be able to configure your own dashboards, including widgets for exception management oversight. This new dashboard functionality will very soon replace the existing function. We’ll share more details about what you’ll need to do to use the more powerful features.
Unique names for your reference data tables
To avoid any confusions with duplicate Reference Data Tables names, we have added duplicate name prevention. The unique names are now enforced when creating a new table name as well as updating names for the existing reference tables.
With this change, when promoting reference data tables using Config deployment, it will avoid failure scenarios when reference data tables with the same name already exist in the target environment, which is coming in the next release.
Fixed bugs
| Issue Addressed | Description |
| In cash processes, 'show my items' does not filter the records. | 'Show my items' should filter the records allocated to my team. |
| NRL rule alignment on the screen shifts unexpectedly. | When hovering, the rule shifts from right-aligned to centre unexpectedly, for example in the Match field screen. |
| Match field fails to be created when using field search. | Sometimes when using search to find an input field to match with another already selected field, the match field fails to be created. |
| Export data with custom view uses wrong filter. | When using a filter in a column by first selecting all then deselecting an item, and making a custom view export, the filter is not applied in the export. |
| Pinning with large number of items sometimes fails. | In generic recon processes, the new pinned items tab sometimes fails when several hundreds of items are pinned. |
| The "Submission date" NRL operator sometimes isn't displayed or working correctly. | For example in workflow rules, when this operator was used, it may no longer display correctly and the rule may not apply when conditions are met. |
| Incorrect popup message when deleting a data input field. | In generic recon, Data input setting page, the popup message when deleting an input field is inaccurate. |
| User can remove a transaction from a rollup that is not assigned to them. | In cash recon, when a rollup is not allocated to the user's group, they should not be able to remove transactions from it. |
| Incorrect link to rule set page. | In generic recon, the link from the Multipass setting page to the ruleset page goes to the old version. |
| Inconsistent behaviour when changing write-off transaction amount. | In cash recon, when manual matching and editing the write-off transactions, sometimes it switches between input sides unexpectedly. |
| Error message is not shown when marking a run as failed. | When the platform encounters issue with marking a run as failed in generic recon, the user does not see any notification. |
| Duplicate data from Data Prep snapshot. | In some rare scenarios, recon process receives duplicated data from Data Prep snapshot unexpectedly. |
| Change request not showing fields being reordered. | When viewing differences between staging copy and parent process, the reordering of passes and reported fields were not shown. |
| Statement deletion and process reset fails in some scenarios. | Splitting a rollup / net transactions can lead to those failures. That action is now disabled. Users can break them apart and reorganise the individual transactions. |
| Recon results not ordered consistently. | Sometimes the results displayed in recon processes are shown in random order. |
| Deleted user caused "Assigned to" filter to break. | When there are exceptions assigned to users who have since deleted, the filter on "Assigned to" does not work in generic recon. |