Configuring Workflows in Microsoft Power Platform
- When to start them?
- Should they run as a real-time workflow or a background workflow?
- What actions should they perform?
- Under what conditions should actions be performed?
- automatically in response to the events such as create, update, delete, change in record status, or change in record ownership (assignment).
- manually by a user.
- as a child workflow that will be started by another workflow process.
|Name||The name of the workflow process does not need to be unique, however you may want to use a naming convention to clearly differentiate your processes. You may want to apply standard prefixes to the name of the workflow. The prefix may describe the function of the workflow or the department within the company. This will help you group similar items in the list of workflows.|
|Category||Select Workflow to create a workflow process. You can’t change the category once the process is created.|
|Entity||Each workflow process is associated with a single entity. Regardless of the method used to start the workflow, each running instance of a workflow process will have a single target record of the entity associated with the process. You can’t change the entity after the workflow process is created.|
|Run this workflow in the background (recommended)||This option appears when you select workflow as the category. This setting determines whether the workflow is a real-time or background workflow. Real-time workflows run immediately (synchronously) and background workflows run asynchronously. The configuration options available depend on your choice for this setting. Background workflows allow for wait conditions that are not available for real-time workflows. As long as you don’t use those wait conditions, at a later time you can convert background workflows to real-time workflows and real-time workflows to background workflows.|
|Type||Specify whether to build a new workflow from scratch or choose to start from an existing template. When you choose New process from an existing template (select from list) you can choose from the available Workflows processes that were previously saved as a process template for the selected entity.|
Want to keep
CloudSwyft Global Systems, Inc. online course,
Dynamics 365: Working with Power Platform Automation
|Process Name||Process name can be changed when the process is deactivated. While references to workflows from other workflows are not affected, often during implementations projects contain developers’ code that may refer to a process by name. Renaming the process that is in use may require additional coordination across the project to deal with these references.|
|Activate As||You can choose Process template to create an advanced starting point for other workflows. If you choose this option, after you activate the workflow it will not be applied but instead it will be available to select in the Create Process dialog. Process templates are convenient when you have a number of similar workflow processes and want to define them without duplicating the same logic, or when you want to provide users with a starting point for the most common tasks they would like to automate for themselves.|
Available to RunThis section contains options that describe how the workflow is available to be run.
|Run this Workflow in the background (recommended)||This check box reflects the option you selected when you created the workflow. This option is disabled, but you can change it from the Actions menu by choosing either Convert to a real-time workflow or Convert to a background workflow.|
|As an on-demand process||Choose this option if you want to allow users to run this workflow from the Run Workflow command.|
|As a child process||Choose this option if you want to allow the workflow to be available to be started from another workflow.|
Workflow Job RetentionFor background workflows this section contains an option to delete information about a workflow run after the workflow execution has completed. For real-time workflows the logs are not retained by default, but this section contains an option to retain the logs for the jobs that encountered errors.
Options for Automatic ProcessesAvailable options in this section depend on whether the process is background or real-time.
ScopeIf the scope is organisation, then the workflow logic can be applied to any record in the organisation. Otherwise, the workflow can only be applied to a subset of records that fall within the scope. The default scope value is the user. For workflows deployed with solutions that you intend to work on all records modified you would want the scope to configured to organisation and the connection’s user to have organisation level read access to work properly. Make sure you verify that the scope value is appropriate before you activate the workflow. Workflow scope is discussed in detail in the next lesson.
Start WhenUse the options in this section to specify when a workflow should start automatically. You can configure a real-time workflow to be run before or after certain events. Configuration of a real-time workflow is discussed in detail in the next lesson. Background workflows always run after the triggering action and may not run immediately. This approach works best for the processing that is not time-sensitive, for example sending an email in response to a certain event. Be aware that some events and subsequent actions may cause a workflow to call itself. For example, triggering workflow on record status changes event and then changing the record status as part of the workflow will cause the workflow to call itself which may or may not be intentional. When record fields change event is selected, use select button to select specific fields that will trigger the workflow. This step is strongly recommended to minimise unnecessary triggering and reduce the possibility of the infinite loop when a workflow updates the record.
Activate a WorkflowWorkflows can only be edited while they are deactivated. Before a workflow can be used manually or be applied due to events it has to be activated. Before a workflow can be activated it must contain at least one step.
OwnershipA workflow can only be activated or deactivated by the workflow owner or by someone with the Act on Behalf of Another User privilege such as the system administrator. You can reassign a workflow you own by changing the owner. This field is on the administration tab. Note that ownership of a workflow defines the scope. Changing the owner of a workflow with any scope except Organisation may change when the workflow is triggered.
NotesDeveloping workflows is a collaborative process. Use the Notes tab to keep track of any changes applied to the workflow when developing new and modifying existing workflows.
Dynamics 365: Working with Power Platform Automation
Our purpose is to transform access to education.
We offer a diverse selection of courses from leading universities and cultural institutions from around the world. These are delivered one step at a time, and are accessible on mobile, tablet and desktop, so you can fit learning around your life.
We believe learning should be an enjoyable, social experience, so our courses offer the opportunity to discuss what you’re learning with others as you go, helping you make fresh discoveries and form new ideas.
You can unlock new opportunities with unlimited access to hundreds of online short courses for a year by subscribing to our Unlimited package. Build your knowledge with top universities and organisations.