Update information
IBM® Safer Payments 6.3.1.01 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.3.0.01 to 6.3.1.09 | 6.3.0.01 and up to 6.3.1.09 |
| Major release | The target version up to the fix pack that you are installing | 6.2.x to 6.3.1.09 | 6.3.0.00 and 6.3.x up to 6.3.1.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.1.x to 6.3.1.09 | 6.2.0.00, 6.3.0.00, and 6.3.x up to 6.3.1.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.0.x to 6.3.1.09 | 6.1.0.00, 6.2.0.00, 6.3.0.00, and 6.3.x up to 6.3.1.09 |
If needed, see:
6.3.1.01 Update information
- To use external models, it is required to have the
Primary URID,Primary instance ID, andURID computation completemeta attributes and the fraud mark index. - Review the definition of remote look up indexes. Ideally, the remote lookup index should provide a value for every transaction. Otherwise, it is possible to see occasional empty values for reporting attributes in case investigation (cases table, case history, case actions, external queries, CPPs) when values are not stored in the case data but need to be read from the transactional data of the case alarm. This does not affect embedded investigation queries.
- The option of record purged entries is automatically enabled if the purged outdated entries is enabled.
- The attribute
system timeof the server response of a message of type JSON now uses the same date format as messages of type XML. This means that the format changed fromyyyy-m-dtoyyyy-mm-dd, so days and months with a single digit now contain a preceding 0. - In past versions, unnecessary attributes were simulated, resulting in additional memory requirements because rules and final rules were automatically added to the simulation if they change the same conclusion attribute as a rule selected for analysis. Now, only selected rules are simulated. If all rules affecting a certain attribute are required (the previous behaviour), make sure to explicitly enable this attribute for simulation in Model>Modelling>Attribute settings.