This October release brings to you important updates that enhance your ability to monitor and control your processes in the Data Prep module, and others:
- Control over the submitted volumes to Data Prep
- New NRL operator to fine-tune your process configurations
Data Prep
Showing data volume information
You can now easily check how much data was submitted to a Data Prep process and processed per snapshot, helping you to quickly assess if all data have been received, or your filter rules are working as expected.
Control reporting of filtered results and balances separately
The result control setting now contains 2 separate toggles, allowing you to report filtered items from the main result set or the balance data individually.
New NRL Operator
Incorporate run start time into your rule logic
We have added a new function in our Natural Rule Language (NRL) to give you the reconciliation run start time. You can now use this information, for example, as part of the workflow rule logic to automatically apply labels to exceptions where data from the other side is not expected to arrive yet.
Cash
See when the Global Accounts screen was last updated
The Global Accounts screen provides a summary of Accounts including trial balance and account proofing calculations. This screen now shows how fresh the fields and calculations are to help users understand if recent automated or manual actions have been accounted for.
Bugs
|
Issue Addressed |
Description |
|
The staging copies dropdown in Data Prep was hidden by other elements on the screen. |
In Data Prep a dropdown to navigate between staging copies was partly hidden behind other elements on the page. |
|
A user is not being logged out automatically after 1 hour of inactivity. |
In some rare cases a user was not logged out from Duco automatically after being inactive for 1 hour. |
|
User administration actions result in a bulk revalidation of processes configuration and may slow down the environment. |
After a user or group update or permissions update, configurations of all the processes were revalidated at once, extending the process runs. |
|
The file sent to Duco is not visible in the submissions log. |
In some cases when a file was too big, it was not fully processed and was not visible on the submissions monitoring page. |
|
Configuration import page is not loading. |
In some cases the configuration import page was loading for a long time and then became blank. |
|
SFTP files submission doesn't trigger the process to autorun. |
In rare scenarios, a file submitted through SFTP does not trigger a run on the configured process. |
|
Not possible to fully promote between environments a configuration of a two-sided process which uses Data Prep as inputs. |
It was not possible to apply a staging copy of a two-sided process which uses Data Prep as inputs to a parent copy after promotion between environments as the data inputs coming from Data Prep processes were not being updated automatically, blocking the configuration. |
|
In a Data Prep process an internal error is shown when a user wants to delete an input field. |
In some cases when data was left in Pending state it was not possible to delete a Data Prep input field and the system was showing an internal error. |
|
In Data Prep it was not possible to delete a data input despite having all the necessary permissions. |
A permissions error was shown when a user tried to delete an input in a Data Prep process. The permissions were too strict and were requiring an additional role of 'Data Source Administrator' to complete the action. |
|
In Data Prep cancelling a data input deletion resulted in an infinite loading indicator. |
In a Data Prep process an attempt to delete and cancel the deletion of a data input when there was data in Pending status was causing an infinite loading indicator with 'Deleting' status. |
|
Improved user feedback in Data Prep. |
More details to users to troubleshoot when a Data Prep process configuration is invalid or submitted data does not conform to input format. |
|
In a Cash process filtered transactions were still visible in the Ungrouped transactions bucket. |
In some cases transactions that were filtered out by a filter rule were still visible in the Ungrouped transactions bucket of a Cash process. |
|
Issues with exporting current result view in Excel in a cash process. |
In a cash process, when exporting the current view as Excel from the ungrouped transaction bucket, transactions from duplicated statements were also included. |
|
Issues with deleting cash statements. |
In a cash process in some cases when a user was deleting many statements at the same time, the system was showing the error and not executing the action. |