Skip to content

Commit 417ddf4

Browse files
committed
updates
1 parent 18637e5 commit 417ddf4

File tree

1 file changed

+21
-19
lines changed

1 file changed

+21
-19
lines changed

articles/active-directory/governance/understanding-lifecycle-workflows.md

Lines changed: 21 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection: M365-identity-device-management
1414
---
1515
# Understanding lifecycle workflows
1616

17-
The following reference document provides an overview of a workflow created using Lifecycle Workflows. Lifecycle Workflows allow you to create workflows that automate common tasks associated with user lifecycle in organizations. Lifecycle Workflows automate tasks based on the joiner-mover-leaver cycle of lifecycle management, and splits tasks for users up into categories of where they are in the lifecycle of an organization. These categories extend into templates where they can be quickly customized to suit the needs of users in your organization. For more information, see: [What are Lifecycle Workflows?](what-are-lifecycle-workflows.md).
17+
The following reference document provides an overview of a workflow created using Lifecycle Workflows. Lifecycle Workflows allow you to automate common tasks associated with user lifecycle in organizations. Workflows automate tasks based on the joiner-mover-leaver(JML) cycle of lifecycle management, and splits tasks for users into categories of where they fall in the lifecycle of an organization. These categories extend into templates, where they can be quickly customized to suit the needs of users in your organization. For more information, see: [What are Lifecycle Workflows?](what-are-lifecycle-workflows.md).
1818

1919
[![Diagram of a lifecycle workflow](media/understanding-lifecycle-workflows/workflow-2.png)](media/understanding-lifecycle-workflows/workflow-2.png#lightbox)
2020

@@ -38,9 +38,9 @@ A workflow can be broken down in to the following three main parts.
3838

3939
|Workflow part|Description|
4040
|-----|-----|
41-
|General information|This portion of a workflow covers basic information such as display name and a description of what the workflow does.|
41+
|General information|This portion of a workflow covers basic information such as display name, and a description of what the workflow does.|
4242
|Tasks|Tasks are the actions that will be taken when a workflow is executed.|
43-
|Execution conditions| The execution condition section of a workflow sets up<br><br>- Who(scope) the workflow runs against <br><br>- When(trigger) the workflow runs|
43+
|Execution conditions| The execution condition section of a workflow sets up<br><br> Who(scope)- The workflow runs against <br><br> When(trigger)- the workflow runs|
4444

4545
## Templates
4646

@@ -51,7 +51,7 @@ Creating a workflow via the portal requires the use of a template. A Lifecycle W
5151
The template will define the task that is to be used and then guide you through the creation of the workflow. The template provides input for description information and execution condition information.
5252

5353
>[!NOTE]
54-
>Depending on the template you select, the options that will be available may vary. This document uses the **Onboarding pre-hire employee** template to illustrate the parts of a workflow.
54+
>Depending on the template you select, the options that will be available may vary. This document uses the [**Onboarding pre-hire employee**](lifecycle-workflow-templates.md#onboard-pre-hire-employee) template to illustrate the parts of a workflow.
5555
5656
For more information, see [Lifecycle workflow templates.](lifecycle-workflow-templates.md)
5757

@@ -72,6 +72,7 @@ Under the workflow details section, you can provide the following information:
7272
|Description|A brief description that describes the workflow.|
7373

7474
### Trigger details
75+
7576
Under the trigger details section, you can provide the following information.
7677

7778
|Name|Description|
@@ -84,6 +85,7 @@ This section defines **when** the workflow will run. Currently, there are two s
8485
- On-demand - can be run immediately. Typically used for real-time employee terminations.
8586

8687
## Configure scope
88+
8789
After you define the basics tab, on the configure scope screen:
8890
- Provide the information that will be used in the execution condition, to determine who the workflow will run against.
8991
- Add more expressions to create more complex filtering.
@@ -99,7 +101,7 @@ You can add extra expressions using **And/Or** to create complex conditionals, a
99101
> [!NOTE]
100102
> For a full list of user properties supported by Lifecycle Workflows, see [Supported user properties and query parameters](/graph/api/resources/identitygovernance-rulebasedsubjectset?view=graph-rest-beta&preserve-view=true#supported-user-properties-and-query-parameters)
101103
102-
For more information, see [Create a lifecycle workflow.](create-lifecycle-workflow.md)
104+
For detailed information on creating a workflow, see: [Create a lifecycle workflow.](create-lifecycle-workflow.md)
103105

104106

105107
## Review tasks
@@ -130,16 +132,13 @@ After reviewing the tasks on the review and create screen, you:
130132

131133
## Scheduling
132134

133-
A workflow isn't scheduled to run by default. To enable the workflow, it needs to be scheduled.
134-
135-
To verify whether the workflow is scheduled, you can view the **Scheduled** column.
135+
While newly created workflows are enabled by default, scheduling is an option that must be enabled manually. To verify whether the workflow is scheduled, you can view the **Scheduled** column.
136136

137-
To enable the workflow, select the **Enable schedule** option for the workflow.
138-
139-
Once scheduled, the workflow will be evaluated every 3 hours to determine whether or not it should run based on the execution conditions.
137+
Once scheduling is enabled, the workflow will be evaluated every 3 hours to determine whether or not it should run based on the execution conditions.
140138

141139
[![Workflow template schedule.](media/understanding-lifecycle-workflows/workflow-10.png)](media/understanding-lifecycle-workflows/workflow-10.png#lightbox)
142140

141+
To view a detailed guide on scheduling a workflow, see: [Customize the schedule of workflows](customize-workflow-schedule.md).
143142

144143
### On-demand scheduling
145144

@@ -150,7 +149,7 @@ Use the **Run on demand** feature to execute the workflow immediately. The workf
150149
>[!NOTE]
151150
> A workflow that is run on demand for any user does not take into account whether or not a user meets the workflow's execution. It will apply the task regardless of whether the execution conditions are met or not.
152151
153-
For more information, see [Run a workflow on-demand](on-demand-workflow.md)
152+
For more information, see: [Run a workflow on-demand](on-demand-workflow.md)
154153

155154
## Managing the workflow
156155

@@ -160,22 +159,25 @@ You can select which portion of the workflow you wish to update or change using
160159

161160
[![Update manage workflow section review.](media/understanding-lifecycle-workflows/workflow-11.png)](media/understanding-lifecycle-workflows/workflow-11.png#lightbox)
162161

163-
For more information, see [Manage lifecycle workflow properties](manage-workflow-properties.md)
162+
For more information, see: [Manage lifecycle workflow properties](manage-workflow-properties.md)
163+
164+
## History
165+
166+
When you have selected a workflow, you can view it's historical information through the lens of its users, runs, and tasks. Being able to view information specifically from these viewpoints allows you to quickly narrow down specific information about how a workflow was processed.
167+
168+
For more information, see: [Lifecycle Workflows history](lifecycle-workflow-history.md)
169+
164170

165171
## Versioning
166172

167-
Workflow versions are separate workflows built using the same information of an original workflow, but with updated parameters so that they're reported differently within logs. Workflow versions can change the actions or even scope of an existing workflow.
173+
Workflow versions are separate workflows built using the same information of an original workflow, but with either the tasks or scope updated, so that they're reported differently within logs. Workflow versions can change the actions or even scope of an existing workflow.
168174

169175
You can view versioning information by selecting **Versions** under **Manage** from the left.
170176

171177
[![Manage workflow versioning selection.](media/understanding-lifecycle-workflows/workflow-12.png)](media/understanding-lifecycle-workflows/workflow-12.png#lightbox)
172178

173-
For more information, see [Lifecycle Workflow versioning](lifecycle-workflow-versioning.md)
174-
175-
## Developer information
176-
This document covers the parts of a lifecycle workflow
179+
For more information, see: [Lifecycle Workflow versioning](lifecycle-workflow-versioning.md)
177180

178-
For more information, see the [Workflow API Reference](lifecycle-workflows-developer-reference.md)
179181

180182
## Next steps
181183
- [Create a custom workflow using the Azure portal](tutorial-onboard-custom-workflow-portal.md)

0 commit comments

Comments
 (0)