Operational Dashboard - Changes & Fixes
This page covers the changes and fixes provided to Operational Dashboard for IPF Release 2025.2.0
Operational Dashboard
The latest version of the Operational Dashboard is 9.3.2.
For the latest version of ops-gui-service, bump ipf-release-ops-gui-bom to 2025.2.0 in pom.xml.
@iconsolutions/common
Changed
-
Ordered Processing Entity list
The order of Processing Entities in the processing entity select component is now configurable by supplying the processing-entities list in ipf.authorisation.conf. If the list is not provided, processing entities will be unordered. If the list is incomplete, any present entities will be in order and any remaining will simply be appended to the list.
-
Dashboard title style improvements
Alignment of page and sidenav titles has been updated to ensure consistency.
-
Error response for invalid or missing cookie
When a network call is made with an expired cookie, the service now returns a 401 rather than a 403. When a user navigates to a page they do not have permission to view, they are no longer logged out on a 403.
-
Accessibility of card components
Sizing of tooltips and buttons in IPF card components has been adjusted for improved accessibility.
@iconsolutions/htm
@iconsolutions/ods
New
-
New column config
We have added payment-columns, recall-columns, bulk-columns and batch-columns to the config. Each of them is an array of objects with a columnName value. These are used to determine which columns are shown in the search results table on the search page for each of the payment types. You can choose any field from the ODS summary response object to add as a column to the table. The columns will be shown in the order they are defined in the config, so if you want to change the order of the columns, you can do so by changing the order in which they appear in the config.
It’s recommended to limit the number of columns to 10, as adding more negatively impacts the table’s readability and appearance.
If no config is provided, default columns are used.
Example:
payment-columns = [
{
columnName: "createdAt"
},
{
columnName: "transactionType"
},
{
columnName: "csm"
},
{
columnName: "amount"
},
{
columnName: "clientRequestId"
},
{
columnName: "debtor"
},
{
columnName: "creditor"
},
{
columnName: "bankingAccount"
},
{
columnName: "globalStatus"
},
{
columnName: "reasonCode"
}
]
Changed
-
Code Mirror update and removal of diff-patch-match
The Operational Dashboard has updated to version 6 of Code Mirror which has improved its diff engine. We believe this is a better experience then the current diff-patch-match component, so we have migrated to the Code Mirror component. Please see migration steps for updated dependency requirements.
-
Multi-select Global Status & Reason Code
We have changed the Global Status and Reason Code fields on the search page for Payment, Recall, Batch and Bulk, to a multi-select dropdown. This allows users to filter results based on multiple statuses or reason codes at once, enhancing the search functionality. The dropdown has a reset-all function which will deselect all selected options. It also has a tooltip that shows the selected options when hovering over the dropdown.
-
Configuration Keys for Establishing Connection to CSM Reachability which consumes DPS V2 - Backwards Compatible
Client connectors provided by the Dynamic Processing Settings API V2 require host and ports to be defined with the following config key prefix:
ipf.dps-api. As a result, host and port for CSM Reachability has to be defined with the mentioned prefix. The Dashboard Service provides backwards-compatible configuration for this by default:
ipf.dps-api {
client-type = "connector"
http {
client {
host = ${ipf.business-operations.processing-settings.http.client.host}
port = ${ipf.business-operations.processing-settings.http.client.port}
}
}
.....
}
-
New date picker component in ODS Search
A new date picker has been implemented on the ODS Search screen. Depending on the date type selected, it is now possible to input either a date or a datetime range.
-
External messages date-time-ago format
In the External Messages tab on ODS Details page, date-time-ago format is now absolute instead of relative.
-
User details added to future dated payment cancellation request
When a payment is cancelled, the User ID of the operator is now mapped to payload.assgnmt.assgnr.pty.ctctDtls.othr.id.
-
CSM search field in ODS Search
It is now possible to search by CSM in ODS Search.
-
Moved ODS Search params to URL
ODS search params are now in the URL, allowing the search criteria to be retained after navigating away from the page and the page to be shared or bookmarked.
-
Top level Global Status shows in red if status is 'Rejected'
The status of a rejected payment now shows in red on ODS Summary/Details page.
-
Format of OriginalInterbankSettlementDate in Recall search results
The date is now correctly formatted according to config.
-
External Messages now includes service info
A source column has been added to the External Messages table in ODS Details to show service info.
-
Remove Use of
anyin comparators of summary-search-results component
any types have been removed and alphabetic and string comparators have appropriate types.
-
Identify recently viewed in ODS Search results
Recently viewed transactions are now identified with an icon in ODS search results.
Fixed
-
ODS Summary search results not loading
The ODS payment summary search results now load correctly when navigated to from the process object search screen.
-
MDS Search page results
The MDS search page no longer shows payments from the previous page when navigated to from ODS Payment Search.
-
Message Log pointer for Instructing External Message
It no longer navigates to Bulk Search when the Message Log Pointer for Instructing External Message is clicked.
-
Payload toggle position
In the payload component in ODS Details, the position of the payload toggle is now fixed and does not scroll.
-
ODS Search works with thousand separators
It is now possible to search with thousand separators (eg. 1,000).
-
Spamming of logs when invalid date format provided to ODS Export
There is now only one error log stating that the date format is invalid.
-
ODS Export issue with no records
Attempting to export ODS results with no records no longer causes an exception. Now, an info message is logged and an empty CSV is returned.
-
PDS History overriding existing history rows
In PDS History tab, the values of previously opened history tabs are not overridden when multiple history rows are opened.
-
Inaccurate search results on OriginalInterbankSettlementDate
Search results for Original Interbank Settlement Date are now accurate.
Migration Steps
-
Change
"@iconsolutions/ods-payment-search"npm module to"@iconsolutions/ods": "^189.3.2"in package.json
Change the following dependencies in package.json:
-
Change
"@ctrl/ngx-codemirror": "^6.1.0"to"@acrodata/code-editor": "^0.5.1" -
Update
"codemirror": "^5.65.12"to"codemirror": "^6.0.1" -
Add
"@codemirror/lang-json": "^6.0.1","@codemirror/lang-markdown": "^6.3.2"and"@codemirror/lang-xml": "^6.1.0" -
Remove
"@types/diff-match-patch": "^1.0.36"