Change log

IBM® Safer Payments 6.4.2.01 includes critical, major, and minor defect fixes, APARs, and changes.

Critical defects

The following critical defect was fixed:

The CPU usage of an instance can reach 100% if more realtime threads are used than the number of CPU cores (APAR PO09914).

Major defects and changes

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

The unrecoverable error message Attribute reference in condition not found displays if case selection attributes are added that do not belong to the selected mandators (APAR PO09632).
During startup, the iris_sql_util.so file cannot be loaded and an error message is displayed. On RHEL7, the message is /lib64/iris_sql_util.so: undefined symbol: initImpl. On RHEL 8, the message is iris_sql_util.so: cannot dynamically load position-independent executable.
Errors about loading external fonts display in the browser debug console (APAR PO09191).
Certain operations that require maintenance mode, for example, golives or saving a mandator, appear to hang in the user interface. Now, when a user performs an operation that requires maintenance mode (except for golives) and the instance is performing another operation in maintenance mode or cannot enter maintenance mode, the operation is canceled. The user is warned and must retry later. When a user performs a golive when maintenance mode is active, the golive is queued and the user is warned. In addition, the maintenance mode status was added to the cluster page and the revision information page. Help text was updated to better explain maintenance mode (APAR PO09570).
An unrecoverable crash might occur if certain invalid mapping definitions are used to generate a message report or if those definitions are in use when a message is received. An example of an invalid mapping definition is a JSON element name that contains double square brackets (APAR PO09847).
In the formulas under model components, saving the form by using the Ctrl+S keyboard shortcut while the focus is on the expression field does not save the formula expression correctly.
Exporting a case table with masked data to CSV can result in incorrect columns. The defect happens when the user cannot see the masked values and the value is smaller than 10 characters. All the characters get replaced by X, including the separator (APAR PO09674).
Cases and case audit files on a remote instance are stored as temporary files in an arc directory rather than as case files in an inv directory when the case is transferred over FLI. As a consequence the case cannot be worked on that instance (APAR PO09831).
Expression elements that are generated from expressions that were pasted from Excel sheets do not remove special characters (white space, newline, and so on) from the expression. The user interface might crash if more expressions are added or if the newly generated ones are sorted manually by the user (APAR PO09445).
If any number of rules are changed within a ruleset, revision comparison displays every rule in the ruleset as changed.
Form fields that contain a message or body template are too small for most use cases. The user must manually resize them to be usable (APAR PO09818).
When the option format values is used in an Outgoing channel configuration or case action/notification, the decimals for the amount attribute are lost (APAR PO08209).
For some dropdowns on several pages, for example, conditions in model elements, the text that is entered to filter the dropdown options sometimes reverts to the initial option that was selected.
When extended authentication is enabled, after a user logs in with two-factor authentication, the navigation menu is not displayed. Additionally, the initially selected tab is not the Start on tab that is defined in the user's profile settings (APAR PO09796).
The attributes that are available on the left side of merging conclusions depend on the system configuration setting Mergings may use DDC in Administration>System>Modeling. If the setting is not enabled, attributes that are stored only in DDC are not available in merging conclusions. In fact, the system setting should affect DDC access only for merging target conditions and termination conditions.
In rare situations, a crash occurs when simulation data selection changes to a smaller URID range and the save hangs. Then, in the same moment, the user opens and runs a simulation report in another tab (APAR PO09850).
A crash can occur during the end of day job if an index is corrupted and the index entry is purged (APAR PO09784).
SSL handshake blocks the system when it waits for the response from external server (APAR PO09605).
In the user interface, improved the performance of the external model page (APAR PO09749).
The filter at the top of the model components page does not initialize correctly. If the filter selection is changed, the results are not updated correctly.
When output attribute values are included in doublet detection responses, the output values might have random data. Added a checkbox that is named Access protection for outputs. If it is selected, access protection is applied to doublet detection. Also, Retry in access protection of mergings was renamed to Attempt (APAR PO09868, PO09814).
On the Own Input Attributes page, default storage options are displayed for existing inputs and outputs rather than the saved options.
In rule conclusion under model revision, if the attribute's data type is anything other than numeric or timestamp and a Python function without parameters is added in the expression field, an error message displays and the conclusion cannot be saved.
A crash might occur if a broken timestamp in YYYYDDDhhmmss format, for example 2022000000000, is sent (APAR PO09882).
Golives can hang if there is a simultaneous case action activity in the user interface to send case actions or display case action previews (APAR PO09888).
In rare cases, the FLI buffer gets corrupted and messages hang if the message header or the complete message exactly hit the buffer end during rollover (APAR PO09873,PO09900).
In case investigation, actions like Followup and Close cannot be completed in Case History (APAR PO09857).
Save and execute simulation query fails and stops simulation when simulation is running on a remote instance. Refresh simulation query result fails when simulation is running on remote (APAR PO09855).
In case investigation, when an attachment comment in the attachments table is edited, the newly entered value is displayed in the table only after the page is reloaded.
Improved message synchronization so that transactions use only a single FLI message. Up until now, IBM Safer Payments used two FLI messages to synchronize a single transaction when that transaction involved the execution of external model components. This method of synchronization led to data loss and data inconsistencies due to the complexity involved in merging the two messages. Notably, in the gap between the two FLI messages, profiling elements like counters produced wrong results by counting (or not counting) unfinished transaction records (transaction records for which the second FLI message was not yet handled).
When a multiline value is present in the title or explanation field in the compliance list xml, only the first line of the text is displayed on the Compliance List Hits pop-up. The appearance of the pop-up for entry details is inconsistent across several pages (APAR PO09557).
The results of group by queries and reporting queries show incorrectly formatted values for timestamp grouping attributes. Also, the results do not take the IBM Safer Payments time zone into account if the system time meta-attribute is used (APAR PO09894).
Messages that are sent through outgoing channel configurations do not adhere to all attribute formats even if Format values is enabled. For numeric attributes, the ID formatting is ignored. For text attributes, the PAN (dashed format) formatting is ignored. Additionally, encrypted attribute values are never formatted in case action previews even if the user has the privilege to view values in clear-text. It's also not possible to configure which digit group and decimal separator should be used for the numeric formats that are working. Now these separators can be set under Administration>System>Configuration>Interfaces>Alert message interface.
If aggressive fail-over mechanisms are employed for the online data interfaces and a transaction that does not compute in a given amount of time is resent to another instance in the same cluster, multiple instances might compute the same transaction at the same time. In rare cases, both instances end up with the same transaction but with different primary instance IDs and URIDs. This leads to problems when fraud marking is performed. The likelihood of this happening is increased when external model components are used. Now, doublet detection handles these cases by correcting the primary instance and URID of the found doublet. The system always takes the smaller primary instance and the corresponding primary URID and stores them in the doublet.
It is not possible to send a case action by using simplified view if that view contains an encrypted, numeric attribute and the investigator is not allowed to see unmasked values.
In case investigation, the query result table sometimes resets the table preferences if the page is refreshed (APAR PO09902).
Tables that contain cases and the Consolidated alarms table within a case display wrong values for encrypted timestamp attributes when viewed by a user with the privilege to see clear-text values.
Case action previews and sent messages do not contain the correct values for query results or consolidated alarms that are attached to the case action if those values are masked for the investigator.
The case action simplified view does not correctly handle masterdata values with decimals. The digits are correct but the decimal period is lost.
Added data to the log message for corrupted FLI buffers (APAR PO09891).
A crash might occur if rules are enabled or disabled while an analysis is running (APAR PO09910).
Performance issues and errors occur in the user interface because queries are not correctly cleared from memory (APAR PO09920).
If the simulation instance is set to an instance that is not the API instance, the getRevisionStatus request is forwarded to the simulation instance. It might contain trailing zeros or more characters at the end of the response that can cause 503 errors in combination with some proxies and load balancers (APAR PO09913).
A crash might occur during rule generation if the page is refreshed at the same moment that the Stop rule generation without saving button is clicked or a rule is committed (APAR PO09885).
Mandator memory limit is calculated with revisions that are not running (APAR PO09548).
When a case is opened, the case history table is not displayed for the selected reporting attributes. It is displayed only after the selected reported attributes are changed (APAR PO09865).
A reporting query might access invalid memory if it runs in parallel with golive (APAR PO09901).
In case investigation, when an attachment comment in the attachments table is edited, the attachment comment editor does not render correctly and is not visible during editing.
Simulation MDC is created for overwritable inputs when data for that input is already available in MDC.
Masterdata update might be lost when it is transmitted by using FLI (APAR PO09940).
The connection to IBM MQ times out if MQ definition values, for example, the channel name or queue manager name, is longer than 19 characters (APAR PO09942).
When bypass is enabled and the MCI uses SSL, a crash might occur during a structural golive. The crash occurs if the golive takes a short amount of time, for example, a few milliseconds if it is the initial golive of a new mandator. It is caused when the instance is establishing the SSL handshake while the golive completes and shuts down the bypass connection (APAR PO09934).
A crash might occur if simulation data selection is saved multiple times and the analysis that is included in the simulation is defined to use simulation data selection (APAR PO09935).
During the end of golive, external models get no response from external systems.
At the beginning of golive, MCI does not respond even if bypass is enabled (APAR PO09960).
At the end of golive, MCI does not respond even if bypass is enabled.
A crash might occur when disabling MCI if bypass is applied earlier.
Golive is blocked due to starting bypass while MCI is inactive.
After upgrading to 6.4.2.00, the first startup of an instance creates elements using duplicate UIDs in the configuration.

Minor defects and changes

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

The audit trail report does not include MDC and DDC retention values. Now, the fields are included (APAR PO09944).
Improved the online help. Added information about multi-relations workflow, model revision golive, index internals, and latest latency violations. Added more details to information about batch jobs, MCI bypass, MCI XML format, and conditions. Corrected tooltip text for Show uncomputed simulation elements, CPP > Case group, Highlight CPP attributes, and Archive sent messages. Also, the error This entry must be greater than or equal to 1 is now printed if the number of records is set to 0 in query definitions.
An unrecoverable error occurs during startup if a revision has an invalid PMML model (either the attachment is missing or it is invalid) (APAR PO09824).
If an error occurs during the sending of a notification, log message 0361 contains an invalid path to OCCM. Now, log message 0490 is listed after log message 0361. It contains the correct OCCM path along with the case action name and case UID, if available (APAR PO08111).
The Show on dashboard checkbox on the Administration tab does not toggle the display of Key Performance Indicator (KPI) tiles (APAR PO09794).
PMML scorecards that do not end in a newline character cannot be imported. For cards that can be imported, there is no notification that an import was successful. There is no warning that all the rules of the ruleset for which the scorecard is being imported will be overwritten by those that are parsed from the scorecard (APAR PO09852).
In the Outgoing channel configuration page, the Show references toolbar button displays a reference list with a nonexistent Case class reference.
External model reference items do not have a link to a corresponding external model definition.
When model profiling is copied, the output keeps the same name as the copy source.
The number of active FLI connections counter can turn negative when FLI threads hang while FLI is disabled and enabled again. This in turn can cause a wrong system time output (APAR PO09790).
The configuration form for collusion and index based evaluation case classes contains the settings Manual case creation and Highlight case alarms in queries. The settings apply only to regular case classes.
It is not possible to delete multiple outgoing channel configurations if at least one of them is of type HTTP. The API always responds with NO_PRIVILEGES and aborts the deletion after it encounters the HTTP channel configuration.
Enhanced the error logging for API requests, for example, interruptions. Now, log message 0459 is written by default in the system logs