If the name and data type of the dataslots in a Business Process and the dataslots in a Web application are identical, default mapping occurs between the processes. If the name or data type differ, default dataslot mapping will not work correctly.
Note: Default dataslot mapping is case-sensitive. For example, dataslots called “Budget” and “budget” are not mapped by default and must be mapped in the workstep Properties.
To map dataslots in a Subprocess workstep:
1. From the drop-down list under Dataslots, select Advanced option, which displays the Set dataslot(s) and Get dataslot columns in the table below that.
The Advanced view enables you to pass dataslot values from the subprocess to an input (Set) dataslot or to an output (Get) dataslot in a parent process.
Note: For Input dataslots added to the subprocess workstep in a Web application, data from the Web subprocess is passed to the parent process only when the corresponding mapped dataslots are added to the End workstep of the Web subprocess.
2. Select a dataslot and click Modify, to launch the Field Properties dialog box. You can enter multiple Set dataslots and one Get dataslot for the Subprocess dataslot.
3. To map a parent process dataslot to one or more inputs in the subprocess, click the ellipsis button beside the Set dataslot(s) box to open the Set Dataslots dialog box.
a. In the text box, enter the name of the dataslot in the parent process that you want to map to the subprocess dataslot and click Add. The parent process dataslot is added to the dataslot list. Use the other command buttons to delete, or move a selected dataslot up or down.
b. Click OK to return to the Field Properties dialog box.
4. In the Field properties dialog box, enter an output dataslot name in the Get dataslot box to map a subprocess dataslot to an output dataslot in a parent process.
5. Click OK.
The dataslots to which you mapped the subprocess dataslots are displayed in the Set dataslot(s) and Get dataslot columns.
Important: There is a list of reserved dataslot names that should not be used as names for a user-defined dataslot in Web applications that communicate with BPM processes for; example, “workitemName”, “performer”, “returnPage”. For more information, see “Reserved Dataslot Names” section of Application Developer’s Guide.
