You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
17
+
The following document provides an overview of a workflow created using Lifecycle Workflows. Workflows automate tasks based on the joiner-mover-leaver(JML) cycle of lifecycle management, and split 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).
18
18
19
19
[](media/understanding-lifecycle-workflows/workflow-2.png#lightbox)
20
20
@@ -34,38 +34,30 @@ The following permissions are required for Lifecycle Workflows:
34
34
35
35
## Parts of a workflow
36
36
37
-
A workflow can be broken down in to the following three main parts.
37
+
A workflow can be broken down into the following three main parts:
38
38
39
39
|Workflow part|Description|
40
40
|-----|-----|
41
41
|General information|This portion of a workflow covers basic information such as display name, and a description of what the workflow does.|
42
42
|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|Defines when(trigger), and for who(scope), a scheduled workflow will run. For more information on these two parameters, see [Trigger details](understanding-lifecycle-workflows.md#trigger-details) and [Configure Scope](understanding-lifecycle-workflows.md#configure-scope).|
44
44
45
45
## Templates
46
46
47
-
Creating a workflow via the portal requires the use of a template. A Lifecycle Workflow template is a framework that is used for pre-defined tasks and helps automate the creation of a workflow.
47
+
Creating a workflow via the Azure portal requires the use of a template. A Lifecycle Workflow template is a framework that is used for pre-defined tasks, and helps automate the creation of a workflow.
The templatewill 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.
51
+
The template, depending on its category, will define which tasks are available to be used, and then guide you through the creation of the workflow. The template provides input for basic description, execution conditions, and task information.
52
52
53
53
>[!NOTE]
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.
54
+
>Depending on the template you select, the options that will be available may vary. The images in this document uses the [**Onboarding pre-hire employee**](lifecycle-workflow-templates.md#onboard-pre-hire-employee) template to illustrate the parts of a workflow.
55
55
56
56
For more information, see [Lifecycle workflow templates.](lifecycle-workflow-templates.md)
57
57
58
-
## Workflow basics
59
-
60
-
After selecting a template, on the basics screen:
61
-
- Provide the information that will be used in the description portion of the workflow.
62
-
- The trigger, defines when of the execution condition.
63
-
64
-
[](media/understanding-lifecycle-workflows/workflow-4.png#lightbox)
65
-
66
58
## Workflow overview
67
59
68
-
Every workflow created has its own overview section, which provides the following:
60
+
Every workflow has its own overview section, where you can either take quick actions with the workflow, or view its details. This overview section is split into the three following parts:
69
61
70
62
- Basic Information
71
63
- My Feed
@@ -75,6 +67,8 @@ In this section you'll learn what each section tells you, and what actions you'l
75
67
76
68
### Basic Information
77
69
70
+
When selecting a workflow, the overview provides you a list of basic details in the **Basic Information** section. These basic details provide you information such as the workflow category, its ID, when it was modified, and when it's scheduled to run again. This information is important in providing quick details surrounding its current usage for administrative purposes. Basic information is also live data, meaning any quick change action that you take place on the overview page, is shown immediately within this section.
71
+
78
72
Within the **Basic Information** you can view the following information:
79
73
80
74
|Name|Description|
@@ -83,14 +77,14 @@ Within the **Basic Information** you can view the following information:
83
77
|Description|A brief description that describes the workflow.|
84
78
|Category|A string identifying the category of the workflow.|
85
79
|Date Created|The date and time the workflow was created.|
86
-
|Workflow ID|A unique string identifier for the workflow.|
80
+
|Workflow ID|A unique identifier for the workflow.|
87
81
|Schedule|Defines if the workflow is currently scheduled to run.|
88
82
|Last run date|The last date and time the workflow ran.|
89
83
|Last Modified|The last date and time the workflow was modified.|
90
84
91
85
### My Feed
92
86
93
-
The **My Feed** section of the workflow overview contains a quick peak into when and how the workflow ran. The following information is provided:
87
+
The **My Feed** section of the workflow overview contains a quick peek into when and how the workflow ran. This section also allows you to quickly jump to the target areas for more information. The following information is provided:
94
88
95
89
- Next target run: The date and time of the next scheduled workflow run.
96
90
- Total processed users: The total number of users processed by the workflow.
@@ -100,70 +94,60 @@ The **My Feed** section of the workflow overview contains a quick peak into when
100
94
- Current version: How many new versions of the workflow have been created.
101
95
102
96
103
-
##Trigger details
97
+
### Quick Action
104
98
105
-
Under the trigger details section, you can provide the following information.
99
+
The **Quick Action**section allows you to quickly take action with your workflow. These quick actions can either be making the workflow do something, or used for history or editing purposes. The following actions you can take are:
106
100
107
-
|Name|Description|
108
-
|-----|-----|
109
-
|Days for event|The number of days before or after the date specified in the **Event user attribute**.|
101
+
- Run on Demand: Allows you to quickly run the workflow on demand. For more information on this process, see: [Run a workflow on-demand](on-demand-workflow.md)
102
+
- Edit tasks: Allows you to add, delete, edit, or reorder tasks within the workflow. For more information on this process, see: [Edit the tasks of a workflow using the Azure portal](manage-workflow-tasks.md#edit-the-tasks-of-a-workflow-using-the-azure-portal)
103
+
- View Workflow History: Allows you to view the history of the workflow. For more information on the three history perspectives, see: [Lifecycle Workflows history](lifecycle-workflow-history.md)
110
104
111
-
This section defines **when** the workflow will run. Currently, there are two supported types of triggers:
112
-
113
-
- Trigger and scope based: Runs the task on all users in scope once the workflow is triggered.
114
-
- On-demand: Can be run immediately. Typically used for real-time employee terminations.
105
+
Actions taken from the overview of a workflow allow you to quickly complete tasks, which can normally be done via the manage section of a workflow.
After you define the basics tab, on the configure scope screen:
119
-
- Provide the information that will be used in the execution condition, to determine who the workflow will run against.
120
-
- Add more expressions to create more complex filtering.
109
+
## Workflow basics
121
110
122
-
The configure scope section determines **who** the workflow will run against.
111
+
After selecting a template, on the basics screen:
112
+
- Provide the information that will be used in the description portion of the workflow.
113
+
- The trigger, defines when of the execution condition.
123
114
124
-
[](media/understanding-lifecycle-workflows/workflow-5.png#lightbox)
115
+
[](media/understanding-lifecycle-workflows/workflow-4.png#lightbox)
125
116
126
-
You can add extra expressions using **And/Or** to create complex conditionals, and apply the workflow more granularly across your organization.
The trigger of a workflow defines when a scheduled workflow will run for users in scope for the workflow. The trigger is a combination of a time-based attribute, and an offset value. For example, if the attribute is employeeHireDate and offsetInDays is -1, then the workflow should trigger one day before the employee hire date. The value can range between -60 and 60 days.
129
120
130
-
> [!NOTE]
131
-
> 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)
121
+
The time-based attribute can be either one of two values, which are automatically chosen based on the template in which you select during the creation of your workflow. The two values can be:
132
122
133
-
For detailed information on creating a workflow, see: [Create a lifecycle workflow.](create-lifecycle-workflow.md)
123
+
- employeeHireDate: If the template is a joiner workflow.
124
+
- employeeLeaveDateTime: If the template is a leaver workflow.
134
125
126
+
These two values must be set within Azure AD for users. For more information on this process, see [How to synchronize attributes for Lifecycle workflows](how-to-lifecycle-workflow-sync-attributes.md)
135
127
136
-
## Review tasks
137
-
After defining the scope the review tasks screen will allow you to:
138
-
- Verify that the correct template was selected, and the tasks associated with the workflow are correct.
139
-
- Add more tasks other than the ones in the template.
128
+
The offset determines how many days before or after the time-based attribute the workflow should be triggered. For example, if the attribute is employeeHireDate and offsetInDays is 7, then the workflow should trigger one week(7 days) before the employee hire date. The offsetInDays value can be as far ahead, or behind, as 60.
140
129
141
-
[](media/understanding-lifecycle-workflows/workflow-6.png#lightbox)
142
130
143
-
You can use the **Add task** button to add extra tasks for the workflow. Select the additional tasks from the list provided.
[](media/understanding-lifecycle-workflows/workflow-5.png#lightbox)
146
134
147
-
For more information, see: [Lifecycle workflow tasks](lifecycle-workflow-tasks.md)
135
+
The scope defines for who the scheduled workflow will run. Configuring this parameter allows you to further narrow down the users for whom the workflow is to be executed.
148
136
149
-
## Review and create
137
+
The scope is made up of the following two parts:
150
138
151
-
After reviewing the tasks on the review and create screen, you:
152
-
- Verify all of the information is correct, and create the workflow.
139
+
- Scope type: Always preset as Rule based.
140
+
- Rule: Where you can set expressions on user properties that define for whom the scheduled workflow will run. You can add extra expressions using **And, And not, Or, Or not** to create complex conditionals, and apply the workflow more granularly across your organization. Lifecycle Workflows supports a [rich set of user properties]((/graph/api/resources/identitygovernance-rulebasedsubjectset?view=graph-rest-beta&preserve-view=true#supported-user-properties-and-query-parameters)) for configuring the scope.
153
141
154
-
Based on what was defined in the previous sections our workflow will now show:
155
-
- It's named **on-board pre-hire employee**.
156
-
- Based on the date in the **EmployeeHireDate** attribute, it will trigger **seven** (7) days prior to the date.
157
-
- It will run against users who have **marketing** for the **department** attribute value.
158
-
- It will generate a **TAP (Temporary Access Pass)**, and send an email to the user in the **manager** attribute of the pre-hire employee.
[](media/understanding-lifecycle-workflows/workflow-7.png#lightbox)
144
+
For a detailed guide on setting the execution conditions for a workflow, see: [Create a lifecycleworkflow.](create-lifecycle-workflow.md)
161
145
162
146
## Scheduling
163
147
164
148
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.
165
149
166
-
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.
150
+
Once scheduling is enabled, the workflow will be evaluated every three hours to determine whether or not it should run based on the execution conditions.
@@ -176,23 +160,13 @@ A workflow can be run on-demand for testing or in situations where it's required
176
160
Use the **Run on demand** feature to execute the workflow immediately. The workflow must be enabled before you can run it on demand.
177
161
178
162
>[!NOTE]
179
-
> 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.
163
+
> A workflow that is run on demand for a user does not take into account whether or not a user meets the workflow's execution conditions. It will apply the tasks regardless of whether the execution conditions are met by the user or not.
180
164
181
165
For more information, see: [Run a workflow on-demand](on-demand-workflow.md)
182
166
183
-
## Managing the workflow
184
-
185
-
By selecting on a workflow you created, you can manage the workflow.
186
-
187
-
You can select which portion of the workflow you wish to update or change using the left navigation bar. Select the section you wish to update.
For more information, see: [Manage lifecycle workflow properties](manage-workflow-properties.md)
192
-
193
167
## History
194
168
195
-
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.
169
+
When you've selected a workflow, you can view its 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.
196
170
197
171
For more information, see: [Lifecycle Workflows history](lifecycle-workflow-history.md)
198
172
@@ -201,11 +175,9 @@ For more information, see: [Lifecycle Workflows history](lifecycle-workflow-hist
201
175
202
176
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.
203
177
204
-
You can view versioning information by selecting **Versions** under **Manage** from the left.
0 commit comments