Update information
IBM® Safer Payments 6.5.0.08 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.01 to 6.5.0.09 | 6.5.0.02 to 6.5.0.09 |
| Major release | The target version up to the fix pack that you are installing | 6.4.x to 6.5.0.09 | 6.5.0.00 and 6.5.x up to 6.5.0.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.3.x to 6.5.0.09 | 6.4.0.00, 6.5.0.00, and 6.5.x up to 6.5.0.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.2.x to 6.5.0.09 | 6.3.0.00, 6.4.0.00, 6.5.0.00, and 6.5.x up to 6.5.0.09 |
If needed, see:
6.5.0.08 Update information
- When you upgrade one instance to the new version and other instances are still on the old version, do not delete any IBM Safer Payments elements. Wait until all instances are on the same version.
- On , be aware that Server time zone will be deprecated in the future. A migration path will be offered at that time. If you use it, no action is needed now. If you are setting up a new installation, do not use it. To raise awareness, an informational warning was added to Server time zone.
-
After you upgrade from a version before 6.5.0.00 to 6.5.0.00 or higher, case alarms might aggregate into unexpected case classes. The upgrade converts aggregation attributes in a version before 6.5.0.00 to aggregation conditions in 6.5.0.00 or higher. In versions before 6.5.0.00, cases are aggregated together only if they have the same aggregation attribute and the attribute is not empty.
In all versions from 6.5.0.00 to 6.5.0.07, the conditions that are automatically created by the upgrade do not prevent cases from aggregating together if the attribute is empty.
After the upgrade is finished, review the following information and examine your case classes. Update them as needed.
If you are upgrading from any version from 6.5.0.00 through 6.5.0.07 to version 6.5.0.08 or higher, no changes are automatically done to your conditions. However, it is a best practice to add an
[Attribute] is not emptycondition to your aggregation conditions. This ensures that cases are not aggregated together when they have empty conditions.A second best practice is to add the condition
[CaseClassId] equal to [CaseClassId]This ensures that no other unexpected aggregations occur. It also ensures that only cases from the same case classes are aggregated together.If you are upgrading from a version before 6.5.0.00 to version 6.5.0.08 or higher, the conversion automatically adds the
[Attribute] is not emptyand the[CaseClassId] equal to [CaseClassId]conditions. Be aware that the behaviour in versions before 6.5.0.00 was different. In those versions, it was possible to aggregate cases from different case classes into the same cases.For more information, see Case consolidation: Behavior across versions and impact on upgrade.