Asynchronous Workflow processing using the Enterprise Service Bus (ESB)

Sept. 25, 2012 - PRLog -- Many times BPM\Workflow processes just don’t execute from start to end. Most processes execute and then waits for some external event to continue the execution of the process.

We had a client who just implemented text messaging from a workflow. But most importantly the workflow sends a question with answers as a text message to a user and waits for a text message reply from the user. Based on the user’s reply (answer to the question), the workflow continues processing. Once the text message is sent to the user, the step also puts a expiration time, if the expiration time is encountered, the step returns a value of “timeout" and continues processing the workflow.


Asynchronous processing is a very important part of automating a process. Another example is, where a job requisition is posted online, when an applicant applies for the job, the workflow wakes up and starts processing the application request. cDevWorkflow offers an Enterprise Service Bus (ESB) to process external events.

ESB – Enterprise Service Bus lets you define events and event handlers. So for example, you can define an event called “Text Message Received” and a custom event handler to handle the event. External system can publish this event to cDevWorkflow using the direct .Net API or the Web service API. When this event occurs, cDevWorkflow ESB will pick up the event from the event queue and process it using the defined event handler.

If you like to learn more about Asynchronous BPM\Workflow processing or the Enterprise Service Bus (ESB), please contact us at sales@cDevWorkflow.com or support@cDevWorkflow.com

Learn more at http://www.cDevWorkflow.com