Following the smaller incremental release a few weeks ago, this release contains a long-awaited feature to make exception investigation collaboration easier, as well as enhancements in the cash module:
- Email notifications for exception assignments and commenting
- More flexibilities on extracting account balances from CSV statements
- More options to delete statements in bulk to recover from bad data
Email notification for workflow actions
Some users involved in exception workflow may not login to Duco everyday, and getting their attention to work on investigation can be time consuming. To proactively notify these users, you can now choose to have Duco to send them email notifications when:
- an exception is newly assigned to them,
- a new comment has been added to their exception, and
- a new comment has been added to an exception that they have previously commented on.
This feature will be enabled by default for any new processes to be created after the release, including generic and cash processes. You can of course choose to enable it for your existing process through the Notifications screen in process settings.
Note: Notifications are not currently available when adding via a staging copy, or when promoting from one environment to another. This will soon be enhanced to make the change management process more straight forward.
Cash
Loading signed balances
Where upstream systems can only produce absolute values with specific characters to state if it’s a positive or negative balance (i.e DR, D, C, CR etc) you can now use the new <debit> and <credit> balance extraction regex capture groups. This allows the user to state the specific characters that will denote the balance being either a Credit or Debit.
Loading balances with no decimal places
Where upstream systems can only produce balance values as fixed integer amounts with no decimal places, you can now use a new <fixedwidthbalance> balance extraction regex capture group. When used it will add a decimal place to convert the integer value to a decimal with two decimal places.
Delete Multiple Statements
Delete all Statement for a Submission
Similar to the above, sometimes an entire submission is corrupt or loaded in error. Users can now trigger that all statements associated with a particular submission are deleted in a single action.
UI enhancements
Confirmation when deleting NRL rules
It can be frustrating when you accidentally delete a complex NRL rule that you’ve just configured. To prevent such accidents, we will now prompt you to confirm when you delete a rule.
Audit log to show when a run was triggered with carry over data only
We have now added information to the audit log entry when a run was manually triggered to use carry-over data only.
Bug fixes
|
Issue addressed |
Description |
|
Filtered and Duplicates buckets do not load properly after refreshing the page. |
In a one-sided or a two-sided process, users get redirected to the overview page after refreshing Filtered or Duplicates bucket with column filters applied. |
|
In a Cash process selected records get unselected when multiple users perform actions on same transactions. |
When one user selects a couple of records on the transactions page and another user performs some operations on the same selected transactions, the selection done by the first user will disappear. |
|
During a new process setup, configurations of the data inputs get reset for one side while the settings for the other side are saved. |
When using the process setup wizard, after saving the configuration of the data inputs (worksheet, sheet index, first data row) for one side, the other side gets reset. The issue is observed when a user configures data inputs for a two-sided process using excel files. |
|
Not able to create a new match field after writing an NRL rule. |
Cannot add a new match field after an NRL rule is created in the existing match field as the button '+Add field' is greyed out. |
| The values in automatic Difference fields are shown twice. | The values of an automatic difference field configured in Reported fields are shown twice, for both sides of the match. |
| Incorrect alignment for values that are present for one side only. | If a value is only present for one side of data, the value is shown in the middle making it unclear which side it comes from. |
| In data platform some label associations are duplicated | In Data Platform, in some cases, a label attached to a record is duplicated and stored twice. |
| Issue with reading first row of data in some processes. | When a delimited file contains headers, the starting row is misinterpreted and causing problem processing the first row of data. |