This release contains incremental changes and bug fixes.
Exception ageing in calculated result
To support your exception management processes relating to when exceptions start ageing, you can now use the “The starting date and time of the exception” operator in Calculated results. By default it will give you the date and time in UTC, up to seconds, of when the exception first appeared in the process.
Note that if you use the “Exception age” feature or workflow rules are used to set when an exception starts ageing, this new operator will not show the updated exception start date as set by those rules, but instead will show you either the default exception start date for new exception or as per specified logic from the last run if it is carried over from previous run with auto-close enabled.
New look for Submission routing configuration
Previously called Submission under Administration module, this screen is now renamed as Submissions routing as part of the UI upgrade. It has been redesigned so that you start with the list of all routing configurations, and you can search for an existing data source configuration using the data source name, file name pattern, linked process code or reference data table name. The upgrade together with new screenflow makes the feature much faster and easier to use.
Bug fixes
|
Issue addressed |
Description |
|
Occasional error for excel export |
If the parent process is linked to multiple child processes, exporting results to excel may fail. |
|
Missing workflow related columns in pinned items |
When some items are pinned, columns related to exception workflow such as Group and Assigned to are not shown |
|
Multipass screen not rendering correctly |
In some scenarios, the multi pass details are shown below the pass list |
|
Disabled workflow rule blocking runs |
An invalid but disabled workflow rule should not block a run from kicking-off |
|
Find matches within roll-ups in cash |
When the option is enabled, in some cases transactions are not fully for some accounts. |
|
Data platform - manual workflow actions are not stored correctly |
Manual actions on exceptions (e.g. changing group assignment or adding a new label) are not visible in the Data Platform until the process is re-run. |