JR56261: NON DEFAULT VALUES SET TO A SERVICE'S INPUT MAPPINGS ARE DELETED WHEN SERVICE MOVES TO A TOOLKIT
Direct links to fixes
Closed as program error.
After you create a process app and toolkit and, in the process app, create a General System service that has multiple input parameters, each of type String, all but one having null values, and one having no default value, you wire the Start event to the End event. Then you create another General System service that you drag the first General System service into and wire between the Start and End events. You then clear the Use Default option for the second General System service and hardcode strings for all the input mappings of the first General System service, for example "param1", "param2". You save your work and move both General System services into the toolkit you created at the same time by highlighting them in the Implementation menu of the palette, right-clicking one of them, and selecting "Move to other toolkit". You then leave the process app, go to the toolkit you created and into the input mappings, and notice that the values you entered aren't there. The input mappings are blank. PRODUCTS AFFECTED: IBM Business Process Manager (BPM) Advanced IBM BPM Standard IBM BPM Express
There are multiple workarounds: - Copy the items to the target app/toolkit, and then delete them from the source app/toolkit, or - You move the items one at a time, the issue does not occur either.
When performing a multi asset move of services or processes, there is the possibility that data mappings become hidden.
A fix will be included in IBM BPM V8.5.7 cumulative fix 2016.09 that ensures the data mappings are not hidden. To determine whether the cumulative fix is available and download it if it is, complete the following steps on Fix Central: 1. On the Select product tab, select WebSphere as the product group, IBM Business Process Manager with your edition from the WebSphere options, All as the installed version, and All as the platform, and then click Continue. 2. In the Text field, enter "cumulative fix?, and click Continue.
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