Executing Processes (Workflow)

The iWay Application Adapter for Microsoft Dynamics CRM 2011 On-Premises allows you to execute workflows and obtain results. The ExecuteWorkflow operation under the Process node is used for this purpose, as shown in the following image.

The following example shows the command that is used to execute the workflow.

<?xml version="1.0" encoding="UTF-8"?>
<is:workflow.ExecuteWorkflow schemaVersion="1.0" xsi:schemaLocation="urn:iwaysoftware:adapter:MSCRM2011:workflow:ExecuteWorkflow ExecuteWorkflow_request.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:is="urn:iwaysoftware:adapter:MSCRM2011:workflow:ExecuteWorkflow">
	<is:ResponseLevel>WorkflowGuid</is:ResponseLevel>
	<is:EntityList>
		<is:Entity>
		<is:Params>
			<is:EntityId>EEEEEEEE-EEEE-EEEE-EEEE-EEEEEEEEE005</is:EntityId>
			<is:WorkflowId>EEEEEEEE-EEEE-EEEE-EEEE-EEEEEEEEE002</is:WorkflowId>
		</is:Params>
		</is:Entity>
	</is:EntityList>
</is:workflow.ExecuteWorkflow>

The workflow GUID and entity GUID are required and must be specified. Since every workflow in Microsoft Dynamics CRM is associated with some entity, the specific entity must be specified.

The ResponseLevel parameter is an important aspect of a workflow execution request. There are three values that can be specified for this parameter:

• WorkflowGuid. The adapter sends a request to execute a workflow, retrieves the GUID of the asynchronous operation started in the thread of the workflow, and returns that GUID. The adapter does not wait until the workflow is completed. You must run additional requests to retrieve any details of the executed workflow. The GUID is a primary key of the entity Process Log.
• WorkflowLog. The adapter sends a request to execute a workflow, retrieves the GUID of the asynchronous operation, waits for the workflow execution to complete (polling requests and checks for the final workflow step is performed), then sends a request to retrieve the entire workflow execution log and returns the log. You can find all of the steps performed in the thread of the workflow in the log and see the GUIDS of all affected entities. No data from the entities is returned in the log.
• EntityDetails. The adapter sends a request to execute a workflow, waits for the workflow execution to complete, retrieves and analyzes the log, finds all affected entities, and then retrieves their details. This parameter value takes the most amount of time to process.

  Note: If workflow contains any Wait Condition steps, then it is strongly recommended to set the response level to WorkflowGuid. If this is not done, it can take much more time for the Wait condition to become true and the adapter will be hanging and waiting for the Workflow end to collect log or entity details.