In addition to the major changes in process permissions that we highlighted in our product change notification last month (click here for details), this July release also includes:
- Improved control over exceptions workflow with option to limit exception auto-close only to records from the previous run
- Performance improvements for the Accounts screen in Cash
- Real-time feedback when there is a problem with NRLs in Data Prep
Limit auto-close to occurrences in the previous run only
Currently the exception Auto-Close function (if enabled) is applied when records in the current run are associated (based on the record tracking logic) with occurrences from any historical runs. There are scenarios, typically with full population intersystem reconciliations, where users only want to auto-close (and therefore continue the ageing) if the current occurrence of the record is associated with a record in the previous run only.
This can now be managed through a new setting in the Process configuration allowing you to limit auto-close to occurrences in the previous run only.
Note that this change would only impact the auto-close logic and tracking will continue to work as normal.
Using this setting can also improve the performance of runs as the system has to evaluate less historical data when executing the auto-close logic.
Transformation and filtering rule feedback
Using Duco natural rule language (NRL), you can perform complex data transformation and filtering in Data Prep without writing any code. We have made it even easier now to configure these rules, by immediately highlighting any problems so that you can correct them accordingly. If your rule results in a field type change (e.g. from integer to text), you will be prompted for confirmation before committing, to stop you making any unexpected changes to downstream processes.
Better handling when reprocessing your sample file
When you adjust the data input parameters such as which row the data starts and ask Duco to reprocess your sample file in Data Prep, it will now preserve as many existing input fields as it can, and therefore the associated mapping and rules. This can save you time from recreating the configurations.
Additional delimiter support
To further streamline the onboarding of data from various systems, Duco now automatically detects generic files that use ¶ or ∂ as field delimiter. Simply upload a sample file, Duco will identify all the fields and their data type for you.
|In Data Prep an incomplete filter rule is stuck and can't be removed.||In a Data Prep process if a user creates an NRL rule using incompatible data types and saves the rule with some blank values, it wouldn't be possible to finish editing the rule or to remove it.|
|Users with Global Permission Viewer role are not able to access a Data Prep proces.||In case if the Global roles are enabled in the environment users or groups with Global Permission Viewer role should be able to access any processes and reference tables. However, this was not working for Data Prep.|
|Chinese characters are not correctly displayed on the Data Prep submissions page.||In a Data Prep process if the input file name had Chinese characters, they were not recognised and were displayed as '?' on the submissions page.|
|Processing of files in Data Prep was failing due to an issue in filter rules.||In some scenarios processing of submitted files to Data Prep was not completing successfully if there was one filter rule used for several inputs at the same time.|
|A user without necessary permissions is able to see the Delete a process button.||In a Data Prep process a user without the "Process Deletor" global role was able to see the Delete a process button, however clicking on it was resulting in an error.|
|When screen is minimised, any click on the Duco page leads to the Dashboards page.||When a Duco screen is opened in a small window, clicking any button on the page loads the Dashboards page.|
|Shifting column values when a column is hidden.||In some cases when a column is hidden via the Column settings menu on the results page, the header gets hidden but the values stay on the page shifting all the other columns.|
|Ambiguous display of minutes on the Submission windows page||If a user sets the value of 1 to 9 minutes, the values are displayed without a leading 0 which in some cases makes the defined time unclear.|
|Values from the reported fields are incorrectly aligned.||In a two-sided process values from the reported fields were vertically aligned in the center making it unclear which side the value belonged to.|
|When clicking on the Calculated results link a user was redirected to the General settings overview page.||When a user clicked on the Calculated results settings page in a two-sided reconciliation, the link led to the General settings overview page instead.|
|Overlapping data input names on the Run overview page and on the Data inputs page.||In a two-sided process if a data input name is long, the name would be overlapping with other elements on the screen on the Run overview and the Data inputs pages.|
|Filtering the list of SFTP submitted files is failing.||When a user selected all the records while filtering by the file name on the submissions monitoring screen, an error is shown.|
|Overriding the accounts list in a cash process blocks the configuration and a process can't be run.||In a cash process overriding a long accounts list in some cases was invalidating the process configuration making it impossible to run it.|
|Issues with promoting a staging copy if data input name contains quote characters.||When names of the data inputs of a two-sided process contain a quote character, promotion of the staging copy was failing.|
|While creating a data source, both sides of the process inputs were shown with the same name.||When a user was creating an SFTP data source for a two-sided process, system was showing the left-hand side process input name for both inputs.|