Direct links to fixes
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5 Refresh Pack 7 for the IBM Business Process Manager products
Closed as program error.
After the V18.104.22.168, V22.214.171.124, or V126.96.36.199 fix pack is installed, the default exposed process value (EPV) overwrites the latest updated EPV during snapshot deployment or instance migration. PRODUCTS AFFECTED IBM Business Process Manager (BPM) Advanced IBM BPM Standard IBM BPM Express
How EPVs are migrated changed because the requirement to use the default EPV specified in the snapshot, if one is defined. The concern depends on the application development process. The application might require this new EPV defined in the snapshot, or the application might use only what is defined in the runtime environment instead of the values defined in the snapshot. Either scenario is valid, but IBM BPM can't accommodate both scenarios.
A new configurable property (<epv-deploy-default>) is available for IBM BPM V188.8.131.52, V184.108.40.206, V220.127.116.11, V18.104.22.168, and V22.214.171.124 and is included in the IBM BPM V126.96.36.199 cumulative fixes (CFs) and V188.8.131.52 CFs. The <epv-deploy-default> property toggles between the two behaviors. After the fix is applied, you notice the default behavior reverts to how it was in previous releases where the latest modified EPV is migrated. This means the property is, by default, set to false. When the property is enabled (set to true), the default EPV from the snapshot is used during deployment or instance migration.
Update the EPV variable after deployment or migration.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
30 June 2017