Update information
IBM® Safer Payments 6.4.1.00 includes changes that might require you to take action.
Read relevant update information
Compare the current operational version to the version that you want to install. Read update information topics that are relevant to your situation.
| If you install a... | Read update information topics for ... | For example, if the version changes from ... | Read update information topics for... |
|---|---|---|---|
| Fix pack | All fix packs between the two versions | 6.4.2.02 to 6.4.2.09 | 6.4.2.03 up to 6.4.2.09 |
| Major release | The target version up to the fix pack that you are installing | 6.3.x to 6.4.2.09 | 6.4.0.00 and 6.4.x up to 6.4.2.09 |
| Major release and skip one major release | The major release for the skipped version and all topics in the target version up to the fix pack that you are installing | 6.2.x to 6.4.2.09 | 6.3.0.00, 6.4.0.00, and 6.4.x up to 6.4.2.09 |
| Major release and skip multiple major releases | The major release for the skipped versions and all topics in the target version up to the fix pack that you are installing | 6.1.x to 6.4.2.09 | 6.2.0.00, 6.3.0.00, 6.4.0.00, and 6.4.x up to 6.4.2.09 |
If needed, see:
6.4.1.00 Update information
- A warning was added when running encrypted import file jobs without AES-CTR, as the previously used AES-CBC had known security issues. It is recommended to switch encrypted import jobs to AES-CTR.
- The remote wait factor was considered redundant with the introduction of interlock. It is recommended to use interlock because it ensures that recreate index jobs are not executed in parallel on multiple instances.
- To use external models, it is required to have the meta attribute
primary uridandurid computation completeas well as the fraud mark index. - The following API requests now enforce to use a POST request. Any potential scripts that use these requests must also use POST: Login, ChangeAuthAddress, InsertPin, ChangePassword, CreateDefinedRiskListImportSettings, GetCaseAction, IsPasswordValid, PathExists, Save, SendCaseActionFromPreview, SetMasterdata, SetQuickSearchCasesTablePreference, SetUserExportPassword.
- To avoid remote code execution in spreadsheet applications, CSV exports are now prepended by a
single quote when text values start with
=, +, -, @,, tab, or return. You can still switch to the old behavior by disabling sanitize CSV exports in . -
Since version 6.0.0.10 IBM Safer Payments has created a backtrace file every time it starts (called backtraces_starting_at_[InstanceID]_[YYYY-MM-DD].iris). This file was previously empty until a crash occurred. The file now has a line stating the version.
If you have automated file management processes which move older log files to a separate directory then you must ensure that the backtrace files are not moved along with the logs. All backtrace files must stay in the logs directory, and if any of them contain more than a single line then they must be shared with IBM support.
-
If the option to Resolve uncached reporting attributes is enabled, it will no longer show values for reporting attributes in the cases table that are not selected in the case class of the respective case. If you want to see additional reporting attributes, enable the respective attributes in the case class. For existing cases, the values for the additional reporting attributes will be loaded from transactional data.
If you are experiencing slow loading times for the cases table, it is recommended that you disable the Resolve uncached reporting attributes and Include DDC to resolve uncached reporting attributes options, if they are not necessary for your use case. For more information, see the online help for more information.
- After a crash occurs, an instance is now automatically invalidated. Use an additional cli parameter
after_crash=startto continue previous behavior. - In case you use channel names with 20 characters, reduce the name to 19 characters to prevent MQ from connection issues for this channel.