Change log

IBM® Safer Payments 6.5.0.08 contains defect fixes, changes, Known Issues, and APARs.

Critical defects

The following critical defects were fixed:

The masterdata value might be empty when it is applied to computing real-time transactions. The problem occurs if the masterdata is based on an index from a higher-level mandator. On Investigation > Queries > Masterdata query, attributes are then empty (Known Issue DT418128).

Major defects and changes

The following major defects were fixed and major changes were made:

On Administration > Case management > Case classes, case alarms might aggregate into unexpected case classes. The problem occurs after you upgrade from a version before 6.5.0.00 to 6.5.0.00 or higher. In 6.5.0.00 aggregation attributes were replaced with aggregation conditions. After you upgrade, the behavior of the converted conditions is different than it was before version 6.5.0.00. For more information, see Update Information.
A fatal error might occur during golive when it processes a PMML boosted tree model. The problem occurs if the model contains an invalid category that is not in the data dictionary (Known Issue DT392090).
When a challenger is promoted during golive, PMML might generate incorrect scores. The problem occurs if PMML boosted tree models are used in a champion and a challenger is created from it (Known Issue DT421950).
The user interface might crash if you delete a condition or master data condition. The problem occurs on Investigation > Investigation > Case selection > Case Selection Condition and Case Selection Masterdata Conditions (APAR PO09883).
On Model > [challenger revision] > Modeling > Simulation, you cannot disable a simulation while simulation queries are running on the same revision (APAR PO10105).
On Monitoring > Defined risk lists > Defined risk lists, in rare situations, duplicate entries might exist. If you delete all the risk list entries on one instance, entries might still exist on another instance. Then, when you delete the risk list on the remote instance, the deletion fails. The instances might then be inconsistent. For example, different revisions might be running on different instances (APAR PO10074).
When an instance is shut down while a golive is running, the golive does not run on remote instances. Now, it is done on remote instances after the API instance is restarted.
On Investigation > Queries > Group by queries, when you run a query, a log message is not printed when it is finished.
When an instance fails to golive, a time gap occurs after maintenance mode is exited and before the shutdown starts. During the time gap, the instance is still counted as active. Other instances in the cluster might proceed with the golive and fail. The minimum active instances setting is ignored (Known Issue DT391830).
In rare situations, an instance whose status is unreachable might block golives on other instances (APAR PO10173).
On Administration > Dashboard settings > Charts, a fatal error might occur if you delete a chart while it is computing. The same problem occurs on Administration > Dashboard settings > Key performance indicator. Now, when you delete these items, the system enters maintenance mode.
In certain scenarios, temporary cases are not promoted (Known Issue DT397122).
On Cluster > System monitoring > Settings > Cluster Settings > [instance], after you click Force startup after crash, the instance displays as invalided until startup finishes.
Updated OpenSSL to 1.1.1za. Updated the elliptic and DOMPurify packages to fix known security vulnerabilities.
On case investigations, for example, Investigation > Investigation > Case search > [case] > Case actions, attribute placeholders that contain large numbers might display wrong values. The problem occurs on numeric reporting attributes that are defined without decimals.
Case classes might be inconsistent on the primary instance versus the remote instances. The problem occurs after an alarm with a lower score is aggregated into a case. The case's case class is then wrong on remote instances.
Throughout the user interface, when you use the checkbox to select multiple rows in a table, your items might later be deselected. The problem occurs if you select multiple items, apply a filter, and then select more items. The previously selected rows that do not match the filter are deselected (Known Issue DT398225).
On Administration > Jobs > Settings, a fatal error might occur if you run multiple fraud marking report jobs that compute the same fraud marking report.
A crash might occur if a user tries to log in multiple times at the same time (Known Issue DT417690).
On Model > [revision] > Scoring engine > All Rules, a rule cannot be saved a second time. The problem occurs if the rule uses Timestamp or Numeric output types in Conclusions with the Reset value operation (Known Issue DT387158).
You cannot cancel a simulation for a challenger revision that is invalidated. The problem occurs if the revision is invalidated while the simulation page is open. For example, say that User1 is checking the simulation report on RevisionA. At the same time, User2 starts a golive on RevisionB on the same mandator. If RevisionB is newer than RevisionA, RevisionA is invalidated (APAR PO09929).
On Administration > System > Configuration > Misc > Miscellaneous, when Define EoD time per instance is enabled, the end-of-day job might run one more time at the old time before it switches to the new time.

Minor defects and changes

The following minor defects were fixed and minor changes were made:

Throughout the user interface, the sort icon in a table column might disappear after you minimize the column's width (Known Issue DT398477).
On Model > [revision] > Data model > Mappings > Input, for mapping messages of type AVRO, some labels display incorrectly.
On Administration > Key management > Encryption keys > Encryption keys, for inactive keys, the text in the Status column is incomplete. The timestamp is omitted.
On Model > [revision] > Data model > Inputs > [attribute] > Show references, the Reporting query label displays as code rather than text.
When alarms are promoted or consolidated, log messages are not generated.
When you create a new indicator on Administration > Dashboard settings > Status alarm indicators, items in the Alarm type list are not in alphabetical order.
On Administration > System > Configuration > Misc > Application Settings, Server time zone is not intuitive and is sometimes used incorrectly. Now, an informational warning states that it will be deprecated in the future.
On the golive report, the symbols for realtime interception missing error and realtime interception missing warning are swapped. The error is assigned an orange symbol. The warning is assigned a red symbol.
When an incoming connection in MCI is rejected due to a connection limit, the following log message is printed: W 0229 Ignored incoming MCI connection from '[IP address]' because IP address is blocked. The log message is misleading because a blocked IP address is not the issue. The log message has been improved.
Throughout the user interface, long option names in multi-select fields are truncated and indistinguishable.