The features we bring you this month will help to manage reconciliation results more easily and provide insight into your company’s activity on the Duco Platform.
Longer field names
This release changes the maximum number of field name characters from 32 to 255, giving you more flexibility when defining your data inputs. Field names will display the first 32 characters as standard. If the name is longer than 32 characters, it will be truncated with an ellipsis (...) and you can hover over the field to see the full name. No complicated abbreviations or scrolling needed. Field names that are currently 32 or fewer characters will show as they are today.
Audit log API
You can now automatically extract audit log data through Duco API, making it easier to integrate with your own audit controls. For example, you can automatically integrate logs with your own database, making it easier to search, analyse and report on actions to your auditors without logging into the platform.
Details of the API can be found in the API documentation page within the app, under Audit Log Entries.
|In rare scenarios, recon run fails because of database deadlock.
|In the rare occasions where a database session was not closed properly, it led to deadlock and caused run failures.
|Error when applying or closing change requests that were created by a deleted user
|This fix resolves the problem whereby a change request created by a given user A cannot be applied or closed by another user B if user A was deleted from the system following the CR creation. Previously an error was being thrown which prevented further action, this has now been fixed.
|Export results in an empty file when a date range filter is applied
|This fix resolves the issue with the system producing an empty file upon export when there is a filter applied to include only certain records that fit a given date range. After the fix the export includes the required data.
|Incorrect value in the calculated field resulting from manually matching a previous partial match
|Given a 2-sided reconciliation with partially matching records to start with, there was an issue being faced whereby a calculated field depending on values from both sides was showing an incorrect value when the records were unmatched and there was an action taken to manually match them. This bug fix ensures that the calculated value is correct
|Exclude staging copy accounts from global accounts screen
|We have resolved the issue related to the misrepresentation of accounts on our global accounts page when there was an open staging copy. Previously, staging copy accounts were included in the Global list of accounts but not actually shown on the UI. We have taken the necessary steps to rectify this and ensure accurate representation of accounts.