Configuring Input Parameters
You must create and/or initialize suitable data fields and map them to the appropriate input parameters.
- All required parameters must be passed to the called operation.
- All data that is passed to the operation must have been initialized earlier in the process. If an uninitialized data field is passed to the operation the service call will fail, causing the process to terminate with an error.
The input parameters required by the lookupUser operation are shown on the right-hand side of the Input to Service tab of the Call lookupUser operation service task. You can find more information about these parameters in two ways:
- See the "lookupUser" section in the EntityResolverService chapter of the BPM Developer’s Guide.
- Open the entityResolverService.wsdl in the bpmRuntimeWsdls project. The source view contains xs:documentation elements that provide descriptions of the operation and its parameters.
The following diagram shows the schema of the input parameters.
For the purposes of this tutorial, you will need to pass the name and get-detail parameters to the call. (get-detail is required because the user’s GUID is part of the detail element in the response message - see Processing Output Data.)
- Creating Required Data Fields
Create a process-level data field called getDetail, of type Boolean. - Initializing Input Data
The userName field will be initialized in the Get user’s name user task. - Configuring Input Mappings
Data fields must be mapped to parameters.
Next topic: Processing Output Data
Previous topic: Configuring the Web Service Call
Copyright © Cloud Software Group, Inc. All rights reserved.