Figure 1: Drag the Integration Activity in the workflow.

Figure 2: After importing the WSDL into the Integration Activity, you should see this pop-up for the setCall function.

Figure 3: You need to edit the Request Form and add the fields that will feed the setCall input values.

Figure 4: Then you need to map all the form fields into flowdata values.

Figure 5: You must map the flowdata values to the input values for setCall.

Figure 6: You must configure the server parameters, if they were not included in the WSDL.

Figure 7: If you have configured authentication for the web service, you must provide the credentials.

Figure 8: After importing the WSDL, you will see one function call for setCallSoapIn. You must copy this call and modify the copy to act on setCallSoapIn/setCall, to properly format the XML document sent to Heat.

Figure 9: Resulting Integration Service with a copy of the step.

Figure 10: Once you have the provisioning request working, you can invoke it from Policy Builder for any driver.

Figure 11: Properties for the Start Workflow Policy Builder action.

Figure 12: It is also possible to invoke the provisioning request from another provisioning request, which together with the Start Workflow action in Policy Builder, provides easy reusability once you have a working provisioning request configured for setCall.