Change log
IBM® Safer Payments 6.6.0.04 includes defect fixes, changes, Known Issues, and APARs.
Critical defects
The following critical defects were fixed:
- Buffer overflow and uncontrolled memory allocation errors occur in MCI when remote systems send arbitrary large requests.
Major defects and changes
The following major defects were fixed and major changes were made:
- A crash might occur when a challenger revision is deleted while a random forest model generation is running (APAR PO09971).
- If you change Fastlink Interface (threads) on , the system must be restarted. Then, synchronization issues occur between instances.
- An error message is printed when messages are computed and then the computation stops. The
problem occurs after a counter is copied, and the original counter uses a peer index with
targetsequence and the new counter uses an index to another nonpeer index. The problem can also occur when events, mergings, patterns, precedents, and profiles are copied in the same way. Also, index queries might return incorrect results after they are copied from a query that uses a peer index withtargetsequence (APAR PO10136). - In rare situations, a crash might occur when a table that shows rules or conclusions is opened (Known Issue DT391564).
- When MCI bypass is deactivated, a long wait time occurs until the instance can process new MCI messages again.
- When a revision is loaded by using a configuration migration script, a reference error might occur on a remote instance. Then, the revision is not properly loaded. The problem occurs if the revision contains multiple new elements that depend on each other.
- When a golive is running and you add new elements or users before it finishes, the remote instances might be invalidated when they run the golive. Also, external mappings are added automatically without a message in the golive report. Now, the golive report includes a message for added external mappings (APAR PO10141).
- When extended authentication is enabled and a new user logs in, the login page is displayed rather than the one-time password (OTP) page (Known Issue DT277055).
- On , when you run a BDI Load file job with Re-create interval index enabled, the indexes on remote instances are not populated after the job finishes (APAR PO10063).
- A crash might occur due to a thread leak in the Kafka Message Interface.
- On , select an item and click Explore all indicators. Data selection conditions and rule generation conditions are not correctly applied. Therefore, data for other items is included in the selected item (Known Issue DT380010).
- Improved performance for rule reports and rule queries. The improvement is especially evident when a ruleset contains many rules whose conditions are not met (Known Issue DT379143).
- Added the new maintenance function. If an error occurs while a re-create index job is running, you can now exit the job or continue. Use the Cancel or continue recreate index maintenance function only under the advice of IBM Support.
- After rule generation is started, the error Only challenger revisions can be simulated might be issued. The error continues to display even after you leave the page and also after the process stops or is disabled. The same problem might also occur when the retention settings report is started.
- When you create a condition in the user interface, for example, in a query, the message
There is no corresponding category defined for the selected attribute might display.
The problem occurs if the selected attribute has categories and the expression uses single wildcard
characters, for example,
*or?(APAR PO09835). - MS SQL statements print with incorrect enclosing characters for table and column names (Known Issue DT381678).
- A crash might occur during the end-of-day job after the
systemtimemetaattribute is resized. The problem occurs when logical golives are enabled and rules with performance report are defined (APAR PO10065). - On case investigations, for example, , only masterdata cards that are linked to one index display content. Masterdata cards that are linked to multiple indexes do not display content (Known Issue DT386110).
- When golive is run, the oldest URID in the index is set to a wrong value if the index was rebuilt (Known Issue DT389262).
- SQL statements for reporting attributes attempt to insert masked numeric attributes into the VALUE_NUMERIC column.
- SQL DELETE statements that are created for cases through the relational data interface (RDI) use invalid syntax.
- Db2 SQL statements that are output through the relational data interface (RDI) wrap table and column names in single quotation marks. As of Db2 version 11, single quotation marks are no longer supported. Now, table and column names are wrapped in double quotation marks.
- A crash might occur when XML files that contain the string
POSTare loaded by using a BDI load file job. The same problem occurs with JSON files that start with the stringPOST(Known Issue DT378504). - Updated OpenSSL to 1.1.1y. Known potential security issues exist in 1.1.1x.
- After a golive finishes, memory usage increases more than expected if is enabled (Known Issue DT387182).
- On case investigations, for example, , if you filter or sort an index query, the wrong rows are highlighted in the query results (Known Issue DT389546).
- When you apply a filter in a table and then click a column title to sort the table by that column's values, the sort does not work (Known Issue DT389548).
Minor defects and changes
The following minor defects were fixed and minor changes were made:
- On
, variables in the tooltips for several fields display as
{0},{1}, and{2}rather than correct values. - On
, hexadecimal query parameters display incorrectly on the
results page. For example, a value like
1111123412341234might display as???4?4?4. Also, sometimes the results page is not displayed. - On , when you click Import entries from a file, the Add condition icon under is sometimes missing (APAR PO10172).
- On , error text for the option no encoded category selected is missing.
- On , Session countdown (seconds) does not allow a zero value. Also, if Notice (seconds) is set to zero, the user interface stops responding (APAR PO10147).
- On , tabs for reminders display on some simulation analysis result pages, for example, rule overlap. Now, the tabs were removed.
- On , click Download IBM Safer Payments configuration but then do not select an instance. An error is displayed rather than a statement that the instance is missing. Now, the current instance is used as the default if no instance is selected.
- On , the REVISION_NUMBER field is missing from the RULESFIRED table in the online help.
- On , open a case that was originally created by using manual case creation. Log message 744 is printed in the logs. It is printed every time that the case is opened (APAR PO10177).
- On , an error occurs if a noninteger value is entered in Buffer size (GB).
- On , decimal values cannot be entered in Reload wait factor (times). The field accepts only integer values. The same problem occurs with Remote golive wait factor (times), which is located on .
- ITEM_NOT_FOUND error messages do not provide sufficient information for debugging. For example, the item that is missing is not provided. Now, many ITEM_NOT_FOUND error messages were improved.
- If the Google Chrome browser is used and you view tables, the table height is too large by half a row. The problem occurs if you click Fit to screen and then later reduce the value in .
- In tables where a more icon might display, the icon is hidden if the cell is too narrow for the content. The more icon might appear in the Comment column on . It might also appear in the table if Generated conditions as popup is enabled (Known Issue DT389549).