In the previous post I have described a possible implementation of the Asynchronous Batch Process Pattern described here.

In this post, I would like to demonstrate the actual implementation in action, using a simple business requirement.

Business Scenario

To demonstrate the implementation process, the following business requirement will be used:

The Krusty Krab restaurant manages customer service calls using Microsoft Dynamics CRM Online. Each service call is assigned a due date according to the organization SLA.
Squidward Tentacles
, the Customer Service dept. manager, requires that all active Cases SLA will be automatically inspected daily. If the Follow Up By date (SLA due date) occurs today (inspection day), the Case priority is automatically updated to ‘High’, so it is promoted to the beginning of the work queue. He would also like the Customer Service Representative who owns such Case to receive an email notification regarding the impending SLA exception.

Solution Implementation Walkthrough

The following steps demonstrate the solution implementation:

  1. Install the Asynchronous Batch Process Pattern solution

    Import the Asynchronous Batch Process Pattern managed solution available here. Please do not install this solution on your production environment before thoroughly testing it in your test environment.  

  2. Set up an Action Workflow rule for the required business entity          

    Create and activate the Action Workflow rule for the Case entity to execute the required business logic. Make sure the rule is available to run as an on-demand process and with no automatic events. The rule does not include a Wait step, as the Scheduling Workflow rule takes care of that.
    In this case, the Action Workflow rule changes the Case priority to ‘High’ and then send an email notification to the Case owner.
    This sample Workflow rule is included in the Asynchronous Batch Process Pattern solution.

    Action Workflow Definition

  3. Define target business records query

    Open Advanced Find and define a query that will return the business records to which the Action Workflow will be applied. Use the Results button to view the business records that may be affected by the Action Workflow.
    To get the query definition, click the Download FetchXML button and save the file to your file system. Open the saved file in a text editor to copy the FetchXML used in the next step.
    Note that FetchXML query result is limited to 5000 records.
    In my case, I am defining a query that will return all Case records which are in Active state and Follow Up By equals Today

    FetchXML Query definition

  4. Set up a Batch Process record

    Create and save a Batch Process record to define

    • Name – A meaningful name to indicate the batch process purpose

    • Action Workflow – The business logic Workflow rule to be activated on schedule (defined in step 2 above)

    • Activation Frequency – The frequency in which the Action Workflow will be activated. In this case, the batch process is set to run daily.
    • Next Activation – The next date and time the Action Workflow will be activated and operate on the target records. In this case the batch process is set to run on 21:10.

    • Target Records – a FetchXML query defining target business records to which the Action Workflow will be applied (defined in step 3)

    • Status – Set the status to ‘Scheduled’ in order to enable the Batch Process automation


  5. Batch Process in action

    You can see the state of my sample Batch Process record after few days. According to the Batch Process definition, each day at 21:10 the Scheduling Workflow rule runs and changes the Batch Process record status to Active. This triggers the Executing Plugin which query for the target business records using the FetchXML query and apply the Action Workflow rule to the result business records.
    Disregard the sudden date skip on 10/11 which was caused by the Online organization scheduled deactivation by Microsoft.  They were kind enough to reactivate the organization per my request.

    Batch Process In Action

    For each affected Case record, you can view the instances of Action Workflow rules that were applied by the Plugin. The Case priority was changed to ‘High’ and a notification email has been sent to the Case owner

    Case Record Action Workflow


    Case notification email

Implementation Notes


The Asynchronous Batch Process Pattern is useful in many business scenarios. Even when Custom Activities will be available in Online deployments, this pattern has an advantage of low resources consumption when compared to activating Workflow Wait steps in large scales.
While the Asynchronous Batch Process Pattern can be implemented in various ways, the suggested implementation main purposes are Online support and MSCRM2011 Solution containment.

I would like to hear your suggestions and remarks on improving this implementation concept.

Add comment " class="ir icon-in">linkedin twitter email