Asynchronous Batch Process Pattern: Part 1

In this and the following two posts, I would like to suggest a solution to a common business problem of executing business logic operation in a scheduled reoccurring manner.
While the current post describes the business problem and a solution concept, the next posts will suggest an actual implementation, based on the Asynchronous Batch Process Pattern described here.

Business Problem

I am often asked by customers about implementing business logic operations in a scheduled reoccurring manner. Here are some of the business requirements I have encountered:

• Check the due date for all open Cases once a day and set ‘Exceeding SLA’ indication if due date has passed
• Send monthly news letter automatically to target customers
• Update MSCRM Users details from Active Directory once a day
• Once a month, disqualify all leads that has no open activities
  

These requirements have some common characteristics: scheduled, repeating, asynchronous activation of a business logic for a selected collection of business records.

Common Solutions

There are some standard solutions in Microsoft Dynamics CRM for such business requirements and the common two are described in the following table:

The Asynchronous Batch Process Pattern

The Asynchronous Batch Process Pattern is based on three basic elements:

1. Schedule: managed by a Scheduling component, able to invoke an Action in a predefined date and time
2. Action: a business logic operation performed of a collection of business records by the Executing component
3. Target business records: A collection of business records defined by a Query Definition

The Action is applied to the target business records on a specified schedule

While this looks like is a simplistic and trivial concept, the pattern defines the weakest coupling possible between the three components. The Scheduling Component is oblivious to the Action it invokes, and the Action delegate is unaware to Target Business Records population it acts upon.

This pattern allows a robust yet flexible solutions to the aforementioned business problem.

Suggested Solution Features

In the following posts, I will describe a possible solution based on the Asynchronous Batch Process Pattern.
I will prefer this solution over the two solution mentioned above if it will support the following main features:

• Supported in Online, IFD and On-Premise deployments
• Can be contained in a MSCRM2011 Solution
• Highly configurable – does not require code compilation
• Does not require Azure/On premise hosting environment