Workflows include a number of options and settings, called workflow properties that are required as part of any workflow in Microsoft Dynamics CRM.
At a minimum, each workflow requires the following properties:
- Entity. Although a workflow can take action on more than one entity, it is still associated with a single primary entity.
- Scope. A workflow's scope determines the records that the workflow can take action on. The scope is limited by the permissions that the workflow's owner has, as well as by the view the owner selects for the scope when they are creating the workflow.
- Type. You can select whether the workflow you create is a workflow or workflow template.
- How automatic workflows are started. You can specify what events in your Microsoft Dynamics CRM implementation will cause the workflow to take action, such as the creation of a new lead record or a specific change to a case record.
- Availability. In addition to workflows that run automatically when certain events occur, you make the workflow available as an on-demand workflow, a child workflow, or both.
The workflow logic you add to your workflow determines the specific actions that the workflow will take on records.
Workflow logic includes the following elements:
- Stages. By adding workflow stages to your workflow logic, you can group the steps in your workflow. Workflow stages make the workflow logic easier to read, and explain the workflow logic. However, stages do not affect the logic or behavior of workflows.
- Steps. Each workflow step you add defines the underlying logic of your workflow. Workflow steps can contain actions, such as creating a new record or sending an e-mail notification, or even other steps. (There is no limit to how deeply you can nest workflow steps.)
You can add the following types of steps to workflows:
- Actions. By adding workflow actions to workflow steps, you define the specific actions you want the workflow to perform.
You can add the following actions to workflows: