Title: Oldest DDC values not shown in Data Caches Internals when deferred writing cycle has yet to commit Description: When transactions are loaded and deferred writing is enabled, if the deferred writing cycle has yet to commit to DDC, the DDC Oldest timestamp in System Internals > Data Caches Internals is shown as empty. Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT452407 === END OF ISSUE === Title: Numeric attributes with null values and "Amount" formatting do not show the correct empty value in the query results. Description: When a numeric attribute has "Amount" formatting applied, and it shows up in a query result with null values, the UI displays these fields as empty or blank instead of the (0) value. Workaround: The "Decimals" formatting can be used instead. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT452081 === END OF ISSUE === Title: Incorrect form validation for SMTP Notification Description: When working with a Notification configured for an SMTP Outbound Connection Channel, "Save" will fail when 'Recipient address' is set to 'variable from meta attribute' and 'Constant email "to" address' is blank. Workaround: Enter a placeholder email address in the 'Constant email "to" address' field to allow the form to save. The system will correctly ignore this email address if 'Recipient address' is set to 'variable from meta attribute'. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT451731 === END OF ISSUE === Title: Get Simulation Status API request can cause a crash in rare situations Description: An automated API request to get simulation status and progress can cause a crash if it arrives at the exact same time that analysis is starting up. Workaround: This issue can only occur if rules are enabled for analysis. It can be made less likely to occur by setting the "Analyses" field in "Page Auto Refresh" settings (Administration tab > system configuration > system) to a large number so that the API request is sent less frequently. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT451269 === END OF ISSUE === Title: The remote instance can be deadlocked if it simulates rule actions with masterdata and the rule gets updated Description: When the remote instance is simulating rule actions with masterdata and the same rule gets updated on the API instance, this remote instance can be deadlocked. Workaround: Disable the simulation manually before updating the rule. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT450673 === END OF ISSUE === Title: Large numeric values from AVRO messages are rounded, causing loss of precision. Description: When consuming AVRO messages with a large numeric value (more than 6 digits), the value is being rounded instead of preserving the expected precision (for example, 1,234,567.89 is converted to 1,234,570.00). Workaround: To preserve precision, convert the large numeric attribute to a 'string' type before transmitting the message via Kafka. The schema must also be updated to define this attribute as a string type. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT450670 === END OF ISSUE === Title: Batch jobs can get stuck in "Running" state if a crash occurs or BDI is switched. Description: A job remains stuck in the "Running" status if the node executing it crashes. The same issue occurs when moving the BDI Interface while a job is running. Attempting to resume the job on a different node fails, the job remains stuck, cannot be stopped, and cannot be executed again on another instance. Workaround: Switching BDI - Please stop the job, switch BDI to another instance, then resume the job.Crashed Node - Please restore the instance, the job will appear as "Interrupted", and can be resumed. Status: Open Affected Version: 6.8.X Fixed Available: No fixed available Known Issue ID: DT450406 === END OF ISSUE === Title: Revision cannot be taken over when FLI is buffered and a remote simulation instance is set. Description: If a challenger revision has simulation set to a remote instance and the FLI is experiencing buffering, takeover of the revision does not occur until the FLI buffer is processed. This causes the revision mode to be stuck on View, despite having the takeover be processed on the API instance and blocks any further updates to the revision, as the user who had ownership before cannot make any changes either. Workaround: Set simulation instance of the revision to the API instance before doing the takeover or wait for the FLI buffer to clear. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT450024 === END OF ISSUE === Title: Deadlock while removing a user and modify working queues. Description: Removing users and modifying working queues can lead to a deadlock. Workaround: NA Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT450014 === END OF ISSUE === Title: MDC records are not trimmed properly when retention by time is enabled. Description: A miscalculation occurs during the trimming of records which should be outside the MDC range, resulting in values for the attribute remaining in the MDC despite being out of range. The records will still be trimmed when they hit the DDC retention time and will still be overwritten once the MDC is full. This issue can lead to unexpected counter calculations. This issue affects version 6.7 or higher. Workaround: To trim attributes which should not be persisted, have the DDC retention be the cutoff. Otherwise, no workaround exists. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT449680 === END OF ISSUE === Title: Simulation with server time absolute can include one record out of range Description: Simulation with server time absolute can include one record out of range Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT449424 === END OF ISSUE === Title: Some attributes enabled for simulation may not be simulated Description: Given two rules, a rule A that has an input attribute in a condition and an output attribute in a conclusion, and another rule B has that same output attribute in condition, and rule A has a lower UID than rule B. If rule B is enabled for simulation analysis but rule A is not, then the input attribute will not be included in simulation. Workaround: Enable all rules for simulation that include the attribute as a conclusion and have a lower UID than rule B Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT448789 === END OF ISSUE === Title: Simulation report does not do the same checks as Golive report for PMML models. Description: There are a series of checks done on PMML models meant to be simulated to ensure that simulation can safely proceed (for example, checking that the PMML file is present). However, these checks are not functioning properly since 6.7.0.00. Workaround: If you have not run into this problem and wish to be extra cautious: Run a golive report immediately following a PMML model upload and save. If there's no error there then simulation can be attempted. If there is, re-upload PMML and repeat.If you have already run into this problem: the revision can be copied and the valid PMML model can be re-uploaded. A restart of the instance is required eventually in order to free the used simulation memory. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT448728 === END OF ISSUE === Title: [Internal Random Forest] Status of model generation is incorrectly shown on UI after user logs out (on versions 6.6 and lower) Description: When running model generation, then if the user who is running the model generation logs out and logs back in, then the model generation status shown on the UI is incorrect. The model generation page will show that model generation has not started, even though it is still running on the backend. The issue happens both when manually logging out and logging back in or letting session expire and logging back in. Workaround: You can either let the model generation finish, or manually stop it by sending an API request. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT448395 === END OF ISSUE === Title: Rule analysis ignores records where the meta attribute timestamp is empty. Description: Records without a value for the meta attribute timestamp are ignored during rule analysis, and the results are executed without including these records. Workaround: NA Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT447827 === END OF ISSUE === Title: Attempting to cancel a golive report or revert a revision to a challenger during maintenance mode can result in forced shutdown(s) of remote instance(s). Description: After starting a golive, then if the golive is blocked by another process, and the user attempts to cancel the golive (by either going to the Golive report page and hitting Cancel, or by going to the Revision general page and hitting Revert to challenger), then there is a small chance to synchronize the revision with an unexpected status to remote instances, causing the remote golive to fail later.In general it is ok to cancel a golive after generating the golive report. However, once the golive is confirmed/begun, please avoid canceling it or reverting the revision back to a challenger. Workaround: A golive can be blocked by other processes occurring on the system, such as interlock due to a restore, synchronization, or other user activity that uses maintenance mode. This is normal for some time, but if you suspect a system hang, please reach out to IBM Support. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT446628 === END OF ISSUE === Title: Case Action - Preview pane does not update if 'Attach data' rows are added or removed. Description: Under Case Investigation, when working on a Case if you add or remove rows from Query results (Add to Case Action), subsequent edits on the Case Action's "Attach data" table, such as deleting or adding a row does not show on Preview. In short, the Preview does not update after toggling between Edit and Preview if you change the attached data. Workaround: Press spacebar anywhere in the "Edit" pane under "Message" body section. Then press [Preview] to see changes. Note, if you are using a case action with a 'simplified view for investigators' option enabled (meaning there is no "Message" body editable to add a space), you will have to press "Reset all fields" under Edit, then press Preview to see changes. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT446268 === END OF ISSUE === Title: Fatal error may occur when executing a simulation query when active connections are present. Description: [SP 6.7, SP 6.8] When running simulation that has a data selection for time absolute and has active MCI, BDI, or FLI connections, in rare cases, running a simulation query with option time absolute matching the simulation's data range can result in a fatal error that invalidates the execution of the simulation query. Workaround: Re-run the query, as the probabilities of running into this issue are too low, or you can use records absolute option instead of time absolute. Status: Open Affected Version: 6.7.0;6.8.X Fixed Available: No fixed available Known Issue ID: DT446142 === END OF ISSUE === Title: Changing attribute of masterdata to a different data type can invalidate the API instance during golive Description: Changing the attribute of masterdata to a different data type can invalidate the API instance during golive, if this masterdata is set by rule action(s) in submandator(s). Workaround: Delete all rule actions that set this masterdata before making the change. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT446056 === END OF ISSUE === Title: Multi-delete of revision elements referenced in export job will generate backtrace. Description: Attempting to multi-delete revision elements that are referenced in an export job will generate a backtrace. Workaround: Delete revision items individually, or remove revision elements that are going to be deleted from any jobs where they might be referenced (use the "show references" button on the element). Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT446053 === END OF ISSUE === Title: The preview in case actions shows wrong data if the attribute is not displayed in the query table when adding transactions. Description: In a case, when adding more than one transactions from a query result table to case action and the attribute is disabled for the table column, the data in the case action preview is only taken from first row for that attribute, so the data is wrong for the other rows. Workaround: N/A Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT445942 === END OF ISSUE === Title: Missed Case Report timestamps are always shown in the GMT+0 time zone. Description: The timestamps in the Missed Case Report table do not reflect the user's timezone offset and are always displayed in GMT+0. This can lead to inconsistencies between case timestamps and may confuse users. Workaround: NA Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT444810 === END OF ISSUE === Title: UI shouldn't allow changing the ID of an existing instance Description: The instance ID is currently editable on the UI, which should be disallowed. Changing the ID of an existing instance in a multi-instances cluster can cause FLI synchronization problem. Workaround: No workaround available Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT444447 === END OF ISSUE === Title: Numeric reporting attribute is set to 0 if it is empty Description: A default value of 0 is set to the reporting attribute in numeric type, if this attribute is empty in the transaction that creates the case. Workaround: No workaround available Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT443916 === END OF ISSUE === Title: Selecting the table header filter text drags the column instead of selecting the text Description: Trying to select the text in a table header's filter field causes the column to be dragged instead of allowing the user to select the text. Workaround: Text can be selected by holding shift and pressing the arrow keys. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT443441 === END OF ISSUE === Title: The context action table is not being selected for the Rule Report. Description: When running a Run Rule Report from the Simulation page or executing a Rule Report on rules, the report is generated, but the context actions are not selectable on the query result page. Workaround: Executing the rule report query from Simulation -> queries page, then the context actions are selectable. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT443439 === END OF ISSUE === Title: Changes to a user are not synchronized to remote instances in certain cases Description: When encryption is enabled, if a user logs in directly on the Defined risk list entries page, or refreshes the Defined risk list entries page, it can cause a JSON error in the user preferences which can cause the user file for that user to not be synchronized to other instances during the next login session. Workaround: The user with the affected file should login, and open the Defined risk list entries page again, then select a defined risk list from the dropdown.The user should then go to another page and then log out and log back in.After this, the preferences should be rewritten and synchronized correctly. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT443237 === END OF ISSUE === Title: The lastActionOn value can be incorrect on some instances if a case update is received before the original case creation Description: When an Instance creates a case, it gets synchronized to the remote instances. Updates to the case are also synchronized to the remote instances, and may come from a different instance than the case was created on. If the case update arrives on an instance before the case creation update then the lastActionOn timestamp can be incorrect. For example, if a case is created on instance 2, and gets synchronized to API instance 1, and then that case is updated on instance 1 and that update is synchronized from instance 1 to instance 3 before the case creation update has been synchronized from instance 2 to instance 3, then the lastActionOn timestamp will be incorrect on instance 3. Workaround: Performing any action which writes a Case update to the FLI (for example an external query or saving the memo), would fix the lastActionOn timestamp. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT443173 === END OF ISSUE === Title: ICCM includes journal entry for each user login or logout Description: For each user login, an entry is created in the configuration change journal because the user account is saved with a new login timestamp on the source system. Workaround: No workaround available Status: Closed Affected Version: 6.5.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT442941 === END OF ISSUE === Title: Importing a revision change can fail when revisions created before 6.5 are involved on both clusters Description: When External model mappings (EMMs) for the same attribute have different UIDs on source and target, every occurrence of EMMs and hence their UIDs in the configuration change journals would cause errors when importing the journal into the target cluster (DUPLICATE_MAPPING or ITEM_NOT_FOUND).EMMs may have different UIDs for multiple reasons, including model revisions which were created in pre-6.5 versions, or imports from configuration journals that were written with a pre-July 2024 fixpack version of Safer Payments Workaround: If you run into this problem, please get in touch with Support. With the help of the Support team, the configuration journal can be manually edited to fix the issue. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT442616 === END OF ISSUE === Title: Download of revision control pages (Audit trail, Compare revisions) isn't possible Description: There is no way to save the revision audit trail page in order to have an external record of the changes made in a revision. When trying to print the page to save it as a PDF then it only shows a small amount of the full audit trail. Workaround: Adjustments can be made in the browser to adjust the viewable area before printing to PDF, and multiple PDFs can be saved, however the formatting is not ideal. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT440640 === END OF ISSUE === Title: Multiple delete requests of a counter may lead to an instance crash Description: If a user sends multiple delete requests of the same counter in a short period of time, the system might crash. This is possible if the user refreshes the page between deletes or due to a UI defect when deleting a counter using the table context actions. Workaround: Users should not refresh the page while deleting counters. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT439938 === END OF ISSUE === Title: Masterdata Relationship - Crash possible when purging outdated nodes during end-of-day job. Description: If deferred writing is enabled, a crash may occur during the end of day job when a large number of outdated nodes are purged along with relationship masterdata. Workaround: Disable deferred writing before EOD. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT439907 === END OF ISSUE === Title: Unconsolidated Alarms during restore can cause instance to hang at shutdown requested. Description:  When an alarm is created (ie. rule triggered) it is added to the unconsolidated alarms list. It is then the responsibility of the case scheduler to remove it from the alarms list and then either create a case or aggregate it into an existing case. However, if a restore happens while this unconsolidated list has alarms, the restore signal will interrupt the case scheduler. The alarms will stop being consolidated and the shutdown hangs. Workaround: Don't use as primary instance the instance that will be restored (Recipient). If you do, confirm that the unconsolidated alarms is 0 in the System internals before starting a restore. Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.11, 6.6.0.09, 6.7.0.05, 6.8.0.02, 6.9.0.00 Known Issue ID: DT439484 === END OF ISSUE === Title: API or MCI could deactivate in unique situations on certain machines. Description: If API threads are being created and killed in a short time in massive amounts the API or MCI could deactivate, and if SSL is enabled, the below error is logged:" E 0025 Error in creating API socket for [IP:PORT], error: use_private_key_file: malloc failure". Note that it is still an issue in non-SSL implementations without this log. Workaround: N/A Status: Closed Affected Version: 6.7.0 Fixed Available: 6.5.0.11, 6.6.0.09, 6.7.0.05, 6.8.0.02, 6.9.0.00 Known Issue ID: DT439478 === END OF ISSUE === Title: Clicking a toolbar action may move focus to the button instead of triggering the action Description: In Model > Revision > Scoring Engine > All Rules OR Model > Revision > Postprocessing > Final rules, when focus is in the expression box of a condition or conclusion, clicking on the toolbar actions Save, Delete, Copy, Help, or "Show complete audit trail" buttons only changes the focus, and a further click is needed to execute the action. Workaround: Click outside the expression box before clicking the toolbar actions button or use shortcut keys (e.g Ctrl-S for Save) Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT439452 === END OF ISSUE === Title: [TLS | SSL] Unable to set TLSv1.3 ciphersuites Description: When setting a custom SSL cipher list (under System > Configuration > Misc) if a TLS v1.3 ciphersuite is added to the list then an error will appear in the logs ("E 0519 Can not set custom SSL cipher list") and the cipher list will not be updated Workaround: TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256, and TLS_AES_128_GCM_SHA256 are enabled by default, so if wanting to use these ciphersuites they don't need to be added to the cipher list. No workarounds exist for setting other TLSv1.3 ciphersuites. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT439165 === END OF ISSUE === Title: Data loss can occur after deferred writing was interrupted and a transaction is still being processed. Description: Data loss may occur if a high-latency transaction is still being processed after deferred writing was interrupted. This issue can arise during shutdown. Workaround: In order to minimize the chances of the problem occurring, all incoming interfaces should be disabled before shutting down the instance. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT438914 === END OF ISSUE === Title: JSON parsing error while running a query that includes Highlighted CPP attribute Description: When the "Highlighted CPP attribute" is enabled in a query definition and a CPP attribute is added to the columns, executing the query results in a JSON error. This issue can also occur when opening a case that has multiple CPPs defined for the same case group, especially if this query is associated with that case. Workaround: Disable Highlighted CPP attribute in query definition. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT438715 === END OF ISSUE === Title: [Simulation | Indexes] Computing index in simulation can cause violations in the index Description: When you have made index changes (for example changing the minimum lifetime) in a challenger and then run a simulation which includes that index, then it can corrupt the index structure and introduce double entries. These structure violations will be automatically identified and repaired on the next startup when the Check indexes on startup option in System Configuration is enabled. Workaround: Don't perform simulations which include the index in the Simulation report. If you need to simulate other changes in a challenger with index changes, then try and revert the index changes, and make the index changes in a separate revision. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.5.0.11, 6.6.0.09, 6.7.0.05, 6.8.0.02, 6.9.0.00 Known Issue ID: DT437904 === END OF ISSUE === Title: The condition returns incorrect results when certain operators are used with an expression that contains the decimal character. Description: When using the operators 'starts with', 'ends with', 'contains', or 'prefix equal to,' the condition does not compute correctly when a decimal character is included in the expression. This occurs because the decimal values are truncated, leading to unexpected results. Workaround: Avoid using the decimal character in the expression with these operators. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT436599 === END OF ISSUE === Title: Fatal error on simulation page after deleting attributes used in Internal Random Forest Description: After an Internal Random Forest is deleted, and the input attributes used by the Internal Random Forest are also deleted, then the user will receive a fatal error when they navigate to the Simulation, Analysis, Random forest, or Rule generator pages. Workaround: The file can be edited directly to fix the issue, please contact IBM support for instructions if necessary Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT436055 === END OF ISSUE === Title: Attributes referenced in a submandator modeling attribute settings can cause shutdown during golive of upper mandator. Description: Attributes from upper mandators, referenced by simulation modeling attribute settings in submandators, are not handled correctly when deleted. This leads to the error ATTRIBUTE_NOT_FOUND at the end of golive in the upper mandator, which forcibly shuts the instance down. Workaround: Delete modeling attribute settings in the sub mandator before golive to avoid it referencing attributes from other revisions, which might be deleted later.Disable instead of delete the attributes element when it is no longer needed. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.7.0.03;6.8.0.01 Known Issue ID: DT435837 === END OF ISSUE === Title: Emails will fail to be sent for SAIs (and a fatal error will be printed in the log) if encryption is disabled Description: When encryption is disabled and the option to send an email for an SAI is enabled, then the emails will not be able to be sent, and a F 0483 fatal error will be printed in the logs. Workaround: Disable the option to send emails for SAI or enable encryption. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT435755 === END OF ISSUE === Title: Crash can occur during a second Simulation when using Absolute Timestamps in data selection Description: When running for a second time a simulation with Absolute Timestamp for data selection, having the "To" range for the data selection in the future, can lead to potential discrepancies with the data range, and cause the simulation to crash the instance. Workaround: Set the "To" to a date in the past, use Record Absolute in the data selection, or Disable simulation before re-running it. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT435722 === END OF ISSUE === Title: Simulation can get stuck if API request disableSimulation is interrupted. Description: In some situations, such as disabling/enabling API endpoint, an internal thread could get interrupted leading to a stuck revision and simulation. The user cannot make changes to the revision (receives error message), cannot try stopping the simulation again (stop icon is greyed out), and cannot restart the simulation (receives error message). Workaround: Copy the revision and run simulation. To clear the memory from memory control page, restart the instance. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT435686 === END OF ISSUE === Title: MasterKey change can fail in rare cases Description: When performing a MasterKey change, with the setting "Reuse keys" disabled, in rare cases the Masterkey change can fail, corrupting the data in DDC for encrypted attributes. If you have ran into this problem reach out to IBM support. Workaround: Enable "Reuse keys" under Administration > System Configuration > Encryption for the duration of the key change . Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.X Known Issue ID: DT435179 === END OF ISSUE === Title: First Deferred Writing cycle after EOD can cause latencies due to index shadow reallocation. Description: When indexes are purged during End of Day job, latencies could be experienced on Index Computation related operations until the first deferred writing cycle finishes. After the first write cycle after EOD completes the latencies go away until the next EOD. Workaround: No workaround available Status: Closed Affected Version: 6.5.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT435169 === END OF ISSUE === Title: Editing model component after Internal Random Forest (IRF) model generation causes simulations to get stuck. Description: After generating a Internal random forest (IRF) model and saving the model, navigating to Scoring Engine > Model Components, and pressing save on the generated model causes the model to get "corrupted". This leads to problems when running simulation, as the page gets "stuck" on simulation and the user cannot make any changes to the revision. Workaround: Copy revision if simulation is "stuck", re-generate IRF model, and don't edit the model in Scoring Engine > Model Components.If needing to change fields of the model (e.g. priority): modify the save request to include correct categoricDataFields, and uniqueCategories values. Please contact IBM Support for assistance on how to do this. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT435020 === END OF ISSUE === Title: Typing spaces in a table column filter can sometimes change the sorting direction for rows Description: If the columns don't fit on the screen, it happens with the columns on the right that were hidden when the page was opened. The problem occurs when you scroll the horizontal scrollbar to these columns and type spaces in their filter field. Workaround: N/A Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT434600 === END OF ISSUE === Title: [PMML Model] Tree models that contain single-node trees are not parsed properly, leading to incorrect scoring Description: Tree models (PMML Random forests and PMML boosted trees) that contain single-node trees do not evaluate the single node trees, leading to incorrect scoring. Workaround: Avoid having single-node trees in the model Status: Closed Affected Version: 6.6.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT434544 === END OF ISSUE === Title: Multi-delete of revision elements creates many FLI messages. Description: No description available Workaround: Limit the number of elements you delete at any one time. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT433604 === END OF ISSUE === Title: There is no stop button for Group by Query and Reporting Query. Description: Currently there is no [stop] button to stop the execution of a Group by query or Reporting query once a user has started it. Workaround: Group by queries and Reporting queries can be stopped by deleting them if necessary. Users can make a copy of the reporting query or group by prior to deleting it to preserve query settings, but the table of existing results will not be copied over. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT433471 === END OF ISSUE === Title: Content of Audit Trail expandable tables is not copyable Description: When the user navigates to Model > Revision Control> Audit Trail and tries to copy the content of the tables, that is not possible. Workaround: User has to start the hold and drag to select from the title of the audit trail form..Then they have to click ctrl + c before letting go of the hold. Status: Closed Affected Version: 6.3.0 Fixed Available: 6.8.0.01 Known Issue ID: DT433250 === END OF ISSUE === Title: Empty values for masterdata show up in extended masterdata query results but not in normal masterdata query Description:  When sending in transactions that don't have any value for masterdata attribute(s), the internal cold storage is updated with the empty value, so that these empty values show up when doing an extended masterdata query. Regular masterdata attributes aren't updated when the input attribute is empty, and so regular masterdata queries will not show the empty values, and will still show the expected masterdata values. Workaround: N/A Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT431956 === END OF ISSUE === Title: Simulating with an invalid PMML model can result in a stuck simulation. Description: If you upload an invalid PMML model (for example, a model with 2 different fields with the same name and different datatypes), then copy the revision and try and run the simulation, then the simulation can get stuck (you will be unable to stop it or start a new simulation). This is also possible if there is any issue opening the PMML, as well as any other error during the simulation, for example, exhausting the index. Workaround: You should not upload invalid PMML models. If you have already run into this problem, then the revision can be copied and the PMML model can be removed, or replaced with a valid PMML model, and then simulation can be done normally. A restart of the instance is required in order to free the simulation memory. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT431949 === END OF ISSUE === Title: Conditions containing backslashes return incorrect results Description: When expressions in conditions contain backslashes \ the API request is crafted with extra \ characters, leading to incorrect results when trying to match a transaction value with a \ (for example in query results, or in rules). Workaround: None available Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT431944 === END OF ISSUE === Title: When a Status Alarm Indicator fails to open the /proc/meminfo file, Safer Payments logs a fatal error in system logs Description:  When a SAI fails to open /proc/meminfo file, a fatal error is incorrectly log (it should be a normal error or warning), and such log doesn't mention the reason why this file failed to be opened. Workaround: If the file has the right permissions and hasn't been moved from that location, in the next SAI's cycle SP should be able to gather the information from it and update the SAI seamlessly. If this is not the case, please contact the Safer Payments support team for further assistance. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT426613 === END OF ISSUE === Title: Safer Payments is missing validation of the client certificate path for Outgoing Channel Configurations (OCCs) Description: When the user selects the Use client certificate option for an OCC, but the certificate file doesn't exist at the path specified, the OCC message is still sent out, which can result in HTTP 401 errors, without any indication to the user that the certificate wasn't found. Workaround: NA Status: Closed Affected Version: 6.7.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT425655 === END OF ISSUE === Title: Expression error causes Case Selection page to be stuck loading and execute button to be greyed out Description: If an invalid case selection condition is specified, i.e. a condition on a numeric attribute with no value specified in its expression, Safer Payments reports an error about the expression after clicking the execution button. The execution button is then greyed out and the user is no longer able to execute Case Selection. Workaround: Reset user preferences from the "My account" page. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT425162 === END OF ISSUE === Title: Rule Action may add empty string entries to Defined Risk Lists and those entries will not synchronize across instances. Description: Rule Action may add an empty value entry to a Defined Risk List with a text input attribute when that input attribute is empty on the transaction triggering the rule. The empty entry will not synchronize across instances, possibly causing different computation across instances. Workaround: Make sure that any rule with a rule action that adds an entry to a Defined Risk List has a condition that verifies that the input attribute is not empty. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT425160 === END OF ISSUE === Title: [FLI] async mode stops handling new connections after ignoring one Description: FLI only allows connections from peer instances. After ignoring a connection from outside, it stops accepting new incoming connections from peers. Workaround: Restart FLI. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.7.0.03;6.8.X Known Issue ID: DT425084 === END OF ISSUE === Title: A crash may occur when parsing a malformed HTTP header in MCI messages Description: A malformed request sent to MCI can cause a null pointer exception, which can potentially end with a crash. Workaround: No workaround available Status: Closed Affected Version: 6.7.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT424773 === END OF ISSUE === Title: [importRevisionChanges] ATTRIBUTE_IN_USE when deleting a previously referenced attribute Description: When a new challenger deletes a previously referenced attribute, the API request first tries to delete the element, before editing the previous references inside the model, therefore the API call falls with ATTRIBUTE_IN_USE. Workaround: N/A Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT424705 === END OF ISSUE === Title: [ICCM] Python upload module ID can conflict in target system Description: When trying to import python modules, with journaling enabled, the ID of the python module can be different in the source and target system. Workaround: Resynchronize them by editing the mandator configuration files. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.5.0.09;6.6.0.07;6.7.0.03;6.8.X Known Issue ID: DT424704 === END OF ISSUE === Title: Persistent outgoing connections should be closed during the shutdown Description: Persistent OCC connections should be closed during the shutdown process. Workaround: No workaround available Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT424503 === END OF ISSUE === Title: Simulation - Priming not copying enough records that leads to incorrect results. Description: [6.7] When a simulation is run that does not include the most recent transactions in the system, input attributes might not be fully primed from production data caches. Simulation results are then incorrect. The problem occurs only when the simulation data selection partially overlaps with the input's production MDC. Some records must be primed from the production MDC and some from the production DDC. Workaround: N/A Status: Closed Affected Version: 6.7.0 Fixed Available: 6.7.0.02 Known Issue ID: DT424346 === END OF ISSUE === Title: Simulation - Analysis of dependent rules could lead to different results. Description: [6.7] When rules that depend on each other are analyzed, simulation might not include all required elements. Simulation results are then wrong. A rule depends on another rule if it sets an attribute in its conclusions that the other rule uses in its conditions. Workaround: N/A Status: Closed Affected Version: 6.7.0 Fixed Available: 6.7.0.02 Known Issue ID: DT424345 === END OF ISSUE === Title: Simulation - Attributes affected by multiple rules could be incomplete. Description: [6.7] Model simulation does not properly recognize attributes affected by multiple rules. The problem occurs when some but not all of the rules require simulation. This could mean for example that within simulation, when two rules determine an output value and only one rule is simulated, the output has incomplete values, making the simulation as a whole have incorrect results. Workaround: N/A Status: Closed Affected Version: 6.7.0 Fixed Available: 6.7.0.03;6.8.X Known Issue ID: DT424344 === END OF ISSUE === Title: The filter text field for tables is draggable on the UI Description: [SP 6.4.2.07, SP 6.3.1.08, SP 6.7.0.00, SP 6.5.0.05, SP 6.6.0.03] When moving the cursor to select the text in a table filter field, this filter field is temporarily moved with the cursor and the text in this field is not selectable. Workaround: The text can be highlighted using other methods, such as double clicking on the text, using Ctrl+A to select the text, or using Shift and the arrow keys to select the text. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT423898 === END OF ISSUE === Title: UI may become unresponsive when viewing a form that has large number of expression values in a condition Description: If a form contains a condition with thousands of expression values, for example in a query form, the UI may become unresponsive when viewing this form. Workaround: No workaround available Status: Closed Affected Version: 6.7.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT423897 === END OF ISSUE === Title: Challenger revision with disabling rule that is selected in simulation analysis failed to be synchronized to remote instances Description: [SP 6.7] It is possible to disable a rule that is currently selected in simulation analysis on API instance. However, such revision change cannot be synchronized to remote instances and will result in a fatal error of ANALYSIS_RULE_NOT_ENABLED reported in the log on remote instances. All subsequent changes to that model revision will be discarded on remote instances and the revision cannot golive with an error of "There are some attributes missing for this model revision. Cannot golive." printed in golive report. until either the analysis is resaved, or the rule is re-enabled. Workaround: Resave the simulation analysis. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT423893 === END OF ISSUE === Title: In sandbox, precedents with expression with attributes in square brackets are not being calculated correctly because it uses the values of the record that is being computed. Description:  In sandbox, the precedents with expressions with attributes in square bracket [] are not being calculated correctly because instead of using the values of the previous records, it uses the values of the record that is being computed. Workaround: No workaround available Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT423754 === END OF ISSUE === Title: ICCM - Creation of KPI fails on target cluster after journal import. Description: When creating KPIs on the source cluster, the configuration change journal entry contains the correct list of keyPerformanceIndicators, but when importing the journal entry using the saveWithUid request, the new KPIs do not show up in the configuration of the target cluster after journal import. Workaround: Create the KPIs manually on the target cluster. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.5.0.09;6.6.0.07;6.7.0.03;6.8.X Known Issue ID: DT423739 === END OF ISSUE === Title: ICCM - Configuration change journal - Deletion of SAI creates an invalid journal entry. Description: When the Configuration change journal is enabled, there is a defect in writing the journal entry for the deletion of a Status Alarm Indicator (SAI). The "deletedItemDetails" are simply omitted, so the entry is not valid JSON. This will lead to an error processing the journal on target cluster. Workaround: Manually insert {} value for the JSON item "deletedItemDetails": in the corresponding journal entry. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.5.0.09;6.6.0.07;6.7.0.03 Known Issue ID: DT423731 === END OF ISSUE === Title: Deadlock may occur when executing golive when there's a KPI for counting number of cases running. Description: When there is a KPI type of "number of cases running" and the user executes a go live there is a possibility that a deadlock can happen. Workaround: Disable the kpi(s) of type "number of cases"Perform goliveRe-enable the kpi(s) that was previously disabledNote: It is not possible to do this workaround if the deadlock has already happened. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT423684 === END OF ISSUE === Title: Instance may crash if its incoming MCI connections are already closed when deactivating bypass Description: If an instance has bypass enabled, it activates bypass during maintenance mode (such as performing a golive and run the end of day job) and then deactivates bypass after exiting the maintenance mode. The instance may crash if its incoming MCI connections are already closed when deactivating bypass. Workaround: No workaround available Status: Closed Affected Version: 6.7.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.X Known Issue ID: DT423270 === END OF ISSUE === Title: Instance may be hanging during shutdown when closing FLI. Description: Instance may be hanging during shutdown when closing FLI due to infinite timeout on the system call. This issue occurs only on SP 6.7 and above. Workaround: NA Status: Closed Affected Version: 6.7.0 Fixed Available: 6.7.0.03;6.8.X Known Issue ID: DT423221 === END OF ISSUE === Title: "Ignore weak akas" option for OFAC sanction list does not work Description: In compliance list OFAC sanction list the option 'ignore weak akas' should make sure that when an entry has an a.k.a. entry that is marked 'weak', then searching for the a.k.a name will not return a result because of the 'weak' marking. However that check does not currently work and it returns the entry anyway as a hit. Workaround: Not available Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT423037 === END OF ISSUE === Title: Unable to enter 0 after decimal point on numeric fields in Case Actions, or conditions 'close to' field. Description: On case investigations, for example, Investigation > Case search > Select a case > Case actions, when you have a decimal field in the preview window, and you try to type a 0 after the decimal, like 1.05, that is problematic. Also, in conditions, in the close to numeric field, such as Amount -> close to -> 1.05 -> {Amount}. Workaround: N/A Status: Closed Affected Version: 6.6.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT422933 === END OF ISSUE === Title: Case class reporting attributes missing in case selection conditions Description: When performing a case selection with some case classes selected, these case classes' reporting attributes are not available in case selection conditions at first after selecting a case class. Workaround: Run the case selection with the case class selected and then reload the page. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT422763 === END OF ISSUE === Title: A case cannot be opened if it contains a compliance list text value with a double quote Description: A case cannot be opened if the value of one of its reporting attributes contains a double quote, and if this reporting attribute is used in compliance list with the value being found in this compliance list. Workaround: This case can be opened after the instance is restarted, however, the compliance list text value is cut off and only the part before the first double quote is kept. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT422297 === END OF ISSUE === Title: UI - Group by Query and Reporting Query results is not always complete for larger running queries. Description: The result page of group by query and reporting query do not get updated automatically when the query result is large, and will only show partial results. Workaround: Refresh [F5] the query results page until you can see no additional results appear. Alternatively, go back to the group by query page and check in the Existing results table if the flag Finished is indicated to be Yes. Then click on the query result from that table. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.7.0.03;6.8.0.01 Known Issue ID: DT422282 === END OF ISSUE === Title: In the UI, MCI shows green (enabled) when it's actually disabled in the logs. Description:  There are some scenarios where due to an error on the MCI, the interface is deactivated in the logs, but the UI still shows the MCI as enabled (Green) in the cluster tab. Workaround: Check if after the event 0239, MessageCommandInterface deactivated, there is an event 0010, Created 'MessageCommandInterface' incoming socket for {ip address}, if not, check if in the cluster tab, MCI is enabled (Green), if so, disable the MCI and enable it again. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT422050 === END OF ISSUE === Title: [PMML] Reused boosted trees generate incorrect scores after golive. Description: When using PMML Boosted trees in a Champion and creating a challenger out of it, when promoting (golive) the challenger, the pmml would generate incorrect scores. Workaround: Change the priority of the PMML boosted tree in the copied challenger revision before golive. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT421950 === END OF ISSUE === Title: UI - Tooltips visible for a longer period of time. Description: Tooltips stay visible for a longer period of time on areas such as Conditions, and can block UI elements including input fields. Workaround: Click on somewhere else on the page to make the tooltip disappear or reload. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03 Known Issue ID: DT421941 === END OF ISSUE === Title: MCI - Bypass - Malformed JSON could be sent back to sender affecting transaction responses. Description: [6.7] Message responses in Safer Payments versions starting from 6.7.0.00 can be malformed if the instance the request is sent to is bypassing to another instance in the cluster. Workaround: Disabling bypass will prevent the issue until a fix is available. Please ensure your Load Balancer is configured correctly to forward messages to the next available instance if the current instance is unavailable. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT421832 === END OF ISSUE === Title: If a text attribute ends with a "\" character, the JSON response of the query's results will be invalidated, causing an error message to pop up. Description: If a text attribute ends with a "\" character, the closure double quote of the JSON element will be detected as an escape character, causing the JSON response of the query's results to be invalidated and returning a pop-up message with an error. This could be caused if a rule's conclusion concatenates the backslash character at the end of the text attribute. Workaround: Avoid having backslashes at the end of a text attribute. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT421669 === END OF ISSUE === Title: Some fields are not saved when creating a case action or a notification by copying from an existing element and modifying its Outgoing Channel Configuration. Description: When you create a new element in the Administration tab > Case Action or Administration tab> Notifications by copying from an existing element which has its OCC as HTTP and you modify it to an OCC with type SMTP, some fields like Constant email "to" address are not saved. Workaround: Edit the case action or notification by adding the missing fields and then save it again. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT420342 === END OF ISSUE === Title: High number of threads when several Outgoing channel configuration (OCC) messages cannot be sent. Description: When an Outgoing channel configuration message cannot be sent, the message is queued up for retry and the created thread does not honor the Alert Message Interface limits in System Configuration. Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT419958 === END OF ISSUE === Title: [Sandbox] Overwritable/output attributes can prevent parsing of model revision by being populated with garbage characters Description: When a sandbox record is computed with rules using the operator append, the appended value can be wrong if the data is empty or including multiple double quotes, causing the model revision to be unreadable. Workaround: No workaround available Status: Closed Affected Version: 6.5.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT419868 === END OF ISSUE === Title: Ad hoc queries are fetching more than allowed number of records Description: The number of records value defined in a query is not exact, and a query result can display more records than the value set in the number of records field. Workaround: No workaround available Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT419669 === END OF ISSUE === Title: Attribute name reference in Precedents, Patterns, and Events conditions causes a UI validation error. Description: When using an attribute name reference in a condition within precedents, patterns, and events and reloading the element from the element table, a validation error appears and the expression is no longer visible. Workaround: Reloading of the element using the URL avoids the issue and can be done by clicking the browser's address bar and hitting the enter key. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT419652 === END OF ISSUE === Title: Can't access Output/Overwritable Attributes in conditions for an External model Description: Output attributes and overwritable Input attributes can't be selected when setting conditions for executing an external model. This limits the capability of modeling. Workaround: NA Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT419551 === END OF ISSUE === Title: Precedent attribute has a default value set if the source attribute is empty Description: The precedent attribute is set to a default value instead of being kept empty, if the source attribute in previous record is empty or if there is no record found in the index.The default value for the precedent attribute in different data types are:Numeric type: 0Text: empty valueTimestamp type: 0IPv4 type: 0.0.0.0Hexadecimal type: 00000000 Workaround: No workaround available Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT419535 === END OF ISSUE === Title: Simulation Query - UI may give a INVALID_DATA_SELECTION error when a remote instance is assigned Description: When the data selected for the simulation is not available, the error value INVALID_DATA_SELECTION is displayed, instead of an informational error message. Additionally, the fields that show the invalid values are not highlighted. This is evident when running a simulation query with Records Absolute choosing a URID range available on the API instance, but not the remote instance assigned for simulation. Workaround: Change the API to the remote instance to see the URID range available to adjust the values, otherwise run the simulation locally as the UI does display the correct URID ranges for local simulations. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT419504 === END OF ISSUE === Title: Overlapping displays on the case investigation page Description: In some cases, if a custom layout is used, the Case actions section on the Case investigation page could overlap other tables when the Case actions section is opened, and some of the tables on the page get misaligned when the Case actions section is closed. Workaround: No workaround available Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT419238 === END OF ISSUE === Title: UI validation triggers as soon as the tab loads or sometimes even before it Description: On the simulation page, UI validation is triggered across all tabs when the Next button is clicked or if the user attempts to navigate forward within the tabs. This behavior may interrupt workflows by prematurely enforcing validation criteria across unrelated sections of the page. Workaround: No workaround Status: Closed Affected Version: 6.7.0 Fixed Available: 6.7.0.03;6.8.0.01 Known Issue ID: DT419116 === END OF ISSUE === Title: Expiration Date Saved as Empty in Defined Risk Lists Description: When expiration is enabled and a default lifetime is assigned, saving an entry without modifying the expiration date results in the field being saved empty. Workaround: Manually set an expiration date before saving. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT418853 === END OF ISSUE === Title: KMIP master key's activation time is set to its last activation time instead of its first activation time Description: KMIP master keys activation time is set to their last activation time instead of their first activation time. This may lead the currently activated KMIP master key to stay active longer than the configured lifetime in Safer Payments, if the cluster is restarted before this KMIP master key expires. Safer Payments also ignores the KMIP master keys deactivation time set on the KMIP server. Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT418802 === END OF ISSUE === Title: MCI fails to send an error response when it encounters an invalid character encoding in a FCD message Description: When the MCI receives a Fixed Column Data transaction message, and encounters an invalid character encoding, the MCI fails to respond to the sending system with an error code causing it to time out. A "W 0441 CHARACTER_CONVERSION_INVALID_INPUT" error is appended to the system log. Workaround: N/A Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT418798 === END OF ISSUE === Title: A fatal error may occur when writing to the stream, if retired revisions contain target or sampling conditions. Description: When writing to the stream, Safer Payments may fail to create the references for target and sampling conditions within retired revisions. As a result, these conditions can be unintentionally removed from the affected revisions. Workaround: If the target or sampling conditions are no longer needed—such as when a newer challenger includes equivalent or updated conditions—the error can be safely ignored. However, if you intend to reuse the retired revision and its target or sampling conditions, follow this workaround:Back up the retired revisions before resizing retention or performing a master key change.Perform the operation.Overwrite the retired revision files using the previously backed-up ones. Status: Open Affected Version: 6.7.0 Fixed Available: No fixed available Known Issue ID: DT418776 === END OF ISSUE === Title: Fatal error from getSimulationStatus and getLoadBalancingInstances if the simulation instance does not exist Description: If the simulation instance previously saved in the challenger revision no longer exists in the cluster, a FATAL_ERROR returns when clicking Simulation in this challenger revision in Safer Payments v6.7. The Safer Payments log shows this error is from "getSimulationStatus" request. For the versions before Safer Payments v6.7, the user cannot select any instance to run the simulation and the log shows a FATAL_ERROR about "getLoadBalancingInstances" request. Workaround: Shutdown the instance, then manually update the "simulationInstanceUid" value in model revision file to the uid of an existing instance in the cluster. Then startup the instance. Status: Closed Affected Version: 6.7.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT418570 === END OF ISSUE === Title: In a masterkey change, Defined Risk List Entries will be improperly decrypted under specific circumstances. Description: Defined risk list entries are generated in the remote instance will be improperly decrypted when they are sent from an instance that has not performed the masterkey change, to an instance that already performed the masterkey change. Workaround: NA Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT418392 === END OF ISSUE === Title: Incorrect query results when including numeric attributes that uses decimals and has categories enabled. Description: When running a query, where in the columns dropdown is selected a numeric attribute that uses decimals and has categories enabled ( should not be possible), the query results can return wrong results.For example, if you try to add some of these transactions to risk lists, the URID of this transaction can be null, causing that this transaction and the other ones selected after it not to be added to the risk list. Workaround: To fix these attributes without losing mdc and ddc data of these attributes you can do the following steps 1 to 6 for each attribute and then step 7 and 8:Open the attribute definitionTake a screenshot to remember the decimals setting that is set in field DecimalsChange formatting to no formattingDisable the checkbox next to Categories (do not save and do not golive, leave the form open)Change formatting to decimals againSet the original number of decimals that was set before. SaveRun golive report. Make sure that it does not show any warning like memory data cache cannot be reused or disk data cache cannot be reused related to the attributesGolive Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT418208 === END OF ISSUE === Title: Masterdata value is not retrieved if it is based on an index from an upper mandator. Description: [SP 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01] Masterdata values are not being populated when the Masterdata and its associated index are defined in different mandators.  Workaround: N/A. Please contact IBM Support for any additional help. Status: Closed Affected Version: 6.7.0.01;6.4.2.09;6.5.0.07;6.6.0.05 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT418128 === END OF ISSUE === Title: When copying or deleting a revision in the mandator revision table the change is not immediately visible until the auto-refresh timer refreshes the table. Description: When you go to the Model tab and either copy or delete a revision, those actions won't trigger an immediate revision table refresh, so the changes won't be visible until the page's auto-refresh timer counts down to 0 and refreshes the table. Workaround: After either clicking on Copy or Delete, refreshing the page manually will show the correct number of challengers.Alternatively, you can set the page auto refresh timer for Revision selection (Under Administration> System> Configuration> System tab> Page Auto Refresh) to a lower number, such as 3. Status: Closed Affected Version: 6.7.0.00;6.3.1.09;6.4.2.08;6.5.0.06;6.6.0.04 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT418104 === END OF ISSUE === Title: API - Multiple parallel logins from the same user can crash the instance. Description: When using an API script with multiple logins from the same user in parallel sessions, the instance could crash. Workaround: Use a different user login per API script. Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT417690 === END OF ISSUE === Title: Latencies can be encountered when deleting index nodes manually Description: The process of manually deleting an index node via masterdata query may take a long time to complete if the node happens to have a long sequence of entries. This will cause index computations to pause for transactions being processed, which results in latencies. Workaround: Do not manually delete index nodes while the system is receiving transactions. Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT417667 === END OF ISSUE === Title: Rebuilding index maintenance function does not completely clear previous DDC data Description: When running the Rebuild Index maintenance function, DDC data is not fully wiped and as a result, some values might remain unchanged in the DDC file. Subsequent restart before all values are overwritten might cause wrong data to be loaded from DDC. Workaround: Before executing the Rebuild Index maintenance function, delete the calendar period DDC files (profile_0000000000000XXXXX_XXXXX.iris) associated with the index to be rebuilt Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01, 6.8.0.00 Known Issue ID: DT417292 === END OF ISSUE === Title: Decision tree outputs not computed Description: Decision trees results are not computed correctly. The output attributes value is empty( ) Workaround: As a workaround you have to change the file structure to resemble random forest or at least add the MiningModel section and move the outputs there. Then it is computed correctly. Please contact Support if you need help with this. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT417271 === END OF ISSUE === Title: A reference to OCC may remain in EMC even when EMC was configured to use dynamic OCC. Description: A reference to an outgoing channel configuration may remain in an external model component even when the EMC was configured to use dynamic OCC. This can cause problems when deleting the OCC. Workaround: Create a challenger from the champion.Go to the external model component and temporarily enable select persistent connection through id attribute (not saving).Disable it again and then save. This will remove the reference. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT416949 === END OF ISSUE === Title: Reporting query thread fails to be erased under some error conditions Description: The reporting query thread may not be erased under some error conditions, and consequently block the maintenance tasks such as golive and end of day job. Workaround: Delete the reporting query. Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT416574 === END OF ISSUE === Title: AMI - OCC - Duplicate notifications are possible when restarting. Description: When an instance is restarted, then if there are notifications which are queued to be sent out over an OCC for that instance, then it is possible that those notifications can be sent out twice. This happens upon restart of the relay instance while AMI notification messages are sent to it via FLI from the primary instance. Workaround: Within Safer Payments, disable the AMI on the relay instance before restarting the instance. After the instance has started up, then wait until synchronization is completed before enabling the AMI again to ensure no further notifications are added to the queue from the FLI before the AMI queue is finished loading. In addition, some downstream systems from Safer Payments can detect and handle duplicate notifications as well. Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT406968 === END OF ISSUE === Title: Final rulesets are not computed for test sandbox records Description: While final rulesets are available for use in simulation and transaction processing, these rulesets are not being computed in the sandbox environment Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT406884 === END OF ISSUE === Title: Slow case consolidation for cases with extremely long aggregation history Description: Case consolidation may slow down dramatically if alarms are consolidated into a case with a long aggregation history that includes many reporting attributes. This is usually only observable if a case has thousands of hits. Workaround: This situation usually occurs when a rule or case class is incorrectly setup so that more cases are being created than expected and/or cases are being incorrectly consolidated together. If that is the case, then adjust the rules or case class configuration to prevent these cases from consolidating together. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT400478 === END OF ISSUE === Title: Saving of defined risk lists or compliance lists can cause transaction latency Description: When there is a save of a defined risk list / compliance list at the same time as this defined risk list / compliance list is computed in messages, these messages could be recorded in latency log with high latency on defined risk list / compliance list. Note that this only happens when the actual defined risk list is saved, not when entries are added to the defined risk list, or when entries of the defined risk list are edited. Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT400477 === END OF ISSUE === Title: Internal model files are not transferred during restore Description: Internal model files in the cfg/internal_models folder on recipient instance are not deleted during a restore, and these files are not transferred from the donor to the recipient instance. If the files were manually deleted on the recipient before starting the restore then after the restore the instance fails to start up if it has internal model files missing. Workaround: Manually copy all the files in cfg/internal_models from donor instance to the same folder in recipient instance. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT400281 === END OF ISSUE === Title: Counting number records in a simulation query can return wrong results Description: If the simulation on remote instance is deregistered while running the request of counting number of records in a simulation query, (SCI Timeout, or SCI error) this request is then automatically redirected and executed on the API instance, which didn't run the simulation. An invalid result is therefore returned. Workaround: Run simulation on the API instance. Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT400197 === END OF ISSUE === Title: SCI timeout causes count number of records operation not to complete on remote simulation instance Description: If the request of counting number of records of a simulation query takes longer than the defined SCI timeout, the simulation on the remote instance is disabled and deregistered. Workaround: Run simulation on the API instance. Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT400196 === END OF ISSUE === Title: Condition fields are throwing a Parsing error when the ~ character is used and the operator is different from [not] equal to Description: When we create a query with a condition where the attribute type is text, and the operator used is different from [not] equal to, the form validation for the field that the customer fills with the string that he/she wants to use to filter the transactions doesn't accept ~ character, even when it should be detected as a regular character.For instance, when we used MerchantName contains Text~ it threw the validation error, but when we used MerchantName contains Text* it returned all the transactions that contained * as a regular character (it was not used as a wildcard/special character). Workaround: Send the API request directly to the server without using UI Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT398647 === END OF ISSUE === Title: Incorrect value of attribute is populated in case action template when the attribute is not selected in Attach data table on UI. Description: If the attribute is referenced using loop construct in a case action template, transactions added to the case action are traversed and attribute values are extracted from the UI table of Attach data for the Case action. If an attribute is deselected in the UI table of Attach data for the Case action, the value will default to the main transaction of the case instead of the selected transactions. Workaround: Make sure attributes are selected in the UI table of Attach data for Case actions. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT398490 === END OF ISSUE === Title: The sorting arrow in table column is not visible if the column is too narrow Description: [SP 6.3.1.08+, SP 6.4.2.07+, SP 6.5.0.05+, SP 6.6.0.03+, SP 6.7+] The sorting 'arrows' now appear at the end of the text in the heading of a table. It won't be visible if the column is too narrow. The table column can still be sorted, although you will not be able to see the sorting arrow indicator unless the column width is expanded. Workaround: No workaround available Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT398477 === END OF ISSUE === Title: Selected items in a table get reset when changing the filter Description: [SP 6.3.1.08+, SP 6.4.2.07+, SP 6.5.0.05+, SP 6.6.0.03+, SP 6.7+] After having some items selected using a filter in a table, if you change the filter and select some other items, the previously selected items are lost. Workaround: No workaround available Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT398225 === END OF ISSUE === Title: UI - Unexpected Error when filtering for visible columns of Transaction Messages report. Description: When viewing the Transaction Messages under Report, filtering for visible columns by typing any characters will throw an Unexpected Error on the UI. Workaround: Reload the page and pick a filter value manually with your mouse pointer instead. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT397666 === END OF ISSUE === Title: Instance crashes when setOffline called during startup. Description: Executing a setOffline API command while the instance is starting could cause a crash. The system log or backtrace will print a FileHandler related error. Workaround: Do not send a setOffline command while instance is in startup on cluster page. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT397205 === END OF ISSUE === Title: It is possible to run a simulation on either the donor or recipient instance during a restore. Description: It is possible to run a simulation on either the donor instance or the recipient instance that is currently involved in a restore, if one of those instances is selected as the simulation instance for a revision, and no changes were made to the revision since the restore was started. This can cause cluster desynchronization and puts the donor at risk. The desynchronization may prevent a user from changing the simulation instance. Workaround: If you find that you are encountering the error message "Either you are running a task on a remote instance or all instances are out of sync. To avoid synchronization problems, you cannot change the instance assignment right now.", then saving the revision (Revision Overview > General > Save button) will fix the error and allow you to change the simulation instance back to the API instance. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT397194 === END OF ISSUE === Title: The outdated index entry being purged by End of day job remains in extended masterdata query Description: The outdated index entries that exceed their maximum lifetime for purging are purged by the end of day job. However, these purged index entries are still displayed in the Extended masterdata query result. Workaround: N/A Status: Open Affected Version: 6.6.0 Fixed Available: 6.7.0;6.6.0.05 Known Issue ID: DT397187 === END OF ISSUE === Title: Temporary case may fail to be promoted as a normal case in some situations Description: A temporary case may fail to be promoted as a normal case on a remote instance, if this instance receives an update that doesn't update the lastAction of a case right before this case itself, for example an audit trail update. Workaround: No workaround available Status: Closed Affected Version: 6.6.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT397122 === END OF ISSUE === Title: [Golive-Shutdown] Instance shutdown when making an input attribute non overwriteable Description: When changing an input attribute that is overwritable by rules, so that is no longer overwritable by rules, and that attribute is used by an External Model Component in the response message mapping, the instance shuts down during golive. Workaround: Before disabling the "overwritable by rules" for an input attribute get all references for this attribute and confirm that it is not used in response mapping for an external model. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT397075 === END OF ISSUE === Title: Clicking 'reload encryption keys' button can cause error KEY_ALREADY_REVOKED and instance shutdown Description: If a new encryption key is activated on one instance but not available on disk on another instance, then a click on the button 'reload private keygen keys from disk' on the other instance can cause an error KEY_ALREADY_REVOKED and a subsequent instance shutdown. Workaround: To avoid the error, first copy the key to all instances, then activate it.If the error already happened, make sure that the key is available on disk on the instance and restart the instance. This will correctly activate the key. In case the instance was already restarted after the error but the key was not available during restart on disk, copy the key to disk and click the button 'reload private keygen keys from disk' which will activate the key. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT397071 === END OF ISSUE === Title: Temporary case audit trail files failed to be archived if deferred writing is enabled Description: With deferred writing enabled, Safer Payments fails to remove the investigation_audit_temporary_*.iris file. Such files are kept in the inv000... folder permanently. Workaround: Manually delete the Case investigation_audit_temporary_.iris file once the investigation_audit_.iris file has been written. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT396989 === END OF ISSUE === Title: Date and Datetime inputs get different values when using the browser timezone and the custom timezone which equals to the browser time Description: When using the Case Action Inputs of type Date and Datetime for sending the Case Actions, the time is converted to UTC in case of the Use browser timezone is enabled in the profile. Workaround: No workaround available Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT396947 === END OF ISSUE === Title: Index query section in case investigation shows animated gray lines when no data is available due to empty index reporting attribute. Description: On "Investigation" > "Case selection" > "case", the query section for an index query whose index attribute was provided to the case as an empty value shows animated gray lines as if loading, even though the query can't run due to the empty index value. Workaround: N/A Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT396881 === END OF ISSUE === Title: Masterdata section missing in case when the masterdata related index attribute is left empty in case creation. Description: On "Investigation" > "Case selection" > "case", the masterdata section is not visible when its related index attribute (reporting attribute) is left empty on case creation. Workaround: N/A Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT396880 === END OF ISSUE === Title: Heartbeat sending instance waiting indefinitely for a response from the remote instance Description: When an instance send it's heartbeat to a remote instance, if a response is never received, it will no longer keep sending it's heartbeat. This might prevent remote instance from entering maintenance mode, as the heartbeat status of sending instance is never updated. Workaround: Restart the instance that is not sending the heartbeats. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT396175 === END OF ISSUE === Title: OCC "URI" shows warning in PA-DSS report Description: OCC "URI" always shows a warning in PA-DSS report, even it isn't used at all. Workaround: Manually check the usage of OCC "URI" and verify that it is either not used or isn't used together with sensitive data. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT395513 === END OF ISSUE === Title: FastLink status shows error after login, the table appears only after the first page refresh. Description: After logging in to SP instance, the Fast Link status tab in 'Cluster > System Monitoring > Settings' page shows an error and only after a few seconds the FastLink Status table gets displayed. The table gets displayed after the first automatic refresh which is defined in 'Administration -> System -> Configuration -> System -> Page Auto Refresh -> Cluster administration (seconds)'. Workaround: Decreasing the auto refresh time can make the table appear earlier but leads to more refreshes in the same time span. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.00 Known Issue ID: DT395359 === END OF ISSUE === Title: When deleting a Performance Indicator in a Reporting query, the condition of the deleted Performance Indicator cascades to the next remaining Performance Indicator. Description: When deleting a Performance Indicator in a Reporting query, the expression on the right hand side of the deleted Performance Indicator will instead move to the next remaining Performance Indicator. Workaround: If you hit save without clicking any of the right hand side expression elements, then the elements will be saved with their correct values. Once you have clicked any of the expression elements, then those elements which were clicked will be saved with the displayed values. You should always check which values were saved by reloading the Reporting Query after deleting any Performance Indicators. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT395089 === END OF ISSUE === Title: Creating an instance that shares an IP and port with another instance can lead to cluster desynchronization Description: If you copy an existing instance and save it without making any changes, the save goes through and the instance is created despite it sharing all of its IP addresses and ports with the instance it was copied from. This change is accepted by the remote instances as well. But all future cluster updates will be rejected by the remote instances because of the conflicting IP and port combos. This desynchronization may result in a crash, as the outgoing FLI queues may point to a non- existent instance after some deletions are attempted. Workaround: Fix the issue on the API node by correcting the newly created instance's IPs and ports. Transfer that cluster.iris file to the remote instances and restart them. Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT394925 === END OF ISSUE === Title: Golive with attribute deleted that is in use in Reporting Query can cause an instance to shutdown. Description: Attribute deletion is not prevented if the attribute is referenced in the conditions of a reporting query's performance indicator settings. The "show references" tool also fails to identify the attribute's inclusion in those conditions. If a user executes a golive to make the deletion permanent, it can fail and cause an instance to shutdown. Workaround: Before deleting an attribute and doing a golive please double-check that it is still not being used in a Reporting Query. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT394592 === END OF ISSUE === Title: A race condition could lead to deactivation of the MCI. Description: When SSL is enabled on MCI, a short-lived MCI connection (open and directly close it) could remain open indefinitely. A massive amount of these would cause the MCI to deactivate and produce an error message in logs. Workaround: N/A Status: Open Affected Version: 6.6.0 Fixed Available: 6.4.2.09;6.5.0.07;6.6.0.05;6.7.0.01 Known Issue ID: DT394259 === END OF ISSUE === Title: Some tables with editable fields trigger unexpected UI errors when the user attempts to edit their values. Description: An error is displayed when attempting to modify the values of some editable columns in the affected tables.For example under Model > Data Model > Inputs > Categories Table and Investigation > Queries.The error reads as follows: "errorName": "TypeError: column.renderEditCell is not a function." Workaround: NA Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT393963 === END OF ISSUE === Title: Time passed between two checks can be wrong by 1 second in KPI, leading to falsely abrupt changes on the chart. Description: In KPI the frequency can be set in seconds. However in edge cases the time passed between two KPI checks can be up to 1 second less or 1 second more. The issue leads to KPI charts sometimes dropping to almost or even 0 and sometimes there are spikes in the chart although the tracked data stream was consistent during the whole time. Workaround: N/A Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT393943 === END OF ISSUE === Title: The Synchronizing status is not reflected once the initial synchronization after startup is completed Description: The status Synchronizing on the cluster page is inconsistent. It only shows Synchronizing during startup, but not afterwards.After Startup, if FLI is synchronizing then the status does not show Synchronizing but shows OK. Workaround: N/A Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT393882 === END OF ISSUE === Title: Modifying the source and output attributes in an existing precedent at the same time causes a wrong precedent file size after golive. Description: The file size of precedent output uses the old length, rather than the newly modified one if changing an existing precedent from no storage to using mdc/ddc. This can multiplicatively increase file size, and ends with a crash if deferred writing is enabled. Workaround: Save the precedent twice after modifying it so the size parameter can be fixed in the second save request. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT393749 === END OF ISSUE === Title: Working queue information is not displayed on open case's investigation page Description: When opening an open case to investigate on the UI, the working queue information is always empty, even if the case was opened from a working queue. Workaround: No workaround available Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT393698 === END OF ISSUE === Title: Limit rulesets filter on All rules page gets reset when selecting a rule. Description: The 'Limit rulesets' filter on the All Rules page gets reset when selecting a rule from the table. Workaround: No workaround. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT393252 === END OF ISSUE === Title: The scrollbar on tables moves to the left when selecting items after hyperlink query overlay was opened. Description: On Chrome on the query results page when clicking on a hyperlink and closing the hyperlink popup and when scrolling the table to the right then on each click of a table row on the selection checkbox the scrollbar will move to the left automatically. Workaround: The problem is only on chrome. It works correctly on Firefox. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT393249 === END OF ISSUE === Title: Event node can be replaced with value from wrong node during index purging when using Deferred Writing. Description: When Deferred Writing is enabled, and an index uses purging, then an event node can get replaced with the value from a different node while the index is purged during end of day job. This will lead to incorrect event outputs in the following days (which have no event). Workaround: No workaround available Status: Closed Affected Version: 6.6.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT392933 === END OF ISSUE === Title: Automatic cold index UID generation can lead to cluster inconsistency and instance shutdown Description: The automatic UID generation for cold indexes can cause problems during the golive. On an index, if "masterdata query conditions" is enabled, this will trigger the automatic UID generation. If another element is created through the API at the same time as the golive, this can cause inconsistencies on the remote instance, and lead to remote instance shutdowns. SP 6.6+ Workaround: N/A Status: Closed Affected Version: 6.6.0 Fixed Available: 6.6.0.05, 6.7.0.01 Known Issue ID: DT392260 === END OF ISSUE === Title: Fatal error in PMML when prediction is null and multipleModelMethod is sum Description: When multipleModelMethod is set to sum and a prediction is null, the model will fail on computing the prediction. This would happen when PmmlTreeModel computes the nodes using a noTrueChildStrategy of returnNullPrediction, which can happen when an invalid category which is not in the data dictionary is sent in. Workaround: N/A Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT392090 === END OF ISSUE === Title: Table flickering causes the UI to crash in Chrome Description: Flickering can happen on UI tables. This may eventually cause the UI to crash if using Chrome. There is no such issue if using Firefox. Workaround: The issue was observed on zoom level 80%, other zoom levels worked correctly. Status: Closed Affected Version: 6.3.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.00 Known Issue ID: DT392078 === END OF ISSUE === Title: Remote instances can still shutdown due to a failed Golive even with minimum active instances enabled. Description: A failed Golive attempt can cause all remote instances to shutdown, even with the configuration Interlock minimum instances configured. Workaround: If you have a 4 instance cluster and want to keep a minimum of 2 active instances, then setting the Minimum active instances value to 3 should prevent all 3 remote instances from performing the golive. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT391830 === END OF ISSUE === Title: Crash when printing rules the first time Description: An instance can crash if specific rule conditions or conclusions are printed for the first time. This may occur when viewing rules in the UI or when adding the rules that were fired to an investigation case. First occurrence: SP 6.6.0.00, 6.5.0.02, 6.4.2.04, 6.3.1.05 Workaround: N/A Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT391564 === END OF ISSUE === Title: Possible deadlock during EOD job when viewing KPI on dashboard Description: There is a potential deadlock when requesting KPI information via dashboard while the end of day job is running. This affects KPI information of the local instance in the same way as KPI information of remote instances. Workaround: The issue can be avoided by not using the dashboard while in EOD. Alternatively, an administrator can unchecking all KPI for all users before running the EOD, and re-enable it after EOD. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT390790 === END OF ISSUE === Title: The memo column in case selection table does not display all the text on a single line. Description: When text of case memo is written across multiple rows, then the memo column on the case selection page only displays the first row of the current memo. Workaround: NA Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT390458 === END OF ISSUE === Title: Index rebuild or resize can initialize masterdata with 0 instead of empty. Description: When rebuilding an index using the maintenance function, or resizing an index capacity during a golive, masterdata that is supposed to be empty/nil will instead be populated with zero. This may not be immediately visible on the query results page, as both empties and zeros appear blank in some cases, but it would be visible when using CSV Export. Workaround: If you have any conditions (ie. rules) that depend on is_empty for numeric or timestamp attributes, consider adding is_equal_to 0, if applicable. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT390397 === END OF ISSUE === Title: Golive of invalidated challenger could cause remote instances to shutdown. Description: It is possible for a user to execute golives on multiple challengers of the same mandator if the golives are triggered while an EoD job or re-create interval indexes job is occurring. If multiple golives are executed, SP will promote one challenger to champion and invalidate the other, and then promote the invalidated challenger to champion. This will go through on the API instance, but will fail on the remote instances, causing the instances to shut down. Workaround: Do not perform golives of multiple challengers of the same mandator during the time period of the end of day job, or when a re-create interval indexes job is running. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT390269 === END OF ISSUE === Title: Reporting Query can return invalid JSON response Description: An error log can occurred from Reporting Query due to in the response contain a invalid JSON as -inf Workaround: N/A Status: Closed Affected Version: 6.3.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT390202 === END OF ISSUE === Title: Case search and Case selection - latest results not shown when reloading page. Description: [SP 6.6.0.1+] Case selection page is not updating the results (e.g. by triggering the Case search request) when page is reloaded. After working on a case and after coming back to case selection screen, the case state is not updated and the former status is shown instead of the latest status (e.g. if a case is closed, after coming to the screen it's still being shown as open in this list). Only after clicking on case search execute button, the list is updated. Workaround: Pressing the case search execute button loads the updated information. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT389975 === END OF ISSUE === Title: Online Help - Case search and Case selection - Missing details for execute button. Description: [SP 6.6.0.1+] Case search is an expensive operation which was previously being performed upon pressing keystrokes. It was affecting the user interface responsiveness and also the performance by using more than necessary resources. That's why a case search execution button was introduced in version 6.6.0.01 and higher. However, it is not documented in the Online Help. Workaround: The below information was shared on our release notes and can be referenced.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 "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 the "execute" button is clicked. If a filter on one of the pages is changed, auto refresh stops until the "execute" icon is clicked again. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT389974 === END OF ISSUE === Title: Multiple save requests for a query with at least one condition may crash the instance Description: Executing multiple save requests at once for a query that has at least one condition may potentially crash the API instance. Although the save button is greyed out after an initial save, executing multiple save requests can happen if a user either executes multiple "save and execute" button clicks (as this button is not greyed out after the initial click), or makes multiple Ctrl+S keystroke combinations (which can bypass the greyed-out button and allows a user to send multiple save requests). Workaround: If a user hasn't made any changes to a query and only wishes to execute it without saving, they can do so by clicking the "Execute query" table action button that appears when selecting a query by clicking the checkbox on the left side of the table. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT389924 === END OF ISSUE === Title: The shutdown process may be prolonged when a group by query is being executed. Description: A group by query that is running slow can block the shutdown process for a longer time. It is stopped after 1000 records during shutdown, rather than after a single record, similar to the end of day job or golive operations. Workaround: Execute the end-of-day job. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT389569 === END OF ISSUE === Title: The "more" button is not displayed in the case audit trail comment column. Description: If the size of the case audit trail comment column is insufficient to show all the text, it causes the "more" buttons in cells to be hidden. Workaround: Execute the end-of-day job or initiate a golive process that puts the system into maintenance mode. Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT389549 === END OF ISSUE === Title: Filtering and sorting cannot be done simultaneously. Description: It is not possible to simultaneously sort and filter columns in the table. Enabling the filter function will cause the sorting feature to become unresponsive. Workaround:  Click the filter button after sorting the items. Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT389548 === END OF ISSUE === Title: Sorting or filtering causes the row highlight to appear on the incorrect row. Description: Enabling row highlighting for index queries in a case will highlight the transaction row(s) belonging to the case in blue. However, sorting or filtering columns will consistently highlight the incorrect row. Workaround: NA Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT389546 === END OF ISSUE === Title: Deadlock in MQI when performing golive and cluster change at the same time. Description: A deadlock can occur if a golive is performed at the same time as a cluster change, while computing MQ messages. Workaround: Perform cluster change a few minutes before starting a golive. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT389462 === END OF ISSUE === Title: Index sequence can be broken after index rebuild followed by a golive Description: If you have an index with the MDC sequence sized smaller than the DDC sequence size, then an index rebuild followed by a golive can break the index sequence, because the DDC Oldest URID is not written to disk during the index rebuild. Workaround: Ensure that the MDC Sequence size of your indexes is set to the same size as the DDC Sequence size. If you have already ran into this issue, then contact support for help to recover. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT389262 === END OF ISSUE === Title: JSON Output can contain values with more decimals than configured in Safer Payments Description: When you are outputting a Numeric attribute with multiple decimals through an external model, or in the model response, then the output may contain more decimals than are configured in Safer Payments. Workaround: In some cases, you may be able to copy the value to a Text attribute as well, and output that value. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT389219 === END OF ISSUE === Title: MDC primed with invalid DDC data when changing storage type and resizing DDC Description: Changing the storage type of an attribute from "stored only in DDC" to "stored in MDC and DDC" has the potential to cause the MDC data to be primed incorrectly if the DDC records retention of the attribute is also increased at the same time. Workaround: Restart all the Safer Payments instances.If unable to immediately restart, a temporary workaround can be to do 2 golives, one which changes the attribute to only be stored in DDC and another which changes the attribute back to having MDC. This will re-prime the data from DDC, however the MDC Oldest URID will still not be correctly updated in the system internals, and a restart should be done as soon as possible. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT387609 === END OF ISSUE === Title: Bypass - Mismatch of Message ID in header and body inhibit MCI response. Description: The Message ID is used during Bypass, and is only required in the HTTP Header. However, if it is also sent in the XML Body, and the two Message IDs do not match, this causes SP to not respond to it during Bypass (golives, eod, etc). Workaround: Sender must ensure that the Message ID sent in the Header (X-SP-Message-Id), and Body (MessageId) match. The Message ID should also be unique for each message, and not longer than 16 characters. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT387498 === END OF ISSUE === Title: Large lists can cause UI hanging or Failed to Fetch errors when editing Description: When working with a sortable component, such as a list of Output Attributes, and adding/changing an item, SP will do requests again for existing items. This can cause the page to become unresponsive or trigger memory errors, especially when a list has many elements, such as 500 values. Workaround: No Workaround Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT387200 === END OF ISSUE === Title: Memory usage could increase after golive with purge outdated entries. Description: Glibc could reserve memory freed from SP during golive instead of releasing it to the Operating system. This happens when processing an internal data structure for the index with purge outdated entries enabled. And the memory growth is particularly significant if the index has large capacity, which could lead to memory exhaustion over time.  Workaround: Consider periodic instance restarts to free up unused memory in the Operating System. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT387182 === END OF ISSUE === Title: Rule cannot be re-saved if "Timestamp" or "Numeric" type of attribute in rule conclusion uses "Reset value" operation Description: A rule cannot be re-saved with form input error reported, if it contains conclusion of a timestamp or numeric type of atttribute that uses "Reset value" operation. Workaround: Create a new rule instead. Status: Closed Affected Version: 6.6.0 Fixed Available: 6.7.0.02;6.4.2.10;6.5.0.08;6.6.0.06 Known Issue ID: DT387158 === END OF ISSUE === Title: Downloading encrypted simulation query results with remote simulation fails. Description: After running remote simulation if the user tries to download a simulation query and Encrypt sensitive exports is enabled in Administration -> System Configuration -> System -> Encryption , a NEW_PASSWORD_TOO_SHORT exception is thrown incorrectly, and the query is not downloaded. Workaround: Run simulation on local instance to download query results if encrypt sensitive exports is enabled. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT387043 === END OF ISSUE === Title: Profile Calendar - Period data can be reset after restart. Description: It is possible for the wrong period to be considered the most recent one if a restart is done when the last transaction that was loaded on the system was a historical, out of order transaction (ie. previous year). The profile calendar values of the more recent periods will be reset to 0, as that is the normal behavior when the period doesn't exist anymore. Workaround: Prevent: Avoid having an old timestamp as the last transaction ingested in the system before restarting. (Recommended)Mitigate (if it has already occurred): Rebuild index will fix the profiles for the next transactions received, but not the ones already scored. Status: Closed Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT387020 === END OF ISSUE === Title: Exception thrown when stopping rule generation Description: A fatal error log message may be generated when stopping rule generation. The fatal error log message is misleading as there's nothing wrong with the action taken by the user or with the program, and there is no adverse effects from the error. Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT386154 === END OF ISSUE === Title: New conditions on attributes with categories, only show the label for the category Description: When a condition is created for an attribute that has a category, the default value that is populated just contains the label of the first category instead of the actual value together with the label. Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT386133 === END OF ISSUE === Title: MCI deactivates before EOD Description: Having an invalid certificate on the CA certificate for bypass, leads to MCI being deactivated during EOD Workaround: Correct the Server CA certificate for Bypass if required or remove if not needed. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT386122 === END OF ISSUE === Title: Masterdata card(s) content not displayed in case investigation if a masterdata card that is associated with another index is also chosen for display Description: When the user chooses more than one master data card to be displayed under "Administration -> Case class->Layout" and the masterdata are associated with different indexes, then only one index's masterdata are displayed. Workaround: No workaround available Status: Closed Affected Version: 6.6.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT386110 === END OF ISSUE === Title: API client certificate validation error during first save Description: When enabling client certificate validation for API, the server may print a "SSL_CLIENT_CERTIFICATE_ERROR" error message and may reject to apply the changes. Workaround: Put in an empty file "password.pwd" to the key folder Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT385983 === END OF ISSUE === Title: Some secure elements like "object-src"are missing from Content Security Policy and "Referrer-Policy" is missing from HTTP header. Description: Some secure elements like "object-src" are missing from our current Content Security Policy and should be added."Referrer-Policy" is missing from HTTP header. In addition, csv exports don't have a Content Security Policy header entry. Workaround: N/A Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.12;6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT382146 === END OF ISSUE === Title: Deferred Writing - Disabling DW or using setOffline with no data logs a Fatal error. Description: On SP clusters with no data (System Internals - Last xDC record = No data loaded), if the instance is setOffline or Deferred Writing is disabled, the system will log "F 0099 Fatal error in DeferredWriter::stop()" . Workaround: This log message can be safely ignored as long as there is no data loaded. If the environment does have data loaded, and reports this error message, please check with IBM Support. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT382132 === END OF ISSUE === Title: Fraud marking report doesn't work on ui when case investigation is disabled in system config Description: When Case investigation is disabled in system configuration, then when opening reports tab you see the fraud marking report on the left side, but clicking on it will open the Transaction messages page. Workaround: N/A Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT382036 === END OF ISSUE === Title: Running simulation after a logical golive may cause a crash under certain conditions Description: If you have a setup with masterdata on a higher mandator, and you simulate on the lower mandator, and then run a logical golive while running a simulation, then change the data selection to a larger data range and restart the simulation, then it may cause the instance to crash Workaround: Disable logical golive in Administration\System Configuration\Modeling Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT382025 === END OF ISSUE === Title: The MSSQL database is generating a syntax error when ingesting Safer Payments RDI files. Description: The MSSQL database encounters syntax errors when ingesting SQL DML commands generated by the Safer Payments RDI, which makes them unusable. Workaround: Use another database format instead of MSSQL and convert them to MSSQL format outside of SP, or manually alter the SQL statements before ingesting them into the database. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT381678 === END OF ISSUE === Title: User preference for defined risk list entries is not saved correctly Description: Fatal Error 0307 is encountered under specific circumstances on the "Defined Risk List Entries" page of the Monitoring tab in an encryption enabled instance. It requires a sequence of page refreshes, logging out and in by the same user, or some combination of both, and the user may see an "An error occurred when processing this request" modal when navigating to this page. Workaround: Selecting any defined risk list from the dropdown menu (or selecting a different one if there is already one selected by default) will clear the error. Resetting user preferences will also clear the error. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT381665 === END OF ISSUE === Title: E0063 when trying to "Copy definition to" on a ruleset Description: If a ruleset contains a numeric encrypted attribute in its condition, it fails to be copied to another revision using the "Copy defintion to" functionality. Safer Payments reports an error of invalid definition of condition in this ruleset element. Workaround: Copy the ruleset manually. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT381500 === END OF ISSUE === Title: FLI fatal error when synchronzing a defined risk list that contains encrypted numeric value in its filter criteria Description: If a defined risk list contains encrypted numeric value in its filter criteria, for example: the condition have expression for encrypted numeric attribute, this defined risk list fails to synchronize to the remote instance(s). A fatal error of "F 0480: ILLEGAL_NUMERIC_VALUE" is reported in the log for the remote instance(s). Workaround: No workaround available Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT381498 === END OF ISSUE === Title: Error when marking transaction Fraud in Simulation query results Description: A "Requested item not found" error is displayed when marking a transaction as fraud in the simulation query results. Although an error is displayed, the transaction does get marked as fraud. Workaround: No workaround available Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT380920 === END OF ISSUE === Title: Defined Risk List - Synchronization to remote instances prevented if CSV upload has non UTF-8 entries. Description:  Uploading a CSV with an invalid DRL entry with non UTF-8 characters gives the error on the screen "Converting to and from this character encoding is not supported." SP does not allow non UTF-8 characters from the CSV file being imported for adding the Defined Risk List entries, but the already added or overwritten Defined Risk List entries should synchronize to the remote instances, and currently only appear on the API primary instance. Workaround:  Please ensure the CSV file does not contain non UTF-8 characters before importing. For Risk Lists missing valid csv entries on remote instances, use maintenance function "rewrite risk list to cluster`" to ensure the valid entries in primary instance risk list get updated on remote instances.  Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT380842 === END OF ISSUE === Title: Risk Lists - Filter on column search will persist across risk-lists entries screen. Description: If you have a column filter on one risk list entries screen, and switch risk lists, the UI remembers the old search filter, even if the new risk list is not related. It could make some risk lists appear to be empty or missing entries. This can happen on filtering other tables as well, such as the logs table. Workaround: Press space and backspace to "reset" the column filter search, or navigate away and come back. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT380535 === END OF ISSUE === Title: Deleting a ruleset or moving rules when running a simulation rule or rule report query may cause a crash. Description:  A crash may occur on an instance when deleting a ruleset or moving rules in a challenger revision, while a simulation rule query or rule report query is running on the same revision. Workaround: Do not delete rulesets or move rules while simulation queries are being executed on the same revision. Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04, 6.7.0.00 Known Issue ID: DT380376 === END OF ISSUE === Title: A crash may occur on the remote instance when a rule report is executed on the remote instance. Description: If a remote simulation is disabled while running a rule report on a remote instance, there is a chance of encountering a crash. Workaround: Run the simulation on the API instance Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT380370 === END OF ISSUE === Title: Random date is displayed when clearing the date value for the first time on the case investigation page. Description: The generation/to date field on the case investigation page is not cleared the first time and displays a random date, the value is cleared in the second iteration. Workaround: N/A. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT380349 === END OF ISSUE === Title: An instance can crash if a save of case class report occurs during an execution. Description: If a user does a save and execute of a case class report and another save is triggered, a crash can occur on the instance in a rare timing issue. Workaround: Saving only once and waiting can lessen likelihood of the crash occurring. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT380188 === END OF ISSUE === Title: Revision Control - Compare Revision and Audit Trial can cause UI error if masterkey is changed. Description: Applying master key change does not refresh the revision audit trail on the file level. So if the instance is stopped before the audit trail is refreshed on file level (such as a GoLive), the audit trail file will remain encrypted by the old encryption key. This can lead to Status 200 UI errors that mention "auditTrail" as Safer Payments tries to decrypt the audit trial with the new key, but the file is still saved with the old key, for the encrypted attributes. Workaround: Contact Support to get instructions to change the affected Revision(s) Audit Trail iris files. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT380187 === END OF ISSUE === Title: Misleading results in simulation hyperlink queries. Description: In simulation hyperlink queries, if the sequence start of the index is out of the simulation data range or the query data range, the urid from where the hyperlink query is triggered, is considered the sequence start.  Workaround: None Status: Closed Affected Version: 6.5.0 Fixed Available: 6.7.0.00 Known Issue ID: DT380094 === END OF ISSUE === Title: Categorical attributes do not consider simulation conditions Description: In the rule designer table of rule generation, the indicators/categories of a categorical attribute are collected from each record within the simulation data range without consideration of the simulation conditions Workaround: None Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT380010 === END OF ISSUE === Title: Sequence loop is created when a single transaction meets the conditions of both a merging and a masterdata Description: When both a merging and masterdata are computed on the same transaction then a sequence loop error can happen. This can result in errors in the logs (F 0099 Sequence loop detected) as well as unexpected results in queries where the same transaction shows up repeatedly. This can only happen when the merging and masterdata are defined on separate mandators in the hierarchy. Workaround: Ideally the same transaction should not be able to trigger both masterdata and mergings. If it is necessary for both to happen on a single transaction a solution is to exclude that condition from the masterdata insertion/deletion condition and instead create a rule with a rule action that inserts/deletes the masterdata.After you have run into the issue, then you will need to perform an index sequence rebuild of the affected indexes in order to fix the issue. Please contact IBM support if you need support with this. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT379229 === END OF ISSUE === Title: Slow rule report and slow rule queries Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] When performing a rule report that has a ruleset with a high amount of rules, the rule report is getting slow. The same happens for rule queries too. Workaround: Copying the rule to an empty ruleset improves the performance of a rule report / rule query. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT379143 === END OF ISSUE === Title: [Cases] Audit trail comment not escaped through SMTP error Description:  The audit trail of the case doesn't correctly escape the comments. Workaround: Shutdown instance, fix the files and restart OR limit the audit trail, and reload the audit trail from disk. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT378978 === END OF ISSUE === Title: Loading XML or JSON file that contains the string "POST" via BDI may crash the instance Description: The inclusion of the string "POST" in an XML file being loaded by the BDI will cause the job to fail and the instance to crash. If the string "POST" is at the beginning of a new line in a JSON file being loaded by BDI, the job will also fail and the instance will crash. Workaround: No workaround available Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT378504 === END OF ISSUE === Title: Defined Risk List Entries with special characters are not deleted from remote instances. Description:  [SP 6.3.1.06, SP 6.4.2.05, SP 6.5.0.03, SP 6.6.0.00] When trying to remove risk list entries that contain special characters that need to be json escaped, the entries are just removed from primary instance but not from remote instances. Workaround: Run the maintenance function "rewrite risk list to cluster" on primary instance.Alternatively, disable rather than delete the risk list entry with special character(s). Status: Closed Affected Version: 6.6.0.00;6.3.1.06;6.5.0.03;6.4.2.05 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT378209 === END OF ISSUE === Title: Group by queries can show results with value 0, when it includes DDC data range, but "include DDC" is turned off Description: If you do a group by query on a numeric attribute such as an MTID, using a data selection range which includes the DDC portion of that attribute, and you turn off "include DDC", then your query result will have some records grouped with a "0" value, even if you don't have any "0" MTID values in your dataset. Workaround: Do not include the DDC range in your data selection, or turn on "Include DDC" Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT366158 === END OF ISSUE === Title: Golive can shutdown remote instances when user opens revision before copy is finished Description: When a user creates a copy of a revision, then in some rare cases this can take longer, and the revision can show up in the revision selection table before the copy is fully completed. In this case, if the user opens the revision before the copy is completed, and the revision was assigned for simulation to a non-API instance, then this can create a corrupted FLI message. Later, when the user tries to golive with this revision then the remote instances will shutdown to prevent data corruption. Workaround: Before the golive there will be a message F 0480 Error in FastLink configuration message, message discarded with error printed in the logs of the remote instances. In addition, if the champion revision which is being copied is assigned for simulation to the API instance then this issue cannot occur. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT365923 === END OF ISSUE === Title: Case attachments have a different file size on disk on different instances Description: After synchronization of case attachments, some case attachment files have more bytes on disk than the files that were uploaded. The files still have the correct file size when downloaded via API. Workaround: Use the API to download case attachments or truncate the files to the file size that is defined in the investigation case json or the one that is displayed in UI. Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT365772 === END OF ISSUE === Title: Random Forest Generator causes the instance to crash upon revision changes. Description: While Random Forest Generator (RFG) is stopping on a remote instance, if any revision changes are saved on the API instance, the instance running the RFG crashes if this RFG belongs to that revision that had saved changes. Workaround: Do not apply any revision changes on the API instance if the Random Forest Generator is still running or is not completely stopped on the remote instance. Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT365628 === END OF ISSUE === Title: Missing documentation of Extended Authentication if SMTP uses password Description: All passwords in Safer Payments are required to be stored encrypted, including the SMTP password set in the Cluster. The encrypted passwords can only be decrypted and used after key activation. Therefore, the extended authentication only works after key activation if SMTP uses password, and so users will be unable to login when the cluster is restarted and the encryption keys need to be entered. This information needs to be added in the documentation for Extended Authentication. Workaround: No workaround available Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT364139 === END OF ISSUE === Title: Extended Authentication - First login by user stays on login page instead of going to OTP page Description: When Extended Authentication is enabled (One Time Password - OTP), the first login by the user stays on the login page, instead of progressing to the OTP page to enter code. This could happen multiple times a day, such as each time the browser is opened and closed, if the user sessions are coming in through a Load Balancer/Proxy connection. Workaround: Press Login again, and then enter the OTP from the second email. Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT277055 === END OF ISSUE === Title: API request "markFraud" may override old records. Description: If the URID is larger than the last URID in the system, the request may overwrite some older existing records, and the response of the API returns OK instead of returning an error. Workaround: No workaround available Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT276336 === END OF ISSUE === Title: Malformatted_message_dump is always incomplete. Description: The content within the malformed message dump file is consistently incomplete and has not been useful for troubleshooting the issues. Workaround: N/A Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT276214 === END OF ISSUE === Title: Rule Report Query results page is inaccessible Description: It's not possible to access the rule report query results page if you attempt to run a rule report query "without context" from the rules form. Instead, it always redirects you to the simulation report page. Workaround: It is possible to get to the rule report page by clicking back a number of times, or by manually editing the URL Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT270505 === END OF ISSUE === Title: Request to check memory status causes fatal error on remote during startup. Description: Safer Payments sends the request via SCI to other instances to check memory status. A fatal error is generated if the remote instance has not read the mandator into the system. Workaround: N/A Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT270399 === END OF ISSUE === Title: Changing a notification's OCC from a higher to lower mandator can result in instance shutdown during golive. Description: This issue requires a sequence of events and is unlikely to occur normally. To start, you must originally have a notification which uses an OCC of a higher mandator, and you use that notification in a rule action on that higher mandator. Later you change the notification to use an OCC of a submandator, and then restart the remote instance(s). Afterwards, when you do a golive on that mandator, then the remote instance(s) will shutdown during the golive. Workaround: Ensure that you do not use any notifications with OCCs of lower mandators in rule actions of higher mandators. It is also not possible to golive if you have done a restart of your API instance since the notification's OCC was changed. Please contact IBM Support for assistance if you run into this issue. Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT270269 === END OF ISSUE === Title: Internal error at attempt to create manually Model component of type 'Internal random forest' Description: Attempt to create manually model component of type 'Internal random forest' fails. Model Components of type Internal Random Forest are supposed to be created as a result of the model training (the model can be trained from Modeling > Model Factory) and this option is not supposed to even show up here. Workaround: N/A Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT269766 === END OF ISSUE === Title: Saving a revision can cause a drop in the FLI tps rate Description: If there are lots of mandators and attributes defined in the cluster, then it can take a long time to compute attribute references for masterdata, . This may cause the FLI tps drops to 0 for some time, when saving a revision. Workaround: No workaround available Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT269755 === END OF ISSUE === Title: MDC/DDC capacity can round down to 0 when enabling retention by time. Description: When retention by records has a small attribute value stored in MDC/DDC, enabling retention by time with a higher value may cause the storage capacity to round down to zero invalidating the attribute definition and preventing a restart. The affected revision also cannot be copied and it will output an error. Workaround: Please contact IBM support for assistance to fix the issue. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT269683 === END OF ISSUE === Title: The SAI form cannot be saved if it has Email enabled with empty "From" field Description: The SAI form cannot be saved if this SAI has Email enabled but the "From" field is left empty, even though the default email address has been set in System Configuration -> Interfaces -> Email "from" address. Workaround: No workaround available Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT269505 === END OF ISSUE === Title: No XML / CSV export for common point query Description: When trying to export a common point query result, the csv or xml is always empty. Workaround: N/A Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261813 === END OF ISSUE === Title: A user associated with a lower mandator can't execute hyperlink queries associated with a higher mandator on the case investigation page Description: If you have a case class that has hyperlink queries which are associated with a higher mandator, then when a user from a lower mandator investigates the case, they will not be able to execute those hyperlink queries. The user from the lower mandator can only execute hyperlink queries from the same lower mandator (which means that the case class also must be defined on the lower mandator as well) Workaround: No workaround available Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261699 === END OF ISSUE === Title: Inconsistent validation of fraud/genuine value in fraud marking. Description: A record could be marked without assigning a fraud value if the fraud meta attribute does not have categories or the value is not marked using one of the category options. Workaround: Ensure that you have categories enabled for the fraud meta attribute, or ensure that a fraud value is always selected. Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT261601 === END OF ISSUE === Title: If Kafka OCC can't connect to a broker and a notification is sent, it continues to try to reconnect and creates Kafka error messages in the log file indefinitely. Description: When a Kafka OCC has a broker which can't be reached and a notification for this Kafka is sent, it will continually try to reconnect to the broker. It will continually print error messages in the logs, stating that it can't connect, and this can sometimes cause the system to hang. This issue persists even after disabling Kafka from AMI and notification. Workaround: Restart the system to stop the continuous error messages. Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT261594 === END OF ISSUE === Title: Export job restarts from beginning after being paused by end of day job. Description: If there is an export job running when the end of day (EoD) job initiates, this export job will be recessed until the EoD finishes. However once the EoD is finished the export job does not continue where it stopped, instead it is restarted keeping the original file with the records previously exported. This results in possible duplicate records. Workaround: Schedule export jobs to not start near the time of the end of day job, and ensure they finish well before. Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT261334 === END OF ISSUE === Title: PO10164: NON-EXISTING INSTANCE CAN BE KEPT IN "SEND VIA" SETTING IN OCC DEFINITION Description: The "send via" setting in OCC definition can have a non-existing instance defined. For example, an instance is set in "send via" setting and this instance is deleted later. This can cause     fatal error when such OCC is triggerred by notification or case action.                                                          Workaround: N/A                                                              Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT261216 === END OF ISSUE === Title: PO10136: FATAL ERRORS CAN BE GENERATED BY THE INCORRECT INDEX SEQUENCE TYPE OF A COUNTER. Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6]When you modify a counter and   change to a peer index and set to the sequence type to 'Target,'and then change the counter index to normal and Golive, the     sequence type would stay as "Target". Then loading the          transactions can result in errors during real-time computation.  Workaround: Create a new challenger, modify the counter to a peer index and select the sequence as source, re-select your correct index and then save and golive                                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT261215 === END OF ISSUE === Title: PO10159: DEADLOCK BETWEEN FLI, SCI, AND MQI ON AN INSTANCE. Description: A deadlock can occur if an FLI configuration update that        requires an instance to enter maintenance mode is received at   the same time that the SCI is handling a cluster update with MQ enabled on that instance.                                        Workaround: N/A                                                              Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT261214 === END OF ISSUE === Title: PO10131: CASE ACTION CANNOT PERFORM TEST WITH THE EMPTY OPTION Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] When trying to send a test case action, and selecting "Empty" under "Fill message from", then  an error dialog is shown saying "Cannot find case".              Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT261213 === END OF ISSUE === Title: PO10130: THE TIMESTAMP ATTRIBUTE PRODUCES INCORRECT RESULTS WHEN THE DATE FALLS BEFORE OR DURING A LOCAL TIMEZONE CHANGE. Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] Safer Payments sets the        timestamp values based on the local timezone set on Linux. Wrongvalue could be set to timestamp attributes in Safer Payments, ifthere were clock changes of that timezone in the past. For      example, if the date of the timestamp value sent to Safer       Payments is exactly during the timezone change, its value is setto 0 in Safer Payments which is the start of the epoch time. If the date of the timestamp value is before the date of timezone  clock change, there is an hourly difference between the actual  timestamp value and the value saved in Safer Payments.           Workaround: N/A                                                              Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT261212 === END OF ISSUE === Title: PO10118: SETOFFLINE DOES NOT PREVENT END-OF-DAY JOB FROM RUNNING Description: [SP 6.3, SP 6.4, SP 6.5] The "setOffline" request does not      prevent the EOD job from running. Therefore, the EOD can re-openindex files for purging, which may cause the index files to havean incomplete state. The "setOffline" request is only available for manual scripts and is not available via User Interface.      Workaround: Time the end-of-day job in a way that it doesn't run in parallelwith potential "setOffline" actions.                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT261211 === END OF ISSUE === Title: PO10142: ATTRIBUTE IS NO LONGER VISIBLE IN OTHER ELEMENTS IF IT DOESN'T EXIST IN A CHALLENGER REVISION Description: [ SP 6.3, SP 6.4, SP 6.5, SP 6.6] If there is a challenger that does not have an attribute which is used in any other element   like in query conditions, then the attribute is not displayed inthat element. For example, the challenger is a copy of an old   revision before the attribute was created.                       Workaround:  Golive the challenger which has this attribute and ensure that only the new challenger is copied from the champion. Otherwise, you can delete the challenger(s) without the attribute.          Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT261209 === END OF ISSUE === Title: PO10133: SAFER PAYMENTS CRASH DUE TO CASE ACTION WITH VALUES FROM QUERY Description: When sending a case action with values from a query, Safer Payments crashes while attempting to format the value (n/a) or Data Accessible only from DDC. Workaround:  If data is in DDC enabling "Include DDC" in the query would    prevent the crash. If some attributes contain n/a (Not in MDC   nor DDC) they should be left out of the column selection in the query.                                                           Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT261208 === END OF ISSUE === Title: PO10129: FATAL ERROR IN RANDOM FOREST Description: There is a fatal error during simulation and later during real-time computation of an  SP generated internal random forest when one of the categorical text attributes has no data during training. The error appears on remote instances immediately after golive and on all instances after copying a revision and performing a golive. Workaround: Re-generate the internal random forest and make sure that       categorical text attributes are never empty during training.     Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT261207 === END OF ISSUE === Title: PO10123: ERROR ON KPI AFTER LOGICAL GOLIVE AND END OF DAY JOB Description: When a KPI's chart is defined on the top mandator and the KPI has an attribute from sub mandator in its condition, after logical golive on the sub mandator and then end of day job the KPI will throw an error when computing the condition. Workaround: Disable the system configuration of Enable logical golive.       Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT261206 === END OF ISSUE === Title: PO10117: SETOFFLINE REQUEST CAN BE PERFORMED TWICE Description: There is no protection to run the "setOffline" request twice. Additionally, the 2nd run is taking much longer than the first one and can block the instance for a long time. The request is only available for scripts and is not available via User Interface. Workaround: Add checks to make sure that the "setOffline" request is not    performed twice before setting the instance online again.        Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT261205 === END OF ISSUE === Title: PO10109: THE INSTANCE MAY CRASH DURING GOLIVE BY A FATAL ERROR WHICH HAS AN ATTRIBUTE OF AN ORPHAN SEQUENCE IN THE INDEX. Description: [SP 6.2, SP 6.3, SP 6.4, SP 6.5]When an index is created, inclusion of an orphan sequence because of an incorrect         condition can lead to the generation of error message E 0063 in the log files, resulting in the instance crashing during the    go-live of that revision.                                        Workaround: Copy the revision and golive on the copied revision             Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT261203 === END OF ISSUE === Title: PO10166: AFTER REFRESHING OR PERFORMING ANY ACTION IN THE QUERY RESULT OF THE NEW UI, THE SORTED ORDER DOES NOT REMAIN CONSISTENT. Description: When sorting a column in an executed query result, then that    sorting order gets updated as default after performing some     actions or refreshing the query table.                           Workaround: Reapplying the sorting after taking any action on the record.    Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT261202 === END OF ISSUE === Title: PO10143: MISSING INPUT FIELD FOR OPERATOR "PREFIX EQUAL TO/NOT EQUAL" Description: The input field o select the number of bytes for "prefix [not] equal to" is missing in the user interface, so this value cannot be changed or configured for new conditions.            Workaround: None                                                             Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.X Known Issue ID: DT261201 === END OF ISSUE === Title: PO10125: GARANTE2 & GDPR ENTRIES ARE BEING LOGGED EVEN WHEN NO ATTRIBUTE IS ENABLED FOR EXTENDED LOGGING Description: [SP 6.4, SP 6.5, SP 6.6] Garante2 and GDPR logs are generated   even if all the attributes in the query have extended logging   disabled.                                                        Workaround: NA                                                               Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT261200 === END OF ISSUE === Title: PO10072: BACKTRACE WHEN ADDING CASE ATTACHMENT Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] There can be a         backtrace after adding a case attachment, if the case doesn't   has a current investigation user yet. This will also result in  not adding the case attachment properly to the case.             Workaround: NA                                                               Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261199 === END OF ISSUE === Title: PO10065: CRASH DURING END-OF-DAY JOB AFTER RESIZING SYSTEM TIME Description: [SP 6.2, SP 6.3, SP 6.4, SP 6.5] All instance in a cluster can  crash during end-of-day job after resizing the meta attribute   systemtime when logical golives are enabled and rules with      performance report are defined.                                  Workaround: Disable logical golives at least 24h before resizing the meta   attribute system time, so that the eod had run on all instances between disabling logical golives and resizing the meta         attribute system time.                                           Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT261198 === END OF ISSUE === Title: PO10046: RESET REFERENCE ATTRIBUTE WARNING SHOWING UP WHEN NO REFERENCE ATTRIBUTE FIELD IS VISIBLE IN COUNTERS Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] In counters, Reset     Reference Attribute warning can show up, even though the        reference attribute field is not visible at all. Also the       warning mentions "click confirm and the selection will be       removed", but the button name is not "Confirm" but "Delete".     Workaround: Click the "Delete" button on the popup and continue saving or   editing the form.                                                Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT261197 === END OF ISSUE === Title: PO10011: CASE CONSOLIDATION PERFORMANCE DEGRADES SIGNIFICANTLY WHEN THERE ARE MANY CLOSED CASES Description: [SP 6.3, SP 6.4, SP 6.5] It may take a long time to consolidate cases when there are many closed cases in the system. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01 Known Issue ID: DT261196 === END OF ISSUE === Title: PO10079: FATAL ERROR DURING ANALYSIS WITH "BITMARKER POSITION IS OUT OF RANGE" Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When running an        analysis that has a data selection for time absolute and still  receiving data while simulating, in rare cases, there can be a  fatal error that invalidates the simulation and analysis        results.                                                         Workaround: It is possible to run the same simulation again afterwards, the original simulation is invalid, but it should be possible to    re-run it. To ensure that the issue doesn't happen any more,    then simulate using with a data selection by record absolute.    Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261195 === END OF ISSUE === Title: PO10067: DELETING EXISTING OUTPUT VALUES FROM A LIST CORRUPTS OTHER OUTPUTS' CONDITION VALUES. Description: 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. Workaround: NA                                                               Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT261194 === END OF ISSUE === Title: PO10037: CASE INVESTIGATION NOT LANDING ON THE TOP OF PAGE Description: [SP 6.3, SP 6.4, SP 6.5] When opening a case for investigation, it doesn't land on the top of page and users have to manually   scroll up to the top.                                            Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT261193 === END OF ISSUE === Title: PO10015: CANNOT UPDATE THE CASE TYPE ADDITION FIELD FOR A CASE ACTION THAT TARGETS HTTP OCC Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When a user tries to   edit the content type addition field for multipart form data for a case action that targets HTTP OCC, the input field value is  updated to [object Object] every time by default and this field cannot be edited.                                                Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261192 === END OF ISSUE === Title: PO10040: FILLED INDEXES CANNOT BE POPULATED AFTER RESET Description: After an index has been filled, and then reset via the maintenance function, the next  loaded transactions will still not be able to insert new values in the index.                                                    Workaround: Increasing the index size of this index and golive.              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT261191 === END OF ISSUE === Title: PO10038: BACKTRACE DURING SHUTDOWN AFTER DELETING GROUP BY QUERY Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5, SP 6.6] When removing aGroup by Query that was just started, the group by query doesn'tget deleted and there will be a backtrace during shutdown.       Workaround: Wait at least 2 seconds after starting a group by query before  removing it.                                                     Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261190 === END OF ISSUE === Title: PO10031: BACKTRACE FILE INCOMPLETE IN RARE CASES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] The backtrace file is incomplete for long stack traces. Workaround: N/A.                                                             Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT261189 === END OF ISSUE === Title: PO10069: CALENDAR PROJECTION RESULTS MAY BE INCORRECT Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Projection results may be unexpected because of the following reasons:                 1. The projection result may be less than the already received  values for the respective period(s) in some cases               2. Calendar projections may be incorrect, as projection         calculation will not always take the newest timestamp into      account                                                         3. Calendar projections may be incorrect, if period intervals   are used, e.g. 0~3                                              4. Calendar projections may be incorrect, if weekly periods are used                                                             Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261188 === END OF ISSUE === Title: PO10021: CUSTOM MULTI-TAB IN CASE INVESTIGATION OVERLAPS CASE ACTION SECTION Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When using a custom    layout for a case class that also has a multi-tab layout, this  layout can overlap with a case action tab.                       Workaround: Place the multi-tab at the bottom so it doesn't overlap with the case action tab. Alternatively, click on the other tab to      re-focus and re-size the tabs for each case action.              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261187 === END OF ISSUE === Title: PO10010: CASE SELECTION TAKES LONG TIME TO FILTER WHEN THERE ARE MANY CASES Description: [SP 6.3, SP 6.4, SP 6.5] When many cases exist, case selection will take an extended amount of time to display the results, regardless of whether the maximum cases shown on selection table is set to a low value Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT261186 === END OF ISSUE === Title: PO10080: SAI - MEMORY CONSUMPTION AND PEAK MEMORY CONSUMPTION SHOW AS 0 IN RHEL 8 Description: Status alarm indicators display zero values. Workaround: Monitor memory consumption externally to Safer Payments.         Status: Closed Affected Version: 6.5.0 Fixed Available: 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT261185 === END OF ISSUE === Title: PO10028: MESSAGE SENT BY CASE ACTION SHOULD NOT CONTAIN ATTRIBUTE PLACEHOLDER Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] In case action template with attribute included in curly brackets as a placeholder,    such placeholder is normally replaced by the actual attribute   value when sending the case action. However, if the attribute   value is not stored in the case file and the hittingUrid is no  longer in the Cluster that has multiple instances, then it will just print the original placeholder with curly brackets.         Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT261184 === END OF ISSUE === Title: PO10097: MODEL FACTORY RANDOM FOREST DATA SELECTION COMPUTATION CANNOT BE STOPPED Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] If data selection for  training and verification data is being computed, random forest generation won't be able to be stopped. This can prevent golivesfrom going through.                                              Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT261183 === END OF ISSUE === Title: PO10052: DETACHING AN INSTANCE CAN CAUSE LATENCIES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] While detaching an     instance, FLI buffering and latencies can be experienced.        Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261182 === END OF ISSUE === Title: PO10088: THE BODY TEMPLATE OF NEWLY CREATED SMTP NOTIFICATIONS OR SMTP CASE ACTIONS ARE NOT SAVED Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When creating a new    notification or case action using SMTP OCC, the body template   set in the SMTP OCC is not saved in this notification when the  notification is first created.                                   Workaround: Edit the notification by adding the text in the body template   and then save it again.                                          Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261181 === END OF ISSUE === Title: PO10061: MEMORY CONTROL TAB ROLE PRIVILEGE STILL UNDER ADMINISTRATION TAB Description: [SP 6.2, SP 6.3, SP 6.4, SP 6.5] Memory Control tab was moved   from administrator tab in old UI to Cluster tab in new UI ,     while role privileges for memory control tab still under        administrator tab.                                               Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261180 === END OF ISSUE === Title: PO10008: DEFERRED WRITING THREAD START DELAYED AFTER STARTUP Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When an instance starts up, is set online or finishes a key change. In rare cases the FLI can start processing messages before the deferred writing thread is fully operational. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT261179 === END OF ISSUE === Title: PO09943: USERS WITHOUT THE "CASES" PRIVILEGE DON'T SHOW UP IN USER GROUPS DROPDOWN Description: [SP 6.3]                                                        Users who don't have the "Cases" privilege in one of their      mandators do not show up as selectable in the Users dropdown on the User Groups page.                                            Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261178 === END OF ISSUE === Title: PO09939: USERS WHO NO LONGER HAVE PRIVILEGE TO BE IN A USER GROUP ARE STILL COUNTED IN THAT USER GROUP Description: [SP 5.7, 6.0, 6.1, 6.2, 6.3]                                    If a user is in a user group, but their privilege changes so    that they can no longer be in that user group, then the 'Number of users' column of the user group will still represent them    being in the user group, but they will no longer be selectable  in the dropdown.                                                 Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261177 === END OF ISSUE === Title: PO09947: USING INTERCEPT CONDITION GIVES "THERE IS NO REALTIME INTERCEPT CODE WITH A CORRESPONDING INTERVAL DEFINED" ERROR Description: [SP 6.1, SP 6.2, SP 6.3] In some elements, for example reporting queries or data export jobs, the validation error "There is no realtime intercept code with a corresponding interval defined"  will prevent to save the condition when using an intercept value in the expression.                                              Workaround: Use an interval in the expression. If the desired value in the  expression is for example 1, use 1~1 as expression value.        Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261175 === END OF ISSUE === Title: PO09968: SAVE ICON IN CPP IS DISABLED IF THE USER IS DEFINED AT A SUBMANDATOR LEVEL Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Sub-level mandator user’s cannot add new CPP due to its save button is not working. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT261174 === END OF ISSUE === Title: PO09961: INVALID QUERY TIMESTAMP VALUE IS ACCEPTED AND CONVERTED TO SOME RANDOM NUMBER Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Safer Payments accepts invalid timestamp value in timestamp format, for example 99:99:99, and  converts it to a random number after the user presses tab or    click the mouse anywhere outside of time input field.            Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261173 === END OF ISSUE === Title: PO09946: MEMO CAN OVERFLOW INTO CASE ACTION PANEL IN CASE INVESTIGATION PAGE Description: [SP 6.3] Memo component overflows into case actions or case     transition panel in case investigation page in smaller screen   resolutions or display scaling (150%) on new UI.                 Workaround: Set display to 100% and maximize the browser tab.                Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261172 === END OF ISSUE === Title: PO09991: DEADLOCK FROM RUNNING RULE REPORT DURING REMOTE SIMULATION Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Running a rule report with context when there is an active remote simulation may lead to a deadlock on the remote instance. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT261171 === END OF ISSUE === Title: PO09967: FATAL ERROR WHEN DELETED USER PART OF FRAUD MARKING REPORT Description: 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. Workaround: Disable instead of deleting the user                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT261170 === END OF ISSUE === Title: PO09956: Possible latencies at beginning of MCI Bypass when deferred writing is enabled Description:  [SP 6.2, SP 6.3, SP 6.4] When bypass gets activated, for example when performing a golive, the initialization of the MCI bypass is not created immediately and my even take more than one second which can result in latencies for the transactions sent. Workaround: None                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.01, 6.6.0.00 Known Issue ID: DT261169 === END OF ISSUE === Title: PO09864: NON-READ ONLY BUTTONS ARE NOT WORKING IN READ ONLY FORMS Description: Buttons that should still be available in read only forms, e.g. the help button, are not working in any browser even though they appear as active.                                                          Workaround: No workaround available Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT261168 === END OF ISSUE === Title: PO09791: QUERY RESULTS - UNIT IN BRACKETS APPEARS INCORRECTLY IN SOME CASES. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The unit specified for an      attribute is taken from 'meta attribute' field instead of 'unit'field when displayed in the UI, which is misleading. In         addition, if no unit (ie. $) is set, the square brackets still  appear (empty inside, for example [ ] ), when they should not ifa unit is unspecified.                                           Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261167 === END OF ISSUE === Title: PO09828: CANNOT ARCHIVE CASE WITH DELETED ATTACHMENT IF THE INSTANCE WAS RESTARTED IN BETWEEN THE DELETION AND ARCHIVING Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] If a case has an attachment    that got deleted, the case cannot be archived after the instance is restarted as Safer Payments throws permission denied error  when trying to archive this case. This is only an issue if it is chosen to rename deleted files to .deleted instead of wiping   them.                                                           Error log example:                                              Cannot archive cases of mandator '':boost::filesystem::status:  Permission denied: ".deleted"                                    Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261166 === END OF ISSUE === Title: PO09882: CRASH WHEN PARSING TIMESTAMPS IN INCORRECT YYYYDDDHHMMSS FORMAT Description: A crash might occur if a broken timestamp in YYYYDDDhhmmss format, for example 2022000000000, is sent. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT261165 === END OF ISSUE === Title: PO09815: DOUBLET DETECTION ON REMOTE INSTANCE UNNECESSARILY LOADS DATA TO CDC. Description: Now, data loading when a doublet is detected is only performed on the primary instance. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT261164 === END OF ISSUE === Title: PO09857: UNABLE TO PERFORM CONTEXTUAL ACTIONS ON CASE HISTORY TABLE Description: In case investigation, actions like Followup and Close cannot be completed in Case History. Workaround: On SP 6.1 or earlier, use the old UI. On new UI, use the case   table provided in case selection/case search/working queues or  case investigation to perform transitions.                       Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT261163 === END OF ISSUE === Title: PO09818: SOME INPUT FIELDS OF NOTIFICATIONS/CASE ACTIONS IN THE USER INTERFACE ARE TOO SMALL BY DEFAULT Description: Fields that contain a message or body template are too small for most use cases. The user must manually resize them to be usable. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT261162 === END OF ISSUE === Title: PO09893: QUERY RESULT NUMBER OF RECORDS IS ROUNDED UP TO BE DIVISIBLE BY 20 Description: If the number of records is limited by a max records number that is not divisible by 20, the query result will show more records, as it rounds up to the next number that is divisble by 20.                              Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261161 === END OF ISSUE === Title: PO09808: ERROR 227 WHEN DELETING SEVERAL MULTI VALUE MASTERDATA VALUES INPARALLEL Description: Broken multivalue masterdata is erroneously detected during data deletion. Workaround: If possible, configure the endpoint of the incoming interface   through which the deletion message is received to use only one  thread. If a job is used, configure only one thread for the job. Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT261160 === END OF ISSUE === Title: PO09916: MODELING ATTRIBUTES ROWS STAY SELECTED IN UI AFTER ACTION AND EVEN AFTER OPENING ANOTHER CHALLENGER Description: [SP 6.2, SP 6.3, SP 6.4] When making changes in modeling        attributes, for example multi selecting an attribute and        enabling it for simulation, the attribute will still be         selected after the action is performed. It will also still be   selected, if another challenger is opened in the same tab.       Workaround: Unselect all rows after the table action was performed.          Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261159 === END OF ISSUE === Title: PO09700: ADD AN ALERT TO INFORM USER GOLIVE IS WAITING ON MODEL GENERATION Description: [SP 6.1, SP 6.2, SP 6.3] When model generation training is      running, it is not possible to finish a GoLive. A check needs to be added if there is currently a model generation running, that would need to finish, in order for the GoLive to proceed.      Currently, the user just has to wait without knowing why the    GoLive does not complete.                                        Workaround: N/A                                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261158 === END OF ISSUE === Title: PO09547: AN INSTANCE COULD CRASH IN RARE CASES WHERE OPERATING SYSTEM COULD NOT CLOSE PREVIOUSLY OPENED FILE. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] An instance could crash in rare cases when operating system was able to open a file,   but then could not close it properly for some reason. SP would  print a log message 0 in that case but since this log message is disabled in most production systems no trace of the error is   left in the logs.                                                Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261157 === END OF ISSUE === Title: PO09742: DOCUMENTATION - REMOVE "MANUAL RESTORE" SECTION FROM ONLINE HELP. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Manual restores are    risky and not officially supported as we cannot guarantee data  integrity. This will be removed from documentation/online help.  Workaround:  Please do not manually restore a production system, use        built-in "Restore" function to ensure data integrity.            Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261155 === END OF ISSUE === Title: PO09692: EXTERNAL MODEL CREATION FAILS DUE TO INCORRECT UI VALIDATION Description: [6.2.1.05, 6.3.0.02] When saving a new external model with all  intended required fields filled, the UI says there are errors   that need to be resolved.                                        Workaround: Send the external model save request via the API directly,      instead of through the UI                                        Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261154 === END OF ISSUE === Title: PO09738: THE COUNT OF SELECTED RECORDS IS NOT SHOWN IN THE QUERY RESULT TABLE Description: Number of selected items is not shown in query result table. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT261153 === END OF ISSUE === Title: PO09682: THE REMOTE WAIT FACTOR IS TO BE REMOVED FROM THE RECREATE INDEX JOBS FORM Description: Removed the remote golive factor from the re-create index job page. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT261152 === END OF ISSUE === Title: PO09641: POSSIBLE CRASH WHEN RE-ENABLING MCI AFTER ENTERING MAINTENANCE MODE WHILE MCI IS DISABLED BUT BYPASS ENABLED Description: [SP 6.2, SP 6.3] A crash might happen when bypass is enabled but MCI is disabled and an action is performed that would trigger  the bypass to send transactions to another instance in case MCI was enabled, for example a golive. There is also a small chance that the crash occurs when MCI was enabled but got disabled     while the instance is still performing the bypass. The crash    will only occur once the MCI gets enabled again after the       described scenarios.                                             Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261151 === END OF ISSUE === Title: PO09623: MERGINGS WITH RECOMPUTATION ENABLED FOR OLD URIDS CAN CAUSE HIGHLATENCIES WITH DEFERRED WRITING ENABLED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] The mergings with      recomputation enabled have to access the DDC directly if they   are recomputing old records that are not within the deferred    writing time gap. Together with the disk access of the deferred writer, this slows down other transactions storing to disk as   the deferred writing can cause the direct ddc writing to stop   for quite a considerable time ~2-3 seconds.                      Workaround: Increase the time gap if most of mergings with recomputation    enabled are within a few minutes of the deferred writing gap.   However, this would not be feasible if they are hours apart.     Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261150 === END OF ISSUE === Title: PO09774: POSSIBLE CRASH IF MEMORY ALLOCATION FAILS WHEN GENERATING HTTP RESPONSE Description: [SP 6.1, SP 6.2, SP 6.3] A safer payments instance could crash  if the allocation of memory fails when generating an response   for an HTTP request. This only happens in rare cases, if the OS cannot provide the requested memory.                             Workaround: Ensure the system has adequate available memory/swap.            Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261149 === END OF ISSUE === Title: PO09739: CASES TABLE IN MY WORKING QUEUES IS NOT REFRESHED AFTER PERFORMING A BULK TRANSITION Description: [SP 6.1, SP 6.2, SP 6.3] The investigation cases table in my    working queues is not automatically refreshed after performing a bulk transition.                                                Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261148 === END OF ISSUE === Title: PO09640: DDC / MDC CAPACITY CANNOT BE SET TO A VALUE GREATER THAN 2,147,483,647 IN THE NEW UI Description: [SP 6.1.0.10, SP 6.2.1.05, SP 6.3.0.02] In the new User         Interface, the DDC / MDC capacity cannot be set to a value      greater than 2,147,483,647.                                      Workaround: None                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT261147 === END OF ISSUE === Title: PO09557: MULTILINE TITLE OR EXPLANATION FIELD IN THE COMPLIANCE LIST IS TRUNCATED WHILE DISPLAYING ON THE UI Description: 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 popup. The appearance of the popup for entry details is inconsistent across several pages. Workaround: Edit the compliance list to change the multiline text into a    single line.                                                     Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT261146 === END OF ISSUE === Title: PO09563: CLUSTER CHANGE WITH MQ CONNECTED BUT NOT ACTIVE CAN BE DELAYED. Description: [SP 6.2, SP 6.3] Cluster operations can take longer when MQ is  connected but not used. For example, you change API from Node1  to to Node2. The status would not update on cluster page until  MQGET timeout is hit or a new message is received.               Workaround: Change MQGET Timeout to 60000ms (1 minute) or wait for a new MQ message.                                                         Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261145 === END OF ISSUE === Title: PO09350: CORRUPTED FLI MESSAGE WHEN THE EXTERNAL SYSTEM PROXY IS ENABLED AND MCI MESSAGE HAS MORE THAN 9999 CHARACTERS Description: [SP 6.2] If the external system proxy is enabled and the MCI    message that triggers the external callout has more than than   9999 characters, the computation thread calculates a malformed  FLI message. This FLI message will not be synchronized to other instances in the Cluster and a fatal error will be logged:        F 0355 Outgoing FLI buffer corrupted.                          Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261144 === END OF ISSUE === Title: PO09222: CANNOT SELECT PEER INDEXES TARGET ATTRIBUTE AS REPORTING ATTRIBUTE FOR AUDIT TRAIL AND HISTORY Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2] In case investigation you      cannot select peer indexes target attribute as reporting        attribute for audit trail and history.                           Workaround: Create a separate index that uses target as source and source   as target. Then you can select the other attribute in the case.  Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261143 === END OF ISSUE === Title: PO09307: MCI CANNOT HANDLE REQUEST WITH EMPTY BODY (NO RESPONSE) Description: [SP 6.2 ] When a message is being sent to SP with an empty http body, SP won't return a response and keep the connection        blocked until the sending site cancels it.                       Workaround: Include any message body. For a status request online help      suggests a message body although, any body works.                Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261141 === END OF ISSUE === Title: PO09270: NUMERIC ATTRIBUTE WITH EMPTY VALUE IS SHOWN AS BLANK INSTEAD OF (0) IN NEW UI Description: [SP 6.0, SP 6.1, SP 6.2] In the new User Interface, if a numeric attribute in the format of (decimals with digits) has any empty values, such values are displayed as blank. In the old User    Interface, they are displayed as (0).                            Workaround: N/A                                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261140 === END OF ISSUE === Title: PO09265: USER MEMORY CONSUMPTION IS NOT UPDATED WHEN ANOTHER USER TAKES OVER A SIMULATION ON A REMOTE INSTANCE Description: [SP 6.1, SP 6.2] When a simulation is started on a remote       instance (an instance other than the API) the memory            consumption is allocated for the user that had the revision     reserved at that point. When a different user takes over the    revision the memory consumption is not updated for the users,   to represent the new ownership                                   Workaround: Do not takeover revision when simulation is started on a remote instance (an instance other than the API).                       Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261139 === END OF ISSUE === Title: PO09333: DOCUMENTATION UPDATE - CLARIFICATION ON HOW KPI IS UPDATED. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.2.1] Documentation will   be updated to add:                                              For mergings that recomputes a target, the                      values from the target record will be used for transaction      message rate KPIs. So in case a KPI has conditions on MTID for  example, the merging source will be counted for the recomputed  target's MTID.                                                   Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261137 === END OF ISSUE === Title: PO09247: REFRESH INDEX OR HYPERLINK QUERY DOES NOT RETURN RESULTS Description: [SP 6.2] Refresh hangs whenever executed for hyperlink / index  queries. This happens after marking fraud or when using the     refresh button.                                                  Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261136 === END OF ISSUE === Title: PO09133: MISSING POPUP MESSAGE IN THE NEW UI, WHEN COPYING A CHALLENGER REVISION THAT IS RUNNING SIMULATION ON REMOTE INSTANCE Description: [SP 6.0, SP 6.1, SP 6.2] The new User Interface doesn't popup a message telling the user why a challenger revision that is      running simulation on remote instance cannot be copied.          Workaround: Wait for the simulation to complete.                             Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261135 === END OF ISSUE === Title: PO09419: THE PENDING OCC MESSAGES SHOULD BE DISCARDED IMMEDIATELY IF THE USER CHOOSES TO STOP PENDING MESSAGES WHEN DISABLING THE OCC Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] If the user chooses to stop pending messages when disabling the OCC, all pending       messages from this OCC should be discarded immediately, instead of waiting for its corresponding AMI interface being enabled    first.                                                           Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261134 === END OF ISSUE === Title: PO09413: TOOLTIPS ARE NOT CLOSING ON DISABLED INPUT FIELDS Description: [SP 6.1, SP 6.2, SP 6.3] After opening the tooltip it's not     closing on disabled input fields                                 Workaround: None                                                             Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261133 === END OF ISSUE === Title: PO09436: "CLOSE DURING END-OF-DAY JOB" OPTION IS DUPLICATED IN OLD UI. Description: This behavior is specific to SP 6.1.0.08 only. While old user   interface is enabled, Message Command Interface option "Close   during end-of-day job" is duplicated.                            Workaround: Use new UI or keep both options in sync.                         Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261132 === END OF ISSUE === Title: PO09414: CASE AUDIT TRAIL SHOWS CASE ACTION FAILED ENTRY ON DELIVERY SUCCESS IF THE EARLIER ATTEMPT FAILED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] If a case action was   successfully delivered after an earlier attempt had failed,     another case action failure message is created in the case audit trail including the reason for the previous failure.            Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261131 === END OF ISSUE === Title: PO09400: ONLINE HELP AND UI WILL HAVE BLACKLIST/WHITELIST LANGUAGE UPDATED. Description: [SP 6.2, SP 6.2.1] In an effort to remove inflammatory language all instances of the terms blacklist/whitelist will be replaced with blocklist/allowlist in the UI/Documentation.                Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261129 === END OF ISSUE === Title: PO09223: CRASH WHEN EXPORTING CASES WHILE WORKING QUEUE GETS UNASSIGNED FROM CASE Description: In rare situations, a crash occurs if a case is exported from a cases table while the working queue is unassigned from it, for example, because a user starts investigating the case. Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT261128 === END OF ISSUE === Title: PO09043: HELP PAGE FOR COMPUTATION CONDITIONS>COUNTER SECTION, DISTORTED IMAGES ARE DISPLAYED IN NEW UI Description: [SP 6.0, SP 6.1, SP 6.2]                                        When opening help page for Computation                          Conditions under the counter section, distorted images are      displayed. This only affects the new UI.                         Workaround:                                                                  Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261127 === END OF ISSUE === Title: PO09006: FREQUENT LOG MESSAGES 781 THAT INDICATE THE CHANGE OF INSTANCES' STATUS TO UNREACHABLE THEN BACK TO THE ACTUAL STATUS. Description: [SP 6.2] The heartbeat service set with not large enough        threshold frequently reports the instances status change to     unreachable then back to the actual state. This could           potentially lead to KMI become active on the instance that      receives the unreachable status but this behaviour was not      observed so far.                                                 Workaround: Set the threshold to a larger value than 3 times the heartbeat  period.                                                          Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261126 === END OF ISSUE === Title: PO09125: SOME ITEMS COULD BE PUSHED PAST WEBPAGE MARGINS ON NEW UI. Description: [SP 6.1, SP 6.2, SP 6.2.1] For example, on Conditions and       Conclusions when the screen resolution is low or the browser is shrunk, the item is pushed into the next line and eventually    past the right webpage margins.                                  Workaround: Use SP on full-screen on the recommended 1920x1080 or minimum   1280x768 resolutions to prevent most of these scenarios from    occurring.                                                       Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261124 === END OF ISSUE === Title: PO09192: "TEXT NOT FOUND" MESSAGES APPEAR IN WEB BROWSER CONSOLE ON NEW UI. Description: [SP 6.1, SP 6.2, SP 6.2.1] Various "Text not found" messages    appear on web browser console when navigating pages in the new  UI. There is no actual text missing, but an attempt to          translate already translated/non-existing text on each page.     Workaround: Ignore the message as it is misleading.                          Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261123 === END OF ISSUE === Title: PO09114: VIEW ATTACHMENT IN CASE SELECTION RESULTS IN "CANNOT DISPLAY IMAGE" ON NEW UI. Description: The preview for case investigation attachments does not display images. Workaround: Use Download Attachment to view the image, or use a custom http header with Accept blob: in the img-src header in               Configuration. For example: img-src 'self' 'unsafe-inline'      data: blob:;                                                     Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT261122 === END OF ISSUE === Title: PO08907: STOPPING SIMULATION SHORTLY BEFORE COMPUTATION COMPLETION CAN CAUSE A 'SEGMENTATION FAULT' INSTANCE SHUTDOWN. Description: [SP 6.1] This particular Segmentation Fault occurs in a rare    situation when a user stops the simulation very shortly before  the simulation computation is completed. This will be addressed in a future fix pack.                                            Workaround: Workaround: Instruct users not to stop simulations shortly      before the end of their computation.                             Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261121 === END OF ISSUE === Title: PO09108: ENCRYPTED ATTRIBUTES IN PRE DEFINED CONDITIONS OF RULE GENERATOR MAY PREVENT INSTANCE START UP Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2] In the internal definition of  the rule generation, the pre defined conditions are written     twice. When a condition includes an encrypted attribute the     first pre defined condition has the uid not encrypted. While the second one will have that attribute encrypted. This is causing reference issues and preventing the instance from starting up.  Synchronising such definition to the remote instances will be   rejected so it is only an issue on the API instance.             Workaround: Do not use encrypted attribute(s) in rule generation condition.  Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261119 === END OF ISSUE === Title: PO08966: POTENTIAL CRASH WHEN SAVING REMOTE JOB WHILE IT'S RUNNING Description: When BDI is on remote instance, the remote instance may crash   when saving a load file job while the job is running.            Workaround: Do not save a load file job while it is running                  Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261117 === END OF ISSUE === Title: PO09200: POSSIBLE FOR SETTINGS VALUES TO BE SAVED INCORRECTLY WHEN CLICKING MULTIPLE TIMES ON SAVE BUTTON. Description: [SP 6.1, SP 6.2] On the system configuration settings page it's possible to have certain values (FLI buffer quotas, password    validity, case investigation 'archive cases after' and 'clear   reporting atttributes caches after') be saved incorrect by      clicking multiple times on the save button.                      Workaround: Do not click multiple times on the save button when saving the  settings page                                                    Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261116 === END OF ISSUE === Title: PO09155: INSTANCE MAY SHUT DOWN DURING GOLIVE WHEN COMPLIANCE LIST IS DELETED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2] When a user deletes a offline  compliance list, which is still reference in a "Evaluate        sanction list" job, there will be a possible shutdown of the    API instance after a golive of the mandator which the sanction  list and job belong to - as long as the job is not deleted yet  or the reference is not removed from the job.                    Workaround: Make sure when you delete a sanction list, it's not referenced  by any job. If it's the only list referenced in the job, delete the job. If there are other references in the job, please make  a small change to the job (like appending a "." to the comment  field) and save the job again to remove the reference from      internal structures.                                             Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261115 === END OF ISSUE === Title: PO08991: [RULE GENERATION] -ERROR WHEN OPENING DATA SELECTION OF RULE GENERATION AND NO META ATTRIBUTE TIMESTAMP OR ACCOUNT Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2]                                In challenger, when either the                                  meta attribute timestamp or the meta attribute account are      missing, when clicking Data selection in Rule generation, a     segmentation fault error is displayed in a popup.                Workaround: Add the missing meta attribute type (timestamp or account)       Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261114 === END OF ISSUE === Title: PO09202: DEFERRED WRITING THREAD IS BEING INTERRUPTED AFTER LOGICAL GOLIVE Description: [SP 6.2] The deferred writting thread is interrupted after a    logical golive is performed. The deferred writing will not take place anymore after the logical golive.                          Workaround: Disable logical golives to not run into this issue at all. In   case you already did a logical golive, disable logical golives  and do another dummy golive which will be a structural golive   that will make deferred writing start again after it completed.  Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261113 === END OF ISSUE === Title: PO09201: DEFERRED WRITING HEAVILY IMPACTS CALENDAR COMPUTATION Description: [SP 6.2] When deferred writing is enabled and calendars are     defined, this leads to high latencies in calendars.              Workaround: Do not use deferred writing in combination with calendars.       Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT261112 === END OF ISSUE === Title: PO08967: OCC QUEUED MESSAGES MAY RESULT IN OOM WHEN AMI IS NOT ENABLED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2] SP queues OCC messages, if the AMI is not enabled for that OCC to send it later when it is     enabled. Messages can build up indefinitely in the queue until  an out of memory exception happens.                              Workaround: Disable the OCC (Cluster tab > outgoing channel configurations  >select the OCC > enabled), or enable the AMI HTTP message from the cluster page.                                                Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261111 === END OF ISSUE === Title: PO09020: CHANGED USER PERMISSION TO SEE THE MASKED DATA NOT REFRESHED. Description: [SP 6.2, SP 6.2.1] In the new UI, under the User Management     section, there are 3 options to control the user access to see  the Masked data. You are still able to change the value but it  appears that the value was not changed in the UI.                Workaround: Workaround: SP does not refresh the UI correctly, so when you   choose new value you still see the old one. However, if you     just press save then refresh you will now see the new value     (ie. "may see clear values") you had tried to select was        actually saved.                                                  Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261110 === END OF ISSUE === Title: PO08906: Online help documentation missing for "Create conclusion expression pair list" and "Rewrite risk lists" Description: To see the missing documentation: Go to Administration > User Accounts > Click on User > Scroll Down to Maintenance Functions > Click HELP Icon. Please note: This maintenance function was created for a specific customer request and is not used normally. Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT261109 === END OF ISSUE === Title: PO09009: CONFIGURABLE NIL VALUES DON'T ALLOW ENOUGH CHARACTERS FOR TIMESTAMPS Description: [SP 5.7, SP 6.0, SP 6.1, S.P 6.2] When validating the number of characters for configurable timestamps SP currently only allows 16 characters. For example, when you set Cluster "Outgoing      Channel Configuration (OCC)" setting for "Nil value timestamp"  to "Configurable", and then set the value of the "Custom nil    value timestamp" to "1900-01-01 00:00:00", you will get a red   warning that "The length of this entry must be smaller than or  equal to 16".                                                    Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261107 === END OF ISSUE === Title: PO09002: MISSING TIME IN CONDITION CONSTANT EXPRESSION SHOULD BE MENTIONED IN THE ONLINE HELP. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2] In conditions that take an     expression as a timestamp (date-time), if the time is omitted,  for example 2020-09-18, SP will append 12:00:00 to it and       becomes 2020-09-18 12:00:00. This can be counter-intuitive in   case of less/greater than operations, which might be confusing  to the user. An explicit mention for this behavior is missing   from the online help.?                                           Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261106 === END OF ISSUE === Title: PO09000: CRASH WITH HARD TIMEOUT FOR PYTHON CODE EXECUTION Description: [SP 6.1, SP 6.2 SP 6.3]                                         If Python code execution is used with a                         hard timeout, the application may crash if the python function  actually times out. Probability for the crash is very high.      Workaround: Use soft timeouts instead of hard timeouts when using python    funtions                                                         Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261105 === END OF ISSUE === Title: PO08852: SIMULATION QUERY PAGE REFRESHES PERIODICALLY AFTER SIMULATION FINISHED Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0 (old UI), SP 6.1 (old   UI)] Simulation query page is automatically refreshed           periodically, even after the simulation has finished.            Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261104 === END OF ISSUE === Title: PO08829: CRASH WHEN SENDING REQUEST GETRULEGENERATIONEXPLORE WHILE NO RULE GENERATION RESULT EXISTS Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1, SP 6.2] The    instance crashes when it handles request                        "getRuleGenerationExplore" while the revision doesn't have any  rule generation result.                                          Workaround: Make sure that the revision has rule generation result before   sending the request "getRuleGenerationExplore".                  Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261103 === END OF ISSUE === Title: PO08784: Levenshtein percentage field does not accept decimal numbers Description: [SP 5.7, SP 6.0, SP 6.1]                                        In compliance lists when activating Levenshtein percentage, the field only takes whole numbers.                                  Workaround: In vesion 6.0 and above, use the new User Interface to insert   decimal numbers.                                                 Status: Open Affected Version: 5.3.0 Fixed Available: No fixed available Known Issue ID: DT261102 === END OF ISSUE === Title: PO08659: DOCUMENTATION: MISSING ONLINE HELP FOR SETTING STOP COMPUTATION Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] Online help for data export job does not mention the   "stop computation" option.                                       Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261101 === END OF ISSUE === Title: PO08841: PRE-PROCESSING RULESET/RULE ARE MISSING IN MESSAGE COMPUTATION FLOW CHART IN ONLINE HELP Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2] The Message Computation flow   chart in online Help needs to be updated to include the process of pre-processing rulesets/rules.                                Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261100 === END OF ISSUE === Title: PO08842: DELETING PROFILING (OUTPUT) IN CHALLENGER CAUSES DISPLAY ISSUE IN CHAMPION CONDITIONS. Description: [SP 6.1] If a profiling or its output is deleted in a           challenger revision, references of the output attribute in      conditions in the champion revision cannot be displayed         anymore. It does not affect the computation of the champion but is only a display issue.                                         Workaround:                                                                  Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261099 === END OF ISSUE === Title: PO08827: MERGING CAUSES SEGMENTATION FAULT ON NEW UI AFTER SWITCH FROM INDEX A TO B. Description: [SP 6.1] Merging causes Segmentation fault on new interface     after switch from Index A to B. This can be reproduced by the   following steps. On the new user interface create merging with  an index A and save. Then, change the index in merging to       another index B and save. Afterwards merging will use index B,  but attribute from index A. The error received is: Safer        Payments is shutting down with error: "Signal 'Segmentation     fault' received. Exiting"                                        Workaround: Workaround: The merging can afterwards only be fixed by         switching to old user interface and saving the merging there,   then doing a go-live. Or by creating a new merging in new user  interface from scratch, with the same settings and the index as desired, then delete the old merging.                            Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261098 === END OF ISSUE === Title: PO08777: DATA NOT WRITTEN TO DISK AFTER RECOMPUTE WHEN DEFERRED WRITING HAS ALREADY WRITTEN THE URID Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] When re-computing a target transaction after a merging, transactions that were already written to DDC in a previous    deferred writing cycle, will not be written to disk again. Thus, attribute values that were set during re-computation, for      example by applying rules or computing profiling elements, may  not be written to DDC.                                           Workaround: Make sure time gap is configured correctly to cover mergings.   URIDs that are not written to DDC until the merging is applied, are not affected.                                                Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261097 === END OF ISSUE === Title: PO08769: RISK LIST ENTRY LAST UPDATE INFO NOT UPDATED ON REMOTE Description: [SP 5.6, SP 5.7, SP 6.0, SP 6.1] When a risk list entry is      updated, its "Last Changed by" and "Last Changed on" are not    updated on the remote instance(s) in the Cluster.                Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261096 === END OF ISSUE === Title: PO08767: VERY RARE CRASH AFTER SESSION TIMEOUT Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6] When working   with multiple tabs and waiting for the session to expire while  having at least one "investigation case" still open in the      browser, it was possible, in very rare cases, that the          application crashed.                                             Workaround: N/A                                                              Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT261095 === END OF ISSUE === Title: PO08751: NULLPOINTER ERROR AND POTENTIAL CRASH WHEN MANUALLY DELETING INDEX ENTRY WITH NO SEQUENCE Description: [SP 6.1] Deleting an index entry of an index that has no        sequence via masterdata query can cause nullpointer error and   may potentially crash the API instance or remote instances in   rare situation.                                                  Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261094 === END OF ISSUE === Title: PO08836: Future timestamps may lead to inconsistent calendar periods after golive/restart Description: [SP 6.3, SP 6.4, SP 6.5] If there was a future value for meta   attribute timestamp, subsequent golives or restarts can cause   instances to have different periods (future periods vs expected periods). As a result, the upcoming calendar outputs may producedifferent results on different instances. If you notice such    differences, contact support for counter measures.               Workaround: It is a general requirement for calendars to work correctly to  avoid the risk of future timestamps which can be done by        enabling the setting 'discard future timestamp'. By having this setting activated, there is no risk of running into this issue  and it avoids the general risk of future periods which always   have a negative impact on computation.                           Status: Closed Affected Version: 5.7.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT261093 === END OF ISSUE === Title: PO08762: CHANGING AN AD-HOC QUERY TO INDEX TYPE RIGHT AFTER ITS EXECUTION MAY CAUSE FATAL ERROR ON REMOTE INSTANCES Description: [SP 5.7, SP 6.0, SP 6.1] If an ad-hoc query is changed to index type right after it was previously saved and executed, there may be fatal error of CANNOT_RESOLVE_INDEX on the remote instances when try to save such change, although the index used in the    query definition does exist on remote instances.                 Workaround: Re-save this query definition.                                   Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261092 === END OF ISSUE === Title: PO08757: NO EXTERNAL SQL FILE IS CREATED WHEN MANDATOR CONTAINS RESERVED CHARACTER(S) FOR FILENAME Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] If a mandator  name contains reserved characters for filename and if this      mandator has relational database interface enabled, there won't be sql file generated. This is because the SQL files generated  have the name "sp_transaction_data_i_m_YYYY-MM-DD_hh-mm-ss.sql" where i is the IBM Safer Payments instance id, m is the name of the mandator and YYYY-MM-DD_hh-mm-ss is the timestamp the file  was generated. The reserved character(s) in the name of the     mandator is preventing such a file from being generated.                                                                        A list of reserved characters for filename can be found at:     https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words                                                             Workaround: Avoid using any reserved characters in Mandator name.            Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261090 === END OF ISSUE === Title: PO08885: POTENTIAL CRASH WHEN LOGGING IN VIA SINGLE SIGN ON WITH KERBEROS. Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1, SP 6.2] The    system can potentially crash when a user logs in via single     sign on with setting 'local then ldap' using kerberos.           Workaround: If the system crashes during login, setting 'use single sign    on' should be disabled.                                          Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261089 === END OF ISSUE === Title: PO08815: INSTANCE CRASH WITH PYTHON 3.5 WHEN WRITING TO TEXT ATTRIBUTE Description: [SP 5.7, SP 6.0, SP 6.1] The instance crashes when using Python 3.5 to write to an attribute in a conclusion that has data type text. There is no such issue with using Python 2.6 or 2.7.       Workaround: Use Python 2.6 or 2.7.                                           Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261088 === END OF ISSUE === Title: PO08789: CHANGING ATTRIBUTE NAME DOES NOT CHANGE RDI ATTRIBUTE NAME APARNOPUB Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] RDI uses the old       attribute name even after the attribute name has been changed in a model revision and a golive has been performed.               Workaround: Create a new Challenger revision by copying the Champion        revision, make no change in this challenger revision and golive it.                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261087 === END OF ISSUE === Title: PO08782: THE RDI DOES NOT OUTPUT FILES ACCORDING TO THE FILE CREATION INTERVAL SETTING WHEN DEFERRED WRITING IS ENABLED Description: When deferred writing is enabled, the RDI output file is only   written once per cycle instead of every x seconds as configured in the RDI file creation interval setting.                       Workaround:                                                                  Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261086 === END OF ISSUE === Title: PO08748: CRC32 PRE-PROCESSING MAY PRODUCE INCONSISTENT VALUE WHEN SENDING MULTIBYTE CHARACTERS THAT EXCEED DEFINED LENGTH BYTEWISE Description: [SP 5.6, SP 5.7, SP 6.0, SP 6.1] Mapping pre-processing Crc32   has a length field which currently defines the number of        characters used for creating a hash from a string. A hash may be created based on a value that exceeds the defined length       bytewise when sending multi byte characters and the sent value  has more bytes than the defined length of the pre-processing.    Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261085 === END OF ISSUE === Title: PO08738: FRAUD MARK TIMESTAMP NOT SET IF ATTRIBUTE IS NOT DEFINED IN ROOT MANDATOR Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] When manually marking fraud, the fraud mark timestamp  can only be stored on attributes defined at root mandator       level.                                                           Workaround: When manually marking fraud, select a fraud mark timestamp      attribute that is defined in the root mandator.                  Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261084 === END OF ISSUE === Title: PO08753: [LISTS] - CANNOT SAVE LIST WITH NEGATIVE NUMERIC OUTPUT VALUE. Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] It is not      possible to save lists with negative values, when the output    attribute is numeric.                                            Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261083 === END OF ISSUE === Title: PO08709: POSSIBLE CRASH IN RULE GENERATION WHEN USING ATTRIBUTE INTERVALS Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] The application may crash during rule generation in    case an attribute is included in rule generation that has       attribute usage intervals and either the same From and To value or a Step that exceeds the interval.                             Workaround: Define interval attribute modellings in a way that ((To - From) / Step) is equal to or greater than 1.                           Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261082 === END OF ISSUE === Title: PO08731: WRONG ONLINE HELP FOR "LOCKDOWN" STATUS. Description: [SP 6.0, SP 6.1] The online help for the "lockdown" status is   wrong. Instead of restoring the lockdown instance, it is        required to restore all other instances from the lockdown       instance.                                                        Workaround: N/A                                                              Status: Closed Affected Version: 6.0.0 Fixed Available: No fixed available Known Issue ID: DT261081 === END OF ISSUE === Title: PO08859: RE LOGIN AFTER LOGOUT IN THE SAME SCREEN DOESN'T WORK WITH OIDC SSO. Description: [SP 6.0, SP 6.1] When using single sign on with OIDC and proxy  url after you logout of safer payments to relogin you currently need to refresh the browser or close it and reopen it.           Workaround: Refresh the browser to re-login                                  Status: Closed Affected Version: 6.0.0 Fixed Available: No fixed available Known Issue ID: DT261080 === END OF ISSUE === Title: PO08855: WRONG TIMESTAMP VALUE SET BY RDI FOR TIMESTAMPS OLDER THAN [1901-12-13 20:45:52] OR LATER THAN [2038-01-19 03:14:07] Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] For timestamp  attributes with values older than [1901-12-13 20:45:52] or      later than [2038-01-19 03:14:07], the value is set wrongly in   the sql statement created by RDI.                                Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261079 === END OF ISSUE === Title: PO08793: NEWLY CREATED CHALLENGER CANNOT BE OPENED WHEN REMOTE USING SIMULATION AND REVISION NOT SYNCHRONIZED Description: [SP 6.1] When a revision is defined to run simulations on a     remote instance and FLI to that instance is not synchronized,   copying the revision and then opening the newly created         challenger fails with fatal error NO_PRIVILEGES. The challenger cannot be opened before FLI is synchronized.                    This is more likely to happen when the FLI is not synchronized  because of running a data export job with setting 'stop         computation' on the remote instance.                             Workaround: Before running data export job make sure champion and challenger revisions that you copy from are assigned to an instance other than BDI instance by either copying champion revision and       assigning another instance in simulation page with button in top right corner. Afterwards do a golive on the challenger.        It can also be prevented by assigning another instance in       simulation page of existing challengers.                        If the issue already appears wait for fli to synchronize.        Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261078 === END OF ISSUE === Title: PO08736: PMML MODEL SIMULATION MEMORY IS NOT CLEARED WHEN STOPPING SIMULATION Description: [SP 5.7, SP 6.0, SP 6.1] When stopping a simulation, the memory that was used to simulate PMML models is not freed.              Workaround: n/a                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261077 === END OF ISSUE === Title: PO08800: JOB ON REMOTE INSTANCE CAN'T BE STOPPED. Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] When stopping a job that runs on a remote instance, the request to do that is  transferred to remote via FLI. When FLI is not synchronized the request does not reach the instance. This is likely to happen   when FLI is not synchronized because a data export job with     setting stop computation is running on the remote instance.      Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261076 === END OF ISSUE === Title: PO08763: CASE TAKEOVER DURING CASE TRANSITION POTENTIALLY CAUSING BACKTRACE Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] If a case is being     transitioned from one state to another by one user and at the   same time another user is taking over the case and does a       transition, it can cause a backtrace to be printed.              Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261075 === END OF ISSUE === Title: PO08745: RANDOM FOREST AND BOOSTED TREE MODEL OUTPUTS NOT COMPUTED AFTER GOLIVE Description: [SP 6.1] When doing a golive with a challenger that has a PMML  Random Forest or Boosted Tree model that already exists in the  champion, the outputs will not be computed after the golive     anymore, if the newly promoted PMML model has no changes        compared to the champion.                                        Workaround: Add a source condition to the PMML model which will always      evaluates to true (so it won't change the normal condition      evaluation). Change this condition before every golive so it is different compared to the current champion but still evaluates  into true.                                                       Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261074 === END OF ISSUE === Title: PO08668: Blocking instance after priority update in working queue or deleting an existing working queue Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] When the priority of an existing working queue is changed or the existing working queue is deleted, it is possible that an instance enters a dead lock state which prevents it from processing messages/updates via FLI or API and dispatching cases. This can affect the API instance or remote instances. A normal shutdown may not be possible      anymore. In this case the instance has to be killed and         restored.                                                        Workaround: Do not change the priority of or delete an existing working     queue.                                                           Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261073 === END OF ISSUE === Title: PO08792: WRONG TIMESTAMP VALUE CAUSED BY THE CHANGE OF TIMEZONE USED BY OS Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] If there is a change of the timezone used by the       Operating System, and a timestamp value to be sent to Safer     Payments is before this timezone change, the value is not saved correctly in Safer Payments.                                    For example, Moscow timezone was changed from permanent summer  time to permanent standard time on October 26, 2014. If sending a timestamp value of 2014-05-11 00:00:00, it is saved as        2014-05-10 23:00:00 in Safer Payments. There is no such problem for a timestamp value after the timezone change.                 Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261072 === END OF ISSUE === Title: PO08810: NO RDI UPDATE STATEMENT CREATED WHEN SAVING MEMO OR CPP Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] RDI will not   write an UPDATE statement when a memo or CPP is saved for an    existing case.                                                   Workaround: n/a                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261071 === END OF ISSUE === Title: PO08719: CRASH WHEN LOADING CSV INCLUDING VALUES CONSISTING OF MORE THAN ONE WHITE SPACE FOR AN ATTRIBUTE WITH LENGTH AS 1. Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] When loading values that only consist of whitespaces   for an attribute of length 1, the instance may crash when the   value has more than one whitespace. It is not an issue to load  more whitespaces to attributes with a length greater than 1.     Workaround: Option 1. Make sure that the maximum length of the value sent to such attribute is 1.                                                                                                           Option 2. Update the attribute's length to 2. This option will  cause the current data saved in this attribute being dropped.    Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261070 === END OF ISSUE === Title: PO08680: CRASH WHEN STARTING SIMULATION REPORT WHILE ANOTHER SIMULATION IS RUNNING Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1, SP 6.2]                                                The application may crash, if a simulation report of a sub      mandator is started while another simulation of a sub mandator  is running that includes rules of a head mandator.               Workaround: Avoid to simulate rules of higher mandators or alternatively    avoid running multiple simulations in parallel when an already  running simulation includes rules of a head mandator.            Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261069 === END OF ISSUE === Title: PO08705: FRAUD TIMESTAMP MISSING IN RDI OUTPUT Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP     6.0, SP 6.1] The fraud timestamp is updated in MDC / DDC, but   it is missing in the RDI output, when marking transactions as   fraud / genuine manually from user interface.                    Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261068 === END OF ISSUE === Title: PO08642: THE MERGING OPERATOR "IS (IF NOT EMPTY)" SET NUMERIC ATTRIBUTE TO 0 IF THE EXPRESSION VALUE OF THE SOURCE TRANSACTION IS EMPTY Description: [SP 5.7, SP 6.0, SP 6.1] The merging operator "is (if not       empty)" sets numeric attributes to 0 instead of keeping the     original value, if the expression value of the source           transaction is empty.                                            Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261067 === END OF ISSUE === Title: PO08630: EXISTING STATUS ALARM INDICATORS CONFIGURATION PAGE DOES NOT LOAD ENABLED CASE STATE CHECKBOXES Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0] Enabled case states checkboxes are not loaded when opening an existing Status alarm indicators of type "cases in investigation".                                Workaround: N/A                                                              Status: Open Affected Version: 6.0.0 Fixed Available: No fixed available Known Issue ID: DT261065 === END OF ISSUE === Title: PO08579: INCORRECT ERROR MESSAGE WHEN TRYING TO ADD AN EIGHT INSTANCE TO A CLUSTER Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP     6.0] The error message should read 'IBM Safer Payments instance Id must be between 1 and 7'.                                     Workaround: None available.                                                  Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT261064 === END OF ISSUE === Title: PO08558: ONLINE HELP DOES NOT MENTION CALENDAR UPDATE DURING NOT CORRECTLY APPLIED WHEN MERGING THAT DOES NOT UPDATE HITS FIRST Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0] Online help            does not mention: Calendar total amounts                        are not updated correctly by mergings when a merging is applied first that does not update calendars, followed by one that      updates calendars, when both set the amount attribute. The      frequency is also not increased by mergings, if a merging that  does not update calendars changes the attributes of a target    first - so the conditions of the calendar are met - and then    another merging that updates calendars changes the attributes   as well.                                                         Workaround: None available.                                                  Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT261063 === END OF ISSUE === Title: PO08548: EMPTY VALUES IN CASE ACTIONS NOT DEFINABLE Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0]Currently, empty values in reporting attributes and other       replacements are printed as () or (0). This may not always be   suitable for every kind of case action, for example when the    case action contains JSON.                                       Workaround: n/a                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261062 === END OF ISSUE === Title: PO08509: CASE SELECTION NOT SHOWING CASES FOR SUBMANDATOR USERS Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0]Cases of head mandator case classes were not visible in the caseselection if the user didn't had the privilege to view the case class of the case, even if he would have the privilege to view  the case. The case classes were not visible in the case         selection form and therefore couldn't be selected to show cases. Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261061 === END OF ISSUE === Title: PO08691: CLOSED CASE ADDED TO WORKING QUEUE Description: [SP 5.7, SP 6.0, SP 6.1] When a case that satisfies the         conditions of a public working queue is closed, it may be       re-added to the public working queue and thus reappear in work  case. As a consequence the closed case will be added to the     private working queue of the user that closed it and            permanently stay in his working queue.                           Workaround: Reopen and close case again.                                     Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261060 === END OF ISSUE === Title: PO08619: BACKTRACE GENERATED DURING SHUTDOWN Description: [SP 5.7, SP 6.0, SP 6.1] A backtrace may be generated during the shutdown of an instance if the instance is processing          transaction messages. Fatal errors may occur in the logs as a   consequence but may be ignored.                                  Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261058 === END OF ISSUE === Title: PO08547: CSV EXPORTS NOT POSSIBLE WHEN USING OIDC SSO Description: [SP 5.7, SP 6.0] Exporting data as csv, for example query       results, results in a SESSION_EXPIRED error when using OIDC     Single Sign-on.                                                  Workaround: n/a                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261057 === END OF ISSUE === Title: PO08541: MISSING TEXT AND TOOLTIP FOR RISK LIST MAINTENANCE FUNCTION Description: [SP 5.7, SP 6.0] The rewrite Risk Lists maintenance function is missing its label and tooltip.                                   Workaround: None available                                                   Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261056 === END OF ISSUE === Title: PO08501: PYTHON FILES NOT INCLUDED WHEN DOWNLOADING SP CONFIGURATION>GENERAL CONFIGURATION Description: [SP 5.7, SP 6.0] The subfolders including python scripts are    not included in the exported config.                             Workaround: manually copy python files to new instance                       Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261055 === END OF ISSUE === Title: PO08429: RULE ACTIONS DO NOT WORK WITH PREPROCESSING RULES Description: Rule actions in preprocessing rules can be defined but are never run. Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT261054 === END OF ISSUE === Title: PO08645: EXPORTCASESTABLE REQUEST TOO LONG Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] The URI of     "export cases table" HTTP request can get too long and can      cause HTTP error 414 during cases export.                        Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261053 === END OF ISSUE === Title: PO08644: LOG MESSAGE 518 CONTAINING INCORRECT INTERFACE NAME Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP     6.0] Log message 518 says "Ignoring incoming SSL API            connection". However, the log message is intended and printed   for all SSL interfaces, ie API, MCI and ECI, not only for the   API.                                                             Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: 6.3.1.02 Known Issue ID: DT261052 === END OF ISSUE === Title: PO08476: TIME INTERVAL CONDITIONS WHERE INTERVAL END IS SMALLER THAN START DO NOT HIT Description: Description: [SP 5.7, SP 6.0] Conditions with "equal to"        operator that use a time interval attribute as reference        attribute in the expression do not evaluate correctly for time  intervals where the right number is smaller than the left one,  like 12:00~1:00 and always evaluates as "condition not hit".    Also it is possible to define "greater than"/"less than"        operator conditions with time interval attributes which should  be rejected.                                                     Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261051 === END OF ISSUE === Title: PO08435: ALARMS WITH LOWER SCORE ARE NOT INSERTED INTO CASE ALARMS Description: [SP 5.7, SP 6.0] At the moment, alarms are only inserted into   case alarms if their score is equal to or greater than the      case's score. All alarms with any score should be inserted into case alarms.                                                     Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261050 === END OF ISSUE === Title: PO08493: ALL EXPRESSION VALUES MASKED IN RULES FIRED TABLE IF ENCRYPTION ENABLED Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP     6.0] If encryption is globally enabled and the user may not     view unmasked values, the expression value will be always       masked in the rules fired table in case investigation no matter if the condition attribute is encrypted or not.                  Workaround: N/A                                                              Status: Open Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT261049 === END OF ISSUE === Title: PO08430: DDC OLDEST URID/TIMESTAMP VALUE FOR THE META ATTRIBUTE "URID COMPUTATION COMPLETE" IN SYSTEM INTERNALS SHALL BE IGNORED Description: The meta attribute "URID computation complete" does not use DDC although it has DDC storage. Its DDC oldest URID/timestamp value in System Internals shall be ignored.                           Workaround: N/A                                                              Status: Open Affected Version: 6.0.0 Fixed Available: No fixed available Known Issue ID: DT261048 === END OF ISSUE === Title: PO08479: DISABLED CASE CLASS SELECTABLE IN MANUAL CASE CREATION Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP     6.0] Disabled case classes may be selected for manual case      creation.                                                        Workaround: Disable the "manual case creation" checkbox in the case class   definition.                                                      Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261047 === END OF ISSUE === Title: PO08687: DUPLICATION OF COMPLIANCE LIST HITS WHEN AGGREGATING CASES Description: [SP 5.6, SP 5.7, SP 6.0, SP 6.1] Aggregation of compliance list hits in cases causes to increase investigation cases files      constantly on remote instances as the compliance list hits are  not replaced but appended to the file for each aggregation.     This could result in FLI issues and crashes on remote           instances.                                                       Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261046 === END OF ISSUE === Title: PO08631: POTENTIAL LATENCIES FOR CALENDAR COMPUTATION WHEN TRANSACTION HAS NO INDEX VALUE Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] Calendars may create latencies by waiting for other    index and calendar related actions even though the transaction  does not contain an index value and the calendar will not be    computed.                                                        Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261045 === END OF ISSUE === Title: PO08646: MISLEADING ERRORS WHEN STARTING UP WITH CONDITIONS/CONCLUSIONS FROM OLDER VERSION THAN 5.7 Description: [SP 5.7, SP 6.0] Conditions with "is empty" or "is not empty"   operator and conclusions with "reset value" operator may create an error log message 062 during the initial start up with 5.7.  This error has no further impact and can be ignored. The        condition/conclusion is parsed correctly and will not create    further error messages during start up anymore. However, in     case the condition is not used in a model element, an           additional fatal error may prevent the loading of the element   that contains the condition.                                     Workaround: In case fatal errors occur for elements that are not part of    the model, for example a SAI, the file of the affected element  needs to be modified. Shutdown, in the file change "type":      "Constant" to "type": "" and start up again for every instance. Perform an additional save of the element via UI once all       instances are up again.                                          Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261044 === END OF ISSUE === Title: PO08546: TIMESTAMPS ARE ALWAYS EXPORTED AS UTC WHEN USING RDI Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0]When system generated data to RDI statements, SP will always usethe internal UTC representation and ignore the configured servertime zone.                                                                                                                       Workaround:                                                                  Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261043 === END OF ISSUE === Title: PO08532: POPUP COMPROMISES UI DROP DOWN SELECTS Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP     6.0]                                                            After moving a pop up dialog, the included select elements      cannot be changed in a proper way anymore. After moving the pop up, every change in the drop down select will reset to the firstselection in the list, but will still display that the selectionworked correctly.                                                Workaround: Do not move pop up dialogs that contain drop down selects. If   you accidentally moved a pop-up that contained a drop-down      select, do not modify its value. Alternatively, disable         "Extended select dialogs" in MyAccount.                          Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261042 === END OF ISSUE === Title: PO08649: ONLY 5 IBM SAFER PAYMENTS SPECIFIC HTTP HEADERS READ FROM MCI Description: [SP 5.7.0.04, SP 6.0, SP 6.1] Custom HTTP Header for the MCI    will be ignored, if more than 5 SP specific headers are sent. Ifthe header "Content-Length" is not within the list of the first 5 SP specific headers in the MCI json request, the request is   hang.                                                            Workaround: Make sure that the headers "Content-Type", "Content-Length" and "X-SP-Message-Type-Id" are among the first 5 headers in the MCI json request. It would be recommended to only send 5 SP specific headers and not send the HTTP header "X-SP-Version", as this is not required for MCI json messages. Alternatively, don't send  the header "X-SP-Request-Type" for "ModelRequest" MCI json      requests.                                                        Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT261041 === END OF ISSUE === Title: PO08528: MEMORY FRAGMENTATION CAUSED BY CASE INVESTIGATION AND OPERATIONS ON REPORTING ATTRIBUTES Description: [SP 5.7, SP 6.0, SP 6.1] Reporting attributes from other case   classes and reporting attributes added retrospectively to case  classes are cached for case selection. Higher memory consumption by the API enabled instance is possible, which could be due to memory fragmentation caused by case investigation and repeated  clearing and rebuilding of cached reporting attributes during   every end of day job.                                            Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261040 === END OF ISSUE === Title: PO08533: PROFILE FREQUENCY INCREASING FOR RE-COMPUTE TARGET MERGINGS WHEN "INCLUDE CURRENT" IS DISABLED Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0] During the re-compute  target part of mergings - only executed if the respective       option is enabled in the merging - frequencies of profiles      whose conditions are satisfied are increased every time, if     "include current" is disabled in the profile. This even happens if the profile has "update during mergings" disabled. So        further output computation will have wrong values for those     profiles.                                                        Workaround: If profiles are known to be triggered for mergings with         re-compute target, it is recommended to enable "include         current", if possible. This will prevent the issue from         occurring again.                                                 Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT261039 === END OF ISSUE === Title: PO08460: ERROR SAVING CASE CLASS UPDATE WITH SOME CASE CLOSE CODE(S) UNCHECKED Description: SP 5.7, SP 6.0] After editing a case class definition by        reducing its total enabled case close codes to a value lower    than what is defined in My Account -> Expand checkbox list      below, this case class definition cannot be saved with an error "At least one of the transitions does not define close codes".   Workaround: Temporarily change the number of "Expand checkbox list below" in MyAccount to a smaller value.                                   Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261038 === END OF ISSUE === Title: PO08495: TIMESTAMP IN CASE ACTION QUERY RESULTS AND CASE ALARMS Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0] Values of timestamp attributes are not formatted as ISO time but are sent as UNIX timestamp    for query results or case alarms that are added via context     menu.                                                            Workaround: If all case alarms should be added to the case action, do not   add any via context menu. All case alarms will be added by      default and timestamps are converted correctly. For queries     there is no workaround.                                          Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261037 === END OF ISSUE === Title: PO08684: DOCUMENTATION: ADD BIYEARLY CALENDAR PERIOD DETAILS. Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP     6.0, SP 6.1] Calendar calculations do not take the creation     timestamp into account. For a bi-yearly calendar, it is         expected that the periods roll over for each even year (2018,   2020, 2022, ...). Thus, if a calendar was for example created   in 2019, it will still rollover in 2020 although its period     only contains values for one year at this point.                 Workaround: N/A                                                              Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT261036 === END OF ISSUE === Title: PO08557: NO CACHING FOR CLIENT RESOURCES Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0]Currently, browser caching is disabled for the UI. However, in  order to decrease wait times when logging on, it shoud be       possible to cache the client files.                                                                                              Workaround: None                                                             Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261034 === END OF ISSUE === Title: PO08544: INTERVAL CONDITION CREATED BY RULE GENERATOR LEADS TO ERROR IN RULE FORM WHEN SAVING Description: [SP 5.7, SP 6.0] When a rule containing an interval like 100~200in a condition expression is committed from rule generation,    there are extra whitespaces added to the interval which leads toa validation error when saving the rule. This does not have     impact on the computation of the rule.                           Workaround: Click on the expression, the expression will be reformatted by  that and the white spaces will be removed. The rule can be savedthen.                                                            Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261033 === END OF ISSUE === Title: PO08434: DOCUMENTATION OF THE MERGING SETTING "UPDATE CALENDAR PROFILES AND EVENTS" IS INACCURATE Description: The current documentation of the Merging setting "Update        calendar profiles and events" in online Help says that if it is enabled, calendar profiles and events belonging to the mergings mandator or submandators will get updated, when they meet the   mergings conditions and have the option 'Update during merging' enabled. This is inaccurate. In such case, the profiles of all  mandators will get updated, not just the mergings mandator and  submandators.                                                    Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261032 === END OF ISSUE === Title: PO08494: NO ESCAPING IN CASE ACTION PLACEHOLDER REPLACEMENTS Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP     6.0] There is no xml/json/url escaping of placeholder values in OCCs, which can result in errors when trying to use XML, JSON   or HTTP-FORM that contains characters that need to be escaped   properly to not break the encoding.                              Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261031 === END OF ISSUE === Title: PO08427: INSTANCE MAY CRASH IF THERE ARE ERRORS DURING DATA EXPORT JOB Description: [SP 5.6, SP 5.7, SP 6.0] There is a possibility that the        instance may crash, if there are errors encountered during the  data export job - for example errors while writing to the export file - instead of just aborting the job.                        Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261030 === END OF ISSUE === Title: PO08282: TIMESTAMP PRINTED AS UNIX TIMESTAMP IN CASE ACTION LOOP CONSTRUCT Description: [SP 5.6, SP 5.7, SP 6.0] Timestamp attributes are printed as    unix timestamp in loop constructs instead of YYYY-MM-DD hh:mm:ss when adding query result records or case alarms to case        actions. Loop constructs exist since Version 5.6.0.02.           Workaround: If all case alarms of the case should be added but no query     results, do not manually add anything to the case action. All   case alarms will be automatically added and the timestamp       attributes will be printed correctly.                            Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261029 === END OF ISSUE === Title: PO08272: RECORDS IN DDC CANNOT BE SELECTED IN SIMULATION DATA SELECTION Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0] The lowest URID that is possible in a simulation data selection is always the oldest URID available in the MDC for any         attribute of the simulation revision or any head mandator       revision. Thus, it is not possible to simulate records that are only available in DDC for all attributes even if "simulation may access DDC" is enabled.                                         Workaround: Increase the MDC of meta attribute system time. This allows to  use all records that are in the MDC of system time to be choosen in the simulation data selection.                               Status: Open Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT261028 === END OF ISSUE === Title: PO08287: BLOCKING INCOMING FLI AFTER NETWORK TIMEOUT Description: [SP 5.5, 5.6] After having a FastLink Interface network         timeout, the incoming FLI was not able to re-connect in rare    situations. This issue was introduced by another fix in version SP_5.5.0.06 and SP_5.6.0.05. Version 5.4.x and 5.7.x were not   affected.                                                        Workaround: No workaround applicable. Only a restart of the instance that   has a blocking incoming FLI resolves the situation.              Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT261027 === END OF ISSUE === Title: PO08184: CANNOT VIEW COMPLIANCE LIST DEFINITION WITHOUT CHANGE PRIVILEGE Description: It is not possible to view the form of a compliance list in case the user only has the compliance list view privilege but not   the compliance list change privilege. A no privileges error is  thrown. This issue exists in IBM Safer Payments 5.5.x, 5.6.x,   5.7.x and 6.0.                                                   Workaround: Grant the user the compliance list change privilege.             Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261026 === END OF ISSUE === Title: PO08093: MEMORY LEAK FOR HEXADECIMAL EVALUATOR CONDITIONS Description: Memory leak for hexadecimal evaluator conditions.                Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261025 === END OF ISSUE === Title: PO08462: ERROR DURING MASTERDATA COMPUTATION WHEN DEFERRED WRITING ENABLED Description: [SP 5.6, SP 5.7, SP 6.0] There is a risk of error message E 227 if deferred writing is enabled and masterdata are computed.     These errors usually have no further impact when occurring on   the receiving instance when synchronizing transactions via FLI, as the messages are retried then. In rare cases, there also is  a risk of a crash.                                               Workaround: LOCAL FIX:                                                     None yet.                                                        Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261024 === END OF ISSUE === Title: PO08399: IT SHOULD NOT BE POSSIBLE TO SET ATTRIBUTE'S DDC SIZE SMALLER THAN MDC SIZE VIA MAINTENANCE FUNCTION AND GOLIVE Description: [IRIS 5.3, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0] Currently it is possible to set attributes' DDC size smaller than MDC size   via the maintenance function and golive. This should be         disabled.                                                       Although the attribute's DDC size appears smaller than its MDC  size in the web client UI, Safer Payments internally fix such   definition by setting the attribute's DDC size to its MDC       size. However, there is no such fix to the index sequence       attribute's DDC size.                                            Workaround: Run the maintenance function and set the DDC size to a value    equals to or larger than the attributes' MDC size.               Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT261023 === END OF ISSUE === Title: PO08240: ATTRIBUTES WITH LEADING NUMBER IN NAME POTENTIALLY PARSED INCORRECTLY IN EXPRESSIONS Description: [SP 5.4.0.10, 5.5.0.02, 5.6.0.00, SP 5.7.0.00, SP 6.0.0.00] In  the mentioned and higher releases, attributes in expressions of conditions and conclusions are saved with their uid instead of  their attribute name. When starting a configuration from an     older release with these releases, if an attribute in an        expression had a name that started with the uid of another      attribute (e.g. "5480 Account number") the other attribute was  used in the expression instead of the correct one. If the data  type of this attribute differed to the data type of the input   attribute of the condition or conclusion, the instance would not start up. The same was true for attributes used in model       formulas when starting with version 5.7.0.00 or higher.          Workaround: Before starting up with the newer release, look in system       internals if there are any attribute names that start with a    number. If these attributes are used in expression(s), first    change the expression(s) to not the use the attribute anymore.  Then rename the attribute so that the name does not start with a number. Afterwards change the expression back to use the       attribute again. This workaround does not apply to retired or   invalidated revisions.                                           Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT261021 === END OF ISSUE === Title: PO08158: MULTIDELETE OF OCC OF TYPE HTTP ALWAYS RESULT IN A NO PRIVILEGES ERROR Description: 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 stops the deletion after it encounters the HTTP channel configuration. Workaround: Delete the outgoing channel configuration in HTTP one by one.    Status: Closed Affected Version: 5.7.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT261020 === END OF ISSUE === Title: PO08162: GOLIVES CAN GET STUCK FOREVER. Description: Some actions do not interrupt automatically anymore due to a    priority issue. Golives will wait until all investigation       queries are finished. There also can be other side effects, for example jobs that need much longer to start and stop. Also      there can be additional latency peaks during message processing.This issue is only present in releases 5.7.0.00, 5.7.0.01 and   5.7.0.02.                                                        Workaround: None.                                                            Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261019 === END OF ISSUE === Title: PO08423: CONTEXT MENU IS MISSING FOR DEFINED RISK LISTS Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0] The context menu for defined   risk lists is missing.                                           Workaround: N/A                                                              Status: Closed Affected Version: 6.0.0 Fixed Available: No fixed available Known Issue ID: DT261018 === END OF ISSUE === Title: PO08378: INCORRECT PRECEDENT OUTPUT VALUES FOR RE-COMPUTE TARGET WHEN INDEX NOT COMPUTED Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0]This only applies for transactions of mergings with re-compute  target. Precedents might compute random values during re-computetarget, if the index value is nil or if the index computation   conditions are not met.                                          Workaround: Add a computation condition to precedents to check, if the index value still fits for the current precedent record by comparing it with the attribute of current: index attribute equalTo {index attribute}".                                                    Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261017 === END OF ISSUE === Title: PO08330: CONFLICTING CASE UPDATE FAILS IF SCORE OF CONSOLIDATED CASE IS SMALLER Description: [SP 5.6, SP 5.7, SP 6.0] There can be case synchronization      issues for investigation cases in special circumstances. The    reporting case attributes of an investigation case can be       deleted, if the case aggregation is received before the case    was created and if the score of the aggregated case is smaller.  Workaround: Not available                                                    Status: Open Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT261016 === END OF ISSUE === Title: PO08278: CONDITIONS / CONCLUSIONS WITH CONSTANT DOUBLE QUOTES IN EXPRESSION NOT COMPUTED CORRECTLY Description: [SP 5.7, SP 6.0] The character " (double quotes) is currently   not computed correctly. For example Text -> not contains -> "   is always false.                                                 Workaround: Do not include the character " (double quotes) in conditions    and/or conclusions.                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261015 === END OF ISSUE === Title: PO08234: MISLEADING LOG MESSAGE FROM PARSING LEGACY FORMULAS WITH GEODISTANCE FUNCTIONS Description: [5.7.0 and above] During the first startup of the instance after upgrading to IBM Safer Payments 5.7, the application may print below example warning messages of invalid definition of         expression in the log for every formula that contains a geo     distance, even if it is valid. The log message should only be   printed, if the pos placeholder is used in a formula without    also using geo distance. In case there are no such formulas,    this message can be ignored.                                                                                                    W 0743 Invalid definition of expression in element ??? when     parsing from disk: Geographic position operand can only be used within geographic distance formula.. To not affect current modelbehavior, expression creation will continue. Please consider to change the expression definition.                                Workaround: The error should no longer exist after restarting the instance.  Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261014 === END OF ISSUE === Title: PO08108: CASE ACTION / NOTIFICATION CAN SELECT OUTGOING CHANNEL OF A SIBLING MANDATOR Description: It is possible to define a case action or notification to use   the outgoing channel of a sibling mandator.                     When clicking on "show references" in the case action or        notification, a fatal error log message is printed.              Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261013 === END OF ISSUE === Title: PO08082: SWITCHING THE API WHILE A SIMULATION IS RUNNING MIGHT CRASH THE INITIAL API INSTANCE Description: Switching the API while a simulation is running might crash the initial API instance when changing the model on the new API     instance.                                                        Workaround: Stop simulations manually when switching the API to another     instance                                                         Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT261012 === END OF ISSUE === Title: PO08344: HANGING GOLIVE WHEN WORKING QUEUE CONDITIONS USE REPORTING ATTRIBUTES NOT SELECTED IN CASE CLASS Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0] A golive might hang, if there  are working queues with conditions that use reporting           attributes that are not selected in the case classes of the     cases to be evaluated for working queue insertion.              Additionally, the end of day job and other operations might     hang as well.                                                    Workaround: Enable all reporting attributes that are used in working queues in all case classes. Additionally for cases                     that have already been created at this point, it might be       possible that the issue only occurs because cases of case       classes that should not be inserted anyway are missing reportingattributes used in the condition. If so, add an additional      condition to the affected working queues restricting it to the  case class so cases of other classes where the reporting        attributes of the following conditions are not enabled, will notbe further evaluated. This additional condition needs to be     placed at the top of the condition list.                         Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261011 === END OF ISSUE === Title: PO08205: BROKEN COUNTER AFTER INDEX ATTRIBUTE CHANGE Description: There is a problem when changing an index attribute, if there   is already a scheduled changed for a counter to use this index  in a lower mandator challenger. This can even result in an      application crash after going live with the lower mandator      challenger when receiving incoming transactions.                It is recommended to first perform a golive in the head         mandator when changing an index, before applying counter        changes that are related to this index in lower mandators.      As workaround, it is sufficient to save the affected counter in the lower mandator again without any change and perform a       golive of the lower mandator.                                    Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261010 === END OF ISSUE === Title: PO08401: FILE CREATION NOT LOGGED Description: [SP 5.7, SP 6.0] Log message 435 is missing during file creation for most files.                                                 Workaround: Setup additional logging via Operating System to track file     creation.                                                        Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261009 === END OF ISSUE === Title: PO08224: TIMESTAMPS IN PYTHON CODE ARE BROKEN IF OUTPUT IS USING DECIMALS Description: Python code in conditions or conclusions cannot handle timestamp values correctly, if there are other attributes involved that  are using decimals. For example, conclusions that try to write  to an output with decimals are filled wrong, if a timestamp     attribute is used as input for the python function.             [SP 5.7.0.00, SP 6.0.0.00]                                       Workaround: Avoid using timestamps together with attribute that use decimalsin python code.                                                  Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261008 === END OF ISSUE === Title: PO08178: FATAL ERROR OCCUR WHEN ACCESSING THE RULE GENERATION DATA SELECTION. Description: Fatal error occur when accessing the rule generation data       selection caused by missing meta attribute account.              Workaround: Do not access the rule generation data selection or add         missing meta attribute account.                                  Status: Open Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT261007 === END OF ISSUE === Title: PO08186: BLOCKING SHUTDOWN IF DEFERRED WRITING ENABLED Description: If the deferred writing is in some specific cycle of deferred   writing, a shutdown may have blocked after writing log message  "0122 Interrupting deferred writing service". This could only   be interrupted by killing the instance.                          Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261006 === END OF ISSUE === Title: PO08467: RDI DOES NOT CREATE UPDATE STATEMENTS FOR RE-COMPUTE TARGET RESULTS Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0] The RDI just writes    SQL statements for the conclusions of re-compute target         mergings. It doesn't create update statements for counter and   attributes of the re-computed transaction.                       Workaround: None available.                                                  Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261005 === END OF ISSUE === Title: PO08361: BULK TRANSITION: STREAM NOT JSON COMPLIANT Description: [SP 5.7, SP 6.0] When 10 or more case classes are defined and a bulk transition is to be done on multiple cases, a "Stream not  JSON compliant" error appears.                                   Workaround: Currently the only possible option is to have less than 10 case classes defined.                                                 Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261004 === END OF ISSUE === Title: PO08249: CASE CONDITIONS IN SAI OR KPI PREVENT START UP AND CANNOT BE CREATED ON THE UI Description: [SP 5.7, SP 6.0] Using case conditions with case placeholders in SAIs or KPIs, e.g. "[CaseAgeInMinutes] equal to 5", will       prevent start up of the application. An error message "Cannot   find referenced attribute for case condition for any mandator"  will be printed. It is also not possible to save such case      conditions for KPIs and SAIs. An error "Attribute reference in  condition not found." is thrown.                                 Workaround: The conditions need to be manually removed on file level to     enable start up of the instance. Please contact IBM support for the instruction.                                                 Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261003 === END OF ISSUE === Title: PO08207: "COPY TO" OF PREPROCESSING RULESET COPIES TO NORMAL RULESETS Description: In the "copyRevision" request, the wrong stream type is used:   "ruleset" instead of "preProcessingRuleset" thus the            preprocessing ruleset is added as normal ruleset.                Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT261001 === END OF ISSUE === Title: PO08134: With deferred writing enabled, changing index size of a profile with a smaller capacity may crash the instance Description: With deferred writing enabled, reducing the size of an index    that is used in a profile may result in a crash. Also, with     deffered writing enabled, changing the index used in a profile  to another index may result in corrupted data for the profile.                                                                  This issue affects all IBM Safer Payments versions.              Workaround: Do not change the index of an existing profile or reduce the    size of the index that is used by a profile.                     Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT261000 === END OF ISSUE === Title: PO08389: PENDING ODBC CASE ACTION OR NOTIFICATION PREVENTS SHUTDOWN Description: [SP 5.6, SP 5.7, SP 6.0] A pending ODBC message may wait for a  response and thus cannot be delivered for a long time, if the   ODBC driver doesn't have any timeout parameter. This may prevent a shutdown.                                                     Workaround: Verify that there is a timeout defined for ODBC driver.          Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260999 === END OF ISSUE === Title: PO08339: CUSTOM PARSER CRASH Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0] Using custom parser with "Use  custom end-of-message marker" and "Use custom response" enabled in System Configuration may crash the application during message load.                                                           Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: 6.1.1.00 Known Issue ID: DT260998 === END OF ISSUE === Title: PO08331: IP ADDRESS CONFLICT CHECK IS NOT REJECTING DURING STARTUP WITH A 2 INSTANCES CLUSTER Description: [SP 5.7, SP 6.0] The IP address conflict check is not rejecting a startup for interfaces that have the same IP / Port           combination, if the cluster only has 2 instances.                Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260997 === END OF ISSUE === Title: PO08326: INSTANCE BLOCKING AFTER CHANGING COMPLIANCE LIST PRIORITY Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0]Changing the priority of a compliance list while there are      incoming transactions computing this compliance list will block all incoming transactions permanently until next restart.       Workaround: Add workaround here if applicable.                   Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260996 === END OF ISSUE === Title: PO08335: INCOMPLETE COMPLIANCE LIST RESULTS FOR SEARCH BY ID Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0]When searching in compliance lists by "list id", some entries   might not be displayed. This happens for entries with very      common names that have multiple entries and where a similar     name with a smaller "list id" exists.                            Workaround: Prefer to search the compliance list by name.                    Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260995 === END OF ISSUE === Title: PO08285: ALLOW SCIENTIFIC NOTATION IN NUMERIC EXPRESSIONS Description: [SP 5.6, SP 5.7, SP 6.0] Safer Payments should allow scientific notation in numeric expressions in PMML model files.             Workaround: In the PMML model files to be imported into Safer Payments, use numeric value without any scientific notation.                   Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260994 === END OF ISSUE === Title: PO08202: EMPTY VALUES IN NOTIFICATIONS FOR MASTERDATA ATTRIBUTES OF TYPE BOOLEAN, HEX OR IP Description: [IBM Safer Payments 5.6, 5.7, 6.0] Values for boolean, hex or IP attributes where the value is applied via masterdata during the computation, are not replaced in notifications when using a {} placeholder. Instead of the actual value, there is an empty     value in the notification.                                       Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260992 === END OF ISSUE === Title: PO08426: ERROR WHEN VIEWING/COMPARING RETIRED REVISION CONTAINING PMML MODELS WITH CONDITIONS Description: [SP 5.6, SP 5.7, SP 6.0] After a restart of the instance,       viewing the model components table containing PMML models with  conditions in a retired revision or comparing retired revisions which contain PMML with conditions will report an error.         Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260991 === END OF ISSUE === Title: PO08447: RDI ADDS ADDITIONAL CHARACTERS('') TO OUTPUT Description: [SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0] Fields with a '\' in   them are outputted with '\\' samples seen are on the 'Card      Acceptor Name' and 'Card Acceptor City' Input: "EST 2011\GUI" , "CASHCARD\7-11 GUILDFORD" In SP displays as: "EST 2011\GUI" ,   "CASHCARD\7-11 GUILDFORD" In RDI: "EST 2011\\GUI" ,             'CASHCARD\\7-11 GUILDFORD".                                      Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260990 === END OF ISSUE === Title: PO08390: PLACEHOLDERS NOT REPLACED IN HTML BODY OF SMTP CASE ACTION Description: [SP 5.7, SP 6.0] In version SP 5.7.0.03 and higher, placeholders are not replaced in the HTML body of SMTP case actions. Only   query result placeholders are replaced. This is not an issue for the standard body of SMTP case actions.                         Workaround: N/A                                                              Status: Closed Affected Version: 6.0.0 Fixed Available: No fixed available Known Issue ID: DT260989 === END OF ISSUE === Title: PO08417: DEFERRED WRITING AND RE-CREATE INDEX FUNCTIONALITY Description: [SP 5.5, SP 5.6, SP 5.7, SP 6.0] Running a re-create index job  and also using deferred writing can cause a fatal error and     also crash the application in rare cases. If there is a fatal   error message, there will usually not be further impact as the  index is written completely during next deferred writing cycle.  Workaround: No workaround applicable.                                        Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260988 === END OF ISSUE === Title: PO08338: INCREASED WAIT TIME WHEN OPENING DASHBOARD PAGE Description: [SP 5.7, SP 6.0] There was a potential performance drop on the  dashboard page and a small performance drop in case             investigation, queries and model, as some requests have become  slower since 5.7.0.00. Some API requests could slow down by 1-2 seconds, which could sum up for multiple seconds on the         Dashboard page. In detail, following API requests became slower: getAttributes, getCppTable,                                    getDashboardKeyPerformanceIndicatorData,                        getDashboardKeyPerformanceIndicators, getReportingAttributes,   createDefinedRiskListImportSettings, getCaseAction, Logout. Only configurations with a large number of investigation cases are  affected by this issue. This issue does not affect the          performance of real time computing, it only affects the         performance of API requests.                                     Workaround: No general workaround applicable. Reducing the number of        un-archived investigation cases or reducing the number of       displayed KPIs on the dashboard improves the performance, but   may be not applicable depending on the environment.              Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260987 === END OF ISSUE === Title: PO08358: BLOCKING DURING INDEX PURGING OF END OF DAY JOB Description: [SP 5.4.1.01, SP 5.5.1.01, SP 5.6.1.01, SP 5.7.0.04, SP         6.0.0.00] The end of day job could block during index purging,  if there was a profile defined on the same index that also had  "update during merging" enabled.                                 Workaround: Either disable "purging" for indexes that have profiles defined that "update during merging", or disable "update during         merging" for profiles on indexes that are purged                 Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260986 === END OF ISSUE === Title: PO08173: MASTERDATA ISN'T FILLED FOR EXTERNAL QUERIES Description: Masterdata isn't filled for external queries in investigation   cases, if the record isn't available in the cache anymore.       Workaround: Add the masterdata attibute as reporting attribute.              Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260985 === END OF ISSUE === Title: PO08159: Issues displaying large numbers in queries with more than 15 digits starting with 9 Description: Large numbers with more than 15 digits starting with 9 are not  displayed correctly in query result in web browser, if it is notdashed formatted. This is because such numbers are converted to floating values by the web browser's javascript engine and may  get a different ending digit. The csv output of the query resultdoesn't have such issue.                                         Workaround: Format the attribute as PAN (dashed format) in its definition.   Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260984 === END OF ISSUE === Title: PO07974: INSTANCE CRASHES WHEN RUNNING GROUP BY QUERIES WITH NUMBER OF RESULTS SET TO 0 Description: The instance crashes when running group by queries with number  of results set to 0 in System Configuration -> Query             Workaround: Set the Number of results to a value greater than 0.             Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260983 === END OF ISSUE === Title: PO07967: OUT OF SEQUENCE TRANSACTIONS MIGHT NOT BE WRITTEN TO INDEX SEQUENCE DDC WHEN USING DEFERRED WRITING Description: When using deferred writing it is possible that out of sequence transactions can be lost after next restart as they might not be written to DDC. This happens for transactions that need to be  inserted at a point in the sequence that has already been       written to DDC during a previous deferred writing cycle.         Workaround: N/A                                                              Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260982 === END OF ISSUE === Title: PO07939: INCORRECT DATA SELECTION DURING HIGH TRAFFIC IN IBM SAFER PAYMENTS Description: Using "time absolute" for a data selection, the lower URIDc     omputation resulted in wrong values when the instance was       loading new data in investigation, group by and simulation      queries. The lower urid sometimes flipped to the lowest         available URID in the system, which then resulted in huge data  selections.                                                     This might also affect "time relative" but this could only be   observed yet in "time absolute".                                 Workaround: None                                                             Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260981 === END OF ISSUE === Title: PO07758: CASE DELTA UPDATES OUT OF SEQUENCE ISSUES ON REMOTE INSTANCE Description: Since IBM Safer Payments 5.6, only the changes to case files areset via FLI to remote instances, not the whole files. In case ofsuch a delta update, e.g. "executeTransition", arrives via FLI  before the case is created on this instance, it is lost. This isan issue if the API instance is not the primary instance        creating the case.                                               Workaround: N/A                                                              Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260980 === END OF ISSUE === Title: PO07941: CONDITION/CONCLUSION CLIENT ISSUE WITH MULTIPLY FORMULA WHEN DECIMAL SEPARATOR IS COMMA Description: Saving an already defined formula/condition/conclusion with the below conditions may report an error.                             1. In "My Account", the decimal separator is set to ","         2. Create condition with an input attribute that contains     decimals. For example: Amount equals to ({Fraud}*2)               3. Save this condition and open it again, click in the        expression field and save it again.                              Workaround: Remove the decimals including the comma, or use dot instead of  comma.                                                           Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260979 === END OF ISSUE === Title: PO08055: NEWLY CREATED SUBMANDATOR HAS ISSUES WITH CERTAIN CHECKS Description: In order for queries, case queues and other checks to work      correctly there needs to be a champion revision for the         submandator.                                                     Workaround: Immediately perform a golive with the new submandator's         challenger.                                                      Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260978 === END OF ISSUE === Title: PO07972: REFERENCES FOR DELETED ATTRIBUTES WEREN'T REMOVED FROM GROUP BY QUERY RESULTS Description: The instance might become invalidated during a golive, if an    attribute being deleted in this golive was used in group by     queries condition once and there are still query results        existing from the time of the usage.                             Workaround: Do not delete attributes, just remove ddc and mdc               N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260977 === END OF ISSUE === Title: PO07931: ITEM_NOT_FOUND WHEN EXECUTING CASE TRANSITION AFTER HYPERLINK QUERY IN WORK CASE Description: Executing a case state transition after clicking a hyperlink in a query in case investigation window will report                "ITEM_NOT_FOUND" error.                                          Workaround: Refresh the page before performing the case transition.          Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260976 === END OF ISSUE === Title: PO07959: QUERY RESULS WILL NOT BE REPLACED WHEN AN ATTRIBUTE CONTAINS A HASH (#) IN IBM SAFER PAYMENTS Description: When exporting docx case actions, query results will not be     replaced when there is an attribute value containing a "#".      Workaround: There is no known workaround, except for omitting the attribute (#).                                                             Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260975 === END OF ISSUE === Title: PO08027: POTENTIAL FATAL ERROR WHEN OPENING CASE INVESTIGATION Description: In rare circumstances, when a user tries to open a case from a  working queue while this working queue is automatically being   updated, or when two users simultaneously try to open a new     case from a working queue, a fatal error can happen due to a    nullptr access of a working queue object inside the case.        Workaround: The issue should happen in very rare situations, and should not lead to other issues except a fatal error message. The user can just open the case again. If it was assigned to a different     user the other user can open the case again with only the       privilege to view the case.                                      Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260974 === END OF ISSUE === Title: PO07978: HTTP CASE ACTION DOES NOT DISPLAY MESSAGE TEMPLATE WHEN EXTENDEDSELECT DIALOG IS DISABLED Description: HTTP case action does not display message template when extended select dialog is disabled.                                      Workaround: Make sure the users have extended select dialog enabled          Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260973 === END OF ISSUE === Title: PO07934: Issue when creating new formulas with decimals Description: When creating a new formula with decimals in expression, the    decimals are cut off when hitting Enter or clicking outside of  the expression field.                                            Workaround: Modify the formula by adding the decimals in the expression and save.                                                            Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260972 === END OF ISSUE === Title: PO07812: NO TEST FUNCTIONALITY FOR OUTGOING CHANNEL CONFIGURATION (OCC) Description: Currently, testing an OCC is not possible. The OCC will only be saved when hitting the test button, but there is no test        execution.                                                       Workaround: Use the OCC in a case action or notification and test the case  action/notification.                                             Status: Open Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260971 === END OF ISSUE === Title: PO07928: CUSTOM PARSER CRASH WHEN USING MTID WITH HIGHEST AMOUNT OF MAPPINGS Description: The application could crash when the custom parser was used to  load a transaction for the message with the highest amount of   mappings.                                                        Workaround: none                                                             Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260970 === END OF ISSUE === Title: PO07969: NO ERROR LOG MESSAGE IF MCI READS INVALID JSON Description: No error log message if MCI reads invalid JSON message           Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: 5.5.1.01;5.6.1.01;5.7.0.04;6.0.0.00 Known Issue ID: DT260969 === END OF ISSUE === Title: PO07968: CASE ACTION DELIVERED CURRENTLY NOT WRITTEN TO CASE AUDIT TRAIL Description: When sending a case action, there is an audit trail entry that  the case action was triggered but no additionally entry that it was delivered.                                                  This issue affects 5.5.x and 5.6.x releases.                     Workaround: None known.                                                      Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260968 === END OF ISSUE === Title: PO07920: HIGH MEMORY CONSUMPTION IN BROWSER WHEN USING CASE INVESTIGATION Description: There is currently a huge increase in memory consumption over   time when using Case investigation.                              Workaround: Press F5 to refresh page or restart the browser.                 Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260967 === END OF ISSUE === Title: PO07904: MAX TRANSACTION LATENCY KPI IS INTERPOLATING Description: The KPI for "max transaction latency" is interpolating its      values in the dashboard chart. By this, it is showing only the  correct values when zooming in very close.                       Workaround: Using higher values in the KPI for "Frequency" or zoom in very  close will reduce the problem. Using lower "Frequency" values,  for example 1 second, will increase the problem.                 Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260966 === END OF ISSUE === Title: PO08114: PERFORMANCE ISSUE IN SP 5.7 CASE SEARCH WHEN LOADING CASES FROM SP 5.4 WITH A HUGE AMOUNT OF REPORTING ATTRIBUTES Description: When starting SP 5.7 with many cases created in SP 5.4, which   contain a huge amount of reporting attributes, then                 case search, when searching for attributes (not searching   for case id)                                                        case selection when searching with conditions like PAN ->   equal to -> constant                                            is much slower than in SP 5.4.                                  It can be reproduced with testsuite test                        caseSelectionPerformance, if you start it with 5.4 and then     start the instance with 5.7                                     To reproduce manually:                                              Create many attributes in SP 5.4 with release build, like   1000.                                                               Create 5000 cases with different entries for PAN                -> If you look at a case file, you see that theres an entry for each of the 1000 reporting attributes.                          Search for a case in case search for PAN -> constant            -> it takes less than 50 ms in release (depending on where  the attribute is in the reporting attribute list)                   Search for a case file in case selection with condition Pan -> equal to -> constant                                             -> takes a similar amount of time                               Start the instance with SP 5.7 with release build               Search with case search and case selection again                -> it takes around 600 ms                                   Customer is running 150,000 cases from 5.4 with 2000 reporting  attributes and says it takes 45s instead of some seconds.        Workaround: For cases created in SP 5.7 the access should be fast. You      could verify this by following test:                                                                                                create a new case class with only some reporting attributes.    For this case class create many cases via a rule                Search for these cases in case selection tab, by only       enabling this case class. This should be faster. Searching via  case search however should still be slow, as it will also       search in the cases from SP 5.4.                                 Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT260965 === END OF ISSUE === Title: PO07963: Incorrect number of decimals in HTTP message Description: When sending a numeric attribute defined with decimals in a     notification or case action without the option to format        values, the created message will always add 3 decimal places,   regardless of the defined number of decimals.                    Workaround: N/A                                                              Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260963 === END OF ISSUE === Title: PO08050: PREFERENCE OF WORKING QUEUES NOT STORED PER WORKING QUEUE Description: The preferences are not saved per working queue.                Thus, the preferences for column order in the working queue     table is not saved correctly and can reset itself if the user   can access multiple working queues that have different          attributes.                                                      Workaround: The preferences should be stored per working queue to avoid     this.                                                            Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260962 === END OF ISSUE === Title: PO07994: DOCUMENTATION FOR ATTRIBUTE ENCRYPTION WITH DEFERRED WRITING ENABLED Description: There is a lack of documentation for attribute encryption and   what happens if attribute encryption is enabled with deferred   writting enabled                                                 Workaround: Information to be added:                                        If an attribute is encrypted will the history of the attibute   get lost?                                                       No. The history will be decrypted, which may take a while.      Do the indexes need to be rebuilt if the attribute              encryption is changed?                                          No, but it will be decrypted too, which will also take some     time.                                                           Other information:                                              Also notice that the index will be written encrypted to disk,   which means that the deferred writing cycle will take longer,   when using deferred writing.                                    Also, startups will take longer, as the indexes will be         decrypted during startup.                                        Status: Open Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260961 === END OF ISSUE === Title: PO07879: UNABLE TO CREATE NEW GROUP BY QUERIES WITH AN ERROR OF "NO PRIVILEGES TO PERFORM THIS ACTION" Description: When the user tries to create a new group by queries, an error  of "No privileges to perform this action" is reported.           Workaround: Make sure the same mandator is set in "Mandator Privileges" and "Mandator association" in the user's profile.                    Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260960 === END OF ISSUE === Title: PO07791: ERROR "CASE TRANSITION IS INVALID, CANNOT EXECUTE" SHOULD BE IMPROVED Description: After the automatic transition happened on a case, the case     state is not updated accordingly in the web client. When a user then try a transition, an error message of "Case transition is  invalid, cannot execute" is reported.                           This error message should be improved. It should display more   information about the problem and that a manual refersh of the  page might be required.                                          Workaround: Manually refresh the case investigation page in web client.      Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260959 === END OF ISSUE === Title: PO07709: SENDING A "RESETPREFERENCE" REQUEST COULD RESULT IN A CRASH. Description: When sending a "resetPreference" request with a type that       doesn't exist in the default preferences file. In this case,    there is a an access violation that could result in an          application crash.                                               Workaround: Not send any "resetPreference" request to the production system by external script / external application.                       Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260957 === END OF ISSUE === Title: PO07683: 'RETRY MERGINGS' CHANGES NOT COVERED BY 'REVISION COMPARISON'. Description: When comparing revisions and using the audit trail, the following attributes are missing: 'Retry mergings', 'Max merging attempts', 'Retry wait time', 'Update calendar profiles', and events fields for 'Mergings'. Even if 'Enforce time' is cleared, 'Tolerance days' incorrectly displays in the revision compare. Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT260956 === END OF ISSUE === Title: PO07674: (UN)MARK AS FRAUD IN CASE INVESTIGATION FOR INDEX QUERY PRODUCES ERROR WHEN OTHER EMPTY INDEX QUERY EXISTS. Description: When a case investigation has two index queries, one with       records, and an empty one, the mark / unmark operation on an    index query record creates an error popup message "No query     parameter for Index query found"                                 Workaround: Workaround: Reload the case investigation page.                  Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260955 === END OF ISSUE === Title: PO07766: DEADLOCK WHEN PERFORMING QUERY CSV EXPORT BEFORE QUERY IS FINISHED Description: The instance can run into a deadlock situation if encrypted     exports are enabled and a csv export is triggered before the    query has finished. The instance cannot shutdown properly       anymore and the accessing the query result may freeze the       browser.                                                         Workaround: no proper workaround available.  Can only kil lthe process, but may havesync problems.                                           Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260954 === END OF ISSUE === Title: PO07651: NO INDEX SELECTABLE FOR SAI IF MANDATOR PRESELECTED Description: No index selectable for SAI if mandator preselected.             Workaround: Save the SAI and then update it.                                 Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260953 === END OF ISSUE === Title: PO07620: The application SHOULDN'T BE ABLE TO REGOLIVE A RETIRED REVISIONWHICH USES A DISABLED NOTIFICATION IN A RULE Description: IBM Safer Payments shouldn't be able to regolive a retired      revision which uses a  disabled notification in a rule.          Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260951 === END OF ISSUE === Title: PO07605: URIDS IN AUDIT LOG ONLY VALID FOR THE CURRENT INSTANCE Description: The URIDs printed in the audit log for Query execution and Fraud marking were only valid for the instances where the API was    active. After switiching the API, it wasn't possible anymore to query the records without changing the API again. Also, after   performing a restore, the urid information might have been lost completely as the restore overwrote most data.                   Workaround: N/A                                                              Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260950 === END OF ISSUE === Title: PO07689: MESSAGE QUEUE INTERFACE (MQI) RESTARTED AFTER GOLIVE WITH "CLOSEDURING GOLIVE" Description: When using the setting "Close during golive", the Message       Command Interface (MCI) and MQI will be deactivated but only    the MCI will be reactivated afterwards.                          Workaround: Save cluster after a golive.                                     Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260949 === END OF ISSUE === Title: PO07681: RHEL 7 SYSTEMD SCRIPT MAY RANDOMLY KILL INSTANCE WHEN PERFORMING SYSTEMCTL STOP Description: The RHEL 7 systemd script in the Safer Payments Implementation  Guide used the parameter TimeoutStopSec=infinity, which is not  available in the RHEL 7.4 systemd version 219 yet. It was added in version 229. The old version accepted this parameter without warning, but did not use it correctly. By running this script,  systemd could randomly kill the application during service      stop, which will result in data loss.                           Incorrect part of the script:                                   [Unit]                                                          Description=Safer Payments Service                              After=network.target                                            [Service]                                                       Type=simple                                                     User=iris                                                       ExecStart=/usr/bin/iris                                         rootpath=/opt/ibm/safer_payments/myInstallation id=1 >          /opt/ibm/safer_payments/myInstallation/log/nohup.out 2>&1       Restart=no                                                      TimeoutStartSec=0                                               TimeoutStopSec=infinity                                         LimitNOFILE=32768                                               LimitNPROC=8192                                                 LimitRTPRIO=20                                                  [Install]                                                       WantedBy=multi-user.target                                       Workaround: As a workaround, replace the above part of the script with this below:                                                          [Unit]                                                          Description=Safer Payments Service                              After=network.target                                            [Service]                                                       Type=simple                                                     User=iris                                                       ExecStart=/usr/bin/iris                                         rootpath=/opt/ibm/safer_payments/myInstallation id=1            Restart=no                                                      TimeoutSec=0                                                    TimeoutStartSec=0                                               TimeoutStopSec=0                                                SendSIGKILL=no                                                  KillSignal=SIGTERM                                              LimitNOFILE=32768                                               LimitNPROC=8192                                                 LimitRTPRIO=20                                                  [Install]                                                       WantedBy=multi-user.target                                       Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260948 === END OF ISSUE === Title: PO07653: ERROR IN ESCAPING OF RDI Description: Currently, text values for RDI ignore surrounding quotes during escaping. For example, it is not necessary to escape double     quotes when surrounding text values with single quotes. The     text value test"test shouldn't be written to RDI as             'test""test' but as 'test"test'.                                Escaping of double quotes " and curved quotes  is not          necessary when surrounding text values with single quotes.       Workaround: alter duplicate double quotes to normal double quotes with sed  sed 's/\"\"/\"/g'                                               sed 's/\\/\/g'                                                Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260947 === END OF ISSUE === Title: PO07823: RULE NAME CANNOT BE PARSED PROPERLY IF IT CONTAINS NUMBERS AND WHITESPACE ONLY Description: Rule name cannot be parsed properly if it contains numbers and  whitespace only. As a result, for example, the changes in such  rule(s) failed to be reported in Revision Comparison.            Workaround: Remove the whitespace(s) from such a rule name.                  Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260945 === END OF ISSUE === Title: PO07704: OCCMS TRIGGERED IN PARALLEL Description: When Clusters > OCCMs (Outgoing channel configuration) are      triggered in parallel. It is possible that only one of the      OCCMs will be delivered then. The other(s) will not be tried to be delivered until the next restart.                             Workaround: No workaround presently                                          Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260944 === END OF ISSUE === Title: PO07608: THE INSTANCE MAY CRASH WHEN THE FILL MASTERDATA FUNCTIONLITY IS CALLED WHILE A GOLIVE IS PROCEEDING Description: The instance may crash when a golive is proceeding at the       same time when the fill masterdata functionlity is called (i.e. sending a case action that contains masterdata values from the  case data).                                                      Workaround: Avoid sending case action with masterdata value filled during a golive.                                                          Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260943 === END OF ISSUE === Title: PO07676: UN SANCTION LIST FORMAT ISN'T ACCEPTED CORRECTLY. Description: Safer Payments isn't parsing the UN Sanction List correctly.    Some XML tags aren't accepted, if they are in the same line as  previous XML tags. This may result in empty names and an empty  search tree.                                                     Workaround: Workaround:                                                     Performing a "pretty print" on the XML of the UN sanction lists avoids these issues. All XML tags must have its own line.        Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260942 === END OF ISSUE === Title: PO07671: CATEGORIES ARE NOT TRUNCATED ACCORDING TO THEIR ATTRIBUTE LENGTH Description: Categories are not truncated according to their attribute       length. The value can much longer, even if the attribute cannot handle the length. This might be even more significant when     using UTF-8 category values that use multiple bytes per         characters. In this case, it isn't visible that the attributes  cannot handle this attribute length.                             Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260941 === END OF ISSUE === Title: PO07647: COULD NOT RESOLVE OLD CHAMPION REFERENCES Description: The retired champion B in the submandator couldn't be loaded    anymore. It is not visible in UI anymore and needs to be        removed from file level on every instance.                      There isn't a solution for this, as the retired champion B has  insufficient information to be displayed, as it would need      revision A for all required attributes.                         But this means an undocumented information loss, as the old     champion B isn't accessible anymore and also requires the user  to delete files by console on multiple instances without having a printed filename.                                              Workaround: N/A                                                              Status: Open Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260940 === END OF ISSUE === Title: PO07805: ECI SOCKET IN USE AFTER RESTORE Description: This issue occurs in rare situations after restarting the       instance via UI button or after restoring it.                   This issue only happens when using domain names for the ECI.     Workaround: Use of IPs as opposed to hostnames                              The instances need to be running and synchronized before        changing hostname to IP.                                        Change ECI and FLI first to IP on all instances. This will      disconnect and reconnect the interfaces and may cause temporary connection issues. After all instances have changed ECI and     FLI, you can change the SCI. All cluster changes are            synchronized via SCI, so changing this may cause temporary      connection issues.                                               Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260938 === END OF ISSUE === Title: PO07790: UPDATING FROM LOWER RELEASE TO SP 5.4.0.09, 5.5.0.02 OR HIGHER CAUSES FATAL ERRORS DURING STARTUP FOR KPI AND SAI CONDITIONS. Description: Updating from lower release to SP 5.4.0.09, 5.5.0.02 or higher  causes fatal errors during startup for Key Performance          Indicator and Status Alarm Indicator conditions. Additionally   when doing a second startup, the SAI / KPI conditions are lost. Workaround: Resave SAI's / KPI's after first startup.            Workaround: Saving the KPI's again is the workaround.                        Status: Closed Affected Version: 5.6.0 Fixed Available: No fixed available Known Issue ID: DT260937 === END OF ISSUE === Title: PO07618: EMAIL NOTIFICATIONS SENT DO NOT HAVE A SUBJECT, EVEN WHEN DEFINED IN THE NOTIFICATION SETTING. Description: Email notifications sent in IBM Safer Payments will not have a  subject, even when defined in the Notification setting. This is an issue in Safer Payments 5.5.0.00 and 5.5.0.01.                Workaround: This issue is fixed in 5.5.0.02.                                 Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260936 === END OF ISSUE === Title: PO07701: OPTIMIZATION OF SHADOW MEMORY HANDLING FOR PROFILE COMPUTATION Description: Inefficient handling of shadow mutexes could lead to extensive  wait time during shadow commit phases while computing profiles.  Workaround: None                                                             Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260935 === END OF ISSUE === Title: PO07603: MULTIPLE FILES OF THE SAME OUTGOING CHANNEL CONFIGURATION AFTER LEGACY CONVERSION Description: Multiple files of the same outgoing channel configuration after legacy conversion.                                               Workaround: N/A                                                              Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260934 === END OF ISSUE === Title: PO07860: INCREASING INDEX SEQUENCE MDC CAPACITY ONLY SHOULDN'T NEED A INDEX SEQUENCE REBUILD Description: If only the MDC capacity of an index sequence is increased, and its DDC capacity keeps unchanged, there is no need to rebuild   the index sequence.                                              Workaround: Before golive a challenger revision which contains no DDC       increase of any index sequence, disable the setting of "Rebuild indexes" in "Administration" -> "System configuration" ->       "Decision Models".                                               Status: Open Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260933 === END OF ISSUE === Title: PO07613: CASE ACTIONS MISSING IN CASE CLOSE CODE SYNCHRONIZATION Description: Case actions missing in case close code synchronization.         Workaround: N/A                                                              Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260931 === END OF ISSUE === Title: PO07851: CASE ADDED TO USER PRIVATE QUEUE ON ALL INSTANCES IS ONLY REMOVED FROM THE PRIVATE QUEUE ON THE API INSTANCE AT CLOS Description: When a case is assigned to a user, the case is added to the     private queue of the user on all instances. But when it is      closed later on, the case is only removed from the private      queue on the API instance. Thus, when switching the API to a    remote instance work case will show cases that have been closed on the former API instance.                                      Workaround: After a restart the private queue is correct again.             This issue is already resolved in 5.6.                           Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260930 === END OF ISSUE === Title: PO07828: CASE CLASS IS NOT UPDATED WHEN UPDATING ITS WORK FLOW'S TRANSITION Description: Changing the case work flow without additionally saving the     case class does not update the case class' transitions. Thus    the old transitions are used within cases in this case class.    Workaround: Manually save the case class after its work flow's transition   is updated.                                                      Status: Open Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260929 === END OF ISSUE === Title: PO07784: PRIMARY RECORD ID NOT ASSIGNED AT SINGLE INSTANCE INSTALLATION Description: The primary record ID is not assigned when using SP with single instance. As more and more clients are requiring us to send     record with unique ID to their existing case management system, and URID cannot be written as output, the primary record ID     becomes the only unique record ID to be sent at single instance installation which is typical during testing phases before      production.                                                      Workaround: Create a second instance and detach it. Primary record IDs are  assigned, if there are 2 instances in the cluster or more.       Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260928 === END OF ISSUE === Title: PO07631: THE OPTION TO DELETE CPP IS MISSING. Description: There is no option for deleting CPP.                             Workaround: N/A                                                              Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260927 === END OF ISSUE === Title: PO07662: DEAD LINK IN DOCUMENT "UPDATING IBM COUNTER FRAUD MANAGEMENT FOR SAFER PAYMENTS" Description: Link in Updating IBM Counter Fraud Management for Safer         Payments located at                                             https://www-01.ibm.com/support/entdocview.wss?uid=swg27049490&aid=1 references a URL that seems to be dead.                                                                                     The URL is under the "About this publication" section.                                                                          To obtain the most current version of this publication go to:   http://publibfp.dhe.ibm.com/epubs/pdf/C3427690.pdf               Workaround: None - Please update document or URL                             Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260925 === END OF ISSUE === Title: PO07814: FCD DATA STREAM MAPPING ERROR AFTER UPGRADE FROM IRIS COUNTER FRAUD MANAGEMENT 5.3.X TO IBM SAFER PAYMENTS 5.5.X Description: The FCD Data Stream gets lost when upgrading from Iris 5.3.0 to Safer Payments. This is due to an issue in Safer Payments code, which doesn't recognise the mappings from Iris 5.3.0.x           Workaround: New mappings can be set by navigating to Models, select a       challenger of the mandator where the mappings are defined and   navigate to General/Mappings. On the upper right dropdown menu  select the Messages which are shown in the mapping table below. Select the Message for which you have your FCD-File loading job defined. Now you have to define the FCD mapping for every       missing attribute again. Help about this can ber found by       clicking on the help button inside the edit section."            Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260924 === END OF ISSUE === Title: PO07783: THE FUNCTION THAT IS USED TO RETRIEVE VALUES FROM THE SHADOW MDC OF BOOLEAN MASTERDATA DOES NOT READ THE CORRECT VALUES. Description: The function that is used to retrieve values from the shadow    MDC of boolean masterdata does not read the correct values.     Thus, depending on the current position in the deferred writing cycle incorrect values may be displayed.                         Workaround: N/A                                                              Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260923 === END OF ISSUE === Title: PO07712: PURGING ALL INDEX NODES IN COMBINATION WITH "RECORD PURGED ENTRIES" COULD RESULT IN AN INDEX VIOLATION. Description: The index root is initialized with node 0. If the purged        records started at another record, they overwrote node 0 again, which created an access violation.                              This option is found within Model>Profiling>Indexes.            Enable Purge Outdated Entries then Record Purged Entries.        Workaround: Avoid to purge all records or to disable "record purged         entries" for indexes that are purged until they are empty.       Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260922 === END OF ISSUE === Title: PO07600: DUPLICATE ENTRY ABOUT THE FIELD "FROM" IN THE ONLINE HELP OF "ALERT MESSAGE INTERFACE". Description: In the online Help for "Alert message interface" in Safer       Payments 5.4.x, there is a duplicate entry for the field "From". Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260921 === END OF ISSUE === Title: PO07561: UNABLE TO CREATE CASE ACTION IF THE EXTENDED SELECT DIALOGS IS DISABLED Description: Unable to create case action if the setting "Extended select    dialog" is disabled.                                             Workaround: Enable the setting of "Extended select dialog" for the user     account.                                                         Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260920 === END OF ISSUE === Title: PO07573: THE IMPLEMENTATION GUIDE IS MISSING SOME CHAPTERS WHICH CAN LEAD TO DEPLOYMENT ISSUES IN SOME SCENARIOS Description: The Implementation Guide for IBM Safer Payments is missing some chapters in the version located in the IBM Support Portal:      https://www.ibm.com/support/entdocview.wss?uid=swg27049489       Workaround: If you are planning any updates / upgrades or new deployments   please contact the Safer Payments Support team via PMR in order to get all the relevant information via PMR.                     Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260919 === END OF ISSUE === Title: PO07401: FATAL ERROR DUE TO MISSING INDEX FOR META ACCOUNT ATTRIBUTE Description: Fatal errors may be generated if there is no index for the meta account attribute. For example, this issue may cause a fatal    error when running the analysis with rule optimization, and the analysis stutas is set to "Aborted due to recent model changes". Workaround: Add an index for the meta attribute account.                     Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260918 === END OF ISSUE === Title: PO07460: SANDBOX TEST should SUPPORT the operator "ATTRIBUTE OF SAME TRANSACTION" Description: When computing the operator "attribute of same transactions"    during a sandbox test, an error "MATHOP_WITH_SAME" is thrown.   There is no extra text explanation of this error.                Workaround: Before running the sandbox test, temporarily disable the        elements which have conditions containing the operator of       "attribute of same transaction" (attribute with square          brackets).                                                       Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260917 === END OF ISSUE === Title: PO07403: CASE SELECTION CONDITION OF META ATTRIBUTE NOTIFICATION AND REMINDER IS NOT WORKING AS EXPECTED Description: The Case Selection condition of meta attributes notification andreminder is not working as expected.                             Workaround: N/A                                                              Status: Closed Affected Version: 5.3.1 Fixed Available: No fixed available Known Issue ID: DT260916 === END OF ISSUE === Title: PO07420: BDI JOB STATUS IS SHOWING INCORRECT STATUS Description: When API and BDI is enabled on different instances, the job     status table is not updated correctly on the API instance, if   the instances are not completely synchronized via FLI.           Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260915 === END OF ISSUE === Title: PO07404: WRONG TIMESTAMP FORMATS ARE NOT GETTING RECOGNIZED AS INVALID. Description: This may lead to future timestamps that have a negative impact  on calendars / profiles.                                         Workaround: N/A                                                              Status: Closed Affected Version: 5.3.0 Fixed Available: No fixed available Known Issue ID: DT260914 === END OF ISSUE === Title: PO07323: MISSING ERROR MESSAGE FOR MCI XML PARSER PROBLEM Description: There is no specific error message for MCI XML parser issue.    Instead, there is a warning:                                     Signal caught after accessing null                              pointer. Raise exception:Segmentation fault                    There are three problems fixed in thia APAR:                        1. Self closing tags are accepted                               2. Whitespace between tags is accepted as in the initial           5.4.0 implementation                                         3. Added error messages for major XML parser issues               (closing tag missing)                                      Workaround: Send valid XML to MCI, as described in the Implementation Guide.Do not send self closing XML tags.                               Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260912 === END OF ISSUE === Title: PO07457: UPGRADE FROM LOWER RELEASES TO 5.4.X OR HIGHER RELEASES CAUSES LOSS OF SAI AND KPI CONDITIONS Description: When upgrading from a lower release to 5.4.x or a higher        release the configuration files for status alarm indicators     (SAI) and charts are rewritten on startup, however conditions   of SAI's and key performance indicators (KPI) (which are part   of charts) are lost in this process, which means they do not    get written to the configuration file. The elements are loaded  correctly with the conditions, but after restarting an instance a second time, the conditions cannot be read anymore.            Workaround: After first startup with the higher release save all charts     that have KPI's with conditions. Save all SAI's with            conditions. This will override the configuration files          correctly with the conditions.                                   Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260911 === END OF ISSUE === Title: PO07336: MISSING COMMA IN JSON OBJECT FOR INVESTIGATION CASE Description: A comma is missed in investigation case written to disk.         Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260910 === END OF ISSUE === Title: PO07330: "NO MAPPING MESSAGE FOR INVALID OR MISSING MTID" EVENT LOG MESSAGE FROM RUNNING "STATUSREQUEST" Description: "No mapping message for invalid or missing MTID" event log      message is reported from running the request "StatusRequest".    Workaround: Add a valid MessageTypeId in the StatusRequest. For example:                                                                    MessageTypeId="1">                                        Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260909 === END OF ISSUE === Title: PO07277: INCREASING MEMORY CONSUMPTION ON THE INSTANCE WITH MQ INTERFACE ENABLED Description: Increasing memory consumption on the instance with MQ interface enabled. This eventually causes instance crash with out of      memory error.                                                    Workaround: Restart the instance when its memory usage is above the defined threshold.                                                       Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260908 === END OF ISSUE === Title: PO07406: ERROR WHEN TRYING TO INSTALL IBM SAFER PAYMENTS. Description: The following error appears when trying to install IBM Safer    Payments using the following command:                           sh ./SaferPayments?.bin                                         Error message:                                                  Preparing to install                                            Extracting the installation resources from the installer        archive...                                                      Configuring the installer for this system's environment...      No Java virtual machine could be found from your PATH           environment variable. You must install a VM prior to            running this program.                                            Workaround: This is expected behaviour if Java is not installed in the      system.                                                         To be able to install IBM Safer Payments without Java installed follow the steps below:                                         unzip ibm_jre_8.0.2.10_linux_x64.vm                             tar xf vm.tar.Z                                                 chmod +x jre/bin/java                                           chmod +x SaferPayments.bin                                      su                                                              export PATH=$PATH:pwd/jre/bin                                 ./SaferPayments.bin                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260907 === END OF ISSUE === Title: PO07316: MISSING STRING ENDING WHEN READING FROM CUSTOM PARSER MEMORY IN IBM SAFER PAYMENTS 5.4.0.04 Description: MISSING STRING ENDING WHEN READING FROM CUSTOM PARSER MEMORY IN IBM SAFER PAYMENTS 5.4.0.04.                                     Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260906 === END OF ISSUE === Title: PO07368: OPERATOR "CONTAINS" IS IGNORING SEARCH STRINGS THAT CONTAIN WILDCARDS * OR ? IN CONDITIONS. Description: The operator "contains" has issues with wildcard characters     while searching in text values. When using wildcard characters  * or ?, the text string is getting ignored completely. The      condition neither hits its original value nor its wildcard      search string counterpart. When using a list with multiple      search strings, only those with wildcard characters are         getting ignored. Others will hit normally. This affects all     kind conditions in the software. Rule conditions, mandator      conditions, case conditions and other conditions. Other         operators are not affected.                                      Workaround: Use other operators                                              Status: Closed Affected Version: 5.4.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT260905 === END OF ISSUE === Title: PO07450: SANDBOX TEST CANNOT BE RESTARTED AFTER THE ERROR MATHOP_WITH_SAME IS THROWN Description: If a sandbox test is failed with the error MATHOP_WITH_SAME,    then it can no longer be restarted.                              Workaround: Restart the instance.                                            Status: Closed Affected Version: 5.5.0 Fixed Available: No fixed available Known Issue ID: DT260904 === END OF ISSUE === Title: PO07463: DISPLAY AND LOG ISSUES IF BDI IS ON REMOTE INSTANCE Description: If the BDI was on another instance than API, there were "I 0276 Batch data interface job was interrupted processing data file"  log messages. Additionally, the Job was not displayed as        "running" in job table, even if the instance was not out of     sync and log message "I 0191 Job stopped" was showing twice the amount of records total.                                         Workaround: This is a display issue. To fix those display isues, you need   to run the BDI on the same instance as the API.                  Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260903 === END OF ISSUE === Title: PO07365: LARGE LISTS CREATE JAVASCRIPT ERRORS WHEN LEAVING THE FORM AND FREEZE CHROME BROWSER Description: Large lists create javascript errors when leaving the form and  freeze chrome browser.                                           Workaround: Use Firefox or disable "Extended select dialogs" in user        account.                                                         Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260902 === END OF ISSUE === Title: PO07051: USER UNABLE TO CREATE GROUP-BY-QUERIES IF HE/SHE IS ASSOCIATED WITH MANDATOR A AND IS GRANTED WITH ROLE FOR SUBMANDATOR B Description: When a user account is associated with mandator A and user is   granted with role for submandator B allowing him/her to view    and edit group-by-queries he is not able to add a new one.       Workaround: Set same mandator for "Mandator association" and "Mandator      Privileges" for the user.                                        Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260901 === END OF ISSUE === Title: PO06997: CLUSTER UPDATE DURING RESTORE (AND DEFERRED WRITING ENABLED) Description: If deferred writing is enabled, the donor instance still can    receive cluster updates during status "dumping". Also, the      incoming FLI of donor will be activated during cluster update   (in status dumping). This might impact the restore and cluster  health.                                                          Workaround: None.                                                            Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260900 === END OF ISSUE === Title: PO06973: SIMULATION OF MASTERDATA WHILE INDEX IS CHANGING WITH DEFERRED WRITING ENABLED INSTANCE MIGHT CRASH. Description: In case of enabled deferred writing, it is also possible that   the simulating instance might crash. It is not relevant if the  data is loaded by BDI jobs, FLI, MCI or MQ. All data that might modify index entries might lead to a crash when simulating      masterdata if deferred writing is enabled.                       Workaround: Do not simulate masterdata of an index that is loading data and might add new index entries. This might lead to wrong simulated masterdata results. In case of enabled deferred writing, it is  also possible that the simulating instance might crash.          Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260899 === END OF ISSUE === Title: PO06838: SAFER PAYMENTS CRASHES WHEN DOING SINGLE SIGN ON. Description: Safer Payments crashes when Single Sign On is enabled and the   LDAP user is trying to logon to Safer Payments instance.         Workaround: Do not enable Single Sign On feature in Safer Payments until    this APAR is fixed.                                              Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260898 === END OF ISSUE === Title: PO07183: COMMON POINT QUERY RESULTS ARE NOT GROUPED IF THE COMMON POINT ATTRIBUTE VALUES ARE FROM DDC Description: If the attribute value is shorter than the defined attribute    length and if the DDC is enabled for the common point query, thequery result may show this common point attribute value not     grouped together if the corresponding records are from DDC.      Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260897 === END OF ISSUE === Title: PO07171: PERFORMING COUNT QUERY IS NOT POSSIBLE ANYMORE. Description: Clicking on the "count" button of a query triggers a F 99 into  the log. There is no workaround to execute the count button.     Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260896 === END OF ISSUE === Title: PO06996: SIMULATION QUERIES CRASHES Description: the issue can occur when rule report queries are stopped        manually or if the underlying simulation is aborted (which is   the case when rules  are changed and/or the simulation is       manually aborted) while the rule report queries are still       running.                                                         Workaround: None                                                             Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260895 === END OF ISSUE === Title: PO06995: CRASH ON DELETION OF DEFINED RISK LIST ENTRIES Description: Iris crashes (debug binary), if the user tries do delete the    entry. If the entry is opened, "no_entry_found" is displayed.   With a release binary, Iris freezes and the entry cannot be     deleted.                                                         Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260894 === END OF ISSUE === Title: PO07261: INCOMPLETE DOCUMENTATION OF META ATTRIBUTE URIDCOMPUTATIONCOMPLETE Description: The documentation of the meta attribute UridComputationComplete (added in IBM Safer Payments 5.4.0.03) needs to be improved.     Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260892 === END OF ISSUE === Title: PO07095: MERCHANT MONITORING LEGACY CODE BETWEEN 5.3.1 AND 5.4.0 Description:  Since the rule mapping ids of merchant monitoring changed      between IBM Safer Payments versions 5.3.1 and 5.4.0.            Safer Payments 5.4.0 might not start, if there are reporting    job definitions that were created with Safer Payments 5.3.1.    This is a production problem, because IBM Safer Payments        instance cannot start if a reporting job is defined that tries  to access a merchant monitoring rule with the wrong rule ids.    Workaround: None at this time.                                               Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260891 === END OF ISSUE === Title: PO06976: MQ CONNECTION PROBLEMS Description: It is possible to lose a thread in the application when the     save button has been hit multiple times. At this stage it won't be possible to shut the interfacer down .The thread will keep   running until the instance is shut down.                         Workaround: Instance is shut down.                                           Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260890 === END OF ISSUE === Title: PO06919: INSTANCE WAITING FOR A PASSWORD INSERTION WHEN LOG MESSAGE COINCIDENT Description: Block console log message completely during password insertion.                                                                 The instance was indeed still waiting for a password insertion. The log message was just a coincident and would not have        disturbed inserting a password.                                  Workaround: The workaround is ignore log messages that are printed during   password prompt (in fact, everything is blocked and there       should not be much log messages).                                Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260889 === END OF ISSUE === Title: PO07083: QUOTES IN DEFINED RISK LIST ENTRIES Description: If a defined risk list entry includes quotes ( " ) these are    escaped on saving the entry. The problem is that for the        comparision the escaped value is used and not the value like    the user entered it.                                            This can lead to wrong results being displayed                   Workaround: Avoid using quotes untilt he issue is resolved.                  Status: Closed Affected Version: 5.3.0 Fixed Available: No fixed available Known Issue ID: DT260888 === END OF ISSUE === Title: PO07060: EMAILS CONTAINING THAI CHARACTERS ARE NOT DELIVERED CORRECTLY Description: When thai characters are used in an email case action, the email received by the target is not correct. All thai characters are incorrect and the placeholders are not filled but displayed as  {attribute}.                                                     Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260887 === END OF ISSUE === Title: PO06999: CRASH IF CASE IS WRITTEN TO STREAM WHILE GOLIVE Description: Masterdata of case queue is written, current champion referencs might not be created for case queue yet. Also a crash happens   when the case is a collusion case and the firstPartyIndex is    accessed. There might be more scenarios due to the fact that    writing cases is not locked against golives.                     Workaround: In order not to experience this issue avoid case investigation  during a go-live.                                                Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260886 === END OF ISSUE === Title: PO06879: LOADING... IN PROFILE PAGE EVEN AFTER THE LOADING PROCESS HAS FINISHED. Description: In the Profile page the word 'Loading' can be seen although the loading has been completed.                                      Workaround: No known workaround.                                             Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260885 === END OF ISSUE === Title: PO06678: CORRECT HELP/DOCUMENTATION Description: Number of threads that are spun off for the respective service  computations (because they are spun off for each step, the      total number of threads started for a service may actually be   larger).                                                                                                                        -The explanation refers to an option that is no longer          supported."                                                      Workaround: N/A                                                              Status: Closed Affected Version: 5.3.0 Fixed Available: No fixed available Known Issue ID: DT260883 === END OF ISSUE === Title: PO06876: MQ CONNECTION ISSUES WHEN THE SAVE BUTTON IS PRESSED MULTIPLE TIMES. Description: When the Websphere MQ Interface is enabled and the Save button  is pressed multiple times quickly (within the reconnect         interval) it is possible for a thread to be 'lost'. Then when   the interface is turned off that thread will continue to        process MQ messages until the instance is shut down             This issue occurs in both IBM Safer Payments 5.4.0 and 5.4.0.01. Workaround: Shut down the instance.                                          Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260882 === END OF ISSUE === Title: PO06885: GROUP BY QUERY RESULTS SCRAMBLED. Description: The schedule on the page Group by query gets out of             alignment depending on the number of records. This happens in   all browsers. This doesn't happen with a low number of records  (such as 200) but with 3000 for example.                         Workaround: None                                                             Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260881 === END OF ISSUE === Title: PO06715: Crash may occur when accessing a peer index while using deferredwriting Description: Crash may occur when accessing a peer index while using deferredwriting                                                          Workaround: N/A                                                              Status: Closed Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT260880 === END OF ISSUE === Title: PO10175: MCI STATUS REQUEST RESPONSE IS XML INSTEAD OF JSON Description: When sending in a status request message with a JSON message    type, SP ignores the message type and responds in XML format.    Workaround: If you are using an HTTP message request you can include the    header -H 'content-type:applicaton/json', which will ensure that the response is in JSON. For example: curl                     http://127.0.0.1:1234 -H 'Content-Length: 2' -H                 'X-SP-Message-Type-Id:1' -H 'X-SP-Message-Id:1212121212121212'  -H 'X-SP-Protocol-Version:1' -H                                 'X-SP-Request-Type:StatusRequest' -H                            'content-type:applicaton/json' -d '{}'                          If you are only able to use a binary (TCP/IP) message, then     there is no workaround.                                          Status: Closed Affected Version: 6.6.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT260792 === END OF ISSUE === Title: PO10178: Disabling and re-enabling indexes or masterdata for extended masterdata queries can cause a crash during golive Description: If there are indexes and masterdata enabled for extended        masterdata queries on a champion revision, certain actions on   challenger revisions can cause crashes. A crash can occur on the                                                                API instance when creating the golive report if a masterdata had                                                                been disabled and re-enabled for extended queries prior to      creating the report. A crash can also occur on the API, or      remote, instance(s) if an index or masterdata is disabled for   extended queries, a golive report is created and canceled, and  the same index or masterdata is re-enabled for extended queries prior to executing a golive.                                     Workaround:                                                                  Status: Open Affected Version: 6.6.0 Fixed Available: No fixed available Known Issue ID: DT260736 === END OF ISSUE === Title: PO10172: UI ELEMENTS SOMETIMES MISSING WHEN IMPORTING A DEFINED RISK LIST. Description: When uploading a defined risk list, the 'Add Condition' element is missing.                                            Workaround: Selecting 'New defined risk list entry' first will cache the    'Add Condition' for use when uploading a defined risk list.      Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT260732 === END OF ISSUE === Title: PO10177: LOG WARNING 744 PRINTED WHEN CREATING CASE MANUALLY Description: [SP 6.3.1.05, SP 6.4.2.04, SP 6.5.0.02, SP 6.6.0.00] Log message744 is getting printed when opening an investigation case that  was created via case creation form and if there are at least twoinstances. This log message has no impact in this case, as      there's no transaction in remote instances that need to be      resolved.                                                        Workaround: Add "remote urid" and "primary instance id" as attributes to    case creation form.                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT260456 === END OF ISSUE === Title: PO10176: INCONSISTENT BEHAVIORS OF HAVING DECIMAL POINT VALUE IN EXPRESSION CONDITION Description: Conditions for non-decimal numeric attributes accept expression that may result in a decimal point value, although decimal point literal values in conditions are not allowed for non-decimal   numeric attributes.                                              Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT260398 === END OF ISSUE === Title: PO10174: DEADLOCK BETWEEN DISABLE SIMULATION AND WORK FLOW. Description: There is a small chance that the work flow for simulation could get stuck in a loop. As a result, it can't be stopped and       operations like golive will be blocked.                          Workaround: N/A                                                              Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT260168 === END OF ISSUE === Title: PO10173: UNREACHABLE INSTANCES CAN STILL BLOCK GOLIVES OF OTHER INSTANCES IN RARE SITUATIONS Description: In rare situations, when a process is killed but still in the   zombie state, then the instance will show up as unreachable, butconnections can still be created over the SCI, which can preventother instances from entering maintenance mode and performing   tasks like golives, even though the "Minimum number of active   instances" setting should be met.                                Workaround: Fully kill the process, or restart the server                    Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT260069 === END OF ISSUE === Title: PO10171: DEADLOCK BETWEEN EOD, CASE INVESTIGATION, AND CASE CONSOLIDATION. Description: [SP 6.5, SP 6.6] The end of day job can get stuck in a deadlock.It happens when EOD tries to archive cases, safer payments triesto consolidate cases, and a user is leaving the case            investigation page of the consolidated one - all at the same    time.                                                            Workaround: This issue does not exist on versions prior to 6.5. However, it is recommended setting the end of day job at the time when thereare only low user activities.                                    Status: Closed Affected Version: 6.5.0 Fixed Available: 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT259324 === END OF ISSUE === Title: PO10170: Simulation of Masterdata on lower mandator may not be populated Description: Masterdata on attributes without production data do not work    during simulation. Even when the masterdata is simulated, its   values are not applied to the simulated attribute. The attributestays empty. Subsequent model components using this attribute,  will compute wrong results.                                      Workaround: In general, masterdata that is used in rules should be stored in                                                                                                                                MDC, to avoid having to simulate masterdata.                     Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT258916 === END OF ISSUE === Title: PO10168: Profiling element's value set to default value when records in simulation data range are excluded by simulation conditions Description: If a record within the simulation data range is excluded from   being simulated as it doesn't meet simulation conditions, the   profiling elements are not simulated for this record, and this  record's profiling attributes are set to a default value by the simulation, depending on the type of attribute ('0' for numeric type and 'False' for boolean type).                              Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT258481 === END OF ISSUE === Title: PO10167: INSTANCE MAY SHUTDOWN AFTER DELETING FILES DURING A RESTORE. Description: During a restore, when the recipient instance finishes deleting the files, there is a possibility that the instance may shutdowncausing the restore process to stop. Contact the IBM support    team immediately for further guidance on recovery steps.         Workaround: N/A.                                                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT258298 === END OF ISSUE === Title: PO09919: POSSIBLE FLI RATE DROP AND INCREASED MEMORY CONSUMPTION IF NO MATCH FOUND ON REMOTE SEQUENCE LOOP. Description:  [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When a case gets created from query, on remote instances right transaction need to be retrieved in order to be altered. If no match is found, in the worst case, such sequence search continues until the end of the sequence. If the sequence is extremely long, such search could take a long time and block other FLI threads in the meantime/lead to high memory consumption. Workaround: Choose a remote lookup index that has rather many entries but a shorter sequence (e.g. customer id) over one with less entries  and long sequences (merchant id).                                Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT257944 === END OF ISSUE === Title: PO10165: CATEGORY COLOR AND LABEL OF MASTERDATA ATTRIBUTE ARE MISSING ON THE CASE PAGE. Description: [SP 6.3.1.06] On the case screen, the category color and        label of masterdata attributes are missing.                      Workaround: N/A.                                                             Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT257338 === END OF ISSUE === Title: PO10163: WHEN CREATING A NEW ATTRIBUTE WITH THE STORAGE TYPE SET TO "STORED ONLY IN DDC" THE VALUE SET IN THE DDC RECORDS FIELD IS SOMETI Description: When creating a new attribute and setting the storage type to   "stored only in DDC" and changing the default value, the new    value is not persisted after save, instead the default value    which is set in the System Configuration "Default xDC           Capacities" is persisted                                         Workaround: Update the DDC value in the attribute and save again             Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT256738 === END OF ISSUE === Title: PO10162: PMML MODEL IS NOT FIRED FOR MESSAGE COMPUTATION ON API INSTANCE AFTER REVISION COMPARISON Description: If a champion revision is compared to another revision that contains an identical PMML model except for its field mappings, the PMML model in the champion revision will not fire during message computation on the API instance. There is no such issue on non-API instances. Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT256707 === END OF ISSUE === Title: PO10161: QUERIES - IMPROVEMENT TO SYSTEM TIME BASED DATA RANGE ACCURACY. Description: When using timed based intervals (server time absolute, timestamp relative) the result might include records that are outside the actual data selection time due to performance reasons. If you need strict restrictions on this, you can always define query conditions that would filter those out. See Online Help for more details.                           Workaround: Per the Online Help, use conditions, such as query condition on SP System time meta attribute.                                   Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT255294 === END OF ISSUE === Title: PO10160: LOCKDOWN WITH DEFERRED WRITING ENABLED COULD LEAD TO DATA GAP. Description: If the FLI buffer is full, the instance goes into Lockdown. Oncea Lockdown status instance is restarted, there is potentially a data gap if Deferred Writing is enabled. Restoring other        instances from this instance could spread the data loss. The    logs would need review to determine potential URID's affected   and determine best recovery plan.                                Workaround: Please contact IBM Support for guidance if your FLI Buffer is   full and a Lockdown occurs.                                      Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT255159 === END OF ISSUE === Title: PO10156: UNEXPECTED ERROR WHEN ACCESSING DASHBOARD ON THE UI Description: The request of getDashboardKeyPerformanceIndicatorData may      return empty data object, leading to an unexpected error thrown on the UI.                                                       Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT254955 === END OF ISSUE === Title: PO10158: ATTRIBUTE VALUES ARE NOT POPULATED IN HTML FORMATTED EMAIL FROM THE REMOTE INSTANCE Description: Attributes defined in email HTML body template of SMTP          notification, are not populated if the email is sent via a      remote instance. There is no such problem if the notification is sent from the API instance.                                    This occurs with for case actions as well. Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT253521 === END OF ISSUE === Title: PO10157: ADDING OR DELETING RULESETS MAY LEAD TO A CRASH Description: In rare cases, adding or deleting Rulesets may lead to a crash if it happens at the exact same time as certain other actions like showing references. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT248150 === END OF ISSUE === Title: PO10155: API REQUEST "GETCPPSTOHIGHLIGHT" MAY CRASH INSTANCE ON NON-EXISTENT UID. Description: Calling "getCppsToHighlight" API request with a wrong parameter will crash the instance.                                         Workaround: N/A.                                                             Status: Closed Affected Version: 6.6.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT247432 === END OF ISSUE === Title: PO10154: DEFINED RISK LISTS - AUDIT TRIAL BUTTON LOCATION HAS CHANGED ON NEW UI Description: The location of the audit trail button for Defined risk lists   has changed on the new UI from the Defined risk list entries    page to the Defined risk list page. If the user role only has   permission to 'View defined risk list audit trial' this does not allow them to view the audit trial.                             Workaround: Add user role permission to access Defined risk lists.           Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT247197 === END OF ISSUE === Title: PO10153: SIMULATION - MODIFYING DATA SELECTION TARGET CONDITIONS AFTER SIMULATION STARTS TRIGGERS LOG 0063 Description: If log message 0063 is enabled, and a simulation is run,        modifying the data selection target conditions and re-saving    them can cause E 0063 Could not write condition: input element  or expression does not exist to print to log.                    Workaround: The log entry can be avoided by updating the target conditions  after disabling the Simulation.                                  Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT247196 === END OF ISSUE === Title: PO10152: WHEN CONFIRMING AN ASSIGNED INSTANCE FOR SIMULATION, AN "UNEXPECTED ERROR" GETS THROWN. Description: When confirming an instance to assign a simulation to, if you   select the same instance to which an instance was already       assigned then an unexpected error is thrown. If this is done on the simulation report page, and a user attempts to initiate a   simulation, then afterwards certain revision actions like       changing the simulation instance and copying the revision will  fail.                                                            Workaround: Start a simulation and then stop it (while it is still on the   previously assigned instance). After that, all actions will be  possible again.                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT247072 === END OF ISSUE === Title: PO10151: QUERY RESULT SUMMARY SHOWS WRONG INFORMATION IF THE ATTRIBUTE FRAUD IS NOT INCLUDED IN QUERY RESULT Description: When the attribute fraud is not included in the query columns,  the number of fraudulent transactions is always zero and all    transactions are genuine in the query result summary. The "count number of records" does not have this issue though.             Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT246977 === END OF ISSUE === Title: PO10150: INCORRECT DISPLAY IN "INVESTIGATION ACTIONS PER CASE STATE" TAB Description: In "Investigator / case class" column in "Investigation actions per case state tab", the display of the case class is not       correct.                                                         Workaround: N/A                                                              Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT246872 === END OF ISSUE === Title: PO10149: GROUP BY QUERY TITLE NOT DISPLAYED IN RESULTS Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] The name of a group by query isnot displayed on the title of the results page.                  Workaround: None                                                             Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT246770 === END OF ISSUE === Title: PO10148: UNABLE TO SAVE COUNTER IF ITS EVALULATION CONDITION CONTAINS AN ATTRIBUTE WITH DDC ONLY STORAGE Description: Counter definition cannot be saved if its evalulation condition contains an attribute with DDC only storage. An error of "An    entry in this field is required" is printed under this attribute in the evaluation condition on the UI.                          Workaround: N/A                                                              Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT246640 === END OF ISSUE === Title: PO10147: PAGE AUTO REFRESH - CHANGING TO 0 FAILS FOR SESSION COUNTDOWN AND FOR NOTICE FREEZES UI. Description: Under System Configuration for Page Auto Refresh, if Session    Countdown is set to 0 and save is pressed, a validator form     error occurs and it does not save. For Notices, setting the     value to 0 can cause UI to be unusable due to constant refresh  of Notices, and could cause a "Failed to Fetch" error.           Workaround: Session Countdown: Set to the value in seconds of the session   timeout setting, or some high value.                            Notices: Set it to some high value to never refresh             automatically, and do not set it less than 10s.                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT246460 === END OF ISSUE === Title: PO10146: PERFORMANCE OF DASHBOARD CHARTS MAY BE SUBPAR WHEN LARGE NUMBER OF KPIS IS ENABLED. Description: Performance of the dashboard user interface suffers dramaticallywhen there are a large number of KPIs enabled for a dashboard   chart.                                                           Workaround: Reduce the number of KPIs enabled for preview on the dashboard   Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT246386 === END OF ISSUE === Title: PO10145: CRASH WHEN REMOVING REVISION THAT RUNS SIMULATION Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5, SP 6.6] A remote       instance might crash or create a backtrace after deleting a     revision that has a rule query running on an active simulation  if the simulation was configured to run on a remote instance.    Workaround: Stop simulation and wait until it is finished before erasing a  revision.                                                        Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT245966 === END OF ISSUE === Title: PO10126: PMML - SAVING MULTIPLE TIMES DURING UPLOAD CAN LEAD TO CRASH. Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] A crash can occur when         attempting to save the model component multiple times while the PMML upload is still in progress.                                Workaround: Only save the model component once.                              Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT245752 === END OF ISSUE === Title: PO10144: REVISIONS NOT LOADED DUE TO DELETED MESSAGES Description: [SP 6.4, SP 6.5, SP 6.6] If a revision has mappings for the     deleted message type, it is not loaded during the startup        Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT245416 === END OF ISSUE === Title: PO10141: AUTOMATIC MAPPING UID GENERATION CAN LEAD TO CLUSTER INCONSISTENCY Description: [SP 6.4, SP 6.5, SP 6.6] External model mappings are created    automatically while doing a golive that contains a new          attribute. This happens on every instance based on the last usedUID, but it may become problematic and can result in duplicate  UID's if there's elements created in between (after the golive  begins but before it completes).                                 Workaround: Reach out to support for steps on how to fix the inconsistency.  Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT245215 === END OF ISSUE === Title: PO10140: GRAPH COLOR CUSTOMIZATION DOES NOT WORK AS SPECIFIED IN THE SETTINGS. Description: [SP 6.3, 6.4, SP 6.5, SP 6.6] In the dashboard page, the chart  colors that are configured under System configuration > Chart   Colors are not reflected.                                        Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT245152 === END OF ISSUE === Title: PO10139: CLUSTER UPDATE TEMPORARILY STOPS MCI BYPASS Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] When performing a change in    cluster settings, like enableFli or disableApi, the bypass will temporarily stops working and the MCI discards the message      instead of forwarding it.                                        Workaround: Avoid cluster changes when bypass is active                      Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT245086 === END OF ISSUE === Title: PO10138: SPECIAL CHARACTERS ARE NOT HANDLED CORRECTLY DURING DML FILE GENERATION FOR RDI. Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] Special characters used in CaseMemo or Case Transition field are not handled correctly when    creating the DML file via RDI. The generated DML file will      contain insert/update statements that may fail on certain       databases.                                                       Workaround: Avoid using special characters in the Case Memo or Case         Transition fields.                                               Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT244976 === END OF ISSUE === Title: PO10137: ALL BUTTONS ARE DISABLED ON THE RULE REPORT PAGE Description: After running a rule report then all the toolbar buttons on the page are disabled and cannot be used. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT244933 === END OF ISSUE === Title: PO10135: SORTING OF "INDICATOR" COLUMN IN THE RULE DESIGNER IS INCORRECT WHEN VALUE IS A RANGE Description: [SP 6.5, SP 6.6 ] When sorting the values in the Indicator      column and values are in a range, the sorting result is         incorrect.                                                       Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT244574 === END OF ISSUE === Title: PO10134: GROUP BY QUERY AND REPORTING QUERY RESULTS DO NOT DIFFERENTIATE BETWEEN NIL [ (0) ] AND ZERO [ 0 ]. Description:  [SP 6.3, SP 6.4, SP 6.5, SP 6.6] When a numeric attribute (ie. SP_FraudFlag) is selected on the Group by Query page as a Group by Attribute, the query results will show both empty and nil    values as 0; thus users are unable to distinguish between them. Zeros and Nils are also counted the same in Reporting Query     result.                                                          Workaround: The nil and zero values can be differentiated on the Ad Hoc     "Query results" table.                                           Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT244570 === END OF ISSUE === Title: PO10132: MCI CONNECTION LIMIT COUTNS INCORRECTLY WHEN SSL HANDSHAKE FAILS Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] If the MCI incoming connection limit is enabled with SSL encryption, the connection counter is not decremented in case there's a problem with the certificates or the SSL handshake failed.                                     Workaround: Use a new endpoint for the MCI or increase the MCI connection   limit                                                            Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT244509 === END OF ISSUE === Title: PO10128: BULK CLOSE ACTION DIALOG IS HIDDEN BEHIND OTHER UI ELEMENTS. Description: When triggering a "bulk close action" from the case audit trail or case history from within investigation case, the dialog is not usable since it is placed behind other UI elements. Workaround: User has to scroll the window first to a UI element that has a  lower Z-Layer index than the overlayed dialog.                   Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT243437 === END OF ISSUE === Title: PO10127: SAVING THE MANDATOR PAGE TO CHANGE MEMORY SHOULD RETURN AN ERROR IF THE USER HAS NO PRIVILEGE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] If the user has no     privilege for changing the memory limit and tries to change it  on the mandator page, no error is displayed, and the memory     limits default to the previous value.                            Workaround: N/A.                                                             Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT243427 === END OF ISSUE === Title: PO10124: ATTRIBUTE ANALYSIS INTERVAL RANGES ARE NOT DISPLAYED CORRECTLY FOR SOME ATTRIBUTES Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] When you enable attribute analysis for an attribute using decimals and assign a non-zero  "from" value, interval ranges for attribute analysis will be    wrong.                                                           Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT243023 === END OF ISSUE === Title: PO10121: DEFERRED WRITING - REDUCE DDC ACCESS FOR MERGINGS CAN LEAD TO LONG WRITE CYCLES Description: If Deferred Writing is enabled, and "Reduce DDC access for mergings" is enabled, and a large volume of mergings happen that are within MDC range but were already written to disk, the write cycle can take much longer. Additionally, debug log message 4 was fixed to display the correct amount of records that were modified by mergings. Workaround: Disable the "Reduce DDC access for mergings" setting and reduce the disk chunk delay to 0. After there are two completed cycles you can change the disk chunk delay back to 1.                   Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT242962 === END OF ISSUE === Title: PO09989: INCORRECT HYPERLINK RESULT AND FRAUD MARKS WHEN "DIRECT TRANSACTION MARKING" ENABLED AND FRAUD/URID COLUMN HIDDEN Description: [6.3, SP 6.4, SP 6.5] Hyperlink queries and direct transaction marking in queries are impacted when "direct transaction marking" is enabled in system configuration and neither the URID nor fraud column is selected in the query definition. This will result in fraud marking wrong transactions and displaying wrong data in hyperlink queries (data from other index nodes). Workaround: Disable "direct transaction marking" or add URID or Fraud Flag  as column to the investigation query. This will fix both - the  hyperlink queries and the direct fraud marking. To really make  use of this feature, it is required to display the fraud column anyway.                                                          Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT242921 === END OF ISSUE === Title: PO10122: UNABLE TO DELETE PYTHON MODULE IF IT SHARES THE SAME ID WITH ANOTHER PYTHON MODULE IN ANOTHER MANDATOR Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Different python       modules from different mandators in a Cluster can have the same id assigned and Safer Payments only uses the id of the python   module to check for its references, it does not additionally    check the mandator UID. This may result in wrong references     being reported and the python module cannot be deleted even if  it is not referenced.                                            Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.08, 6.4.2.07, 6.5.0.05, 6.6.0.03 Known Issue ID: DT241831 === END OF ISSUE === Title: PO10120: POSSIBLE DEADLOCK WHEN PERFORMING CASE INVESTIGATION WHILE EOD IS RUNNING. Description: [SP 6.3, SP 6.4, SP 6.5] If there is additional case investigation by users, for example performing a takeover or transition of an investigation case, when the instance is running EOD and archiving cases, there is a chance the instance could end up in a deadlock. Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT241597 === END OF ISSUE === Title: PO10119: INCORRECT VALUES WHEN PROCESSING FCD FILE WITH ROWS HAVING SHORTER THAN EXPECTED LENGTH. Description: [SP 6.3, SP 6.4, SP 6.5] When processing FCD data rows with     shorter than expected length, some of its missing values can be overwritten by values of previously processed record. The impactis limited to the records with shorter FCD rows.                 Workaround: Please check your FCD file and ensure it has correct row        lengths, add padding where necessary.                            Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT241073 === END OF ISSUE === Title: PO10115: MDC AND DDC CAPACITY DIFFER WHEN CREATING A NEW ATTRIBUTE AND DOING A GO-LIVE. Description: [SP 6.3, SP 6.4, SP 6.5] When creating a new attribute and doinga go-live the MDC and DDC capacity will differ on "System       Internals->Data caches internals" page. After instance restart, numbers will match again.                                        Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT240628 === END OF ISSUE === Title: PO10116: NO VALUE SET FOR REVISIONAUDITTRAILFILTER KEY IN USER PROFILE FILE Description: [SP 6.3, SP 6.4, SP 6.5] When the user view revision audit trailwithout any filter, the key "revisionAuditTrailFilter" is added in the user profile file but there is no value set for it.       Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT240340 === END OF ISSUE === Title: PO10113: WHEN ENABLING CONNECTION LIMIT ON AN INTERFACE USING SSL, THE SSL WILL BE RESET DURING SAVE. Description: [SP 6.3, SP 6.4, SP 6.5] This affects all interfaces that offer this functionality, including API and MCI.                       Workaround: Manually re-enable SSL again.                                    Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT240184 === END OF ISSUE === Title: PO10114: SIMULATION FINAL RULE AND PREPROCESSING RULE RESULTS DON'T MATCH NORMAL COMPUTATION RESULTS Description: The simulation order for final rules and preprocessing rules is different from the order in real-time computation. Workaround: N/A                                                              Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT239736 === END OF ISSUE === Title: PO10112: INSTANCE MAY CRASH WHEN A QUERY COUNT IS RUNNING WHILE API IS INTERRUPTED Description: When a query count is running while API is interrupted, the instance may crash.  Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT239118 === END OF ISSUE === Title: PO10111: Long time spent on deactivating MQ interface Description: If the MQGET timeout is set to a large value, i.e. 10 minutes, it can cause long delay to run operations such as save of cluster change, golive, shutdown and restore, which need to deactivate MQ interface. This can take up to the sum of MQGet timeout setting of all MQ queues defined in Safer Payments, as the disconnection of each MQ queue is performed in sequence. Workaround: Set MQ timeout to a smaller value, i.e. 1000ms.                  Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT239050 === END OF ISSUE === Title: PO10110: CRASH CAN OCCUR WHEN INSTANCE DELETION IS FOLLOWED BY RESTORING INSTANCE. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] If the outgoing FLI queue to a deleted instance is not properly erased, a crash can occur if   the instance where the queue erasure failed is used as a donor  instance for a restore.                                          Workaround: If you have deleted an instance from the cluster, and have not  restarted the donor instance since that was done and want to    perform a restore, then disable and re-enable the FLI of the    donor instance before starting the restore.                      Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT238808 === END OF ISSUE === Title: PO10076: DETACHING AN INSTANCE WITH A LARGE FLI BUFFER APPEARS AS AN OUTAGE. Description: Detaching an instance with a large incoming buffer (ie. remote Instance), will cause the instance with the large outgoing buffer (ie. primary MCI instance) to hang. That instance may appear unreachable on the Cluster Page, the API may not be reachable, and the MCI may show as [enabled but not active], until it finishes marking the entire FLI buffer to that detaching Instance as acknowledged (ie. no longer needed). Workaround: When detaching an instance move the MCI/API/BDI away from the instance with large outgoing buffer. For example, if you are detaching Instance 4 and there is a large buffer going to it from Instance 1, ensure that API/MCI/BDI is enabled on either Instance 2 or 3. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT238595 === END OF ISSUE === Title: PO10108: UNABLE TO SEE FULL COLUMN TITLE IN INVESTIGATION QUERY CONFIGURATION Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] In investigation query configuration, column titles are not displayed in full if the   number of columns require a scrollbar to view, and there is no  option to resize them to see the full title                      Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT238400 === END OF ISSUE === Title: PO10104: THE DATE SELECTION IN UI IS ALWAYS IN ENGLISH Description: 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. Workaround: No workaround                                                    Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT238387 === END OF ISSUE === Title: PO10107: INHERITED PROFILING ELEMENTS WITH NO STORAGE NEED TO BE SIMULATED Description: [SP 6.3, SP 6.4, SP 6.5] If the profiling element has no storagefor its output, the element needs to be simulated if the output is required by others. Currently, it primes data, which has     nothing as there is no storage for it.                           Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT238161 === END OF ISSUE === Title: PO10106: REVISIONS BEING DELETED AND PROMOTED IN PARALLEL ON SAME MANDATOR CAN CAUSE INSTANCE SHUTDOWN Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Rule generation will   block deletion requests if running on the same revision that a  user is trying to delete. If a golive is started for a different revision of the same mandator, it will also be blocked by rule generation. Once the rule generation finishes, the two requests will execute in parallel and possibly cause a shutdown.          Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT237779 === END OF ISSUE === Title: PO10105: SIMULATION CANNOT BE DISABLED IF THERE ARE ONGOING SIMULATION QUERIES STILL RUNNING ON THE SAME REVISION Description: [SP 6.3, SP 6.4, SP 6.5] Disabling simulation should go through and cancel ongoing simulation queries being run on the same     revision as this simulation. However, this does not happen and  therefore the simulation cannot be disabled.                     Workaround: Stop the simulation queries manually if you wish to run a new   simulation                                                       Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT237777 === END OF ISSUE === Title: PO10103: CONSTANT INDEX REPAIR DURING STARTUP Description: After startup, encrypted indexes are repaired even if the index is not damaged. Workaround: Partial workaround to avoid crashes during index repair: Disable"check index on startup" in system configuration.                Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT237776 === END OF ISSUE === Title: PO10102: BACKTRACE WHEN RUNNING BDI JOB USING NESTED XML WITH AN XML HEADER Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Using XML headers in   BDI job files may result in backtraces as they do not have a    closing tag. For example: ?>                                                               Workaround: Avoid XML headers when using Nested XML.                         Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT237540 === END OF ISSUE === Title: PO10101: INSTANCE CRASH WHEN USING NESTED XML ON BDI WITH MULTIPLE THREADS Description: Loading Nested XML on the BDI with multiple threads may result in a crash.             Workaround: Define the BDI job to just use 1 thread for Nested XML.          Status: Closed Affected Version: 6.5.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT237539 === END OF ISSUE === Title: PO10048: DUPLICATE ATTRIBUTES IN DATA OUTPUTS DROPDOWN IN EXPORT DATA JOB SETTINGS Description: [SP 6.3, SP 6.4, SP 6.5] When selecting more than 1 mandator in "Data Selection" tab of the export data job settings, duplicate attributes equal to the number of selected mandators are        displayed in the data outputs dropdown. Selecting 1 attribute   will multi-select all the duplicate occurrences.                 Workaround: N/A.                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT237434 === END OF ISSUE === Title: PO10095: MODEL - MOVE RULE IS IGNORED Description: On Model > Scoring engine > All Rules > [select multiple rules > Move rules, it is possible to select rules to move but they are not moved. Workaround: Make a copy of the rule and assign it to the new ruleset and    then delete the old rule                                         Status: Closed Affected Version: 6.5.0 Fixed Available: 6.4.2.05, 6.5.0.03, 6.6.0.00 Known Issue ID: DT237253 === END OF ISSUE === Title: PO10100: PERFORMANCE OF CASE SEARCH AND CASE SELECTION MAY BE IMPROVED. Description:  [SP 6.3, SP 6.4, SP 6.5] Currently, search functionality       triggers new underlying search operation per character of user  input. This might potentially use more system resources than    necessary, as well as affect user interface response time.       Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT237231 === END OF ISSUE === Title: PO10093: USER UNABLE TO NAVIGATE ON TABS WITH READ ONLY ACCESS Description: On Cluster > System monitoring > Settings > [instance] > Interfaces, users with read-only access cannot switch between the tabs in the Interfaces section. Workaround: Increase privilege from view cluster to edit cluster if the usermust navigate sub-tabs of cluster page (ie. SCI tab).            Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT237060 === END OF ISSUE === Title: PO10099: Categories cannot be imported correctly if they are quoted in csv file Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Attribute's categories cannot be imported correctly if they are quotes in the import   csv file. Also, the exported categories csv file from Safer     Payments cannot be reimported back in Safer Payments without    manual edits, as the categories in the exported file are quoted. 5 items of note were observed:                                                                                                 1. The online help says that the number of columns can be eitherthree (value, label, comment) or four (value, label, comment,   fraud), however the export allows for more than 3 or 4 columns.                                                                 2. In case of numeric data type inputs, the CSV file should     contain the interval range specified in the value field         following the format startValue~endValue but the exported file  separates the value range into two columns (e.g. 10;20), and theimport feature looks for the value in one column (e.g. 10~20).                                                                  3. The export contains quotes for numeric value ranges (e.g.    "startValue""endValue") , however it should export without      quotes in case of numeric attributes (to match with the import  format). For example startValue~endValue.                                                                                       4. Even if the export format is correct (the import feature     loads the values as "actualValue" but it should load the data   without double quotes - e.g. the way it was being shown in the  table when exported).                                                                                                           5. When trying to import categories for an attribute in CSV     format, tab delimited files are rejected. A workaround is to usea semicolon. Using comma also works as long as the values       themselves do not contain comma.                                 Workaround: Manually edit the CSV file with the workarounds noted. An       example that will import:                                                                                                       Value;Label;Comment                                             70~950;testing label;Comment                                     Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT237041 === END OF ISSUE === Title: PO10098: EXPORT JOB CANNOT CONTINUE AFTER GOLIVE, IF "URID" ATTRIBUTE IS INCLUDED IN THE JOB'S DATA OUTPUT. Description:  [SP 6.3, SP 6.4, SP 6.5] When export job that includes "Urid"  attribute as its data output resumes after being suspended by   golive - the job will fail and fatal error message is produced.  Workaround: Job should resume without any issues if "Urid" attribute is     excluded from the output.                                        Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT236468 === END OF ISSUE === Title: PO10029: NEW UI MAY CRASH IF THERE IS A HUGE AMOUNT OF DATA IN MAPPINGS Description: The new UI cannot handle the huge amount of data in mappings and the UI page gets unresponsive and slow or may crash.                              Workaround: N/A.                                                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT233553 === END OF ISSUE === Title: PO10096: KMIP MASTER KEY CHANGE DETACHES API INSTANCE WHEN PASSPHRASE IS USED FOR THE PRIVATE KEY Description: [SP 6.2, SP 6.3, SP 6.4, SP 6.5] KMIP master key change fails onthe API instance if the passphrase is used for the private key. The API instance is then detached. The other non-API instances  do not fail in this manner but get stuck in the final stages of the master key change.                                           Workaround: N/A                                                              Status: Closed Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT233377 === END OF ISSUE === Title: PO10087: ATTRIBUTES MIGHT BE REMOVED FROM EXPORT JOB DATA SELECTION Description: Attributes that are selected for inclusion in the data output of a data export job might be excluded from the export file. Workaround: Only select a single mandator which has all the attributes whichyou want to export. If that is not possible, you can try to     create a new mandator that will own or inherit all attributes   needed for export data, and make it part of the data selection.  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT228887 === END OF ISSUE === Title: PO10094: ERROR FROM RUNNING API REQUEST ON REMOTE INSTANCE IS NOT FORWARDED TO THE API INSTANCE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] API requests and       responses can be forwarded via SCI between the API and remote   instances, but the error is not. If an error occurs on the      remote instance when processing the forwarded request, it throws an exception and shows Failure in std::string                  StatusControlInterface::handleRequest(std::string&):... in the  log. The user does not get the error information on UI. The     exception logged in the remote instance also needs to be        improved.                                                        Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT228886 === END OF ISSUE === Title: PO10084: IN RARE CASES IT IS NOT POSSIBLE TO CONFIRM A GOLIVE WHILE OTHER SYSTEM OPERATIONS ARE TAKING PLACE Description: [SP 6.3, SP 6.4, SP 6.5] When trying to perform a new golive, insome rare cases (for example when another golive or simulation  "by records" is already running) then the goliveCheckAndReport  request may not complete in a reasonable time frame. Attempting to confirm such a golive before the request has completed will  show a "REVISION_NOT_WAITING_FOR_CONFIRMATION" error instead.    Workaround: Wait for the other system operations to complete and try again  to perform the golive                                            Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT228884 === END OF ISSUE === Title: PO10092: RARE CRASH DURING SHUTDOWN WHEN STARTUP IS NOT FINISHED YET Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] There can be a crash   during shutdown if the instance is shutdown while the startup   was not completed yet and the API is accessed via browser or    script during shutdown.                                          Workaround: Wait until the API is enabled before shutting an instance down  (look for log message 10 saying that the API socket is created)  Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT225579 === END OF ISSUE === Title: PO10091: TABLE COLUMNS CANNOT BE RE-POSITIONED WHEN THE TABLE IS IN A TAB IN THE CUSTOM CASE LAYOUT. Description: [SP 6.3, SP 6.4, SP 6.5] Columns belonging to audit trails,     consolidated alarms or any other custom queries, cannot be      re-positioned when they are added to a new tab in the Case      Layout.                                                          Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT225400 === END OF ISSUE === Title: PO10090: FATAL ERROR IN RETIRED REVISION WHEN VIEWING ITS EXTERNAL MODEL OR COMPARING IT WITH ANOTHER REVISION AFTER INSTANCE RESTARTED Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] In a retired revision  that has external model defined, viewing its external model or  comparing this retired revision with another revision can result in a FATAL_ERROR on the user interface after the instance is   restarted.                                                       Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT225352 === END OF ISSUE === Title: PO10089: IN RARE CASES, INSTANCE SELECT DIALOG FOR SIMULATION MAY BE EMPTY Description: [SP 6.3, SP 6.4] If an instance that is assigned to a revision  as its remote simulation instance, is no longer part of the     cluster (ie. it got deleted), then instance select dialog for   Simulation may be empty.                                         Workaround: Take an instance offline and perform a file-level edit to       reassign the remote simulation instance id of every model       revision to that of an instance which exists. Once this is done,that instance can be used as a donor to restore the others.      Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT225305 === END OF ISSUE === Title: PO10086: INSTANCE FAILED TO START WITH THE ERROR NO_CHAMPION_FOUND Description: [SP 6.3.1.04, SP 6.4.2.03, SP 6.5.0.01] After an instance is    updated to Safer Payments v6.3.1.04, v6.4.2.03 or v6.5.0.01, it can fail to start with the error NO_CHAMPION_FOUND if it        contains a data export job where mandator(s) that have no       champion are selected in the data selection.                     Workaround: Remove mandators with no champion in the export job's data      selection before updating the instance.                          Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT224978 === END OF ISSUE === Title: PO10085: QUERIES AND SIMULATION ARE PAUSED WHEN SYSTEM REQUESTS TO ENTER MAINTENANCE MODE FOR GOLIVE Description: 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. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT224861 === END OF ISSUE === Title: PO10083: UNABLE TO CHOOSE A CUSTOM VALUE FOR FRAUD MARKING IF THE VALUE IS NEGATIVE IN THE NEW UI Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5 ] When attempting to    choose a custom value for fraud marking, if the value is        negative, an error will be displayed.                            Workaround: Enable the option "Direct transaction marking in queries" as it will allow you to select negative values for fraud               Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT224742 === END OF ISSUE === Title: PO10081: GLITCH WHEN USING "CLOSE TO" OPERATOR WITHIN RULE CONDITIONS WITH PERCENTAGE VALUE. Description: [SP 6.3, SP 6.4, SP 6.5] When editing rule conditions based on  "close to" operator, entering a percentage value might add a    decimal difference. For example 7 will cause the value to       immediately become 7.000000000000001.                            Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT224647 === END OF ISSUE === Title: PO10082: LATENCY ISSUES WHEN CALENDARS DO DATE ROLLOVER, EVEN WITH DEFERRED WRITING ENABLED Description: 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. Workaround: No known workarounds. It would help to use a filesystem that is optimized to delete large files quickly. The longer the OS needs to delete a file, the bigger is the latency spike.              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT224623 === END OF ISSUE === Title: PO10078: DEADLOCKS BETWEEN GOLIVES/SIMULATION AND INITIALIZING THE RULE DESIGNER DUE TO MODELING WORKFLOW Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, 6.5] A deadlock may occur if a golive is being executed on a mandator while any revision of the same mandator, or any sub-mandator, is executing the           "initialize rule designer" step of its modeling workflow. Also, there is a small chance of a deadlock when stopping the         simulation while the rule generation is running.                 Workaround: Remove the "Initialize rule designer" step from your modeling   workflow. Instead of initializing the rule designer using       modeling workflows, manually set the data selection for rule    generation inside the model factory settings.                    Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT224384 === END OF ISSUE === Title: PO09974: SIMULATION MODEL TABLE MAY INCORRECTLY STATE THAT "PRODUCTION DATA IS AVAILABLE" FOR AN ATTRIBUTE Description: [SP 6.1, SP 6.2, SP 6.3] The modelling attributes table states  that Production is available as long as the attribute data is   either available in MDC or the simulation may access DDC and the data is available in DDC. However, only simulation queries may access the DDC. Computationwise, the DDC cannot be accessed e.g. to evaluate conditions of simulated elements or in rule        generation. With APAR PO09839 it was already improved that the  simulation automatically detects rule condition attributes that need DDC access and informs the user in the report and primes   them automatically. However, the general logic needs to be      changed so attributes that are not fully stored in MDC are not  treated or shown as if production data is available but should  be primed into their own simulation mdc.                         Workaround: Enable the attribute manually for simulation, if it is not fully stored in MDC.                                                  Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT223977 === END OF ISSUE === Title: PO10077: POSSIBLE CRASH WHEN MULTIPLE COPY RETIRED REVISION REQUESTS ARE EXECUTED AT ONCE Description: A crash might occur if multiple requests to copy a retired revision are made while a golive is running. Workaround: 1) Limit the ability of users to copy retired revisions by      removing the associated role privilege                          2) Ensure that the copy revision button is only hit once.       Attempts to copy a retired revision should not be performed     while a golive is pending or occurring on the same mandator.     Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT223897 === END OF ISSUE === Title: PO10075: DEADLOCK BETWEEN SIMULATION QUERY AND RULE DELETION Description: 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. Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT223519 === END OF ISSUE === Title: PO10073: GOLIVES CANNOT PROCEED IF OTHER REVISIONS ARE EXECUTING RULE GENERATION. Description: Golives cannot proceed if other revisions are running rule generation. Workaround: Wait for rule generation to finish or manually stop it to allow golive to proceed.                                               Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT223518 === END OF ISSUE === Title: PO10074: DUPLICATE ENTRIES IN DEFINED RISK LISTS CAN CAUSE INCONSISTENCY BETWEEN INSTANCES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Depending on the       configuration and the specific steps taken, it is possible in   some cases for defined risk lists to have duplicate entries. If all the entries of the risk list are deleted on one instance,   but there are still entries remaining on another instance, then an attempt to delete the risk list will fail on the remote      instance. This can then potentially cause inconsistencies       between the instances, such as a different revision running on  different instances.                                             Workaround: N/A.                                                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT223072 === END OF ISSUE === Title: PO10050: CASE TRANSITIONS WITH DIFFERENT CASE CLOSE CODES CAN CAUSE A CRASH. Description: A crash might occur or backtrace be generated if case transitions are queued. Later, all are performed at the same time in parallel. The problem might also happen if a case transitions while the case actions of a case close code are being changed. Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.00 Known Issue ID: DT223057 === END OF ISSUE === Title: PO10066: UNABLE TO PERFORM GOLIVE WITHOUT PRIVILEGE TO VIEW SYSTEM CONFIGURATION Description: [SP 6.3.1.04, SP 6.4.2.03, SP 6.5.0.01] A user without the privilege to view the system configuration (Administration > System > Configuration) cannot perform a golive of a revision. When opening the golive report, the error "No privileges to perform this action" is shown. Workaround: Grant the privilege to view system configuration                 Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02 Known Issue ID: DT222792 === END OF ISSUE === Title: PO10071: INSTANCE DOESN'T STARTUP IF THERE ARE CASE CLASSES OF MANDATORS WITHOUT ACTIVE CHAMPION Description: [SP 6.5] After upgrading to 6.5, the instance will not startup, if there are case classes defined on mandators without active   champions that are also using case aggregation.                  Workaround: Perform a golive of the mandator of the case class before       installing the upgrade                                           Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT222784 === END OF ISSUE === Title: PO10070: RULE REPORT: "WITHOUT CONTEXT" IS NOT DISPLAYING THE REPORT RESULT Description: [SP 6.1, SP 6.2, SP 6.3, SP, 6.4, SP 6.5] In the Rule form thereis a option "Rule Report" with the option "without context" thatis currently not displaying the report result after the         execution of the simulation.                                     Workaround: After executing the Rule report, navigate manually to the url   /model///ruleReport//without to visualize the rule report                                        Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT222333 === END OF ISSUE === Title: PO10068: THE TEXT "GENERAL REVISION SETTINGS" IN MODEL REVISION OVERVIEW IS NOT TRANSLATED Description: [SP 6.3, SP 6.4, SP 6.5] The text "General Revision Settings" in Model revision overview -> General is not translated, when user is using non-English langauge.                                  Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT222107 === END OF ISSUE === Title: PO10064: WHEN A REMOTE INSTANCE RECEIVES THE RECREATE INDEX JOB VIA FLI AND A GOLIVE IS SENT RIGHT AFTER, A DEADLOCK MAY OCCUR Description: [SP 6.4, SP 6.5] When a remote instance receives the recreate   index job via FLI and a golive is sent right after a deadlock   may occur.                                                       Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT215920 === END OF ISSUE === Title: PO10063: INDEX ON REMOTE INSTANCE IS EMPTY AFTER RECREATING INDEX Description: [SP 6.2, SP 6.3, SP 6.4, SP 6.5] On BDI instance, first index isreset and transactions are computed. Once threads finish        processing, index reset is set through FLI. On remote instances,transactions are processed and then index is reset. Index on    remote index will be empty after recreating index job.           Workaround: 1. Confirm in index internals that the capacity of the index is still at 0 on remote instances.                                 2. Run a Golive that increases the capacity of the index atleastby 1.                                                           3. Reload the masterdata but remove the recreate index, just as a regular masterdata load.                                       Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT215919 === END OF ISSUE === Title: PO10058: FLI MESSAGES TO OTHER INSTANCES WILL BE BLOCKED WHEN SENDING EXTERNAL QUERIES TO RETRIEVE AND/OR UPDATE MASTERDATA THAT IS ENCRY Description: External queries that update encrypted masterdata block FLI. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT215687 === END OF ISSUE === Title: PO10062: ACCOUNT ANALYSIS DOES NOT WORK IN REPORTING QUERIES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Account Analysis is not working in Reporting queries even if it is enabled.             Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT215583 === END OF ISSUE === Title: PO10060: REGOLIVE DOES NOT HONOR PEER CONFIRMATION SETTING Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When peer confirmation setting is enforced for golives, a regolive can still be        performed by a single user. The regolive could be monitored by  enabling the log message "455" and checking for debug log       message "Processing HTTP Request reGoliveRevision revision".     Workaround: N/A.                                                             Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT215457 === END OF ISSUE === Title: PO10059: CRASH OF THE INSTANCE WHEN SAVING THE CASE WORKING QUEUE WHILE THIS WORKING QUEUE IS COMPUTED Description: A crash might occur if working queues are saved while they are computed. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT215422 === END OF ISSUE === Title: PO10056: MESSAGE COMPUTATION CAN BE BLOCKED BY DEFERRED WRITING DURING SAVE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] This is regression on SP versions with the APAR PO09594 fix. Previously, when saving mandator, deferred writing was interrupted. After the fix, if mandator save coincides with deferred writing long running method (like an index dump) it has to wait for it to complete. This can block MCI processing for greater than an expected amount of time. This should not affect customers where the load balancer decision is based on transaction processing timeout. Workaround: For those affected, here is a manual workaround for Save        Mandator:                                                                                                                       - Make sure you do not send transactions (ie. MCI traffic) to   API instance.                                                   - On all instances disable FLI.                                 - Save the mandator on API instance.                            - Send transactions to API instance temporarily instead of to   other instances.                                                - Enable FLI on all instances again.                            - After a while the mandator update will save on the other      instances as well.                                              - You can then resume normal operations (transactions to any    instances).                                                      Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT215330 === END OF ISSUE === Title: PO10057: WITH INTERLOCK ENABLED, FAILED MANDATOR SETTINGS SAVE WILL BLOCK QUERIES AND SIMULATIONS Description:  [SP 6.3, SP 6.4, SP 6.5] If interlock denies an attempt to savemandator settings, any currently running or newly started       simulations and queries will pause their operation indefinitely. Workaround: A simple workaround is to re-attempt the mandator settings save either after whatever instance was in maintenance mode completesits activity, or after reducing the minimum number of active    instances. So long as the settings save is able to go through   eventually, it will allow other functions to proceed.            Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT215222 === END OF ISSUE === Title: PO10054: ONLINE HELP/UI - FRAUD RATIO FORMULA IS NOT UP TO STANDARD PRACTICES. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Fraud ratio in         group-by-queries is currently calculated as fraud amount /      genuine amount. It should be fraud amount / total amount. In    addition, fraud ratios are usually very small. Most of them are currently displayed as 0.00 (less than 0.5%). They should be    displayed in basis points (i.e. times 10,000; 0.01 = 100BP). In the future, we plan to adjust this column to say 'Fraud Ratio   [BPS]' and update the formula itself to: Fraud Ratio [BPS] = (  Fraud Amount / Total Amount ) * 10000                            Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT214614 === END OF ISSUE === Title: PO10055: SEARCHING ONLINE HELP FOR SQUARE OR ROUND BRACKET CAN CRASH UI. Description: [SP 6.2, SP 6.3, SP 6.4, SP 6.5] Searching online help for      square or round bracket can crash UI.                            Workaround: Use complete manual that is available right next to the search  field.                                                           Status: Open Affected Version: 6.5.0 Fixed Available: No fixed available Known Issue ID: DT214451 === END OF ISSUE === Title: PO10053: MEMORY LEAK IN GROUP BY QUERY ACCOUNT ANALYSIS Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] There is a memory leak in group by queries, if account analysis is enabled and if the  meta attribute account is of type text. The memory that is used for the group by query is not released, even after deleting the group by query and causes to increase the memory usage.          Workaround: Disable account analysis of group by queries                     Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT214187 === END OF ISSUE === Title: PO10051: NEWLY CREATED PRECEDENT MAY GENERATE WRONG SIMULATION RESULT Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Newly created precedent may generate wrong values in production and simulation, if its source attribute has decimals. For example, if the source       attribute has decimal as 2, the simulation value is the correct value multiplies by 100.                                         Workaround: Hit the save button twice after either creating a new precedent, or changing the source attribute of an existing precedent.      Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT213631 === END OF ISSUE === Title: PO10049: Deadlock possible when adding or deleting DRL entries Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, 6.5] When adding or deleting Defined Risk List (DRL) entries a deadlock is possible if there is already a disk-write operation (DRL update in-progress) happening. Workaround: If you are adding/removing to Defined Risk Lists often consider enabling Deferred Writing to reduce chances of the deadlock.     Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT213415 === END OF ISSUE === Title: PO10047: SIMULATION QUERY / RULE REPORT IS BLOCKING GOLIVE, IF NO RECORD WAS FOUND Description: When golive is started, it might get blocked if simulation queries and rule reports that are already running cannot find records. While the golive is blocked, it does not start/run and it waits until the simulation query or rule reports finish. Workaround: Manually cancel simulations of parallel revisions or revisions  of submandator, if those block the execution of golive.          Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.00 Known Issue ID: DT213285 === END OF ISSUE === Title: PO10043: UNABLE TO ENTER [MAINTENANCE MODE] WHILE REPORTING QUERY IS RUNNING. Description: Golives and end of day jobs are blocked while reporting queries are computed. Workaround: Reporting queries have an existing results table. Clicking into each query and seeing if any of them aren't finished would confirm which one(s) are still going. Look at the one(s) that have a "last changed on" value that's after the previous day's EoD, but before the current EoD or GoLive that isn't going through. Copy the reporting query, and then delete the one(s) that have queries still running, note that existing results of the query that's deleted will be lost. The Golive or EoD should now proceed. Please contact IBM support if you still require assistance. Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT213205 === END OF ISSUE === Title: PO10042: DEADLOCK BETWEEN CASE INVESTIGATION AND PERIODIC CASE ESCALATION. Description: A deadlock might occur if there is an automated transition to close the case. Workaround: This is a rare timing event, however, if Deferred Writing is    enabled you will not be impacted.                                Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.00 Known Issue ID: DT213204 === END OF ISSUE === Title: PO10044: A CRASH MAY OCCUR IF AN EXCEPTION IS THROWN WHILE AN OCC IS DELETED. Description: [SP 6.3, SP 6.4, SP 6.5] In rare situations, a crash may occur  if an exception is thrown while an OCC is deleted.               Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT213067 === END OF ISSUE === Title: PO10041: MISMATCH TABLE COLUMNS/CONTENTS IN MASTERDATA QUERY RESULT Description: On Investigation > Queries > Masterdata query, values are not correctly rendered if one attribute is used with categories in two masterdata with different insertion conditions. Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT212579 === END OF ISSUE === Title: PO10039: UNABLE TO SAVE A SIMULATION QUERY WHEN THE "CHANGE" OPTION FOR A ROLE IS UNCHECKED FOR INVESTIGATION QUERY Description: [SP 6.3, SP 6.4, SP 6.5] A user is unable to save a simulation  query when the "Change" option for a role is unchecked for      Investigation Query as the save button and the other buttons on the form are disabled                                            Workaround: The user can still save by typing [ctrl]-[s] in order to save   the form. In order to execute the query they will need to be    given the "Change" option for Investigation Queries              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT212064 === END OF ISSUE === Title: PO10036: PERMISSION ERROR FOR A USER WHO ONLY HAS ACCESS TO CHANGE/VIEW SYSTEM CONFIGURATION. Description: On Admininstration > System > Configuration, an access error is issued even if the user has the privilege to view the system configuration. Workaround: The user will need permission to one of queries, common point   queries, model or case investigation to avoid this error. For   example, the Investigation > Query permission.                   Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.00 Known Issue ID: DT211428 === END OF ISSUE === Title: PO10035: UNABLE TO OPEN EXTERNAL MODEL COMPONENT OF RETIRED REVISION Description: [SP 6.4, SP 6.5] It is not possible to open an external model   component of a retired revision that was already retired during startup of the instance. Trying to open it creates a fatal errorin UI, logs and a backtrace.                                    Workaround: None                                                 Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT211011 === END OF ISSUE === Title: PO10034: MISSING VALIDATION IF MESSAGE MTID ALREADY EXISTS Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When saving a message  with an MTID that was already used by another message, there is no warning. The user has no visible feedback if an MTID is used twice, which then can result in computing a message with wrong  mappings.                                                        Workaround: Make sure to not define a message ON an already existing MTID.   Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT210824 === END OF ISSUE === Title: PO10033: AFTER DISABLING RULE PERFORMANCE REPORT THE FILE IS NOT ALWAYS REMOVED FROM DDC. Description: The rule performance report file is not removed from the DDC even after disabling the rule performance report and restarting the application. Workaround: 1. Disable the rule performance and go live.                    2. Enable it again and go live.                                 3. Disable it again and go live.                                  At step 3, SP will actually delete the file and after that    this problem never reoccurs.                                     Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.00 Known Issue ID: DT209451 === END OF ISSUE === Title: PO10032: ALL SAFER PAYMENTS OBJECTS ARE SHOWN WITH THEIR UIDS IN THE FORMS, REGARDLESS OF "SHOW UIDS" SETTING. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Safer Payments ignores the     "Show UIDs" setting and always displays all objects' UIDs in thescreen.                                                          Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT209354 === END OF ISSUE === Title: PO09972: WRONG CALENDAR/EVENT/DEVICE IDENTIFICATION/MASTERDATA VALUES AFTER LOGICAL GOLIVE Description: [SP 6.2, SP 6.3, SP 6.4] It is possible that index dependent elements which store their computation result in an own MDC/DDC i.e. calendars/events/device identifications/masterdata, compute unexpected values. Their output attributes could show values that do not make sense. The pre-requisite for this to happen is that the last golive performed on the same mandator as the index is defined is a logical golive and afterwards index nodes are either purged or deleted on the fly as their minimum lifetime is reached. During this delete operation there is a chance that values get wrongly assigned so the index dependent elements will show values that previously belonged to other index nodes. If the last golive performed on the index owning mandator was a logical golive, the setting for logical golives should be disabled, and another dummy golive should be performed which will be structural this time. After the structural golive, the issue will not occur anymore. A restart or EOD will also lead to the issue not occurring anymore. Already corrupted values, will stay corrupted though. Workaround: Disable logical golives and perform a structural golive once.    Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01 Known Issue ID: DT209096 === END OF ISSUE === Title: PO10030: TRIMMING WHEN USING RETENTION BY TIME, LEADS TO DDC FILES BEING CREATED FOR UNSTORED ATTRIBUTES. Description: [SP 6.2, SP 6.3, SP 6.4, SP 6.5] When retention by time is used, the end of day job causes DDC files to be created for attributes that are not stored. The DDC files itself are not the problem, and don't consume much disk space, but further operations such as doing a golive where this attribute is now stored, can lead to a crash. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT209093 === END OF ISSUE === Title: PO10025: RECORDS CONDITIONS ARE NOT POPULATED CORRECTLY IN PATTERN DEFINITION Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Stencils / Records conditions are not populated correctly when displaying the pattern. The attribute name(s) and operator(s) are not displayed in the conditions. They become visible when editing the pattern form. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT208203 === END OF ISSUE === Title: PO10022: GOLIVE OF MDC STORAGE INCREASE DOESN'T INCREASE SAFER PAYMENTS MEMORY USAGE UNTIL THE INSTANCE IS RESTARTED Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] The SP memory usage is not changed after a golive of increasing MDC storage, although Safer Payments does request for those additional memory allocation from the Operating System. Safer Payments can still be used normally, but the SAI of Safer Payments memory consumption may show misleading information. The memory usage is only updated after a restart of the instance. Workaround: Use the RAM information in System Internals to evaluate the RAM actually needed by Safer Payments.                               Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT208201 === END OF ISSUE === Title: PO10027: SIMULATIONS FAIL ON A REMOTE INSTANCES DUE TO THE OIDC TOKEN NOT BEING ABLE TO BE PARSED CORRECTLY Description: [SP 6.3, SP 6.4, SP 6.5] Simulations fail on remote instances due to the OIDC token being structured as a JSON object and not being able to be parsed correctly by the remote instances Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT207550 === END OF ISSUE === Title: PO10026: MERGING RE-COMPUTATION OF EVENT/CALENDAR IS WRONG WHEN ITS OUTPUT HAS NO STORAGE. Description: [SP 6.2, SP 6.3, SP 6.4. 6.5] When re-computation is enabled fora merging, events/calendars outputs that are recomputed but not stored result in empty values.                                   Workaround: Do not enable merging re-computation for messages that include  event/calendar outputs with no storage, or if required, add     storage (mdc/ddc).                                               Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT207548 === END OF ISSUE === Title: PO10024: PMML FILES ARE NOT DELETED WHEN USING CLEANOUT MAINTENANCE FUNCTION AND NEED TOO MUCH DISK SPACE. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Despite revision being cleaned out by maintenance function, Safer Payments does not    delete PMML files on disk. Additionally, PMML models are stored by deep copying the PMML model files next to each revision, evenif the PMML model did not change. This can lead to significant  storage space usage over time.                                   Workaround: Remove the revisions manually by using the API                   Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT203424 === END OF ISSUE === Title: PO10018: LOG MESSAGE FOR RANDOM FOREST GENERATION ERROR DOES NOT PROVIDE FAILURE DETAILS. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] After Random Forest    generation finishes with error, log message is unclear about the reason of the failure. Ideally, error message printed to log   should be in sync with message reported by the UI client.        Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT202849 === END OF ISSUE === Title: PO10023: CASE ID DISAPPEARING UNDER CUSTOM CASE LAYOUT Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When using a custom    layout in a case class, using a header and displaying rules     fired on the upper right section, the case ID starts            disappearing. When putting it on the right, the case transition buttons partially disappear.                                     Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT201280 === END OF ISSUE === Title: PO10019: INSTANCE GETS STUCK IN "SHUTDOWN REQUESTED" STATE IF SHUTDOWN WHILE SIMULATION IS ONGOING. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When instance is       shutdown while simulation is in progress, instance can get stuck in "Shutdown requested" state. In this state the instance needs to be killed and restored.                                      Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT197859 === END OF ISSUE === Title: PO10020: SOME SETTINGS FIELDS DO NOT HANDLE DECIMAL VALUES CORRECTLY. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] Some settings fields do not handle decimal values correctly, ie. remote go live wait   factor only accepts integer values.                              Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT197581 === END OF ISSUE === Title: PO10017: SIMULATION SHOULD USE PRODUCTION DATA OF INHERITED NON-INPUT ATTRIBUTES Description: Safer Payments should not allocate simulation memory to inherited noninput attributes if their data is available in MDC and does not need to be simulated. It should use those attributes' production data instead. Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT197366 === END OF ISSUE === Title: PO09983: CLOSE CODES APPEAR MULTIPLE TIMES IN "BULK CLOSE" DIALOG. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Close codes appear multiple times in "Bulk Close" dialog. This affects both old and new UI. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT197147 === END OF ISSUE === Title: PO10014: BYPASSING NOT POSSIBLE ANYMORE AFTER PROCESSING A PROBLEMATIC HEADER Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] When bypass is enabled and messages to be redirected have a problematic header because the message was bypassed several times as several instances are in parallel in maintenance mode (mostly possible due to PO09863 at the moment), the instance is not able to perform bypass anymore afterwards. Workaround: Restarting MCI on the instance where bypassing is enabled.       Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT197032 === END OF ISSUE === Title: PO10013: The name of changed rule is displayed as "undefined" when comparing with a retired revision Description: The rule name is displayed as "undefined" when a rule is changed, in Revision Comparison (Model>Revision Overview>Revision Control), when comparing thecurrent revision with a retired revision.                        Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT197007 === END OF ISSUE === Title: PO10012: CRASH WHEN DISABLING RUNNING SIMULATION USING SIMULATION METHOD "IN CHUNKS" Description: [SP 6.2, SP 6.3, SP 6.4] This issue was introduced in versions  6.4.2.02, 6.3.1.03 and 6.2.2.03. When simulating with method "inchunks", a crash may occur when disabling the simulation while  the simulation computation is still in progress.                 Workaround: Use simulation method "by records" instead.                      Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT196845 === END OF ISSUE === Title: PO10009: WRONG DISPLAY ERROR IN DATA SELECTION WHEN QUERYING DATA RANGE THAT IS ONLY AVAILABLE IN DDC FOR THE META ATTRIBUTE SYSTEM TIME Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When querying a data range thatis only available in DDC for the meta attribute system time, thedata selection textbox wrongly gives an error that the data fromthe selected date and time is not available even though "IncludeDDC" setting is enabled. The impact is only on the UI, the      required data is retrieved after saving the page and running thequery.                                                           Workaround: N/A.                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT196229 === END OF ISSUE === Title: PO09987: THE USER GROUPS IN CASE TRANSITIONS ARE NOT SET ON REMOTE AND LOST AFTER STARTUP Description:  [SP 6.3, SP 6.4] User groups selected in the case class transition settings are no longer selected after the instance is restarted. They are also not synchronized to remote instances. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT189109 === END OF ISSUE === Title: PO09886: COPY FROM RETIRED REVISION WITH NO CHANGE OF PMML MODEL MAY LEAD TO MISSING MODELS IN CHAMPION Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Some PMML model values become  empty in retired and invalidated model revisions, such as the   number of models in boosted trees. This should not cause any    issue as such revisions are not used in message computation.    However, doing a regolive of such revision or creating a copy   and doing a golive with it without any change of such pmml      models may lead to the PMML not being fully functional and      leading to incorrect results.                                    Workaround: If a copy from retired/re-golive is required, re-upload the PMML model file before doing the golive.                             Status: Closed Affected Version: 6.2.0 Fixed Available: 6.4.2.09, 6.5.0.07, 6.6.0.05, 6.7.0.01 Known Issue ID: DT189063 === END OF ISSUE === Title: PO10007: INSTANCE STATUS REMAINS IN "CHECKING CLUSTER INTERLOCK" EVEN THOUGH NO PENDING GOLIVES EXIST. Description: If many cases exist, case selection takes a long time. Workaround: The instance can be restarted, or a golive can be performed in  order to reset the status (the golive can have changes or it    could just be an empty golive with no changes), or the status   can be left until the EOD job happens, when it will also be     reset.                                                           Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT188610 === END OF ISSUE === Title: PO09986: MCI BYPASS TO ANOTHER MCI BYPASS NOT THROWING A MEANINGFUL ERROR Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] In case that 2 instances are   switching to maintenance mode simultaneously - which by design  should not be the case and is mostly due to another APAR PO09863 - and open a MCI bypass to each other, the bypass is not       working correctly and creates log message 785 and 795. Instead  there should be a more meaningful error indicating that a       bypassed message was bypassed again which is not supported.      Workaround: Set Cluster Interlock setting of minimum active instances to at least 2 to help reduce chances of multiple maintenance mode     activities. Also ensure heartbeat threshold is set to 3x the    average ping latency between your instances.                     Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT187991 === END OF ISSUE === Title: PO09985: GOLIVE CAN HANG, IF STARTED WHILE SIMULATION QUERY/RULE REPORT IS RUNNING Description: [SP 6.2, SP 6.3, SP 6.4] A deadlock can occur when starting a golive in the same mandator or a head mandator of a revision where a simulation query (all types) is running. Note, that a simulation query of type rule report is also started when starting a rule report. Workaround: Let simulation queries finish before starting a golive in the   same mandator or head mandator. This is indicated by log message 0824 "Query of type '...' finished ..." or 0434 User '...'     executed unmasked '...' query ..."                               Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT180661 === END OF ISSUE === Title: PO10004: MULTIPLE 419 "USER VIEWED CASE" FOR EACH CASE INVESTIGATION WHEN USING EXTERNAL QUERIES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] There are multiple 419 "User   viewed case" log message for each case investigation. Each      external query triggers an additional "get" request for each    investigation case, even if this isn't necessary, for example ifthe external query isn't changing the cases values.              Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT180617 === END OF ISSUE === Title: PO10002: SAFER PAYMENTS MAY CRASH WHEN PYTHON 2.7 IS USED, A PYTHON FUNCTION RETURNS A UNICODE STRING WITH NON-ASCII CHARACTERS, AND THE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4, SP 6.5] In this case, Safer    Payments has to convert the function's result into a string,    using the python function str(). This throws an exception in    case of a unicode string with non-ASCII characters. Safer       Payments does not handle that exception gracefully.              Workaround: Use Python 3.x                                                   Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT180394 === END OF ISSUE === Title: PO09984: WRONG TIMESTAMP VALUE IN THE TOOLTIP OF REPORTS Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] In the new UI, the timestamp in the "Current state" tooltip of reports is displayed in UTC instead of the user's time zone. Workaround: N/A.                                                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT179963 === END OF ISSUE === Title: PO10000: WARNING + ERROR DASHBOARD FILTER IS NOT WORKING ON NEW UI Description: [SP 6.1, 6.2, 6.3, 6.4] On the dashboard page, when selecting   the filter "W+E" it is not filtering out the results to display only the warnings and errors.                                    Workaround: The warning and errors are still shown, they just need to be    found on the page                                                Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT179451 === END OF ISSUE === Title: PO09999: USING DECIMAL SEPARATOR "DOT" AND DIGIT GROUP SEPARATOR NONE LEADS TO WRONG VALUES WHEN ENTERING VALUE WITH "COMMA" Description: The digit and decimal group separators for numeric expressions are not correctly enforced. Also, the wildcard values are truncated on the user interface. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT179439 === END OF ISSUE === Title: PO09998: KPI WITH CONDITIONS RETURNS 0 AFTER END OF DAY JOB WHEN LOGICAL GOLIVE WAS DONE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When logical golives are enabled in system settings and a logical golive is done on a mandator of the kpi or parent mandator, then after end of day job the kpi will return 0 if it has any condition. The KPI will work again when saving it after the EOD. Workaround: Disable logical golives.                                         Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT179310 === END OF ISSUE === Title: PO09913: Errors when working in model revisions and using remote simulations Description: 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. Workaround: Use the API instance as the simulation instance for that        revision.                                                        Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT179269 === END OF ISSUE === Title: PO09980: MISLEADING AUDITTRAIL IN CASE ON REMOTE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When an investigation case is  updated, there are two FLI messages sent, one for the audit     trail update and one for case update. It is possible that the   remote instance has received the audit trail information first, but not the case update yet, when a user opens the case, which  will cause an additional audit trail entry with the old case    state. Afterwards, the case update is received. This causes the investigation case being inconsistent with its audit trail.      Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT179264 === END OF ISSUE === Title: PO09994: CASE_ACTION_INPUT ATTEMPTED TO BE READ AS CASE ACTION Description: Case action inputs are not read into the system after the instance is restarted twice. Workaround: N/A.                                                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT179091 === END OF ISSUE === Title: PO09995: EXPORT DATA JOB ONLY PRINTS ATTRIBUTES FROM THE MANDATOR WITH SMALLEST UID Description: When several mandators are selected in a data export job, the result will only contain attributes visible to the mandator with the smallest UID. Workaround: Only select the leave mandator, it will inherit all attributes  from above and thus for this mandator hierarchy stream all      attributes will be available.                                    Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01 Known Issue ID: DT179063 === END OF ISSUE === Title: PO09993: CONCATENATION OF STRINGS WITH TRAILING WHITESPACES CUT AFTER FIRST STRING Description: [SP 6.1,SP 6.2,SP 6.3,SP 6.4,SP 6.5] When concatenating 2       attributes and the first attribute value has trailing           whitespaces, the string is cut after the first value in case    another mapping exists for the first attribute and is processed before the concatination mapping.                                Workaround: 1. Remove trailing whitespaces from data that is loaded into SP or                                                              2. if it is desired to have whitespaces in between the values,  remove the other mapping and re-add it so it is processed after the concatination mapping or                                    3. Instead of a concatenation mapping use a preprocessing rule  with the "append" operator                                       Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT178173 === END OF ISSUE === Title: PO09992: DELETING ATTRIBUTES REFERENCED IN SUB MANDATOR MAY CAUSE ERROR DURING GOLIVE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When an invalidated revision ofa sub mandator uses an attribute from a top mandator and on top mandator the attribute is deleted, a golive on the top mandator will lead to an error saying "0321 Revision xxx configuration   error: FATAL_ERROR" and as a consequence will delete the        invalidated revision to prevent this error from occurring again. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT178067 === END OF ISSUE === Title: PO09978: POSSIBLE DEADLOCK WHEN API SWITCH IS EXECUTED DURING RUNNING EODAND SIMULATION Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] If there was a logical golive inbetween the last EOD and the current EOD, and in addition a simulation is running, switching the API during the current EOD may cause a deadlock event. Workaround: Disable logical golives. Workaround: Disable logical golives.                                         Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.01, 6.6.0.00 Known Issue ID: DT174532 === END OF ISSUE === Title: PO09941: POSSIBLE WARNING 0312 WHEN DEFERRED WRITING IS ENABLED AND CASE UPDATE ARRIVES BEFORE ACTUAL CASE. Description: [SP 6.1, SP 6.2, SP 6.3. SP 6.4] When deferred writing is       enabled, and a case update has been received before the actual  case, which is mostly only possible when there is an FLI buffer and incoming data interfaces are enabled on a different instancethan API, the message " W 0312 Cannot archive case uid ..." may be output to system log. This can be ignored.                    Workaround: Enable MCI/MQ/Kafka and API on the same instance.                Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT174397 === END OF ISSUE === Title: PO09940: POSSIBLE LOSS OF MASTERDATA UPDATE THROUGH EXTERNAL QUERY ON REMOTE INSTANCES. Description: Masterdata update might be lost when it is transmitted by using FLI. Workaround: Enable MCI/MQ/Kafka and API on the same instance.                Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT174396 === END OF ISSUE === Title: PO09975: POSSIBLE LOSS OF STATUS UPDATES OF NOTICES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Updates of notices through FLI could be discarded, if the original notice does not exist yet onthat instance.                                                   Workaround: N/A.                                                             Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT174395 === END OF ISSUE === Title: PO09988: EXTENDED AUTHENTICATION - ENTERING WRONG PIN WITH SAME NUMBER OF DIGITS CAUSES USER DEADLOCK. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When "Extended Authentication" is enabled with One-Time-Password (OTP) based 2 factor authentication, and the user enters the wrong PIN, but with the same number of digits as the correct PIN, a deadlock occurs preventing further logins for that user. Workaround: Until this is fixed, entering a wrong PIN (with the same number of digits as the correct PIN) will always require an API        instance restart to release the lock on that user login.         Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT174111 === END OF ISSUE === Title: PO09973: COPYING A NON-RULESET MODEL COMPONENT DOES NOT COPY TYPE AND MAPPINGS Description: [SP 6.4] When copying a non-ruleset model component, the type   will appear as "ruleset" and other fields such as data field    mappings are not copied to the new model component.              Workaround: N/A.                                                             Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT173995 === END OF ISSUE === Title: PO09971: CRASH WHEN DELETING THE CHALLENGER REVISION THAT IS STILL RUNNING RANDOM FOREST MODEL GENERATION Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The instance may crash when    deleting a challenger revision, while there is random forest    model generation running in this challenger revision.            Workaround: N/A                                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT173678 === END OF ISSUE === Title: PO09960: AT THE BEGINNING OF GOLIVE, MCI DOES NOT RESPOND EVEN IF BYPASS ENABLED. Description: At the beginning of golive, MCI does not respond even if bypass is enabled. Workaround: None                                                             Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT173412 === END OF ISSUE === Title: PO09969: INSTANCE STATUS CHANGES TO CHECKING CLUSTER INTERLOCK WHEN DOING LOGICAL GOLIVE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When doing a logical golive, the instance state changes to "OK checking cluster interlock" even though the instance does not go into maintenance mode and thus does not require this check. The state is changed back automatically later when maintenance mode is entered by another activity such as an EoD job. The impact is only on the UI display of the instance status. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.01, 6.6.0.00 Known Issue ID: DT173404 === END OF ISSUE === Title: PO09982: INITIAL GOLIVE MAY FAIL IF MANDATOR SAVED MULTIPLE TIMES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When a new mandator is created the first revision is created on each instance individually instead of being synchronized. It is possible, this would end up not using the same UID on all instances which could lead to some instances are shut down during golive. The UIDs may diverge in case the mandator save button was clicked multiple times while the first save attempt was hanging. Workaround: Do not click the mandator save button several times. When a new mandator is created, double check that its initial revision has the mandator UID+1 as its own UID. Otherwise, take over its     initial challenger revision and perform a save on the general   revision page without any modifications.                         Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT172703 === END OF ISSUE === Title: PO09981: IN THE BYPASS SCENARIO, THE MCI STATUS CHECK MESSAGE IS NOT HANDLED IF IT DOES NOT HAVE A MESSAGE ID Description: [SP 6.2, SP 6.3, SP 6.4] When bypass is running, it is required that a unique message id is assigned to each message. Otherwise, the message is discarded on the remote instance. Such messages are not dumped even if the option of "Dump message data" is enabled, which makes it difficult to troubleshoot the root cause of why the message failed to load into Safer  Workaround: Add a message ID to the status request                           Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT172575 === END OF ISSUE === Title: PO09979: SIMULATION PROGRESS SHOWS INITIALIZING WHEN SIMULATION IS COMPLETE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The simulation progress        component displays "simulation initializing" when a simulation  is run without any elements being simulated. This gives a false impression that simulation work is still being conducted when ithas already finished.                                            Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT171930 === END OF ISSUE === Title: PO09977: A REFERENCED UNSTORED ATTRIBUTE MAY LEAD TO INSTANCE SHUTDOWN IF A GOLIVE IS ATTEMPTED WITH A RETIRED REVISION WHERE IT DOES NOT Description: It is possible to create a copy of a retired revision and golive on that revision. If this revision contains a not stored attribute that is referenced in some other element, for example a condition, the golive may fail and shut down the instance with an error "ATTRIBUTE_REFERENCE_IN_CONDITION_NOT_FOUND" or "FATAL_ERROR". Workaround: Copy only from active champions and make the required changes   based on that copy.                                              Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01 Known Issue ID: DT171798 === END OF ISSUE === Title: PO09966: PAGE AUTO REFRESH FOR WORK CASE IS NOT WORKING Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Although there is a page auto  refreshing interval settings for Investigation->Work Case page  in System Configuration->System, the page will not be           automatically refreshed.                                         Workaround: Refresh the page manually.                                       Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT171725 === END OF ISSUE === Title: PO09964: ASYNC ENDPOINTS CAN LEAD TO ERRORS/CRASH/DEADLOCK Description: [SP 6.2, SP 6.3, SP 6.4] MCI async mode performs concurrent accesses on the socket, which can lead to error log messages, crashes or deadlocks that can show for example as MCI or FLI snychronization not working anymore. The instance needs to be killed, if it runs into the deadlock scenario. Workaround: N/A.                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00, 6.6.0.00 Known Issue ID: DT171624 === END OF ISSUE === Title: PO09952: GOLIVE CAN HANG AFTER SENDING CASE ACTION Description: Golives can hang if there is a simultaneous case action activity in the user interface to send case actions. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02 Known Issue ID: DT169884 === END OF ISSUE === Title: PO09959: ADDING OUTPUT MAPPINGS TO ANY MESSAGE TYPE INCREASES THE LATENCY FOR ALL MESSAGE TYPES Description: When a malformed transaction message is received, the system issues a misleading log message that FCD data stream is faulty even though the message type is not FCD. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00, 6.6.0.00 Known Issue ID: DT169784 === END OF ISSUE === Title: PO09970: Remote instance shutdown after multiple consecutive regolives in a short period of time Description: Multiple regolives that are run and queued at the same time might result in FLI errors and failed golives on remote instances. Workaround: The regolive privilege can be disabled, and a retired champion  can be copied instead of using the direct "regolive: action.     Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.01, 6.6.0.00 Known Issue ID: DT169469 === END OF ISSUE === Title: PO09958: NO INFO ABOUT SENDER OF SIGNAL Description: Logs do not show who sent the signal. Workaround: Use dtrace to get info about the sender of signal, for example  via sudo dtrace -n 'proc:::signal-send { printf("Process %d (%s by UID %d) sending signal %d to                                 pid=%d\n",pid,execname,uid,args[2],args[1]->pr_pid); }'          Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT169351 === END OF ISSUE === Title: PO09957: MCI BYPASS CHANGE IS NOT APPLIED Description:  [SP 6.2, SP 6.3, SP 6.4] Change in instance' bypass setting is not applied and Safer Payments keeps using the old bypass setting. Workaround: Re-enable the MCI interface of the instance whose bypass setting is changed.                                                     Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00, 6.6.0.00 Known Issue ID: DT169265 === END OF ISSUE === Title: PO09953: OUTPUTS MISSING IN PIE CHART IN GENERAL REVISION OVERVIEW AND ELEMENT TYPE SHALL NOT BE SELECTABLE IN MEMORY STATISTICS TABLE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] In the General Revision        overview page, outputs are never displayed in the pie chart.    Also, the element type column shall not be made selectable in   the Memory Statistics table.                                     Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT169055 === END OF ISSUE === Title: PO09965: NOTICES POPUP WINDOW SHOWS INCORRECT TIMESTAMPS OF A NEW NOTICE Description: [SP 6.3, SP 6.4] When a new notice is received, the Notices popup window shows incorrect timestamp. Workaround: Open the Notices panel to view the accurate timestamps.          Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT169024 === END OF ISSUE === Title: PO09963: POPUP ERROR SHOWN WHEN A NOTICE IS DELETED JUST AFTER CREATION. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] While attempting to delete a   notice from the queue, an error message is shown saying that    File '/eml/notices/notice_xx.iris' cannot be removed:           boost::filesystem::file_size: The system cannot find the file   specified. This can happen when a notice is deleted from the UI before the system has written the file to disk (which is most   likely to occur when deferred writing is turned on). In this    case, the notice actually gets deleted from the UI, but the filestill exists in the /eml/notices directory.                      Workaround: This is due to the rapid timing, if adequate time is provided   for notice to write to disk, the error will not occur.           Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT161080 === END OF ISSUE === Title: PO09962: INSTANCE WITH OFFLINE STATUS SET BY THE SETOFFLINE API CALL BLOCKS OTHER INSTANCES FROM DOING GOLIVE Description: [SP 6.3, SP 6.4 ]SP allows instances to enter maintenance mode only one at a time. If there is an offline instance, it will block operations like golive for the whole cluster. Workaround: Bring the offline instance back online with the setOnline API   call                                                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT160800 === END OF ISSUE === Title: PO09948: WRONG EXECUTION TIME OF SCHEDULED MONTHLY JOB Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The execution time of scheduled monthly job can be different from the time defined in the job. The execution time for monthly job is incorrectly adjusted by an unexpected offset. There is no such issue with the scheduled   daily and weekly jobs.                                           Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT160296 === END OF ISSUE === Title: PO09949: ADD URID INFO TO OCCM ERROR MESSAGE AND ARCHIVE FAILED MESSAGES Description: 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. Workaround: N/A.                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT160283 === END OF ISSUE === Title: PO09918: MCI CONNECTION CLOSED EARLY WHEN RECEIVING SHUT_WR Description: 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. Workaround: Do not send SHUT_WR before the response is read.                 Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT160192 === END OF ISSUE === Title: PO09934: CRASH IN BYPASS WHEN SSL IS ENABLED AND GOLIVE TAKES A VERY SHORT AMOUNT OF TIME Description: 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. Workaround: Do not use bypass in combination with very short golives or     disable bypass completely.                                       Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT160188 === END OF ISSUE === Title: PO09912: FATAL ERROR WITH BACKTRACE FROM DATA EXPORT JOB AFTER A LOGICAL GOLIVE AND EOD Description: 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. Workaround: Re-save the data export job, after every logical golive on the  mandator that the job's condition attribute belongs to.          Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT160184 === END OF ISSUE === Title: PO09954: PREPENDING NEW OUTPUT VALUES IN A LIST MAY CORRUPT OTHER OUTPUTS' CONDITION VALUES Description: [SP 6.2, SP 6.3, SP 6.4] Existing output values of a list may   get corrupted when trying to add a new output value to the front(prepending) or rearranging existing output values of this list. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT149335 === END OF ISSUE === Title: PO09955: PERFORMANCE OF WRITING THE MODEL RESPONSE FOR MANDATORS WITH MANY OUTPUTS AND MAPPINGS CAN BE IMPROVED Description: When a malformed transaction message is received, the system issues a misleading log message that FCD data stream is faulty even though the message type is not FCD. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00, 6.6.0.00 Known Issue ID: DT149332 === END OF ISSUE === Title: PO09935: SAVING DATA SELECTION MULTIPLE TIMES WHILE USING ANALYSIS WITH THE SAME DATA SELECTION, MAY LEAD TO A CRASH Description: 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. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT149209 === END OF ISSUE === Title: PO09950: CASE ESCALATION SCHEDULER IS NOT STOPPED DURING A RESTORE OF A HEALTHY INSTANCE. Description: A crash can occur during restoration because the case service is not stopped. Workaround:  Start the instance to be restored (recipient) as Invalidated,  then perform a restore from healthy donor.                       Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT149163 === END OF ISSUE === Title: PO09951: EXPLORE INDICATORS TABLE PERCENTAGES APPEAR ROUNDED DEPENDING ON DECIMALS OF ATTRIBUTE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Rounded down values, rather    than exact values may be shown. This affects the columns hit    rate, false positive, saved amount and intercept.                Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT149062 === END OF ISSUE === Title: PO09921: NUMERIC ATTRIBUTE WITH DECIMALS IS UNAVAILABLE IN GROUP BY ATTRIBUTE DROPDOWN LIST Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] If an input attribute in       numeric type is defined with non zero decimals, it is not       included in the dropdown list for Group by attribute in Group by query definition form.                                          Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT148960 === END OF ISSUE === Title: PO09931: CRASH WHEN OPENING A CASE WHOSE MASTERDATA USES A CATEGORIC ATTRIBUTE BUT THE INDEX NODE IS INVALID Description: A crash can occur if a case is opened whose masterdata uses a categorical attribute but the index node is invalid. Workaround: Do not create manual cases using example data for index         attributes for which no actual index entry exists. You can      check, if an index entry exists by running a masterdata query   for the index value. It will only show a table with masterdata  columns when there is an index node.                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT148959 === END OF ISSUE === Title: PO09930: NEW USER SHOULDN'T INHERIT THE LAST LOGIN AND LAST PASSWORD INFO FROM THE USER IT IS COPIED FROM Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] If creating a new user from    copying an existing user, the newly created should shouldn't    inherit the last login and last password change information from this existing user.                                             Workaround: Use the old user interface in SP v6.1. There is no workaround in SP v6.2 and above.                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT148956 === END OF ISSUE === Title: PO09929: SIMULATION MEMORY CANNOT BE FREED IF ITS SIMULATION REPORT PAGE WAS OPEN WHEN IT WAS INVALIDATED Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] If a challenger revision is    invalidated while the user is still on its simulation report    page, this simulation can no longer be cancelled. For example,  the user is checking simulation report on revision A and in the meantime another user golive revision B in the same mandator.   After the golive the memory is still reserved but it can no     longer be freed.                                                 Workaround: Restart the instance where the simulation was performed          Status: Closed Affected Version: 6.3.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT148947 === END OF ISSUE === Title: PO09885: POSSIBLE CRASH ON RULE GENERATION PAGE Description: [SP 6.1, 6.2, 6.3, 6.4] When running rule generation it is      possible for a crash to occur when a page refresh request       happens at the same time as another action such as stopping rulegeneration, or committing a rule. If the "model element         generation" page refresh time is set low, then this greatly     increases the likelihood of running into this crash              Workaround: If the "Model element generation" refresh time is set to a low  value, then greatly increasing it (for example over 120 seconds)should lower the chances of running into this crash              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT148850 === END OF ISSUE === Title: PO09945: OPTIONS TO RESELECT, ADD OR DESELECT RULES IF YOU CANCEL OUT OF "SAVE SELECTED RULES AND END RULES GENERATION (MODEL>MODEL TRAIN Description:  [SP 6.3] Unable to reselect, add or deselect rules if you      cancel out of "Save selected rules and end rules generation     (Model>Model Training>Generated Rules) because these actions aregreyed out. To make them active again, refresh the page.         Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT148769 === END OF ISSUE === Title: PO09944: ATTRIBUTE AUDIT TRAIL DOES NOT RECORD THE RETENTION VALUES Description: The audit trail report does not include MDC and DDC retention values. Now, the fields are included. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT145578 === END OF ISSUE === Title: PO09942: CONNECTION TIMEOUT TO MQ IF CHANNEL NAME HAS MORE THAN 19 CHARACTERS. Description: The connection to IBM MQ times out if MQ definition values, for example, the channel name or queue manager name, are longer than 19 characters. Workaround: Rename the MQ channel name or MQ manager name to make it 1      character shorter than the maximum value.                        Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT145133 === END OF ISSUE === Title: PO09938: SEVERAL REPORTING QUERIES WITH SAME NAME CAN BE SAVED IN RARE CASES WHICH PREVENTS STARTUP Description: In rare situations, an element can be saved with a name that is already used, which invalidates the configuration. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT144733 === END OF ISSUE === Title: PO09917: A CRASH MAY OCCUR IF CHANGING THE RULE GENERATION SETTINGS WHILE RUNNING RULE GENERATION Description: A crash can occur if rule generation settings are saved while it is running. Workaround: Stop the rule generation before changing the settings once you  have clicked the initialize rule designer button. If there is no response on the model training page after clicking the         initialize rule designer button and the stop button remains grey out, please wait for a while and the stop button will become   clickable. Please ensure you stop it before clicking the save   button on the settings page.                                     Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT144718 === END OF ISSUE === Title: PO09937: GOLIVE - REPORT CAN SHOW `` INSTEAD OF THE ACTUAL COLOR RED FOR AN ERROR. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When pressing golive and       reviewing the report if an error preventing golive is raised it can show  next to operation. It should actually color the  line red so it is an UI issue.                                   Workaround: Note that  means the message is an error that needs        correction in order to successfully golive.                      Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT144692 === END OF ISSUE === Title: PO09936: DEFERRED WRITING - INSUFFICIENT MEMORY LOG SHOWS INACCURATE UI ERROR MESSAGE. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The error message for MDC      capacity being insufficient for attributes "Deferred writing    cannot be enabled because the mdc capacity of some stored       attributes is not sufficient" is also possible when the OS does not have enough free memory remaining to enable Deferred        Writing.                                                         Workaround: The SP system log can be referenced for the correct error       message. and appropriate adjustments made.                      "E  0009            Insufficient physical memory for this action(requested memory: X,XXX,XXX,XXX Bytes)"                        "D  0122            Deferred writing could not be started. Theremight not be enough memory available."                           Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT144691 === END OF ISSUE === Title: PO09933: SHUTDOWN DOESN'T WAIT FOR MQ TO FINISH PROCESSING MESSAGES Description: [SP 6.2, SP6.3, SP 6.4 ]If a user triggers a shutdown and there are still MQ messages being processed, SP may exit with a backtrace. The transaction that caused the backtrace, will not be fully computed anymore. Workaround: To further reduce the possibilities of it happening, MQI could  be disabled before trying to shut down the instance.             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT144330 === END OF ISSUE === Title: PO09932: UI CAN CRASH WHEN CHANGING THE SETTINGS IN A FORM Description: [SP 6.2, SP6.3, SP 6.4 ] When settings are changed in forms,    that can affect the active conditions, the UI may crash. For    example when changing the 'Include DDC' setting of a query when there's a condition with an attribute that is only available    through DDC.                                                     Workaround: Remove the conflicting condition before changing the form.       Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT144218 === END OF ISSUE === Title: PO09906: ERROR IN RULE GENERATION IF RULE GENERATION ATTRIBUTES REQUIRE SIMULATION AFTER INITIAL SET UP IN MODELLING ATTRIBUTES PAGE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] If a user enables an attribute for rule generation in Modelling, and the attribute does not    have Production data available for the defined simulation range, the attribute will automatically get enabled for simulation. If there is an attribute that has Production data available and is enabled for rule generation, but at a later point a change is  made so it will not have Production data available anymore, the attribute will not be enabled for simulation although it would  require simulation now. This can happen for example, if the user changes the stored attribute to not stored and golives the     change. As a consequence, if the user starts a rule generation  and clicks "commit as condition" or "explore all indicators",   the error is raised "The results of simulation are not valid.   Restart the simulation first."                                   Workaround: Check all attributes that are enabled in modeling for rule      generation or attribute analysis and make sure they say either  "Production data available" or "Included" in the simulation     column.                                                          Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT144179 === END OF ISSUE === Title: PO09928: GENERATION DATE IN CASE SELECTION PAGE CHANGES TO A PREVIOUSLY ENTERED VALUE Description: [SP 6.2, SP 6.3, SP 6.4] When a user sets up the Case Selection page (specifically the Generation date) and then navigates away from the page and back again the Generation Date changes to a   previously entered value but is still showing the results for   the date that was entered. Additionally, if the page refresh    button is clicked the Generation Date clears completely but the results are still showing for the entered date range.            Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT143801 === END OF ISSUE === Title: PO09926: BY DEFAULT HIDDEN COLUMNS ARE NOT DISPLAYED AFTER BEING SELECTED Description: [SP 6.2, SP 6.3, SP 6.4] When a user select a hidden by default but selectable column (such as Uid or Revision) in table settings, the column won't be shown in the UI. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT143684 === END OF ISSUE === Title: PO09927: IF SCI FAILS, CHANGE TO REVISION WHILE REMOTE ANALYSIS IS RUNNING MAY TEMPORARILY BLOCK FLI Description: 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. Workaround: Avoid revision changes until Analyses status shows Finished. If analysis is not required, remove it from the workflow.           Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT143682 === END OF ISSUE === Title: PO09924: TOOLBAR ACTIONS PERMANENTLY DISABLED Description: SP 6.3, SP 6.4, SP 6.5] In the rule designer if an error is     received from the server, for example "The indicator could not  be enabled/disabled", then all the actions remain locked (greyedout) and no other actions can be performed. After navigating    away from the page and back, the actions are available again.    Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT143315 === END OF ISSUE === Title: PO09923: INCONSISTENCIES IN SYNCHRONIZATION WHEN USING EXTERNAL MODEL COMPONENTS Description: [SP 6.2, SP 6.3, SP 6.4, SP 6.5] Safer Payments uses two FLI    messages to synchronize a single transaction when that          transaction involves the execution of external model components.This method of synchronization can lead 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 can produce wrong results by   counting (or not counting) unfinished transaction records, i.e. transaction records for which the second FLI message has not    been handled yet.                                                Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT143311 === END OF ISSUE === Title: PO07649: ENCODING ISSUE IN "PREFIX [NOT] EQUAL TO" CONDITIONS Description: Safer Payments is not using the number of characters in "prefix [not] equal to" conditions of text attributes, but it is using  the number of bytes instead. Therefore, the condition operator  "prefix [not] equal to" may have an unexpected behavior, when   using UTF-8 encoded text with multi-byte characters.             Workaround: N/A                                                              Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT143180 === END OF ISSUE === Title: PO09922: AVRO - INCOMING MESSAGE DUMP IS EMPTY. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The avro message incoming dump ( incoming_kafka_message_dump*.iris) is always empty.            Workaround: Have a kafka console consumer consume from the same topic as SP to view incoming structure.                                      Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT143134 === END OF ISSUE === Title: PO09899: RELATIONSHIP ATTRIBUTES VALUE ARE NOT DISPLAYED IN MASTERDATA QUERY RESULT Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Relationship attributes are not displayed in masterdata query results on the user interface.    Workaround: Use the old user interface in SP v6.1. For SP v6.2 and above,   there is no workaround.                                          Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT143057 === END OF ISSUE === Title: PO09920: QUICKLY SWITCHING BETWEEN CASE SELECTION AND WORK CASE CAN LEAD TO "REQUESTED ITEM COULD NOT BE FOUND" ERROR Description: Performance issues and errors occur in the user interface because queries are not correctly cleared from memory. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT142956 === END OF ISSUE === Title: PO09892: POSSIBLE CRASH WHEN EOD WITH RETENTION CHANGES AND INTERNAL RANDOM FOREST OVERLAPS. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] During EOD pending retention   setting changes are executed which may cause the MDC to resize. If Internal Random Forest is run while EOD with retention       changes that change the MDC happen in parallel, this might      result in a crash.                                               Workaround: Avoid any retention change while IRF is running.                 Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT141657 === END OF ISSUE === Title: PO09891: ADD INFORMATION OF READ POSITION IN THE FLI BUFFER CORRUPTION LOG MESSAGE Description: Added data to the log message for corrupted FLI buffers. Workaround: N/A.                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT141542 === END OF ISSUE === Title: PO09915: USER LAST CHANGED TIMESTAMP IS NOT UPDATED ON REMOTE INSTANCE Description: [SP 6.4] The last changed timestamp of a user does not update   on the remote instances, when it is updated by a change on the  API instance.                                                    Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT141430 === END OF ISSUE === Title: PO09914: INSTANCE CPU CAN REACH 100% UTILIZATION DUE TO PRIORITY INVERSION EVENT. Description: The CPU usage of an instance can reach 100% if more realtime threads are used than the number of CPU cores. Workaround: To avoid, reduce the number of RT threads to be at maximum the  number of CPU cores in the server.                                                                                              Alternatively, only use                                         priority level lower than "Highest", note that this can have a  negative effect on latencies.                                                                                                   As a workaround if CPU is                                       already at 100%, try strace -f -o out.txt -p  and     contact IBM Support.                                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT141325 === END OF ISSUE === Title: PO09911: PASSWORD SHOULD NOT AUTOCOMPLETE WHEN EXPORTING ENCRYPTED QUERY RESULT TABLE Description: [SP 6.2, SP 6.3, SP 6.4] When exporting encrypted query result  table, it has a popup asking for the password. The password is  auto-completed and displayed in the "value" entry.               Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT141154 === END OF ISSUE === Title: PO09910: POSSIBLE CRASH WHEN RULES ARE ENABLED AND DISABLED WHILE AN ANALYSIS IS RUNNING. Description: A crash might occur if rules are enabled or disabled while an analysis is running. Workaround: Only enable/disable rulesets and rules when analysis is not     currently running.                                               Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT141099 === END OF ISSUE === Title: PO09881: INSTANCE MAY CRASH WHEN PARSING CORRUPTED PMML FILE DURING GOLIVE Description: The server might crash if invalid xml is uploaded in a pmml model file. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03 Known Issue ID: DT141080 === END OF ISSUE === Title: PO09909: INCONSISTENT ATTRIBUTE ORDER IN BDI EXPORT JOB FILE Description: When exporting data via BDI job, the order of attributes in the export file may vary.        Workaround: To sort the attributes based on UIDs, press the save button, before pressing the execute button for the job. If that does not work, please perform these additional steps:On existing job, start by removing the last field in use, but one you intend to keep (the attribute called "URID" for example). Then add or remove any fields you'd like from the job and click save.Then add the previously removed field (URID in this case), and save once more. Press "execute job" only.At this step, the fields are alphabetical ascending order of the field's Name. If that is what you desire, do NOT press save or "save and execute" again, and ONLY press "execute job" from now on. Otherwise, you must redo the steps. To instead get the order of the columns to follow the Attribute UID in ascending order click "save and execute job" once more. This is the expected ordering. Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.10;6.6.0.08;6.7.0.04;6.8.0.01 Known Issue ID: DT141023 === END OF ISSUE === Title: PO09908: COMMON POINT QUERY RESULTS PAGE DOES NOT AUTO REFRESH AND SHOWS INCOMPLETE RESULT Description: When a common point query is run, it is possible that the query returns different results in several runs as the page is not auto refreshed while it is running and  will thus not always show the final result. Instead, it may show a temporary result. To get the final result, the user can manually refresh the page using browser's refresh button after the query has finished. Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT141022 === END OF ISSUE === Title: PO09907: DATA RANGE IN SIMULATION QUERY IS SET BACK TO RECORDS ABSOLUTE WHEN NAVIGATING BACK TO QUERY DEFINITION Description: [SP 6.2, SP 6.3, SP 6.4] When a simulation is run on a leaf     mandator and a simulation query is run with data range server   time absolute, the data range is set back to records absolute   after going back to the query page.                              Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT141021 === END OF ISSUE === Title: PO09897: CHECKING AND UNCHECKING "USE SIMULATION DATA SELECTION" RESTRICTS ATTRIBUTES SELECTABLE IN CONDITIONS Description: [SP 6.2, SP 6.3] When "Use simulation data selection" is        selected in a simulation query (e.g. to transfer the data range from the simulation) and unselected to enter a condition, the   dropdown field of attributes on which conditions can be defined is restricted to input attributes, hence it is incomplete as    output attributes are missing.                                   Workaround: After unchecking "Use simulation data selection" save and reloadthe simulation query page, before defining conditions.           Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT141020 === END OF ISSUE === Title: PO09895: DEFINED RISK LIST BULK DELETIONS ARE SLOWER ON THE API INSTANCE. Description: The deletion of large bulk defined risk list entries is slow on the API instance. Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT141018 === END OF ISSUE === Title: PO09905: REFRESHING ONE QUERY RESULT, REFRESHES THE ENTIRE CASE INVESTIGATION PAGE Description: [SP 6.3] Refreshing one embedded query result in Case           investigation, refreshes the entire Case investigation page      Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT140165 === END OF ISSUE === Title: PO09904: "CANNOT FIND MODEL REVISION" POP UPS WHEN VISITING MODEL PAGE Description: [SP 6.2, SP 6.3, SP 6.4] When opening the simulation page of a  revision                                                        after you have previously visited the simulation page of anotherrevision, the request getSimulationProgress will still be sent  with the previous revision UID when you enter the page. In some customer scenarios this can cause random "pop-ups" to appear,   for example if the previous revision was already deleted.        Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT140057 === END OF ISSUE === Title: PO09903: RULE PERFORMANCE - ANALYSIS AND RULESET DROPDOWN BROKEN AFTER REPEATED PAGE NAVIGATION Description: [SP 6.3] When navigating to the Rule Performance page with a    completed simulation and an enabled analysis, repeated          navigations to and from the page can result in the user's       preferences breaking, and causing the Analysis dropdown to be   empty. In addition, it is possible that the ruleset dropdown    breaks so requests are triggered with an incorrect rule UID     which leads to "Cannot find rule" warning dialogs. After        running into such issues, it helps to reset your user           preferences on the My Account page and select the desired       analysis and ruleset/rule afterwards. Refreshing the page may   also help to recover.                                            Workaround: Refreshing the page at any time serves to prevent the analysis  dropdown from breaking. This can cause some inconsistent        oddities, however, such as the analysis becoming deselected     (though the dropdown will work to select it again) or the rule  selection boxes becoming read-only. Repeated refreshes and      navigations to/from the page can help circumvent those.          Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT140052 === END OF ISSUE === Title: PO09474: THE RISK LIST FILE CANNOT BE LOADED DURING STARTUP IF IT CONTAINS EMPTY VALUE(S) Description: [SP 6.3] If a risk list file contains empty value(s) in any risk list entry, it fails to be loaded during the instance startup in Safer Payments version 6.3. Workaround: Manually modify the risk list file by removing the risk list    entry that contain empty value, or replace the empty value with a dummy non-empty value.                                         Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT140047 === END OF ISSUE === Title: PO09902: THE USER PREFERENCES OF QUERY RESULT TABLES RANDOMLY RESET Description: In case investigation, the query result table sometimes resets the table preferences if the page is refreshed. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT140018 === END OF ISSUE === Title: PO09901: REPORTING QUERY DATA IS NOT HANDLED CORRECTLY DURING GOLIVE Description: A reporting query might access invalid memory if it runs in parallel with golive. Workaround: Avoid executing reporting queries before a go-live.              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT139992 === END OF ISSUE === Title: PO09877: AUDIT TRAIL COMMENT DISPLAY FORMAT COULD BE IMPROVED. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When opened, audit trail       comment is not being correctly wrapped, instead creating a      scrollbar. This significantly decreases user experience of      reading longer rationales.                                       Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT139924 === END OF ISSUE === Title: PO09876: CATEGORIES SHALL BE REMOVED IN INTERCEPT ATTRIBUTE Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When enabling intercept of an  output attribute that has categories, all information related to categories of this attribute shall be removed. This is because the intercept attribute values are taken from realtime intercept codes definitions automatically.                                Workaround: Delete all categories of the attribute before enabling Intercept of it.                                                          Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT139842 === END OF ISSUE === Title: PO09898: EXPRESSIONS NOT VALIDATED IN CONDITIONS Description:  [SP 6.4] Input validation for expressions is missing for some  condition attribute types, for example for timestamp attributes. Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT139821 === END OF ISSUE === Title: PO09875: DELETION OF KPI DEFINITION DOES NOT REMOVE CORRESPONDING KPI DATA FILE FROM DISK. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The deletion of a KPI          definition does not remove the corresponding KPI data file from kpi folder. This has no other impact than file retention.        Workaround: Corresponding file can be safely deleted manually.               Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT139744 === END OF ISSUE === Title: PO09896: COMPARE REVISION THROWS AN ERROR IF CHANGES TO AN EXTERNAL MODEL ARE MADE BETWEEN REVISIONS. Description: When comparing revisions, an error is issued if changes to an external model were made between these two revisions. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT139534 === END OF ISSUE === Title: PO09894: GROUP BY QUERY SHOWS TIMESTAMP ATTRIBUTES AS UNIX TIMESTAMP Description: The results of group by queries and reporting queries show incorrectly formatted values for timestamp grouping attributes. Also, the results do not take the Safer Payments time zone into account if the system time meta-attribute is used. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT139125 === END OF ISSUE === Title: PO09859: HIGH CPU USAGE DURING THE OPERATION OF THE RULE GENERATION Description: Rule generation creates too many threads, which cause real-time processing to stop for a few seconds. Workaround: Reduce the number of the enabled attributes for rule generation, or reduce the element generation threads in the system         configuration.                                                   Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT139054 === END OF ISSUE === Title: PO09874: INVESTIGATION REPORTS DOES NOT DISPLAY DECIMAL FIGURES FOR TIMING FIELDS Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Some fields in the timing part of the report investigation section are not displaying decimals, thus when values are for example less than 1, they appear as 0. Workaround: N/A.                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT135279 === END OF ISSUE === Title: PO09873: FLI BUFFER CORRUPTED AFTER NEW MESSAGE WRITTEN 17 BYTES BEFORE BUFFER OR EXACTLY AT END Description: 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. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT135143 === END OF ISSUE === Title: PO09890: DELETING A KPI DEFINITION FROM UI DOESN'T STOP THE KPI ON REMOTE INSTANCES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When deleting a KPI definition from API instance, the KPI on remote instances continues to run and thus keeps updating the KPI data file.                       Workaround: After the deletion, restart the remote instance to stop the KPI. Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT135118 === END OF ISSUE === Title: PO09889: REFRESH SIMULATION QUERY OF REMOTE SIMULATION DOES NOT WORK Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Simulation query can not be runfrom the refresh button on simulation query result page after a remote simulation.                                               Workaround: Restart the query from the table by choosing the context menu   execution to get fresh results.                                  Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT135117 === END OF ISSUE === Title: PO09888: POSSIBLE DEADLOCK BETWEEN GOLIVE AND OPENING A CASE Description: Golives can hang if there is a simultaneous case action activity in the user interface to send case actions or display case action previews. Workaround: 1. perform golives when no investigations are being done.       2. remove the masterdata from the case actions templates         Status: Closed Affected Version: 6.4.0 Fixed Available: 6.4.2.01, 6.5.0.00 Known Issue ID: DT135105 === END OF ISSUE === Title: PO09887: ERROR MESSAGE APPEARING BEHIND MODALS Description: [SP 6.3, SP 6.4] If an error is thrown while a modal dialog is  displayed on the screen, then the actual error message appears  behind the modal on SP 6.3 and up. Example of such behavior     could be observed after importing a PMML scorecard that         generates an error. The error message is only visible after     clicking out of the upload PMML scorecard modal.                 Workaround: Close modal dialog or click the background to see the actual    error message.                                                   Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT135103 === END OF ISSUE === Title: PO09866: IN THE NEW UI, COPYING MULTIPLE VALUES FROM A SPREADSHEET INTO A CONDITION FIELD IS NOT WORKING AS EXPECTED Description: [SP 6.1, 6.2, 6.3, 6.4] In the new UI, copying multiple values  from a spreadsheet, using a semicolon as a separator, into      condition field is not working as expected. This functionality  was working in the old UI.                                       Workaround: Extract the values from xls into a plain text document and      modify by mass replacing the newline character with empty value. Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT134843 === END OF ISSUE === Title: PO09883: DELETING A CASE SELECTION CONDITION CAN CRASH THE UI Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4]When deleting a Case Selection  condition when there are two or more conditions, the UI can     crash with "Unexpected Error".                                   Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.4.2.10, 6.5.0.08, 6.6.0.06, 6.7.0.02, 6.8.0.00 Known Issue ID: DT134777 === END OF ISSUE === Title: PO09884: ON SOME PAGES YOU ARE UNABLE TO ACCESS ADDITIONAL VALUES IN THE DROP DOWN, NO SCROLL BAR AVAILABLE Description: On some pages, for example on the queries page or on the rules page, users are unable to access additional values in the drop down, and there is no scroll bar available. You also cannot move the page scroll bar any further down. Workaround: If you know the value you are selecting you can type the name inthe field. In addition, if you select a value, then often an    element will be added to the page, resulting in a longer page,  so that you can see the other values                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT134655 === END OF ISSUE === Title: PO09860: SCROLLING APPEARS TO GET STUCK IN LARGE TABLES Description: [SP 6.3, SP 6.4] When scrolling through large tables using      trackpad or mouse wheel, the scroll can get stuck. To continue, please stop and restart the scrolling. This issue has been      observed in Google Chrome and Microsoft Edge browsers.           Workaround: Use scroll bar when scrolling through large tables, or use      Firefox if available.                                            Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT134399 === END OF ISSUE === Title: PO09880: FLI BUFFER IS AT 0% WHILE THERE ARE MESSAGES IN THE BUFFER DURING RESTORE Description: When an instance is restored from a donor instance that has FLI buffer for the recipient, the FLI buffer could be 0% while thereis still a number of messages shown in the buffer during the    restore process. After the restore, the messages will be gone asexpected to match the percentage.                                Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT134034 === END OF ISSUE === Title: PO09879: NOT_ENABLED_IN_SETTINGS FEEDBACK WHEN DELETING A USER ACCOUNT WITHOUT DELETE ENABLED. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The text is missing for        NOT_ENABLED_IN_SETTINGS feedback, but this message just means   the user is trying to delete a user when "user account deletion"configuration permission is disabled.                            Workaround: Go to System Configuration > User Accounts > User account       deletion > Check it on > Save. Re-try the deletion.              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT133825 === END OF ISSUE === Title: PO09878: POSSIBLE CRASH AFTER "TOO MANY OPEN FILES" OR "SOCKET IN USE" LOGS AT STARTUP. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] "Too many open files" or       "socket in use" errors may be followed by a crash when starting up SP due to SCI listener not being able to initialize. The logswould also usually show a log message "0513 Could not initializeincoming socket for StatusControlInterface" before crashing.     Workaround: To reduce the risk of the crash, running into "too many open    files" or "socket in use" should be prevented by the following: 1.  Change ulimit nofile to 65536 and/or service script limit   for SPUser to LimitNOFILE=65536.                                2. Switch to an SCI socket outside of the Ephemeral Port Range. (Check: sysctl -A | grep ip_local_port_range)                                                                                   Switching the SCI on a live production can have a risk of       instances to not synchronize the changes correctly. In worst    case, it might be required to restart the instances and manuallycopy the cluster.iris from one instance to another. It is       therefore recommended to only change the SCI port if all        instances are up and healthy and to use a time-frame where it ispossible to restart the instances and having admins available   that can copy the cluster.iris from one instance to another.     Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT133823 === END OF ISSUE === Title: PO09853: THE CATEGORY ATTRIBUTE VALUE'S COLOR PANEL IS CUT OFF Description: 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.    Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT133618 === END OF ISSUE === Title: PO09334: SYSTEM TIME ATTRIBUTE IN THE LATENCY REPORT DISPLAYS INCORRECT DATES Description: Timestamps in the latency report files are stored in the system time zone, but they should be stored in the UTC+0 time zone. When the system time zone setting is not UTC +0, the latency timestamp in system internals is different from the system time of the same record in query output. Workaround: n/a                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT133603 === END OF ISSUE === Title: PO09852: WHILE IMPORTING PMML FILE XML PARSER ERROR CAN BE THROWN Description: 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. Workaround: Add newline to the end of PMML file.                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT133505 === END OF ISSUE === Title: PO09851: EXTRA WHITE SPACE IN CASE ID Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The case id contains extra     white space in case investigation view (e.g. 1- 123) and two    extra white spaces in the cases table (e.g. 1 - 123).            Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT133503 === END OF ISSUE === Title: PO09848: UNABLE TO ADD COMMENT IN CASE ATTACHMENTS TABLE Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] Comment field in case          attachments table is not editable in SP v6.3. In new UI of      previous versions, comment field can be modified, but the change is only made visible after page refresh, otherwise it stays    with the previous value.                                         Workaround: On SP v6.0, v6.1 and v6.2, refresh the page after adding comment in case attachments table.                                      Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT133315 === END OF ISSUE === Title: PO09872: RESTORE - COMPRESSION PERFORMANCE DURING RESTORE CAN BE IMPROVED, AND OPTIONALLY DISABLED. Description: Added an option to the System configuration that allows compression to be disabled during a restore. Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT133182 === END OF ISSUE === Title: PO09871: RESTORE - PERFORMANCE CAN BE IMPROVED WHEN SENDING AND RECEIVING DATA. Description: Modified the purging mechanism to replace outdated values with constant values that are easier to compress. This change increases the performance of the restore. Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT133181 === END OF ISSUE === Title: PO09823: UNABLE TO SELECT/UNSELECT ALL FOUND COLUMNS AT ONCE IN THE NEW USER INTERFACE Description: [SP 6.3, SP 6.4, SP 6.5, SP 6.6] In the new User Interface, it  is not possible to select / unselect all found attribute columnsat once.                                                                                                                        For example, in Query results settings -> Select columns, the   user can only select / unselect all columns. When using a stringto search for some columns, the user is not able to select /    unselect all found columns at once.                              Workaround: No workaround available Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT133130 === END OF ISSUE === Title: PO09870: APPLICATION MAY HANG DURING VARIOUS TASKS Description: Safer Payments hangs and some operations never finish. Certain operations, for example, disabling or changing FLI, SCI, or MCI, are more likely to cause the problem even though they themselves might not hang. Workaround: N/A.                                                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT133128 === END OF ISSUE === Title: PO09869: WRONG RESULTS WHEN PMML BOOSTED TREE MODELS USE MULTIPLEMODELMETHOD INSTEAD OF MODELCHAIN. Description: Wrong results are produced when a PMML boosted tree model uses multipleModelMethod which would result in different results from using modelChain. Safer Payments always uses the method 'modelChain' instead, which yields wrong results. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT133054 === END OF ISSUE === Title: PO09868: DOUBLET DETECTION MAY RESPOND WITH INCORRECT OUTPUT VALUES. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] In case the to be detected     transaction is not fully computed and stored yet, as it was justreceived by the current instance, doublet detection already     detects it preventing a duplicate, but may read inconsistent    values for the outputs and respond with such values instead of  the correct ones.                                                Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT132955 === END OF ISSUE === Title: PO09867: SHOW REFERENCE ICON SHOULD NOT BE AVAILABLE AT THE ELEMENT LEVEL, ONLY AT THE ATTRIBUTE LEVEL Description: The Show reference button for attributes of patterns causes an error. Removed the Show reference button for counters because counters cannot have references. Also, the Show reference button for attributes of events incorrectly shows untranslated text. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT132941 === END OF ISSUE === Title: PO09844: DELETING USER TAKES A LONG TIME WITH MANY CASES IN THE SYSTEM Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When deleting a user, all the  cases in the system are checked to reset the user on the cases  and then write to RDI if required. If RDI is enabled, then this will result in as many disk writes as the cases in the system   which takes a very long time resulting in FLI stuck for that    time. Once the operation is completed, the FLI synchronization  will automatically resume.                                       Workaround: Avoid deleting user accounts while RDI is enabled.               Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT132905 === END OF ISSUE === Title: PO09865: CASE HISTORY WILL NOT AUTOMATICALLY WORK FOR SELECTED REPORTING ATTRIBUTES AFTER REVISITING THE PAGE OR OPENING A NEW CASE Description: 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. Workaround: Clearing the selection and re-selecting the required            reporting attributes                                             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT132876 === END OF ISSUE === Title: PO09490: EMPTY VALUES IN COLUMN CANNOT BE SORTED Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] When sorting a column, empty   values in this column do not move but stay at the same position. Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT132814 === END OF ISSUE === Title: PO09734: THE JOB STATUS (.STA) FILE SHOULD BE UPDATED AFTER PROCESSING A RECORD Description: [SP 6.1, SP 6.2, SP 6.3] For load file jobs, the status file    should be updated at the end of processing a row, not at the    beginning, so in case of an unforeseen crash, the chance of     losing a record is lower. Currently, if the instance crashes    after the status file is written but before the transaction has been synchronized, then there is the chance that a transaction  will be lost. After the fix, the risk will be if the instance   crashes when a transaction is synchronized and before the statusfile is written, which could result in duplicate transactions.   Workaround: In the case of a crash, examine the data present on the systems which did not crash, and check if the last transactions ingestedare present on the other instances. If they are not, then updatethe status file so they are ingested as well (contact support   for details on how to do this).                                  Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT132559 === END OF ISSUE === Title: PO09863: MULTIPLE INSTANCES COULD ENTER MAINTENANCE MODE AT THE SAME TIME IN CERTAIN CONDITIONS. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Cluster interlock relies on    heartbeat settings to determine if an instance is in maintenancemode or not (for example if the instance is performing go-live).If heartbeat communication incorrectly assumes that another     instance is unreachable for example because the defined         heartbeat threshold is exceeded in the communication between theinstances, this could allow multiple instances to enter         maintenance mode at the same time, when it should not.           Workaround: Set Cluster Interlock setting of 'minimum active instances' to  [total number of instances - 1] to help reduce chances of       multiple maintenance mode activities (such as two instances     performing go-live) at the same time. Also ensure heartbeat     threshold is set to 3x the average ping latency between your    instances.                                                       Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT132501 === END OF ISSUE === Title: PO09862: PRECEDENT'S DEFAULT BEHAVIOUR IS TO INCLUDE FUTURE TRANSACTIONS WHEN USING "RECOMPUTE TARGET" Description: When a merging happens with "recompute target" selected, and a  precedent is recomputed, then if there have been additional     transactions on this index then the values from the latest      matching transaction will be selected, which could be after the original transaction. This is expected, and is documented in theonline help, but the user experience could be improved.          Workaround: Use a target condition that restricts time to be in future.      Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT132420 === END OF ISSUE === Title: PO09807: ERROR MESSAGE WHEN REFERENCING A CALENDAR'S OUTPUT IN A LOWER PRIORITY CALENDAR IS TOO GENERIC Description: [SP 6.4] It is not possible to use an output of a higher        priority calendar in a lower priority calendar condition as the lower priority calendar is computed before the higher priority  calendar. When trying to save a calendar with such condition a  generic error dialog is shown: "The calendar profile definition contains errors. The profile cannot be created." which does not indicate the problem.                                            Workaround: Change the priority so the calendar that uses the output in its condition is computed after the other calendar.                  Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT132359 === END OF ISSUE === Title: PO09489: SIMULATION REPORT PRINT VIEW IS NOT WORKING IN THE NEW UI Description: The Simulation report print view function is not working. Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT132233 === END OF ISSUE === Title: PO09861: DEADLOCK CAN OCCUR DURING WORKING QUEUE UPDATES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When adding, removing or replacing a Working Queue, while working queues - with conditions using attributes that do not exist in all cases as reporting attributes per definition - are computed in the background, a deadlock is possible. This can cause FLI to block, EOD and golive to hang and requires to kill and restore the instance. Workaround: Only use conditions in working queues for attributes that are   enabled as reporting attributes in all case classes of the      working queue mandators.                                         Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.05*, 6.4.2.04*, 6.5.0.02*, 6.6.0.00* Known Issue ID: DT132117 === END OF ISSUE === Title: PO09842: FILTER IS NOT WORKING IN TABLE OF A READ ONLY FORM Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] For example in the attribute form, it is not possible to filter the category table in champion or retired revisions. Workaround: The category can be filtered in a challenger revision.           Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01 Known Issue ID: DT132099 === END OF ISSUE === Title: PO09835: WILDCARD IS NOT ALLOWED IN CONDITIONS FOR CATEGORICAL ATTRIBUTES Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Attribute using category is not allowed for wildcard character to add in conditions.            Workaround: For Safer Payments v6.1.x, use the old User Interface. For SaferPayments v6.2 and above, there is no workaround.                 Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.09, 6.4.2.08, 6.5.0.06, 6.6.0.04 Known Issue ID: DT132024 === END OF ISSUE === Title: PO09858: PEER MASTERDATA DISPLAYED INCORRECTLY IN CASE INVESTIGATION Description: Description: [SP 6.4] In case investigation, when a case has a  value for a peer index source and target and these attributes   are selected as reporting attributes and the index has          masterdata which is enabled in the case class, only the source  is displayed (twice) with the source masterdata attribute also  appearing twice. The expectation is both the source and the     target should be displayed.                                     Workaround:                                                      Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT131802 === END OF ISSUE === Title: PO09826: WHEN THE DIGIT GROUP SEPARATOR IS SET TO "NONE", CUSTOMERS CAN'T TYPE NUMBERS BIGGER THAN 5 DIGITS IN THE NUMBER FIELDS Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4]                                When the digit group separator is set to "none" in the user's   profile, customers can't type numbers bigger than 5 digits in   the number fields                                                Workaround: Choose a different digit group separator than "none".            Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT131797 === END OF ISSUE === Title: PO09832: RESERVE CALL SHOULD NOT BE DONE IF THE USER DOES NOT HAVE PRIVILEGE TO CHANGE AN ELEMENT Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Reserve request is sent for an element even if the user does not have change permission for the element, in which case the reserve will fail. The error has no further impact than creating an error log message 449.           Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT131781 === END OF ISSUE === Title: PO09856: WRONG ERROR MESSAGE WHEN DOWNLOADING CONFIGURATIONS LARGER THAN 4GB FROM UI. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] A user receives the error      message "Archive cannot be created as the size would be larger  than 4 GB" when attempting to download the configuration from   the user interface on the System Internals page. This only      occurs when the uncompressed size of the cfg folder on disk is  larger than 4GB, not the resulting archive as the error message suggests.                                                        Workaround: If your config is larger than 4 GB, copy the configuration      manually from the file level and archive.                        Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT131427 === END OF ISSUE === Title: PO09855: SIMULATION IS INVALIDATED IF SIMULATION QUERY IS RUN ON REMOTE INSTANCE. Description: 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. Workaround: Use the context menu execute instead of the "save and execute"  button as this does not trigger a save.                          Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT131175 === END OF ISSUE === Title: PO09854: POSSIBLE CRASH WHEN COMPUTING RISK LISTS WHILE ADDING/DELETING ENTRIES Description: A crash occurs if a defined risk list is concurrently queried and modified. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT131161 === END OF ISSUE === Title: PO09831: CASE UPDATE FROM FLI IS IGNORED AS THE INSTANCE HAS MORE RECENT LOCAL MODIFICATIONS Description: 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. Workaround: Keep incoming data flow that may result in cases and API enabled on the same instance.                                           Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT131149 === END OF ISSUE === Title: PO09813: LONG WAIT TIME IF NO REMOTE LOOK UP INDEX CAN BE USED TO FIND THE RECORD AND IT MAY BLOCK OTHER API OPERATIONS Description: Retrieving data for reporting attributes from transactional data during case investigation takes too long if the remote lookup index cannot be used to find the unique record IDs (URIDs). Now, the search is omitted and it is assumed that the remote lookup index provides a URID for each case. As a consequence, it is possible to see occasional empty values for some attributes if a case (alarm) does not have a value for the remote lookup index. Workaround: Disable the settings "Resolve uncached reporting attributes" and "Include DDC to resolve uncached reporting attributes". Other  workarounds may be required, if the problem persists. Please get in contact with support. For example, it may be required to    make the API instance as the primary instance for all incoming  messages and let the investigators only work on investigation   cases primarily created on the API instance, by adding case     selection condition of: "caseUid" starts from                                                            Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.0.03 eFix 01 Piraeus, 6.5.0.00 Known Issue ID: DT131096 === END OF ISSUE === Title: PO08111: MISLEADING PATH IN AMI LOG MESSAGE Description: 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. Workaround: N/A                                                              Status: Closed Affected Version: 5.7.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT131023 === END OF ISSUE === Title: PO09756: A MERGING RECOMPUTATION MAY SET WRONG OLDEST URID FOR A NEWLY CREATED ATTRIBUTE Description: 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. Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.00 Known Issue ID: DT130961 === END OF ISSUE === Title: PO09850: AN ANALYSIS THAT USES A DIFFERENT DATA SELECTION THAN THE SIMULATION CAN LEAD TO A CRASH Description: 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. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT130930 === END OF ISSUE === Title: PO09849: MDC/DDC VALUES ARE INCORRECT WHEN VIEWING A THE ATTRIBUTE SPECIFICALLY. Description: SP 6.1.0.10, SP 6.2.1.05, SP 6.3.0.02, SP 6.4.0.00] MDC/DDC     storage is incorrectly showing values when viewing a the        attribute specifically although the attribute is not stored.    When viewing the MDC/DDC value of the attribute in the table of attributes, the values are correct. This is only a UI issue,    however saving the incorrect values could lead to persisting    them.                                                            Workaround:  Switch to another tab and come back (refresh), the value will  display correctly                                                Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT130795 === END OF ISSUE === Title: PO09847: USING DOUBLE SQUARE BRACKETS IN A JSON ELEMENT NAME IS NO LONGER ALLOWED AND MAY CAUSE A CRASH Description: [SP 6.1, 6.2, 6.3, 6.4, 6.5] Using double square brackets in a JSON element name is no longer allowed and may cause a crash Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT130526 === END OF ISSUE === Title: PO09846: GO-LIVE A CHALLENGER WHEN FRAUD MARKING REPORT EXISTS COULD LEAD TO CRASH Description: Fraud mark report column references are sometimes created from challengers and invalidated revisions instead of from champions. Workaround: Remove the fraud marking report temporarily until a fix is      provided.                                                        Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT130360 === END OF ISSUE === Title: PO09845: RUNNING A REPORTING QUERY WITH RULE PERFORMANCE WILL ALWAYS RESULT IN A FATAL LOG ENTRY. Description: An error occurs when a reporting query is run with rule performance checked. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT130192 === END OF ISSUE === Title: PO09814: CONFIGURATION OF MERGING RETIRES MAY BE MISLEADING Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When retry is enabled for a    merging, "Max Merging Tries" defines the total number of times  it is tried to find a merging target. It does not refer to the  retries but total attempts. So 0 number of retries means that   the merging would never try to find the target and always fail. And 1 means there is no retry.                                   Workaround: For example if number of retries is desired to be 2, set the    value to actually 3 (1 original + 2 retries).                    Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT130157 === END OF ISSUE === Title: PO09821: UPLOAD CASE ATTACHMENT ATTACHMENT BUTTON IS NOT ENABLED Description: In case investigation, the upload button for attachments is always deactivated and drag and drop for it does not work. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT129826 === END OF ISSUE === Title: PO09781: QUERY COLUMN DATA ISSUES WHEN ATTRIBUTES/MASTERDATA HAVE THE SAME NAME Description: [SP 6.4] When several columns of a query have the same name,    i.e. when there are several attributes or masterdata with the   same name, the order of data contained in it may be incorrect,  also if (masterdata) attributes in addition also have           categories, an UI error may occur.                               Workaround: N/A                                                              Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT129206 === END OF ISSUE === Title: PO09780: INVESTIGATION CASE CANNOT BE VIEWED WITH AN ERROR IF IT HAS MULTIPLE MASTERDATAS WITH CATEGORY ENABLED Description: In certain situations, cases with masterdata on category attributes are not displayed in case investigations. Workaround: In case class definition, make sure that only one of the        selected masterdatas' attributes has categories enabled.         Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT129205 === END OF ISSUE === Title: PO09843: MISSING PROGRESS BAR FOR REPORTING QUERY, GROUP BY QUERY, MASTERDATA QUERY, AND COMMON POINT QUERY. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The user interface is missing aprogress bar for Reporting Query, Group by Query, Masterdata    Query, and Common Point Query. It is most noticeable when       searching many transactions (ie. 50K+) when the results take    longer to compute and display on browser. This currently exists for normal Investigation Queries (ie. Ad Hoc), and will be addedfor the other query types in a future release.                   Workaround: N/A                                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT129188 === END OF ISSUE === Title: PO09841: USING LIMIT_MDC AND LIMIT_DDC DEBUG FLAGS CAN IMPACT AUDIT ENTRY TO SHOW WRONG SIZE. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] When using debug parameters of limit_mdc and limit_ddc the audit entry falsely shows the       limited value instead of the real stored value. Thus, the       attribute audit trail does not record the actual capacities     (before the limit) as it should.                                 Workaround: Do not use these debug flags for Production systems.             Status: Closed Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT128950 === END OF ISSUE === Title: PO09840: SWITCHING TO RETENTION BY TIME FOR EXTREMELY LARGE MDC/DDC RETENTION NUMBERS CAN CAUSE A FREEZE. Description: [SP 6.2, SP 6.3, SP 6.4] If using Retention by Record and clienthas extremely large MDC/DDC retention numbers (i.e. 5           quadrillion was added accidentally), when switching to Retentionby Time that could cause SP to hang. Note that this can likely  only happen on test environments which have limits set, as      otherwise the hardware limits will prevent numbers which are    this large from being used.                                      Workaround: Contact IBM support for assistance identifying and fixing       extremely large retention numbers.                               Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT128949 === END OF ISSUE === Title: PO09839: RULE CONDITION ATTRIBUTES NOT PRIMED IF NOT AVAILABLE IN MDC FORSIMULATION Description: Now, simulation automatically detects rule condition attributes that need DDC access and informs the user in the report. Workaround: Users would need to know for how long attributes are stored, andthen according to that enable attributes manually that are not  stored in the MDC, for the whole data range of the simulation.  This information is provided in the system internals Data cachestable as "MDC Oldest URID" and "MDC Oldest Timestamp" columns.  For example, if an attribute's MDC Oldest Timestamp is          2022-04-01, it needs to be enabled for simulation, in case the  simulation data range reaches further into the past than this   date. If users do not have access to that page, it could be     exported as CSV and provided to them on a regular basis.         Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT128812 === END OF ISSUE === Title: PO09809: ERROR 227 AND BLOCKED FLI DURING VALUE DELETION OF MULTIVALUE MASTERDATA WHEN RELATIONSHIP ATTRIBUTE(S) EXIST Description: Broken multivalue masterdata is erroneously detected during data deletion that involves relationship attributes. Workaround: Remove the relationship attribute in the masterdata definition.  Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT128680 === END OF ISSUE === Title: PO09837: POSSIBILITY THAT FLI BUFFER OVERFLOW IS DETECTED WHEN THERE IS NO ACTUAL OVERFLOW Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] SP could falsely detect a FLI  buffer overflow resulting in Instance Lockdown. This happens    when the write and delete position are pointing to the same     location, meaning that there is no other message in the buffer  that is not acknowledged, and the remaining of the buffer is    just enough to fit the incoming message perfectly. Contact IBM  Support if your instance goes into Lockdown.                     Workaround: N/A                                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT128457 === END OF ISSUE === Title: PO09811: OPERATOR "ENDS WITH" IS NOT WORKING CORRECTLY FOR NUMERIC VALUES WHEN EXPRESSIONS CONTAINING DOTS ARE USED. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] The condition operator "ends with" is not working correctly for numerical values when  expressions containing dots are used.                            Workaround: For expressions starting with non zero digit, remove dot from   expression. There is no workaround for expressions starting with zero, like 0.00, 00.00 etc.                                     Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT128238 === END OF ISSUE === Title: PO09834: SYSTEM INTERNALS "MCI OPEN CONNECTIONS" COULD DISPLAY AN INACCURATE TOTAL ON THE UI. Description: The system information page can show a wrong number of open MCI connections if multiple MCI connections get opened or closed at the same time. Workaround: Run this command against the MCI port:                          netstat -anp | grep IP:PORT | grep ESTABLISHED | wc -l                                                                          (Optional) Restart the instance to reset the MCI Open           Connections count, however it could become inaccurate again.     Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT128161 === END OF ISSUE === Title: PO09816: IMPROVEMENT OF RETENTION BY TIME PERFORMANCE. Description: Using retention by time can lead to increased computation latencies for huge configurations. Now, there is no difference in the computation flow between retention by records and retention by time. To limit the visibility of data to the configured retention periods, the end of day job removes outdated values from the data caches in a process called trimming. For more information, see the online help for Administration>System>Retention settings. Workaround: If experiencing latency, use Retention by Record.                Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT128145 === END OF ISSUE === Title: PO09830: USER PREFERENCES RELATED TO SEARCH IGNORE CASES, DEFAULT IGNORE CASES, PRINT VIEW, AND COPY EXPRESSIONS ALWAYS FALSE. Description: [SP 6.3, SP 6.4] Under the users My Account preferences the     following settings are always false (unchecked) after you save  and navigate back to the page (not saved).                      1. Ignore cases in search                                       2. Print view for individual elements                           3. Copy view for expressions                                    4.  Set ignore cases as default                                  Workaround: Contact IBM support who can help you modify the users           preferences at file-level if absolutely necessary.               Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT127633 === END OF ISSUE === Title: PO09825: WHEN THE FILTER COLUMN TOOLBAR IS SHOWN, THE SCROLLBAR MISBEHAVES FOR FULL TABLE Description: [SP 6.1,6.2,6.3,6.4] When the filter toolbar is shown above the table, the vertical scrollbar does not fit for the current table. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.01, 6.6.0.00 Known Issue ID: DT127327 === END OF ISSUE === Title: PO09824: A FATAL ERROR IS PRINTED WHEN A REVISION HAS A PMML MODEL WITHOUT ATTACHMENT. Description: An unrecoverable error occurs during startup if a revision has an invalid PMML model (either the attachment is missing or it is invalid). Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT127326 === END OF ISSUE === Title: PO09787: "COMPARE TO REVISION" IN REVISION CONTROL SHOWS PREVIOUSLY SELECTED REVISION Description: After selecting two revisions and then clicking the 'Compare Revision' button, the 'Revision to compare' drop down display the wrong revision or no selection. It only works the first time, the first revision that was selected will stay in the "Compare to revision" drop down for following comparisons to other revisions. Workaround: Manually select the model to compare.                            Status: Closed Affected Version: 6.3.0 Fixed Available: 6.4.2.11;6.5.0.09;6.6.0.07;6.7.0.03;6.8.0.01 Known Issue ID: DT127199 === END OF ISSUE === Title: PO09786: DATA EXPORT JOB CONTINUES DESPITE AN OUT OF DISK SPACE ERROR Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Data export job        continues executing, even though the actual write is no longer  successful due to an out of disk space error. Error F 0099 "No  space left on device" is logged as a result, but otherwise no   other feedback is displayed to the user and the job just        continues.                                                       Workaround: Keep free space available. Monitor log for fatal "No space left on device" message (F 0099).                                     Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT126750 === END OF ISSUE === Title: PO09819: DAILY SCHEDULED JOBS CAN EXECUTE TWICE THE SAME DAY Description: [SP SP 6.1, SP 6.2, SP 6.3, SP 6.4] A scheduled job can execute twice if certain conditions are met. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT126521 === END OF ISSUE === Title: PO09767: DATA RANGE IN NEW QUERY ALWAYS SET RECORDS RELATIVES AS DEFAULT Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] User account's Data range      default option setting is ignored for new data selection.        Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT126341 === END OF ISSUE === Title: PO09770: VALUE OF TIMESTAMP ANALYSIS AND ACCOUNT ANALYSIS SWAPPED IN REPORTING QUERY RESULT Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] The values of timestamp        analysis shown in the "Period" column and account analysis shown in the "Accounts" column were swapped and thus shown           incorrectly in reporting query results.                          Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT126338 === END OF ISSUE === Title: PO09772: INCONSISTENT BEHAVIOUR WHEN ADDING/DELETING CONDITIONS IN RULE GENERATION SETTINGS Description: When adding/deleting additional conditions on the rule          generation settings page, inconsistent behavour may occur such  as duplicated conditions.                                        Workaround: When planning to add/delete conditions, after opening the       settings page, first delete all existing conditions and then    re-add them including the new condition/without the to be       deleted condition.                                               Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT126193 === END OF ISSUE === Title: PO09769: REPEATING JOBS MAY BE EXECUTED TWICE Description: [SP 6.2, SP 6.3] A scheduled job may be executed twice on certain occasions when the job scheduler that repeats within a certain interval (defined in system configuration) to check, if jobs should be started, does the check at the same second that the job is supposed to run per schedule definition. Workaround: It cannot be fully prevented as it is a timing issue. But the   lower the repeat interval, the higher the chance of running into this so increasing the repeat interval may decrease the chance to run into it but may also lead to delays in the job execution. Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT126099 === END OF ISSUE === Title: PO09686: LOW POSSIBILITY OF FLI OUTGOING CONNECTION TO HANG Description: [SP 6.1, SP 6.2, SP 6.3] When an FLI message is transferred, the receiving side sends keep alive pings to the sending side until the message transfer is completed. In rare cases it may not    cancel sending pings which may lead to the FLI outgoing         connection to hang on the sending side.                          Workaround: Disable and enable the FLI on the receiving side in case the    issue occurs.                                                    Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT125786 === END OF ISSUE === Title: PO09805: ADDING A PREDEFINED CONDITION WITH THE LEFT ATTRIBUTE ENCRYPTED CAUSES DATA LOSS. Description: Saving rule generation settings with a condition that uses an encrypted attribute fails. This problem leads to an invalid revision being sent using FLI, causing remote instances to remove all elements in that revision. Workaround: Avoid using a left attribute that is encrypted on a Predefined  Condition until this issue is addressed. Do not GoLive with     this.  Proceed removing this revision. If you have gone live getin touch with support.                                           Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT125580 === END OF ISSUE === Title: PO09725: Instance hangs when saving cluster page/disabling MCI during golive or updating certain elements while MCI is waiting Description: [SP 6.1] The issue may occur during a golive or when saving a   mandator/case class/case state/SAI/case workflow/user           group/working queue/reminder/KPI/Notification/External query or message. When the MCI is not closed during a golive (for the    golive scenario) and has accepted transactions that will wait   for the golive/update to finish, it is possible that the        instance enters a hanging state, if the cluster page is saved or MCI is disabled during the golive/save action. The instance    needs to be killed and restored in that case.                    Workaround: Do not perform any changes to the cluster during a golive or    when performing updates to the named elements and do not disable the MCI via context menu.                                       Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT125497 === END OF ISSUE === Title: PO09800: AFTER NEWLY CREATED ATTRIBUTE WITHOUT LOADING DATA QUERIES DISPLAY EMPTY VALUE INSTEAD OF N/A Description: [SP 5.7,SP 6.0,SP 6.1,SP 6.2,SP 6.3,SP 6.04] When a newly       created attribute is queried, the query for example returns 0   instead of n/a for numeric attributes. After loading one more   record, the n/a will be displayed as expected.                   Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT125209 === END OF ISSUE === Title: PO09735: RUNNING INTERNAL RANDOM FOREST GENERATION MAY CRASH INSTANCE WITH OOM Description: [SP 6.1, SP 6.2, SP 6.3] There is no preventative mechanism during model generation when exceeding the memory limits so it is possible that the instance may crash with Out Of Memory error during a model generation. There is only a log message indicating memory allocation issues but it will still let the user continue running model generations. Workaround: Monitor the Safer Payments log for error of "Cannot allocate    memory" and reduce the scale of the data set accordingly.        Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT125044 === END OF ISSUE === Title: PO09796: WHEN USING EXTENDED AUTHENTICATION, THEN AFTER LOGIN THE NAVIGATION MENU DOES NOT APPEAR AND START ON TAB IS ALWAYS MYACCOUNT. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] After checking on "Enable      extended authentication" and entering the One Time Password     (OTP) code to login, the user is directed to MyAccount, despite Start On Tab being set to something else (ie. Investigation or  Administration), and the Navigation Menu does not appear.        Workaround: Press Reload (CTRL+R) on browser, or [New Window] icon on       top-right of SP to reload the page for the navigation menu to   appear.                                                          Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT124957 === END OF ISSUE === Title: PO09794: SAI CHECKBOX "SHOW ON DASHBOARD" DOES NOT TOGGLE DISPLAY ON/OFF IN DASHBOARD AS EXPECTED. Description: [SP 6.1, SP 6.2, SP 6.3, SP 6.4] Going to "Administration >     Dashboard settings > Status Alarm Indicators" and checking on oroff the "Display in Dashboard" setting does not toggle the SAI  from appearing in the dashboard as expected.                     Workaround:  Under General settings uncheck "Enabled" to prevent display of the SAI. Note this will also stop any Log/Email alerts.          Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT124833 === END OF ISSUE === Title: PO09793: ADDING A CONDITION TO CASE SELECTION IMMEDIATELY HIGHLIGHTS DROPDOWNS TO RED Description: :[SP 6.1, SP 6.2, SP 6.3, SP 6.4] Adding a new condition to CaseSelection immediately highlights its dropdowns for condition    attribute and operator to red and prints "an entry in this fieldis required".                                                    Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT124804 === END OF ISSUE === Title: PO09790: DATA SELECTION MAY SHOW INCORRECT DATES FOR SYSTEM TIME AFTER DISABLING/ENABLING FLI DURING INDEX RESET Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3, SP 6.4] When the FLI gets deactivated and re-activated while an index reset is ongoing, there is a chance that data selections afterwards show "Last available sever date/time is 1970-01-01 00:00:00". There is also a theoretical chance that the same happens without index reset, in case the FLI gets deacticated an re-activated within a very short time span. If the situation occurs, try to disable FLI, wait for 10 seconds then re-enable FLI again to resolve it. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT124624 === END OF ISSUE === Title: PO09788: DURING REBUILD/RESET OF AN INDEX, THE MCI/BDI/FLI/KMI SHOULD NOT BE ALLOWED TO BE ENABLED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3, SP 6.4] During rebuild/reset of an index, the MCI/BDI/FLI/KMI should not be allowed to be enabled Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.03, 6.4.2.02, 6.5.0.01, 6.6.0.00 Known Issue ID: DT124622 === END OF ISSUE === Title: PO09789: DURING THE REBUILD/RESET INDEX PROCESS, THERE SHOULD BE BETTER PROGRESS INDICATION. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3, SP 6.4] During both the rebuild and reset index process ,there should be better progress indication. Currently there is no indicators in the UI or logs. Workaround:                                                                  Status: Closed Affected Version: 6.4.0 Fixed Available: 6.5.0.00 Known Issue ID: DT124621 === END OF ISSUE === Title: PO09619: Possible crash with backtrace after a golive if the data from the champion to retire is accessed via query, investigation etc. Description: A backtrace or crash can occur after a golive if the data from the champion to retire is accessed from a query, case investigation, and so on. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT124561 === END OF ISSUE === Title: PO09727: MQ RESPONDER URL SHOULD BE OPTIONAL Description: The responder URL field on the MQI configuration page is erroneously marked as required. Workaround: Put a dummy place holder URL in "Responder URL", if OCSP is not used in the MQ configuration.                                    Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT124556 === END OF ISSUE === Title: PO09761: MANY LONG RUNNING QUERIES MAY CAUSE UNRESPONSIVENESS AND FATAL ERRORS Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3, SP 6.4] It is possible that queries are set up for long data ranges accessing DDC so   they run for many hours. If these queries continue running in   the background, it is possible that all threads are used up overtime which can lead to fatal errors indicating a                boost::thread_resource_error. As a consequence the API may      become unavailable and SP may not be able to process messages   anymore. There should be a possibility to terminate all queries that are running in the background.                              Workaround: N/A.                                                             Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT124281 === END OF ISSUE === Title: PO09427: FCD RESPONSE FILLS WITH 0X00 (NULL) INSTEAD OF 0X20 (SPACE) Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2] When a transaction response is sent in FCD Format and the space needs to be filled, safer      payments uses 0x00 as a fill-byte. Instead the response should  be filled with 0x20 as fill bytes                                Workaround: N/A                                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT124173 === END OF ISSUE === Title: PO09785: FATAL ERROR MESSAGE 99 PRINTED IN THE LOGS WHEN SP IS WRITING OUT LATENCY INFO AND RUNS INTO A RESERVABLE UID WHICH HAS BEEN DE Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3, SP 6.4] The fatal errormessage "F 0099 Cannot find reservable for message statistics,  uid" is printed in the logs when SP runs into a reservable uid  that is deleted. This message can be ignored as there is no     further impact if this happens.                                  Workaround:                                                                  Status: Open Affected Version: 6.4.0 Fixed Available: No fixed available Known Issue ID: DT124051 === END OF ISSUE === Title: PO09784: CRASH MAY OCCUR IF INDEX IS CORRUPTED AND INDEX ENTRY IS PURGED. Description: A crash can occur during the end of day job if an index is corrupted and the index entry is purged. Workaround: Always restore after a crash to prevent running into a corruptedindex related crash.                                             Status: Closed Affected Version: 6.4.0 Fixed Available: 6.3.1.02, 6.4.2.01 Known Issue ID: DT124042 === END OF ISSUE === Title: PO09760: MODEL REVISION COMPARISON RESULT SHOWS CHANGE FOR LIST WITHOUT CHANGE Description: List element is shown as changed in revision comparison result if it has more than two output values, even though there is no change between these two revisions. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT123784 === END OF ISSUE === Title: PO09778: REBUILD INDEX COMPUTES ALL MESSAGES WITHOUT APPLYING MANDATOR CONDITIONS Description:  [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] The rebuild index     maintenance function computes the index for all messages and    does not apply mandator conditions to limit the messages that   shall be computed, if the index is on a lower level mandator.    Workaround: Make sure mandator conditions are added in the index computationconditions. They can be removed after the rebuild index job is  completed.                                                       Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT123566 === END OF ISSUE === Title: PO09758: MISSING [ESC] KEYBOARD SHORTCUTS TO CLOSE DIALOGS Description: [SP 6.1, SP 6.2, SP 6.3] In the online help User Access page, it is mentioned that the dialogs should be closed by [ESC] button. However, this is not the case.                                  Workaround: Close the dialog via the close button.                           Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT123279 === END OF ISSUE === Title: PO09776: UI JSON ERROR WHEN ACCESSING CASE INVESTIGATION RELATED PAGES. Description: On encrypted instances, a popup error might appear when a case creation page is opened. Workaround:                                                                  Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT123272 === END OF ISSUE === Title: PO09771: CASE GROUPS AND CPPS ARE NOT DELETEABLE FROM UI Description: [SP 5.7,6.1,6.2,6.3] UI does not allow Case Groups or CPPs to bedeleted on old or new UI.                                        Workaround: Disable case groups and CPPs. To actually delete them, remove   the respective case_group_xxx.iris file from the cfg folder on  every instance when the instance is down.                        Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT123101 === END OF ISSUE === Title: PO09755: MOVING THE API TO ANOTHER INSTANCE DOES NOT DISABLE INVALID TABSFROM THE MENU Description: [SP 6.1, SP 6.2, SP 6.3] When on the API instance and switching the API to another instance, the top navigation bar does not    refresh the privileges.                                          Workaround: Refresh the browser after switching the API.                     Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT123084 === END OF ISSUE === Title: PO09768: CASE SEARCH PROVIDES NO RESULTS WHEN INPUT HAS DASHED PAN FORMAT Description: [SP 6.1, SP 6.2, SP 6.3] While searching for a PAN in case      search (ie. copied from case investigation), if an input is usedthat is in dashed PAN format, there will be no results returned. Workaround: Remove the dashes manually from the copied PAN after pasting    into case search to get a result.                                Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT123023 === END OF ISSUE === Title: PO09753: RISK LIST WRITTEN TO DISK AFTER ENTRY DELETION EVEN THOUGH NO ENTRY WAS FOUND FOR DELETION Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Safer Payments writes a risk list to disk on the API and remote instance when deleting risk list entries even if no entry is found to be a fitting     target for deletion (i.e. when deleting risk list entries via   script) and there was effectively no change. This unnecessary   write operation on remote may impact the FLI synchronization.    Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT122994 === END OF ISSUE === Title: PO09720: CASE SELECTION PAGE CONTAINING A CONDITION WITH EMPTY EXPRESSIONVALUE GIVES ERROR Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] The validation on UI   checks if the condition is valid, but it does not check if the  parameters in expression is empty. As a result, it can send     request with empty value. The user gets an alert on the page anderror in the log (E 0063 - Invalid definition of condition      created from API).                                               Workaround: Fill in or remove the empty expression.                          Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT122969 === END OF ISSUE === Title: PO09751: INSTANCE OPTION MISSING IN SOME SAIS IN THE NEW USER INTERFACE Description: Maximum latency, FLI rate, and latency violations SAIs do not work correctly because the option for instance selection is missing in the user interface. Workaround: When creating these SAI types, create a copy from an SAI with   instance selection option, then change the type to "MCI latency violations", "MCI maximum latency" or "FLI rate". Following SAI types can be used as a copy source: Message rate, External, Disk usage, average latency.                                         Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT122752 === END OF ISSUE === Title: PO09740: FREE DISK SPACE SAI IS NOT TRIGGERED, IF SPACE IS ALREADY BELOW SET THRESHOLD Description: [SP 6.1, SP 6.2, SP 6.2.1] A status alarm indicator (SAI) to    monitor free disk space that is updated with a new threshold,   may not log/send an email, if the disk space of the system is   already lower than the set threshold. The dashboard on UI will  display it correctly.                                            Workaround: The workaround is to update the free disk space SAI where the   threshold has not yet been breached. Or, to create a new SAI    from scratch.                                                    Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT122704 === END OF ISSUE === Title: PO09732: PEER INDEXES DO NOT SHOW UP CORRECTLY FOR SOME PROFILINGS IN CHALLENGER REVISIONS Description: Model elements like counters and events do not display the peer index aspect attribute when the page is opened from within a challenger. Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT122427 === END OF ISSUE === Title: PO09730: TIME FILTERS ARE NOT TRIGGERED WHEN USER HITS THE ENTER KEY Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] In the new User Interface,     after the user enters a value in a time filter, for example in  case selection filters, and hit the Enter key, the time filter  is not applied.                                                  Workaround: Hit the Tab key or click any empty space on the page             Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT122189 === END OF ISSUE === Title: PO09749: THE EXTERNAL MODEL COMPONENT FORM IS SLOW WHEN THERE ARE MANY MAPPINGS. Description: In the user interface, improved the performance of the external model page. Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT121982 === END OF ISSUE === Title: PO09726: INDEX BASED EVALUATION CASE WITH REPORTING ATTRIBUTE CONTAINING EMPTY VALUE CAUSES UI ERROR Description: [SP 6.1, SP 6.2, SP 6.3] Index based evaluation cases can have a reporting attribute whose value is empty if the index allows   such value to be inserted. An error occurs when viewing such    index based evaluation case. As the case cannot be viewed, it   should be closed via table action. You can also temporarily     disable all masterdata in the case class, to be able to open it. Workaround: Use index computation and insertion condition to exclude        transaction records with empty value for index attribute from   index computation.                                               Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT121834 === END OF ISSUE === Title: PO09743: INCONSISTENT RESULTS WITH MERGINGS AND EXTERNAL MODEL COMPONENTS Description: [SP 6.3] When mergings create new records for which external    model components get computed or mergings do a recomputation of a record for which external model components get computed, the  results may differ between the primary instance and remote      instances. For example, when a merging does not find a source   and creates a target, it is possible that on remote the merging is re-applied to the newly created target.                       Workaround:                                                                  Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT121739 === END OF ISSUE === Title: PO09722: MULTI VALUE MASTERDATA PRINTS MISLEADING COUNT MISMATCH LOG MESSAGE ON STARTUP Description: [SP 6.1, SP 6.2, SP 6.3] During startup the log may contain     following log message: 'W 0733 DDC for masterdata 'XXXX' linked list pointers donor max fill count does not equal champion max  fill count. This could indicate ddc corruption. Using donor max fill count' This warning can be ignored as long as the log      message 'I 0224 DDC for masterdata 'XXXX' linked list pointers  taken unchanged with 100,000,000 entries, using 0.745 GB disk'  is printed after the warning. If this is not the case, please   contact support.                                                 Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT121676 === END OF ISSUE === Title: PO09736: IN THE OLD UI, CASE IS UNRESERVED WHEN EXPORTING QUERY RESULTS Description: [SP 6.1] In the old UI, when query results are exported, this   leads to the clearing of the investigative user for the case, soany subsequent action results in the error, "the model is not   reserved for the user"                                           Workaround: Use new UI or user has to go back to case selection in order to access the case again                                            Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT121442 === END OF ISSUE === Title: PO09719: EUROPEAN DATE TIME FORMAT TIME IS DISPLAYED AS INVALID Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] In the new User Interface, the time filter field displayed as Invalid if using European date time format. This affects for example data selections, case     selection, cpp selection, logs, dashboard, reports.         Workaround: Use other date time format for the user, such as date time in   ISO Standard or U.S.A. format.                                   Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT121421 === END OF ISSUE === Title: PO09716: Remote simulation result is invalidated after save and execute of simulation query or saving any element Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] After running a        simulation on a remote instance, if the user executes a query   from within the form using the \"save and execute\" button, the simulation result on the remote instance is invalidated. The    simulation is also invalidated for every change applied to the  revision, e.g. saving an attribute or saving the general        revision settings.                                                                                                              Update: The issue reported in this APAR has been fixed in Safer Payments 6.2.2.02, 6.3.1.02, 6.4.2.01, 6.5.0.00. Refer to the   description and change log for APAR PO9855 for details.          Workaround: Execute the query from the table with the \"Execute query\"     option. Do not perform any save operations while a simulation is running on remote.                                              Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT121004 === END OF ISSUE === Title: PO09698: FATAL ERROR FOR MULTI ERASE WHEN TO BE DELETED ELEMENT IS NOT FOUND Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] With multiple tabs     open, deleting the same elements from two tabs, i.e., deleting  some revision elements from one tab and deleting the same       revision elements from second tab gives a fatal error. The same could happen when using a script and sending a multi erase      request for a non existing UID. The erase action will be        canceled at that point where the invalid UID is encountered so  not all UIDs may be deleted and the delete operation should be  repeated if needed. Other than that the error as no impact.      Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT120753 === END OF ISSUE === Title: PO09724: CRASH MAY OCCUR IF CERTAIN ACTIONS ARE EXECUTED IN PARALLEL TO A DELETION OF AN ANALYSIS Description: In rare situations, a crash occurs if an analysis is deleted while it is being accessed by another part of the code. Workaround: Do not delete an analysis in parallel to any one of the above   actions                                                          Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT120570 === END OF ISSUE === Title: PO09723: SENDING MULTIPLE STOP REQUESTS FOR AN ANALYSIS WITHIN SECONDS OF EACH OTHER CAN LEAD TO A CRASH IN RARE CASES Description: A crash might occur when analysis is stopped multiple times. Workaround:                                                                  Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT120568 === END OF ISSUE === Title: PO09690: EMPTY STRINGS IN JSON MCI RESPONSE FOR OUTPUT MAPPINGS Description: Empty double quotation marks appear in the response object if more than 10 rules are mapped from a client response. Workaround: Split the JSON array with more than 10 elements into separate   elements with less than 10 array elements.                       Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT120526 === END OF ISSUE === Title: PO09669: CASE INVESTIGATION FOLLOW UP DATE IS INCONSISTENTLY SET WHEN NOT EXPLICITLY CHOOSING A DATE Description: [SP 6.1, SP 6.2, SP 6.3] Depending on whether the user access   the values via the case selection or while inside the case the  date for the follow up is either the current date or the date of the last transition.                                            Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT120473 === END OF ISSUE === Title: PO09721: INSTANCE MAY CRASH IF STOPPING MODEL GENERATION WHILE FETCHING THE STATUS OR COMMITTING IRF Description: A crash occurs if the application tries to save a model that is generated by the random forest generator and the user stops the generation. Workaround: Do not stop a running model generation while it is running but  let it finish naturally.                                         Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT120404 === END OF ISSUE === Title: PO09688: CASE STATE CHANGE REVERTED IF REMOTE INSTANCE DELIVERS TRANSITION CASE ACTION Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] If a case transition   has a case action assigned, and the local instance does not have the AMI enabled (for the case action's OCC type) for delivering this case action, the case state change will be reverted. As a result the new state which should be set after the transition   was executed, is not applied correctly to the case.              Workaround: Enable AMI on all instances.                                     Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT120071 === END OF ISSUE === Title: PO09687: INSTANCE CANNOT START UP WHEN THERE IS AN EMPTY VALUE IN NUMERIC CONDITION Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] The instance cannot be started and throws the following example error if there is      numeric condition that has empty value in the expression:                                                                       E 0063 Invalid definition of condition in element '...' when    parsing from disk: Numeric constant expression contains invalid characters. Constant value is ''. To not affect current model   behavior, expression creation will continue. Please consider to change the expression definition. Revision: ..., status:        Champion                                                                                                                        Although it is now not possible to insert empty values into     expressions via User Interface, this issue might impact the SP  clusters which still have empty value in an expression from an  older version.                                                   Workaround: Delete the the empty value (encrypted value is "AA==")          conditions in the Champion model revision file.                  Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT119743 === END OF ISSUE === Title: PO09714: "EXTRACT DATA" OPTION MISSING IN QUERIES IN NEW UI Description: Extract query data functionality is missing in query result tables in the user interface. Validation for the extract query template is also missing. Now, the whole extracted data can also be copied with the Confirm button in the popup window. Workaround:                                                                  Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT119658 === END OF ISSUE === Title: PO09685: COUNTER SHOULD NOT COMPUTE CURRENT TRANSACTION WHEN TRANSACTION HAS NO INDEX VALUE Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] If include current is  enabled, counters compute the current transaction as long as the computation conditions is fulfilled even if it has no index    value.                                                           Workaround: Add index attribute is not null in counter computation          condition.                                                       Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT119586 === END OF ISSUE === Title: PO09026: PARSER ERROR WHEN DOUBLE QUOTES IN EXTERNAL QUERY RESULT Description: [5.7, 6.0, 6.1, 6.2]                                            When external query result contains double                      quotes this causes a parser error when opening a case that      executes the external query. There is also a parser error when  an external query has the overwrite case values option enabled  and the external query result is added to the case data. This   can afterwards lead to a parser error in case selection and     investigation queries as well.                                   Workaround: Temporarily disable the external query in the case class from   External queries on load.                                        Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT119503 === END OF ISSUE === Title: PO09706: OLD UI - THE SIMULATION QUERY FORM REFRESHES EVERY 10 SECONDS. Description: [SP 5.7, SP 6.0, SP 6.1] Simulation query changes can be        automatically reverted if not saved in under 10 seconds. The    refreshing is triggered only if the simulation is valid and the simulation is enabled, and only occurs on the Old UI.            Workaround: Save before 10 seconds, or disable Simulation to make the changeand re-enable it. On 6.1+, use new UI.                           Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT118943 === END OF ISSUE === Title: PO09701: CRASH MAY OCCUR WHEN CONDUCTING MULTIPLE SAVE OPERATIONS ON A CASE. Description: In rare situations, a crash might occur when a case is saved multiple times. It can happen when a CPP or memo is saved multiple times for the same case during a short timeframe, for example, by double-clicking Save. Workaround: Only click the button once, wait until the save operation was   performed successfully before triggering another one.            Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT118640 === END OF ISSUE === Title: PO09664: DEADLOCK POSSIBLE WHEN LOAD FILE JOBS ARE INTERFERING WITH CURTAIL MASTERDATA JOBS. Description: A deadlock might occur if a curtailing masterdata job is run at the same time and in parallel with an update to index entries. Workaround: To prevent the situation, it would be recommended not to run the curtail masterdata job in parallel with other jobs.             Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT118507 === END OF ISSUE === Title: PO09696: DEADLOCK DUE TO POSSIBLE INFINITE LOOP WHEN MULTI VALUE MASTERDATA IS CORRUPTED. Description: [SP 6.1, SP 6.2, SP 6.3]In case there is a corruption in multi  value masterdata, for example caused by a crash that was not    followed by a restore, it is possible that during operations on the masterdata, such as deletion or insertion, a blocking       situation may occur due to an endless loop in the masterdata    operation. This may lead to the EOD, golive or other activity   hanging and requires to kill the instance. To avoid running into this situation restores should be performed after crashes and  the multi value option should not be disabled and later         re-enabled for any masterdata.                                   Workaround:                                                                  Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT118331 === END OF ISSUE === Title: PO09695: THE "INCLUDE DDC" OPTION IS IGNORED WHEN EXPORTING DATA VIA JOBS. Description: When data is exported, the attributes that are stored only in DDC are ignored even if the 'includeDdc' checkbox is checked. Now, data for the attributes that are stored only in DDC can be exported. Workaround: On SP 6.1 switch to the old UI and save the job there. On SP 6.2and 6.3 please add some MDC storage for the attributes.          Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT118325 === END OF ISSUE === Title: PO09691: EOD JOB COULD RUN ON SEVERAL INSTANCES IN PARALLEL. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] EOD is a sequential    job, run node by node in order of instance id. However it could unintentionally run in parallel. One such scenario is a SCI     communication interruption. The second scenario is long running EODs where a higher id instance has not finished its EOD yet,   when the lower id instance starts the next iteration, and it    does not check higher id instances.                              Workaround: Ensure EOD jobs start/finish in minutes/hours (in same day) and monitor SP log for SCI communication issues.                     Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT118139 === END OF ISSUE === Title: PO09672: MULTIVALUE MASTERDATA IS NOT WIPED IF CAPACITIES ARE DECREASED ON FILE LEVEL. Description: [SP 6.1, SP 6.2, SP 6.3] If multivalue masterdata capacity is   not                                                             decreased with a golive, but on file level, and the instance is started up with changed capacities afterwards; there is a       chance of a crash or incorrect results when loading additional  masterdata or applying/querying existing masterdata values.     Using a regular golive to decease sizes will wipe the data      instead and is the common use case. This issue is mostly        relevant for custom config deployment processes that involve    moving configs between environments.                             Workaround: Decrease multivalue masterdata sizes with a golive instead of   using file level modifications.                                  Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT118127 === END OF ISSUE === Title: PO09673: STARTING AN INSTANCE WITH LIMIT_INDEX PERSISTS MULTIVALUE MASTERDATA CAPACITY INCORRECTLY Description: [SP 5.7.0.13+, SP 6.0.0.10+, SP 6.1.0.08+, SP 6.2.1.03+,        6.3.0.0+ ]                                                      A change was made to enable limit_index debug flag to also applyin a factor to multivalue masterdata for test environments.     However, in the event of a revision write (for example copy     revision, golive, masterkey change...) that test capacity value is written incorrectly to revision files, permanently affecting the masterdata's capacity size even after the instance is       started without limits.                                          Workaround: Note: Debug/limit flags are not recommended for Production      systems.                                                                                                                        1. Use SP versions lower than the ones noted in description, or an upcoming version with fix before using this flag.            2. Do not use this limit_index debug flag if using multivalue   masterdata . Especially for cfgs that may be used for Prod.     3. Double-check all multivalue masterdata capacity values beforeand after deployments for consistency. Contact IBM support if   you see an issue.                                                Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT118126 === END OF ISSUE === Title: PO09631: THE INSTANCE MAY CRASH IF A DEFINED RISK LIST ENTRY THAT HAS CONDITIONS IS COMPUTED IN PARALLEL OF BEING UPDATED Description: A crash might occur when a defined risk list entry is saved while it is being computed. This problem is due to a read access violation. Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT117953 === END OF ISSUE === Title: PO09671: Accessing of large event logs in the UI may cause high CPU usage and cause latencies Description: Accessing large event logs in the User Interface may cause high CPU usage and increased latencies. Workaround: If possible avoid accessing large log files on UI and access them on file level instead. If accessed via UI, wait for the log table to be loaded before changing any other filter setting.    Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT117840 === END OF ISSUE === Title: PO09647: WRONG CALCULATION OF THE INDEX_LIMIT STARTUP PARAMETER FOR MULTIPLE VALUE MASTERDATA CAPACITY Description: [SP 5.7.0.13, SP 6.0.0.10, SP 6.1.0.08, SP 6.2.1.03, SP         6.3.0.00] ATTENTION: "limit" startup parameters should only be  used in non-production environments since it can affect data    integrity! The start up parameter limit_index is applied to     multi value masterdata in the mentioned releases and above.     Using this start parameter, the size of the masterdata will be  the capacity of the multi value masterdata multiplied with the  limited index size. However, the calculation of the multi value masterdata capacity is incorrect.                                Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT117621 === END OF ISSUE === Title: PO09643: FOR COMPLIANCE LISTS, THE METAPHONE ALGORITHM WILL NOT FIND ANY HITS FOR NAMES WITH MULTIPLE WORDS, Description: A compliance list excludes records in search results if the list uses the metaphone setting and a search is done for more than one name. Workaround:                                                                  Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT117476 === END OF ISSUE === Title: PO09680: BYPASS SECTION SHOULD BE READ-ONLY IF THE INTERLOCK IS DISABLED Description: [ SP 6.2, SP 6.3 ]                                              For bypass to work, the interlock setting must be enabled. Thereis currently no mention of this in the online help or any       indication by the UI that the bypass will not work.              Workaround: Enable interlock if you want to use the bypass setting           Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT117460 === END OF ISSUE === Title: PO09661: Unexpected long wait times for various functionality Description: [SP 6.1, SP 6.2, SP 6.3] Various actions in the application     could appear blocked which could lead to deferred writing being interrupted longer than expected or computational paths being   blocked leading to overall performance problems. For example,   when saving an element that should temporarily stop deferred    writing, the deferred writing did not continue immediately      afterwards.                                                      Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT117440 === END OF ISSUE === Title: PO09646: RANDOM FOREST GENERATION IGNORES CONDITIONS AND SAMPLING CONDITIONS Description: [SP 6.2*] When computing records for the internal random forest generation, URIDs are not checked whether they are included by  the simulation conditions. Also training and verification       conditions and their sampling conditions are not considered.     Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT117274 === END OF ISSUE === Title: PO09675: THE DEFAULT TIMESTAMP, WHEN CREATING NOTICES, IS SET TO A VERY OLD TIME Description: The default timestamp for notices is a date far in the past. Now, it is the current date and time. Workaround: NA                                                               Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT116919 === END OF ISSUE === Title: PO09674: INCORRECT COLUMNS WHEN DOWNLOADING A CASE TABLE WITH MASKED DATA. Description: 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. Workaround: Ask a user who "can see masked values" to Export the Data, then manually replace sensitive values.                               Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT116865 === END OF ISSUE === Title: PO09645: SIMULATION INSTANCE SELECTION IS CUT SHORT, MUST SCROLL DOWN TO SELECT. Description: On some pages, for example on the queries page or on the rules page, users are unable to access additional values in the drop down, and there is no scroll bar available. You also cannot move the page scroll bar any further down. Workaround: Scroll down or across to see all options to select. Higher      resolutions may fare better.                                     Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT116859 === END OF ISSUE === Title: PO09644: ENTERING TEXT IN CASE INVESTIGATION MEMO FIELD IS SLOW. Description: [SP 6.1, SP 6.2, SP 6.3] Typing 3 or more letters into the case memo field appears to cause a refresh related delay.             Workaround: Type memo text into Notepad and paste it to avoid the refresh ORif possible reduce case query row results.                       Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT116857 === END OF ISSUE === Title: PO09632: FATAL ERROR WHEN RUNNING CASE SELECTION WITH CASE SELECTION CONDITIONS Description: [SP 6.1, SP 6.2, SP 6.2.1] When the default HTTP header is used or SSO is enabled, then a font loading error appears and the font is substituted on the new UI. (Refused to load the font '' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'font-src' was not explicitly set, so 'default-src' is used as a fallback.) Workaround: Reset the user preferences and only select the mandator that    contains the attribute in case select conditions or one of its  sub mandators.                                                   Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT116437 === END OF ISSUE === Title: PO09650: EDITING RULE CONDITION EXPRESSION LIST AND SAVING WITH CTRL+S CAN CAUSE WRONG VALUE TO SAVE. Description: [SP 6.1, SP 6.2, SP 6.3] If the user saves the form with CTRL+S right after editing the value in expression list without pressing enter, the value will be wrong after saving it. The value will show the [attribute name] in square brackets.         Workaround: Save using the UI button, or press [enter] before saving.        Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.07;6.4.2.06;6.5.0.04;6.6.0.02 Known Issue ID: DT115712 === END OF ISSUE === Title: PO09630: EXPRESSION ELEMENT FOR "IS TRUE" AND "IS FALSE" OPERATORS IS VISIBLE IN CONCLUSION Description: The user interface unnecessarily displays 'is true / false' in the expression field for conclusion operators. Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT115303 === END OF ISSUE === Title: PO09628: DELETING MANDATOR WITH CASES MAY LEAD TO FATAL ERROR Description: A \"px != 0\" fatal error may occur after a mandator is deleted, if there are still cases in this mandator and some of these    cases are still in a working queue that a user currently        requests cases from. In older versions this may also lead to a  crash. It only produces a fatal error starting from 5.7.0.13,   6.0.0.10, 6.1.0.08, 6.2.1.03, 6.3.0.00.                          Workaround: None                                                             Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT115276 === END OF ISSUE === Title: PO09620: ATTRIBUTE CAN BE REMOVED ALTHOUGH IT IS STILL USED BY A SUBMANDATOR REVISION THAT IS WAITING FOR GOLIVE CONFIRMATION Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Attribute can be       deleted although it is still referenced by a submandator        revision that is waiting for golive confirmation. After the     golive of this attribute deletion, the revision that is still   using this attribute is unloaded from memory and Safer Payments reports below error logs:                                         E 0063 Cannot find referenced attribute (uid=) in condition ofrevision '' (uid=)                   E 0321 Revision  configuration error:           ATTRIBUTE_REFERENCE_IN_CONDITION_NOT_FOUND                       Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT115181 === END OF ISSUE === Title: PO09639: Degradation in query/simulation performance as number of mandators grow Description: For systems with many mandators, improved performance of queries and simulations if either all mandators are selected or if a few are selected that contain a small subset of the overall transactions. Workaround: To improve the performance for analysis and simulation queries, always enable the "adopt simulation data selection" option. To  improve the performance of simulation, add the mandator         conditions of the selected mandators to the simulation data     selection.                                                       Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT115114 === END OF ISSUE === Title: PO09638: CHANGING CASE CLASS IN CASE SELECTION DOES NOT REFRESH THE CONDITIONS ATTRIBUTES Description: [ SP 6.1, SP 6.2, SP 6.3 ] Changing case class selection does   not refresh the case selection conditions attributes             Workaround:  Press F5 or visit another page and come back                    Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT115082 === END OF ISSUE === Title: PO09608: THE CSV FILE FROM EXPORTING THE COMMON POINT QUERY RESULT IS EMPTY Description: [SP 6.1, SP 6.2, SP 6.3] In the new User Interface, there is    download button available for downloading common point query    result. However, the csv file from exporting the common point   query result is empty.                                           Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT114656 === END OF ISSUE === Title: PO09606: IT IS POSSIBLE TO GENERATE 2 RULESETS REFERENCING THE SAME RULE UID, WHICH CAN LEAD TO A CRASH DURING REVISION COMPARISON. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] While rule generation  is being stopped it is possible to open second tab and create   rules again, thus generating 2 rulesets that reference the same rule UID. This can later cause a crash during revision          comparison, if one duplicate ruleset (one with higher uid) was  deleted.                                                         Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT114655 === END OF ISSUE === Title: PO09607: MASTERDATA UPDATES WRITE INTO DDC DIRECTLY WHEN DEFERRED WRITING ENABLED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Masterdata updates are written to DDC directly when the deferred writing is enabled.   This may result in additional disk usage and latencies for      masterdata rule actions.                                         Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT114654 === END OF ISSUE === Title: PO09605: STRUCTURAL GOLIVE BLOCKED IF THE INSTANCE IS CONNECTING TO AN OUTGOING CHANNEL WAITING FOR HANDSHAKE Description: SSL handshake blocks the system when it waits for the response from external server. Workaround: Shutdown the connection from the target that the outgoing       channel configuration is sending to.                             Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT114632 === END OF ISSUE === Title: PO09601: INCORRECT MESSAGE WHEN SIMULATION IS INITIALIZING Description: The icon and text of the simulation progress component does not indicate that a simulation started and is undergoing initialization. Now, a distinct icon and text line makes that transition more apparent. Workaround: Wait for the simulation to display a text change to "simulation computing"                                                       Status: Closed Affected Version: 6.2.0 Fixed Available: 6.5.0.00 Known Issue ID: DT114350 === END OF ISSUE === Title: PO09621: CREATING THE CASE MANUALLY FROM THE QUERY RESULTS IN "NO PRIVILEGES" ERROR. Description: [SP 6.1, SP 6.2, SP 6.3] Manual creation of the case from the   query with new UI ends with "No privileges to perform this      action" error. This is because SP unnecessarily checks for "EditCPP" privilege.                                                  Workaround: Add "Edit CPP" privilege to be able to manually create a case.   Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT114105 === END OF ISSUE === Title: PO09444: CASES FROM DIFFERENT INDEX BASED EVALUATION CLASSES CANNOT BE CONSOLIDATED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Safer Payments should  allow cases from different index base evaluation classes be     consolidated. This is currently not allowed.                     Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT114064 === END OF ISSUE === Title: PO09594: TRANSACTION RECORDS ARE STORED TO DISK WHILE DEFERRED WRITING IS INTERRUPTED Description: Deferred writing is needlessly interrupted when mandators, messages, working queues, key performance indicators, status alarm indicators, charts, case classes, case close codes, case workflows, case states, case user groups, notifications, external queries, or reminders are saved. Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT114062 === END OF ISSUE === Title: PO09584: REMOTE INSTANCE MAY CRASH WHEN RUNNING CURTAIL MASTERDATA JOB Description: [SP 6.1, SP 6.2, SP 6.3] There is a low likelihood that remote  instances may crash when curtailing masterdata.                  Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT114046 === END OF ISSUE === Title: PO09615: INCORRECT TEXT DISPLAYED IN THE INVESTIGATOR REPORT WHEN NO USER OR CASE CLASS OPTIONS AVAILABLE. Description: On Report>Report>Investigator> [report], some fields are missing text translations. Workaround:                                                                  Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.00 Known Issue ID: DT114043 === END OF ISSUE === Title: PO09577: THE ONLINE HELP MANUAL DOES NOT WORK IF THE USER LANGUAGE IS SET TO FRENCH OR PORTUGUESE. Description: [SP 6.3] It is not possible to generate online help manual while French or Portuguese language is set as current interface      language.                                                        Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT114036 === END OF ISSUE === Title: PO09578: INCREASING THE INDEX SIZE FOR SLOW FULL/NEAR FULL INDEXES DOES NOT IMMEDIATELY INCREASE ITS PERFORMANCE. Description: Enhanced the index performance after index size is increased. Fixed a potential buffer overflow after index size is decreased. Workaround: When an index is full/almost full and it is required to quickly resolve that, enable "purging" if not enabled, enable "Record   purged entries", increase the capacity and restart.              Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT114026 === END OF ISSUE === Title: PO09610: INSTANCE COULD POTENTIALLY CRASH IN RARE CASES FROM FLI CONNECTION INACTIVITY. Description:  [SP 6.1, SP 6.2, SP 6.3] In rare cases the instance could crashwhen FLI connections are being closed due to inactivity.        Frequent inactivity timeout connection closing by SP could be a byproduct of communication interruptions for the node.           Workaround: Increase FLI timeout settings to try to reduce chance of        timeout, and review node/network health.                         Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT113939 === END OF ISSUE === Title: PO09613: SIMULATION: INSTANCE IS NOT ENABLED FOR SIMULATION MESSAGE WHEN THE MANDATOR DOES NOT HAVE SIMULATION MEMORY. Description: [SP 6.3] Running a simulation with low available memory would   show an misdirecting error message suggesting that simulation   wasn't available "selected instance is not enabled for          simulations", rather than one indicating that there was         insufficient memory assigned.                                    Workaround: Ensure that the user and mandator on which the simulation is    tried to be run has sufficient memory assigned.                  Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT113789 === END OF ISSUE === Title: PO09611: SIMULATION MDC OF OUTPUTS/OVERWRITABLE INPUTS IS NOT RESET CORRECTLY AFTER A GOLIVE ON A HIGHER MANDATOR AND MAY LEAD TO UNDEFIN Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Safer Payments reuses  memory allocated from previous simulations. Depending on the    simulation settings, the simulation memory might need to be     reset when changes are made, e.g. when the data selection is    changed. This currently does not work correctly when the        simulation uses an output attribute from a higher mandator. Whena golive is performed on the higher mandator, the memory for    that attribute is not currently reset correctly.                 Workaround: Run simulations on a newly created challenger (copy of the      current challenger) after a golive was performed on a higher    mandator                                                         Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT113746 === END OF ISSUE === Title: PO09548: MANDATOR MEMORY LIMIT IS CALCULATED WITH SIMULATIONS WHICH ARE NOT CURRENTLY RUNNING. Description: Mandator memory limit is calculated with revisions that are not running. Workaround: User A should actually run the simulation, then end it, to free up the mandator simulation memory for User B.                    Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT113469 === END OF ISSUE === Title: PO09582: THE CFG.ZIP IS SAVED AS CFG%2EZIP IN SOME OLD WEB BROWSER VERSIONS Description: [SP 6.1.0.09, SP 6.2.1.04, SP 6.3.0.01] There is a change in the mentioned patch releases about correcting the download of files that contain non ASCII characters on the filename. With this   change, the cfg.zip created from Download IBM Safer Payments    configuration is saved as cfg%2Ezip when using some old Chrome  and Firefox versions.                                            Workaround: Use the latest Chrome or Firefox version.                        Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT113445 === END OF ISSUE === Title: PO09579: The dimension or currency symbol is missing in Alerted Transactions table in case view Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] In the new user interface, the dimension or currency symbol is missing in Alerted Transactions table in case view.                                              Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT113443 === END OF ISSUE === Title: PO09552: INSTANCE RUNNING A REMOTE SIMULATION MAY CRASH IF THE REVISION THAT RUNS THIS SIMULATION IS CHANGED Description: In rare situations, a crash might occur on a remote instance if a model element is saved while a simulation is running on the remote instance. Workaround: Do not make any change in the model revision which has a        simulation currently running on the remote instance.             Status: Closed Affected Version: 6.3.0 Fixed Available: 6.5.0.00 Known Issue ID: DT113420 === END OF ISSUE === Title: PO09576: BYPASS CRASHES WHEN HANDLING MESSAGE WITHOUT MESSAGE ID DURING GOLIVE Description: When bypass is activated during a golive and handles messages   without message ID, there is a chance that the instance crashes when it should only return an error code as response.            Workaround: None                                                             Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT113297 === END OF ISSUE === Title: PO09575: DASHBOARD SAI DOES NOT DISPLAY ITS TITLE WHEN TOOLTIP IS NOT AVAILABLE Description: Status alarm indicators do not display a title if a tooltip is unavailable. Workaround: Set SAI's "Display tooltip" property to non empty value.         Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.06, 6.4.2.05, 6.5.0.03, 6.6.0.01, 6.7.0.00 Known Issue ID: DT113111 === END OF ISSUE === Title: PO09599: DATA SELECTION FOR QUERIES REVERTS BACK IF ACTIONS ARE TAKEN TOO FAST. Description: [SP 6.1, SP 6.2, SP 6.3] "Server time absolute" changes to      "records absolute" when navigating back from a query and coming back to edit queries, if done too quickly.                       Workaround: Manually adjust query back to  "Server time absolute".           Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT113017 === END OF ISSUE === Title: PO09598: QUERY COLUMN ORDER CHANGES ARE NOT REFLECTED. Description: [SP 6.1, SP 6.2, SP 6.3] Query column order changes are not     reflected once a new order is created.                           Workaround:  Reset the table preferences.                                    Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT113016 === END OF ISSUE === Title: PO09597: CASE INVESTIGATION MEMO SECTION COULD OVERLAP OVER TRANSITION SECTION. Description: [SP 6.3] The memo section could overlap over the transition     section for investigation cases on some lower resolutions, or ifthe browser window is not maximized.                             Workaround: Use 1680x1050 or 1920x1080 or higher resolutions, and keep the  browser window maximized.                                        Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT113000 === END OF ISSUE === Title: PO09596: INCORRECT VALUES EXPORTED TO CSV EXPORTS FROM UI TABLES Description: [SP 6.1, SP 6.2, SP 6.3] Some values are not exported exactly as they are seen in UI Workaround:                                                                  Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01, 6.6.0.00 Known Issue ID: DT112859 === END OF ISSUE === Title: PO08160: FLI FOLDER CANNOT BE CHANGED Description: Changing the FLI folder in the cluster settings isn't possible. The fli folder is always used relative to the root path.        This is due to the initialization order. The                    FastlinkInterface::setValues function sets the FLI paths, and itis called before Iris::readDirectoryString is executed. By this,the fliBuffer filehandle is not changed.                         Workaround: N/A                                                              Status: Open Affected Version: 5.4.0 Fixed Available: No fixed available Known Issue ID: DT112853 === END OF ISSUE === Title: PO09558: INSTANCE UNREACHABLE MESSAGE SHOWN FOR SYSTEM OR AUDIT LOGS ON UI IF NO USER SELECTED Description: In a multiple instance cluster when looking at Cluster > Logs,  when no users are selected in filters, a misleading warning is  displayed "At least one IBM Safer Payments instance was         unreachable".                                                    Workaround: Select at least one user from the drop-down, such as the [IBM   Safer Payments] placeholder for non-user logs.                   Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT112816 === END OF ISSUE === Title: PO09589: SAVING A SIMULATION QUERY STOPS A RUNNING REMOTE SIMULATION. Description: [SP 6.2, SP 6.3] Saving a simulation query of the same revision,will cause the Simulation to be stopped, if the simulation is   performed in a different node than the API. This includes       executing query via the "play" button as it does a save and     execute.                                                         Workaround: Run the simulation on the API instance or, as a workaround whileusing a remote instance, you should execute the query with the  context action on the table.                                     Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT112680 === END OF ISSUE === Title: PO09191: "REFUSED TO LOAD THE FONT" MESSAGE APPEARS IN WEB BROWSER CONSOLE ON NEW UI. Description: [SP 6.1, SP 6.2, SP 6.2.1] When the default HTTP header is used or SSO is enabled, then a font loading error appears and the font is substituted on the new UI. (Refused to load the font '' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'font-src' was not explicitly set, so 'default-src' is used as a fallback.) Workaround: Ignore the message and a substitute font will be used,          otherwise set a custom header. Note that disabling the default  headers will disable caching of the UI resources, which will    result in slower load times when Safer Payments is loaded.      Administration > System > Configuration > HTTP Requests > Use   default HTTP Headers ("Use Custom HTTP header" is actually what it means). Set Custom header to include:                        font-src 'self'                                                 'unsafe-inline';                                                 Status: Closed Affected Version: 6.1.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT112653 === END OF ISSUE === Title: PO09538: INVESTIGATOR CANNOT AGGREGATE AUDIT TRAILS FOR REPORTING ATTRIBUTES AFTER CASE IS CLOSED Description: [SP 6.2, SP 6.3] For closed cases the user is unable to list all reporting attributes and select them to aggregate the audit    trail. The reporting attributes are read only and keep the state from before the case was closed.                                Workaround: n/a                                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT112600 === END OF ISSUE === Title: PO09545: PIE CHARTS IN REPORT TAB INCLUDES WRONG DATA Description: [SP 6.1, SP 6.2, SP 6.3] Pie charts in the Report tab include   one slice which has incorrect data                               Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT112174 === END OF ISSUE === Title: PO09542: BDI instance may crash if changing curtail masterdata option of a job that is currently running Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] BDI instance may crash if changing curtail masterdata option of a job that is currently running after a golive. For example, this issue may happen in  below scenario:                                                 Step 1. Successfully run of the job with curtail masterdata.    Step 2. Disable curtail master data after the job has finished. Step 3. Perform a golive.                                       Step 4. After the golive, run the job with curtail masterdata   disabled.                                                       Step 5. While the job is running, enable curtail masterdata thensave.                                                            Workaround: Do not change the job's curtail masterdata setting while it is  running.                                                         Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT112008 === END OF ISSUE === Title: PO09569: SAVING ANALYSIS WITH CONDITION ON ENCRYPTED ATTRIBUTE LEADS TO ENCRYPTED TEXT IN VALUE FIELD. Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Creating an Analysis   and setting a condition on an encrypted attribute (such as PAN) will result in the condition value appearing as garbled text    (encrypted) after save.                                          Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.08;6.4.2.07;6.5.0.05;6.6.0.03 Known Issue ID: DT111734 === END OF ISSUE === Title: PO09570: CERTAIN OPERATIONS CAN APPEAR TO HANG ON UI WHEN INTERLOCK IS BLOCKING. Description: [SP 6.2, SP 6.3] The interlock (cluster-wide guard) setting of minimum active instances can block certain operations that require maintenance mode (such as go-live or end-of-day job) if that threshold is met. However, there is no indication to the end-user on the UI that SP is waiting for the guard condition to be lifted to proceed. Workaround: Wait for the minimum active instances to be available and       operation will proceed, or reduce value as needed.               Status: Closed Affected Version: 6.3.0 Fixed Available: 6.3.1.02, 6.4.2.01, 6.5.0.00 Known Issue ID: DT111725 === END OF ISSUE === Title: PO09212: NOT ALL ATTRIBUTES ARE AVAILABLE FOR SELECTION IN GROUP BY QUERY CONDITIONS IN THE NEW UI Description: Now, group by queries can use all valid attributes in conditions. Workaround: If you are on SP 6.1 then perform the change in the old UI to   select the necessary attributes. If you are on SP 6.2 then      please contact support.                                          Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT111699 === END OF ISSUE === Title: PO09568: COLUMNS SHIFT AND APPEAR MIXED WHEN ATTRIBUTE HAS A CATEGORY BUT DATA IS UNAVAILABLE. Description: [SP 6.3] When an attribute is displayed in a query result, and  its data its not available, and it has categories enabled, the  columns will be shifted on the UI.                               Workaround: As a workaround you can export the query results table to CSV   using the download button.                                       Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT111674 === END OF ISSUE === Title: PO09525: SIMULATION QUERY IS NOT INVALIDATED IF THERE IS A CHANGE OF THE ATTRIBUTE AFTER A SIMULATION Description: Saving attributes with computation impact does not invalidate an active simulation, which results in potential access to invalid data. Now, when revision elements are saved, a warning is displayed if a simulation is active. Workaround: Re-run the simulation and run the simulation query again after  changing an attribute during an active simulation.               Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT111669 === END OF ISSUE === Title: PO09530: OUT OF MEMORY ERROR WHEN RUNNING QUERIES IN THE NEW USER INTERFACE Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] When running queries in the new User Interface, especially if the query has a large number of  query results fetched from the server, the web browser may      report out of memory error and the user cannot view the query   results.                                                         Workaround: Reduce the number of query results returned by the query, or the number of columns in the query. For queries where the size     cannot be reduced, use batch job in Export data type to export  the query result.                                                Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT111040 === END OF ISSUE === Title: PO09536: UI CRASHES IF INCONSISTENT NUMBER OF INSTANCES DEFINED IN CLUSTER.IRIS FILES Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] The new User Interface may     crash with unexpected error reported, if the file               cfg/cluster.iris from different instance in the Cluster contains different number of instances defined.                          Workaround: Make sure that the cluster.iris from all instances in the       Cluster have the same instances definition.                      Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT111030 === END OF ISSUE === Title: PO09540: DATE FIELD MODIFIED BY A BADLY FORMATTED TIME Description: When modifying a date time field, and entering a wrongly        formatted time value (such as a value over 24 hours, like 1000) this changes the date to a new date in the future, as the number of hours are added to the date.                                 Workaround: n/a                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT110916 === END OF ISSUE === Title: PO09533: Counters are not working for negative amounts. Description: When using negative amounts, counters will not work for most computation options. This is caused by initializations of the local attributes to 0, which will for example lead to a maximum amount of 0 for negative amounts.                                                         Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT110763 === END OF ISSUE === Title: PO09580: CHARACTERS "+/(" ARE NOT ALLOWED IN RULE CONDITIONS USING A TEXT ATTRIBUTE Description: [SP 6.3] Any string containing "+/(" in a rule condition will   throw an error and can not be saved.                             Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT110701 === END OF ISSUE === Title: PO09553: DEACTIVATING MCI WITH BYPASS RUNNING CAN CAUSE CRASHES. Description: [SP 6.2, SP 6.3] Disabling MCI can cause a crash of the         instance, if bypass is currently active on that instance. On    versions prior to 6.2.1.04/6.3.0.01 any cluster page save       unrelated to the MCI deactivates MCI briefly, which increases   likelihood of crash occurring.                                   Workaround: Upgrade to 6.2.1.04/6.3.0.01 to avoid deactivation of MCI duringcluster changes (ie. API change). However, manual MCI related   changes can still cause the crashes. An alternative would be to disable bypass all-together.                                     Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT110698 === END OF ISSUE === Title: PO09551: KPI DOES NOT RETURN THE MESSAGE RATE DATA ON THE INSTANCE THAT HAS BOTH MCI AND BDI INTERFACES DISABLED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] KPI does not return themessage rate data on the instance that has both MCI and BDI     interfaces disabled, even if another incoming data interface is enabled on that instance, e.g. MQ.                               Workaround:                                                                  Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT110689 === END OF ISSUE === Title: PO09531: FATAL ERROR WHEN SENDING OCC MESSAGE VIA A DELETED INSTANCE Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] When an instance has   been deleted and it is selected to deliver an OCC, the other    instance that tries to deliver the OCC message via this deleted instance might create fatal errors. In versions that still      suffer from APAR PO09327 the instance may actually crash        instead.                                                         Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT110347 === END OF ISSUE === Title: PO09504: UNEXPECTED ERROR FOR FAILED REQUESTS WHEN RESPONSE IS NOT JSON Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] SP UI attempts to parse HTML as JSON and fails for example when a Proxy/CDN returns a  non JSON response which gives the "Unexpected token < in JSON at position 0" message on new UI. On the old UI you could get     blank pages and unexpected error messages.                       Workaround: If possible, configure the proxy to send JSON messages as-is    instead of the HTML response. Responses generated by SP can     always be parsed correctly, the error only occurs for additional layers sending their own (error) response.                      Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT110309 === END OF ISSUE === Title: PO09543: QUERY STATUS SHOWS COMPLETE ALTHOUGH QUERY RESULTS TABLE STILL LOADING RESULTS. Description: [SP 6.1, SP 6.2, SP 6.3] Larger query results (ie. 50K records) show the "Computation of query results are finished" message    before the UI finishes loading all the rows on new UI.           Workaround: Wait a bit longer for browser to finish loading query results   for larger queries.                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT110304 === END OF ISSUE === Title: PO09526: INTERNAL RANDOME FOREST MODEL CANNOT BE VIEWED IF IT HAS TEXT VALUE THAT CONTAINS " CHARACTER Description: [SP 6.1, SP 6.2, SP 6.3] If an internal random forest model     contains " in string value, it cannot be parsed by Safer        Payments. This issue is preventing Safer Payments from loading  all internal random forest models from the same model revision  during startup and prevents the internal model from being viewed after it has been saved. This may occur whenever an attribute  containing a " is included in the model generation data.         Workaround: N/A                                                              Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT110250 === END OF ISSUE === Title: PO09537: BYPASS SETTING LABEL IS INCORRECT FOR CERTIFICATE PRIVATE KEY FILE. Description:  [SP 6.3] In Cluster Settings for MCI under Bypass settings the first 'Private client key password file' instead should instead read 'Certificate private key file'.                             Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT110195 === END OF ISSUE === Title: PO09524: OCCM RELAY DOES NOT PROPERLY CHECK THE AVAILABILITY OF THE INSTANCES Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] When an instance fails to deliver an OCC message and if this message's outgoing channel configuration has relay enabled, Safer Payment will delete the OCC message file on this instance and forward it to another     randomly picked instance in the Cluster to deliver. When Safer  Payments picks the next instance, it doesn't check if the       instance is shutdown or starting up.                            If the picked instance is shutdown or starting up, the OCC      message will be queued in the FLI buffer waiting for this       instance's AMI to activate after startup. This can cause some   delay of sending the OCC message.                                Workaround: N/A                                                              Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT110084 === END OF ISSUE === Title: PO09523: BETTER HANDLING OF WRONG PATHS FOR AES KEY PATH Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Currently, if in       encrypted jobs the value for AES key path is set to a directory, this will print a generic error message "file loading error".  It should be explicitly mentioned in the help/tooltip that a    file needs to be provided here and the validation should already prevent it from being saved otherwise. If it fails it should   ideally not fail with such generic error message.                Workaround: N/A                                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT110047 === END OF ISSUE === Title: PO09522: MESSAGES FAIL TO PARSE WHEN HTTP AND TCP MESSAGES ARE MIXED ON THE SAME CONNECTION Description: [SP 6.2, SP 6.3] If you have HTTP messages and TCP messages sent over the same connection then it is possible that the messages will be incorrectly processed by Safer Payments, resulting in   parsing errors for valid messages.                               Workaround: Create different MCI endpoints for the different message types, one for the TCP messages and one for the HTTP messages, and only send the same message type over a single endpoint.              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109946 === END OF ISSUE === Title: PO09408: MESSAGES WITH IP HEADER CANNOT BE FORWARDED VIA BYPASS Description: [SP 5.7, SP 6.1, SP 6.2, SP 6.3] This affects format FCD, nested XML and JSON. The messages will not be processed on the        instance that receives them via bypass.                          Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT109933 === END OF ISSUE === Title: PO09520: NEW CONCLUSION TOOLTIP STATES "NEW CONDITION" INSTEAD OF "NEW CONCLUSION" Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] For new UI, when cursor is over "+" button to add new conclusion on the rule page, tooltip     states "New condition" instead of "New conclusion"               Workaround: N/A                                                              Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109845 === END OF ISSUE === Title: PO09515: POSSIBLE CRASH AFTER CREATING CASE MANUALLY Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] When the user creates a case manually from query or from normal manual case creation,  there is a small chance that the application crashes afterwards. This is a rare timing issue between the background thread that consolidates alarms from rules and the manual case creation.     Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109821 === END OF ISSUE === Title: PO09514: USER NOT IN THE USER GROUP OF A TRANSACTION IS ABLE TO EXECUTE THIS TRANSITION Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] If a user has          Investigation supervisor privilege, or is assigned to the       working queue, this user is able to transit the case in this    working queue even though this user is not enabled in the user  group assigned to the case transition.                           Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109739 === END OF ISSUE === Title: PO09519: INSTANCE NAME IS NOT FULLY VISIBLE WHILE SELECTING THE INSTANCE TO DOWNLOAD CONFIGURATION Description: [SP 6.1, SP 6.2, SP 6.3] While downloading configuration of     instances, the instance name is not fully visible in the        instance selection drop-down list.                               Workaround: Hover over the name in the drop-down list to display the        complete instance name in the tooltip.                           Status: Open Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT109718 === END OF ISSUE === Title: PO09518: CHANGING WORKFLOW UNDER CASE CLASSES CAUSES SAVE ICON TO FLASH THEN DISAPPEAR Description: [SP 6.3] In Administration under Case classes when selecting on a class and changing the workflow to another workflow with      different states/transitions the [Cancel][Save] buttons appear  for a second (flash) then disappear.                             Workaround: Click on name or comment field and press space-bar then         backspace and press save.                                        Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109711 === END OF ISSUE === Title: PO09508: ONLINE HELP MISSING FOR ENABLEXFORWARDEDFORCHECK AND ENABLEIPSESSIONCHECK. Description: [SP 6.3] The online help is missing for these two new           configuration options. However, tool-tips already exist to      explain the settings under Administration > System >            Configuration > User > Authentication Settings > Mouse over eachto read.                                                         Workaround: Draft of potential Online Help text in a future release:                                                                        EnableXForwardedForCheck:                                       Use HTTP Header X-Forwarded-For for session binding. (Default:  True)                                                           If the value of the XFF changes, the session will be terminated.Most application servers can leverage the XFF header with the   source IP address for logging or blacklisting. For some clients,the X-Forwarded-For may be changed between requests by a proxy  server preventing them from using Safer Payments. This feature  will allow a server admin to disable the X-Forwarded-For check  for sessions for that scenario.                                                                                                 EnableIpSessionCheck:                                           Use IP address for session binding. (Default: True)             If the IP address of an authenticated user changes, the session will be terminated. By default, the IP will be checked for each request to ensure that the caller is who they say they are. For some clients, their IP is changed between requests, preventing  them from using Safer Payments. This feature will allow a serveradmin to disable the IP check for sessions for that scenario.    Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109680 === END OF ISSUE === Title: PO09492: Conditions expressions context menu is not opened near the expression field Description: [SP 6.1, SP 6.2, SP 6.3] In conditions, if the user focuses on  an expression field and presses space bar to see the context    menu, it would not appear near the expression field but with an offset.                                                          Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109509 === END OF ISSUE === Title: PO09509: ERROR OF "NO PRIVILEGES TO PERFORM THIS ACTION" WHEN ACCESSING CLOSED CASES IN WORKING QUEUE Description: [SP 6.3] With the setting "Show closed cases" enabled in a      working queue, the user of this working queue can see closed    cases in it. However, the user will get an error of "No         privileges to perform this action." when try to access/transit  the closed cases in working queue.                               Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109500 === END OF ISSUE === Title: PO09502: CPP CANNOT BE CREATED FOR LOWER MANDATOR USERS Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] In the new User Interface, the Save button is disable when creating a new CPP, if the user is  not defined in top mandator and does not have the privilege of  "Compliance List -> Ad hoc check".                               Workaround: For SP 6.0 and 6.1, use the old User Interface. There is no     workaround for SP 6.2 and 6.3.                                   Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT109458 === END OF ISSUE === Title: PO09493: WORK CASE FUNCTION PICK UP CLOSED CASES FROM USER'S WORKING QUEUE Description: [SP 6.3] If a user's investigation case working queue has closed cases, such closed cases will be picked up as cases to work on in Work case.                                                    Workaround: Disable the setting "Show closed cases" in working queue        definition.                                                      Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109447 === END OF ISSUE === Title: PO09517: TOOLBAR ICONS CAN OVERLAP WHEN SCROLLING ON THE USER INTERFACE. Description: [SP 6.3] Primary header icons can overlap with secondary icons  on toolbars when scrolling down on tables, query details, or    attribute properties throughout the UI.                          Workaround: Scroll back up to unstack the toolbars to select the option     desired.                                                         Status: Open Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT109429 === END OF ISSUE === Title: PO09516: COUNTER SIMULATION GETS THE PAST AMOUNT VALUES FROM MDC/DDC INSTEAD OF CHECKING/USING SIMULATION MDC FIRST Description: [SP 5.7*]                                                       Counter simulation gets the amount value from MDC/DDC instead ofchecking/using simulation MDC first.                             Workaround:                                                                  Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT109396 === END OF ISSUE === Title: PO09454: RECREATE INDEX JOB MAY DUPLICATE ENTRIES WHEN DEFERRED WRITING IS ENABLED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] When the recreate index job is executed and deferred writing is enabled, duplicate     entries may occur in the index. To check whether you are        affected go to index internals on system internals and verify   that "filled" and "distinct" have the same amount of entries.    Workaround: Reload the interval index job. The issue only occurs            sporadically and depends on timing so you may be able to load it successfully after some retries. Check index internals to see  if it was successfully done without duplicates.                  Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT109177 === END OF ISSUE === Title: PO09439: UNABLE TO UPLOAD MORE DEFINED RISK LIST FILE IF THE PREVIOUS RISK LIST FILE UPLOAD FAILED Description: [SP 6.1, SP 6.2, SP 6.3] If the previous risk list file upload failed, for example due to unsupported file encoding, the user is unable to upload any risk list file. When uploading another risk list file, Safer Payments reports a message of "upload in progress, please wait". Workaround: Restart the instance in order to be able to upload to the risk  list again. Make sure to use supported file encodings like UTF-8 or ANSI going forward.                                          Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT109174 === END OF ISSUE === Title: PO09512: THE OPTION OF ALLOWING DDC ACCESS IN THE REPORT IS NOT AVAILABLE Description: The reports do not have the option of accessing the DDC, a      checkbox needs to be added to optionally allow reports to accessthe DDC. In addition, this should be mentioned in the online    help                                                             Workaround:                                                                  Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT109105 === END OF ISSUE === Title: PO09485: TRANSITIONING CASE FROM "MY WORKING QUEUE" TO WORK QUEUE THAT USER HAS NO VIEW PRIVILEGE, EMITS AN ERROR PAGE. Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] While using new UI,            transitioning case from "My working queue" to work queue that   user has no view privilege, emits error page instead of         returning back to "My working queue" page.                       Workaround: Use old UI if possible.                                          Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT109071 === END OF ISSUE === Title: PO09484: NUMBERS ARE NOT ACCEPTED FOR REALTIME INTERCEPT CODES IN CONDITIONS Description: Realtime interception code for the conditions field shows an invalid verdict even with the valid code. Workaround: Using a range instead of just a number (e.g. 3~3 instead of just3) works for the "equal to" operator, but this does not work for"greater than" / "less than" like operators.                     Status: Closed Affected Version: 6.1.0 Fixed Available: 6.5.0.00 Known Issue ID: DT109041 === END OF ISSUE === Title: PO08739: PARALLEL CASE TABLE REQUESTS OF THE SAME USER MAY CAUSE CRASH Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP 6.1] When the cases table is requested in parallel for the  same user, for example by using scripts that run at the same    time for the same user or using several browser tabs, a crash   may occur in very rare cases. The affected requests that should not be sent in parallel are getCasesTable, SetUserExportPassword and IsCasesTableEncrypted.                                      Workaround: Avoid the same user sending the requests getCasesTable,         SetUserExportPassword and IsCasesTableEncrypted in parallel.     Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT108841 === END OF ISSUE === Title: PO09482: POSSIBLE SHORT FREEZE WITH BACKTRACE WHEN ACCESSING THE NEW REVISION STILL BEING CREATED Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] When copying a         revision, the revision is added to the mandator list and visibleto the user to use even before create references is called on   it. Performing operations on any revision of any mandator that  accesses this not completely created revision may lead to a     short freeze of the instance and generate a backtrace, e.g., getattribute references.                                            Workaround: Wait until the copy of the revision is complete and response is received. The user and timestamp fields of "Currently being     edited" in the revision table would indicate the readiness of   the revision.                                                    Status: Open Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT108667 === END OF ISSUE === Title: PO09478: THE "EXTRACT EXPRESSIONS TO COPY" BUTTON IS DISABLED IN CHAMPION REVISIONS Description: [SP 6.0, SP 6.1, SP 6.2, SP 6.3] In the new User Interface, the "Extract expressions to copy" button is disabled in Champion    revisions even though the user is enabled for "Copy view for    expressions".                                                    Workaround: Create a challenger revision by copying the champion revision   and copy the expression from this challenger revision.           Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT108541 === END OF ISSUE === Title: PO09466: SAFER PAYMENTS SHOULD NOT READ SSL FILES DEFINED FOR OTHER INSTANCES IN THE CLUSTER Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, SP 6.3] Safer Payments tries to read the the SSL files defined on all instances in the Cluster and reports "SSL settings error" if the path of the SSL files does not exist on the local instance. Such error can be ignored if all the SSL related files defined for the local instance do exist. Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.05, 6.4.2.04, 6.5.0.02, 6.6.0.00 Known Issue ID: DT108210 === END OF ISSUE === Title: PO09472: UNABLE TO SAVE 'CONDITIONS' AS AN INPUT TO AN EXTERNAL MODEL Description: [SP 6.3] It was not possible to save external model components  that included conditions.                                        Workaround: N/A                                                              Status: Closed Affected Version: 6.3.0 Fixed Available: No fixed available Known Issue ID: DT108180 === END OF ISSUE === Title: PO09495: GOLIVE CAN FAIL IN AN UPPER MANDATOR IF AN ATTRIBUTE IS CHANGED IN A SUB MANDATOR SIMULTANEOUSLY Description: Description: [SP 5.7, SP 6.0, SP 6.1, SP 6.2, 6.3 ]             When there is a golive in a head mandator where an attribute    data type, name or categories is changed, a crash may occur if  in a sub mandator revision this attribute is referenced in      conditions of a data selection and the conditions are changed atthe same time.                                                   Workaround:                                                                  Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT108171 === END OF ISSUE === Title: PO09494: TEMPORARY CASES MIGHT NOT HAVE A TEMPORARY AUDIT FILE Description: When temporary cases are created then in some scenarios a corresponding temporary audit file are not created. This causes an issue when the EOD archiving job runs and assumes both the temporary case and temporary audit file exist. Workaround: Create dummy temporary audit files so the archiving can         progress. (e.g. create a                                        investigation_audit_temporary_.iris file where corresponds to the uid which is causing an error in the logs)                Status: Closed Affected Version: 6.2.0 Fixed Available: 6.3.1.04, 6.4.2.03, 6.5.0.01 Known Issue ID: DT108168 === END OF ISSUE === Title: PO09475: REPORTING QUERIES COLUMN HEADERS MISSING IN EMAIL SENT VIA REPORT JOB. Description: [SP 6.1, SP 6.2, SP 6.3] When triggering an email from within a report job, the column headers are missing if a reporting query is selected for that job.                                        Workaround: N/A                                                              Status: Closed Affected Version: 6.1.0 Fixed Available: No fixed available Known Issue ID: DT108152 === END OF ISSUE === Title: PO08657: RISK LIST FILTER CANNOT FIND ENTRIES LAST CHANGED BY AN ALREADY DELETED USER Description: [IRIS 5.3.0, IRIS 5.3.1, SP 5.4, SP 5.5, SP 5.6, SP 5.7, SP 6.0, SP6.1] There is no option in Risk list filters to show risk    entries that were last changed by users which were already      deleted in the Cluster.                                          Workaround: Search risk list entries with the option "Show all entries".    Open the risk list entries with "Last changed by" as "User not  available" and save them, in order to change the last changed   user to one that exists.                                         Status: Closed Affected Version: 5.7.0 Fixed Available: No fixed available Known Issue ID: DT108127 === END OF ISSUE === Title: PO09488: QUERY RESULT SORTING FOR MODEL OUTPUT ATTRIBUTES TREAT NUMERIC ATTRIBUTES AS STRINGS. Description: [SP 6.1, SP 6.2, SP 6.3] When sorting a column of an output     attribute (counters, formulas, etc..) in a query, the sorting   function on the numeric attributes would not sort them          numerically but as a string. This can lead to ascending or      descending order being inaccurate.                               Workaround: N/A                                                              Status: Closed Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT108102 === END OF ISSUE === Title: PO09487: SORTING TEXT COLUMNS SEPARATES UPPERCASE LETTERS FROM LOWERCASE LETTERS. Description:  [SP 6.1, SP 6.2, SP 6.3] If your text column starts with       lowercase letters and uppercase letters the results will be     separated into two groups when sorting ascending or descending.  Workaround: N/A                                                              Status: Open Affected Version: 6.2.0 Fixed Available: No fixed available Known Issue ID: DT108101 === END OF ISSUE ===