Create real-time workflows in CRM 2015 Online and On Premises

Similar to asynchronous workflows, real-time workflows can be used to model and automate real world business processes. They can optionally require user input, can start automatically based on specified event conditions, or can be started manually by a user. Real-time workflows are for business users, for example business analysts, to implement similar functionality to synchronous plug-ins without requiring .NET Framework programming experience. You can create asynchronous or real-time workflows in the Microsoft Dynamics CRM web application or in code.

WorkFlow Stages:

1. If the workflow is to be triggered by the creation of a record, the workflow will only be apply post event, i.e. after record is created

2. When there is a change in the record status, owner or a designated field value changes, the workflow can be set to either post or pre-event, i.e. make it will make a validatation before data is changed

3. When record is deleted, the real time workflow will only apply on pre event, i.e. before record is deleted

Real Time Workflows are beneficial in a situations where data validation is required to preserve data integrity by reverting back the operation if a particular condition isn’t validated, or if calculation fails due to any technical or constructive issue.

Some key points about a real-time workflow include the following items:

• Defined by using a Workflow entity record, similar to an asynchronous workflow.
• Executes in a stage of the event execution pipeline, similar to synchronous plug-ins. The real-time workflow can execute before (pre-operation), after (post-operation), or during the core operation. A real-time workflow that is executed during the core operation is the implementation of a custom action. Real-time workflows can be ranked within a stage just like you can do with plug-ins. More information: Pipeline Stages
• Whether configured to run on-demand or in response to an event, a real-time workflow runs immediately rather than being queued to run at a later time.
• Can run in the security context of the logged on user or owner of the workflow. However, workflows set to run on-demand always run under the security context of the logged on user. 
• Can’t contain any delay or wait activities.
• Only logs errors, and only when logging is enabled.
• Executes in the current transaction. All activities in the workflow and any child workflows, except asynchronous workflows, are part of a single transaction. Asynchronous child workflows are queued and execute in a separate transaction.
• Can be converted to asynchronous workflow and back to real-time.