Change log

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

Critical defects

The following critical defects were fixed:

  • Changing the master key fails if the new key is a KMIP master key and it uses a certificate private key that is protected by a passphrase. The instance that is used to perform the master key change becomes detached. Other instances in the cluster get stuck in the state Changing master key: finalize (APAR PO10096).
  • Simulation order for final rules and preprocessing rules is different from the order in real-time computation (APAR PO10114).
  • On Administration > System > > Configuration > System > Deferred Writing, the Reduce DDC access for mergings checkbox is now cleared by default.
  • A crash might occur during golive if the golive tries to activate masterdata for use in extended masterdata queries and Administration > System > > Configuration > Misc > Enable configuration change journal is selected.

Major defects and changes

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

  • On numerous pages in the user interface, single select component dropdown values are cut off if they display at the bottom of the page. The same problem occurs for autocomplete dropdowns for condition forms and for color picker components (APAR PO09884, PO09853, PO09645).
  • On Investigation > Queries > Masterdata, values are not correctly rendered if one attribute is used with categories in two masterdata with different insertion conditions (APAR PO10041).
  • Status alarm indicators do not display a title if a tooltip is unavailable (APAR PO09575).
  • External queries that update encrypted masterdata block FLI (APAR PO10058).
  • A deadlock might occur if simultaneously a case that has reporting attributes and queries is opened and a golive is run.
  • There is no setting to prevent end-of-day jobs from running. Now, added an End of day (Eod) job checkbox on Administration > System > Configuration. If selected, end-of-day jobs are allowed to run. If cleared, they are prevented. The default is selected. Contact IBM Support before using.
  • On Model > Challenger > Rules, when a rule report without context is run, the All Rules page is displayed. Instead, the actual rule report page should be displayed. Also, if you navigate away from the Simulation Report page by clicking another menu entry, the All Rules page is displayed (APAR PO10070).
  • The digit and decimal group separators for numeric expressions are not correctly enforced. Also, the wildcard values are truncated on the user interface (APAR PO09999).
  • DDC files are not removed during golive after an element is deleted if the element already existed during startup.
  • Data synchronization is slow when it writes an audit trail for a large defined risk list.
  • Some HTTP requests are not producing log messages. The lack of log messages makes problem resolution difficult for IBM Support.
  • A crash might occur if multiple requests to copy a retired revision are made while a golive is running (APAR PO10077).
  • A deadlock might occur when a simulation rule report query is started. Then, before that is finished, a rule is deleted that has a conclusion or masterdata rule action (APAR PO10075).
  • Status alarm indicators display zero values (APAR PO10080).
  • During computations like golive, other computations like queries and simulation might pause while the instance tries to enter maintenance mode, even if the instance is not ready to enter maintenance mode. Now, the queries and simulations are paused only when the instance enters maintenance mode (APAR PO10085).
  • Simulation performance is slower than expected. Now, simulation performance is still slower than real-time performance in most situations, but it is improved, especially when using many elements.
  • Golives and end of day jobs are blocked while reporting queries are computed (APAR PO10043).
  • On Administration > Jobs > Settings > Export data jobs, if multiple mandators are selected on the Data Selection tab, duplicate attributes display on the Data output tab. The problem occurs if the selected mandators inherit attributes from the same parent mandator (APAR PO10048).
  • Attributes selected for inclusion in the data output of a data export job may be excluded from the export file (APAR PO10087).
  • Golives cannot proceed if other revisions are running rule generation (APAR PO10073).
  • When manually marking records as genuine or fraudulent from query results on Investigation > Queries > Queries, there is no control over which notifications are selectable. Now, notifications can be configured to be selectable by setting the new Available for manual fraud marking checkbox on Administration > External system integration > Notifications. The Trigger notifications on fraud marking role privilege on Administration > User management > Roles is also new. It controls the ability to trigger notifications.
  • Binary StatusRequests values in MCI that are non-zero are interpreted as StatusRequests. Now, only values of 1 are interpreted as StatusRequests.
  • A crash might occur if working queues are saved while they are computed (APAR PO10059).
  • When records are marked as fraud on Investigation > Queries > Queries, negative fraud values cannot be selected in Fraud value (APAR PO10083).
  • After startup, encrypted indexes are repaired even if the index is not damaged (APAR PO10103).
  • On Investigation > Investigation > Case search and case selection, a search is triggered with every keystroke that is entered in Search term. It causes numerous unnecessary server requests. Now, a search starts only when the newly added Case search icon (right triangle)(execute) icon is clicked or the Enter key is pressed. Auto refresh was added to the case search page. Whether auto refresh works depends on the System configuration > System > Page auto refresh > Investigation setting. Auto refresh on case search and case selection is done only when Case search icon (right triangle) is clicked. If a filter on one of the pages is changed, auto refresh stops until Case search icon (right triangle) is clicked again (APAR PO10100).
  • On Investigation > Investigation > Case search, the search does not respect the Maximum cases shown on selection table setting. It also takes longer than expected.
  • Broken data of encrypted masterdata after startup if encryption of the index attribute is getting enabled and no entry was added yet on the mastedata index. Additionally, there is broken data of attributes after startup, if the encryption of the attribute changed and if no record was loaded yet on the instance.
  • Added information about the Maximum session timeout field to the online help. It was missing. The field is located on Administration > System Configuration > Interfaces > Application Programming Interface.
  • On Model > [mandator revision] > Model components > PMML model component > PMML Model Import, the tooltip for the download icon is not formatted correctly.
  • On Model > Modeling > Analyses > Statistics, after visible columns are configured, the header of the Name column is empty.
  • On Investigation > Queries > Queries, for queries with empty results, False alarms per hit is incorrectly formatted (APAR PO09255).
  • Timestamps in the latency report files are stored in system timezone, but they should be stored in UTC+0 timezone. When the system timezone setting is not UTC +0, the latency timestamp in system internals is different from the system time of the same record in query output (APAR PO09334).
  • On Cluster > System monitoring > Settings > [instance] > Interfaces, users with read-only access cannot switch between the tabs in the Interfaces section (APAR PO10093).
  • In numerous places in the user interface, when a date is chosen in a calendar, the text is not localized with the user's language (APAR PO10104).
  • On Model > [model] > Profiling > Calendars, if Calendar Period is changed, for example from daily to weekly, calendar dates are then incorrectly calculated. After the instance is restarted, the calendar values are calculated correctly from that point forward.
  • Case action inputs are not read into the system after the instance is restarted twice (APAR PO09994).

Minor defects and changes

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

  • Updated Libcurl to version 8.2.1.
  • In numerous places where lists are defined in the user interface, after an output value is deleted, the condition values in other outputs in the list are corrupted (APAR PO10067).
  • A small latency spike occurs during the deferred writing cycle because of the time that is consumed for the deletion of the calendar period file for the rollover (APAR PO10082).
  • On Administration > System > Configuration > Interfaces > FastLink Interface, an error message for Receive timeout (seconds) is incorrectly issued.
  • Improved the tooltip text for the All connections checkbox and Connections from text box. They are located on Cluster > System monitoring > Settings > > [instance] > Interfaces > Message Command Interface and Cluster > System monitoring > Settings > > [instance] > Interfaces > Application Programming Interface.
  • Now, on Administration > System > Configuration > Interfaces > Application Programming Interface, the Session timeout and Maximum session timeout fields must be greater 60 seconds. Also, a warning is issued if they are set to a value between 60 and 300 seconds.
  • On Monitoring > Defined risk lists, the table contains two Mandator columns. It should contain a Mandator column and a Mandator UID column. The same defects also occur on Monitoring > Merchant Monitoring Rules and Monitoring > Index Based Evaluations.
  • On Model > [mandator] > Scoring engine > All Rules, the column headers are all UID. Now, they are Ruleset UID, Revision UID, and so on.
  • On Model > [mandator challenger] > Modeling > Simulation > Queries, the header contains the placeholder text, Simulation Queries {0}. The text was removed.
  • On Model > [mandator challenger] > Modeling > Rule Scoring > Rule Scoring Results, the plus icon in the toolbar is disabled.
  • Added information about FCD response formats to the online help. It was missing.
  • Added Log latencies also for FLI checkbox on Administration > System > Configuration > Misc > Log latency violation details. It controls whether latencies are logged for messages that are computed from FLI.
  • When a role is assigned to a user on Administration > User management > Accounts > [user account] > Mandator Privileges, log message 370 is not written. It should be.
  • HTML formatting tags are sometimes included in golive messages.
  • On Cluster > System monitoring > Settings, added a Heartbeat Debugging Status column to the list of instances.
  • On Model > [mandator] > Data Model > Mappings, for mapping messages of type Fcd, the tooltip for Start length pairs contains typos.
  • On Model > [mandator] > Profiling > Formulas, a vague error message (_FORMULA_DIVISION_BY_CONSTANT_ZERO_) displays if an expression is defined that divides by zero. Now, the error message is Division by constant of zero is not allowed.