Designer 10.7 | webMethods BPM Process Development Help | Building and Uploading Processes | About Mapping Services
 
About Mapping Services
Designer generates a type of flow service called a mapping service on its specified logical server (Integration Server Name), using the signature specified in the step inputs and outputs. When you build and upload a process, Designer automatically updates the mapping services of all steps to include the current step signatures, and generates mapping services for all steps that do not yet have them defined. See Configuring Build and Upload Preferences and About Inputs and Outputs.
Important:
You must be connected to the Process Audit Database to update process data mapping services during generation.
Designer names mapping services using the conventions are listed in the following table:
Step Type
Flow Service
Tasks
(except Manual Tasks)
<step label>
Manual Tasks
no wrapper flow service
(OLD STYLE)
webMethods Subprocess (Deprecated)
<step label>_START
<step label>_END
(NEW STYLE)
BPMN Subprocess
PRECALL_<step label>
POSTCALL_<step label>
(OLD STYLE)
webMethods Referenced Process (Deprecated)
PRESUB_<step label>
POSTSUB_<step label>
(NEW STYLE)
BPMN Call Activity
PRECALL_<step label>
POSTCALL_<step label>
Start Events and Catching Events
(except None Events)
<step label>
None Events
no wrapper flow service
Boundary Events (Interrupting and Non-Interrupting)
no wrapper flow service
Throwing Events
no wrapper flow service
End Events
no wrapper flow service
Note:Designer supports non-unique and empty step labels. When creating mapping services for these steps, Designer uses the <step ID> in place of the <step label>.
By default, Designer does not display generated flow services in the Package Navigator view. For more information, see Displaying Generated Flow Services in the Package Navigator View.
Important:Designer does not validate the existence of document fields referenced by a process during generation. If a document is edited to remove a field that is used in a subscription filter or a transition condition, generation will still proceed without error. However, this may cause the process to fail to run (in the case of a subscription filter), or to follow an incorrect path (in the case of a transition condition).
Related Topics