Change log

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

Critical defects

The following critical defect was fixed:

  • A crash or data corruption can occur if asynchronous mode is enabled on MCI endpoints (APAR PO09359, PO09964).

Major defects and changes

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

  • When external models call systems that reply with the message ID in the response body that uses slightly different JSON formatting, the response is not recognized by IBM Safer Payments and the callout fails. The problem occurs even if, for example, the white spaces between JSON keys and values are different.
  • Unconsolidated alarms can cause the application to hang during shutdown.
  • In rare situations, a crash occurs with external model components after a remote EMC server is enabled or disabled.
  • A deadlock can occur if a simulation is running on a lower-level mandator when a mandator higher up in the subtree runs a golive (APAR PO09978).
  • PCI DSS-relevant event log message number 834 is not automatically enabled for audit logs on fresh installations.
  • The user interface might crash if an input attribute with categories is added while, at the same time, a compare revision is done.
  • A no privilege error is issued if a case moves to another nonexclusive working queue for which the user has no privileges from the My working queues page (APAR PO09485).
  • On Cluster > Interfaces > Inbound, the thread priority selection options are not limited by the respective thread priority limit in the system settings. An option to set a thread priority limit for Kafka endpoints is missing in the system settings. If the thread priority limit for MCI or KMI is lowered, the respective values of inbound endpoints are not updated.
  • Mergings cause direct disk access even if deferred writing is enabled.
  • Report generation jobs that use outgoing channel configurations mask values of encrypted attributes according to the starting user's privileges and ignore the masking setting of the outgoing channel configuration. Jobs that are not triggered by a user always mask values and also ignore the setting of the outgoing channel configuration (APAR PO08864).
  • If an empty cookie is sent in the HTTP header, it can cause incorrect responses.
  • The deletion of large bulk defined risk list entries is slow on the API instance (APAR PO09895).
  • If a table filter is activated, the table's vertical scrollbar overlaps the contents (APAR PO09825).
  • A crash can occur when rule generation data selection is saved multiple times (APAR PO09925).
  • A crash can occur during restoration because the case service is not stopped (APAR PO09950).
  • Rule generation creates too many threads, which cause real-time processing to stop for a few seconds (APAR PO09859).
  • A crash occurs if a data export is run after the EOD job and it contains a condition or column attribute that is owned by a mandator who ran a logical golive before the running of the EOD job (APAR PO09912).
  • A crash can occur if rule generation settings are saved while it is running (APAR PO09917).
  • An error message is logged by the donor of a restore if IBM Safer Payments is started with Python 3.x support and at least one Python script is uploaded. The error message ID is 0354 and the text states that a folder named __pycache__ is skipped for the transfer. Now, the folder is skipped but the error message no longer displays. The restore itself is not impacted.
  • If numerous case investigations exist, some cases do not have a working queue (APAR PO08747).
  • IBM Safer Payments closes the connection early when it receives a SHUT_WR TCP message on the MCI. This can prevent sending an MCI response. It happens mostly when MCI Bypass is enabled and active (APAR PO09918).
  • Stopping deferred writing in system configuration or during shutdown might lead to loss of data.
  • If you generate rules, and then click Explore all indicators, percentages in the Amount, Hit rate, and other columns are incorrectly rounded depending on the decimals of the attribute (APAR PO09951).
  • Changes that are made to certain fields of some revision elements are not shown in the compare revision and audit trail of the model revision.
  • If element generation threads are configured to be greater than one, rule generation results are not accurate, and might be different between multiple runs.
  • In rare situations, an element can be saved with a name that is already used, which invalidates the configuration (APAR PO09938).
  • In rare situations, a crash can occur after a golive when a query is started during the golive.
  • Rule actions in preprocessing rules can be defined but are never run (APAR PO08429).
  • An instance can hang if you stop a simulation that was started as workflow with rule designer enabled. Shut down is prevented.
  • A crash can occur if a case is opened whose masterdata uses a categorical attribute but the index node is invalid (APAR PO09931).
  • A generate report job can fail if it computes a fraud mark report that processes a record that is marked as fraud by a deleted user (APAR PO09967).
  • Potential security issues exist in some external statically linked server libraries. Updated Libcurl, librdkafka, libxml, opencv, lib, and zstd to the most current version.
  • During merging, recomputation messages are computed differently than during normal computation.
  • When a merging is recomputed, the MDC oldest URID on an attribute can be set to a value before the attribute is created. Queries then contain unexpected results. Also, the MDC oldest URI is then smaller than DDC oldest URID (APAR PO09756).
  • Logs do not show who sent the signal (APAR PO09958).
  • Multiple regolives that are run and queued at the same time might result in FLI errors and failed golives on remote instances (APAR PO09970).
  • Logs for simulation show the user name.
  • Realtime computation performance is slow if many outputs and mappings are processed (APAR PO09955, PO09959).
  • During golive, bypass is activated after deferred writing and jobs are stopped. However, stopping them can take time during which latencies can occur (APAR PO09956).
  • A crash can occur if a save request for a persistent connection outgoing channel configuration is sent without a connectionPoolPriorities field.
  • Primary URID and Primary Instance ID are not printed when the Outgoing Configuration Channel message is sent by a case action, and the message is not archived when delivery fails (APAR PO09949).
  • Updating a persistent outgoing configuration channel is slow.
  • If an instance's bypass setting is changed, the change is not applied (APAR PO09957).
  • An invalid HTTP response is returned if the simulation instance is different than the API instance and the response is larger than 3000 characters.
  • SSL settings to reject TLS 1.0 and TLS 1.1 connections are not enabled by default for MCI, ECI, and API.
  • During a logical golive, the instance status is set to waiting for interlock and stays this way until a structural golive is done. This also happens when interlock is disabled in system configuration (APAR PO09969, PO10007).
  • MCI, FLI, BDI, MQI, and KMI can be enabled while a maintenance function is running that requires them to be disabled (APAR PO09788).
  • If settings on Administration > System > Configuration are changed, some warning and error messages are not issued.
  • MCI responses of type JSON contain unnecessary white space.

Minor defects and changes

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

  • In the Output Attributes table, the meta attribute case class displays inconsistent values.
  • When a simulation is run without attributes that require simulation, the message simulation initializing is displayed. The simulation appears to be in progress when, in fact, it is finished.
  • If a master key is changed, the case class configuration is not written to disk even though case classes can use encrypted attributes in condition forms.
  • Improved the online help for Main Memory settings, MCI StatusResponse example, and Fraud marking reports. Added more content to several topics, for example, case types, internal model generation, outgoing channel configuration, and inbound endpoints. Improved user interface text about feedback. The language options in the user interface are now always listed in their own language (APAR PO09422).
  • If the SCI communication to a remote instance fails and thus does not prevent updating a revision while a remote analysis is running, the analysis is not stopped upon the revision update (APAR PO09927).
  • If space is limited in the user interface, multiselect dropdown fields sometimes do not display all options.