Skip to content

Commit 41d9574

Browse files
Merge pull request #228678 from OWinfreyATL/owinfreyATL-History-Updates
History Conceptual updates
2 parents 8d70d48 + 97856ce commit 41d9574

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/active-directory/governance/lifecycle-workflow-history.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,13 @@ Workflows created using Lifecycle Workflows allow for the automation of lifecycl
2121

2222
## Lifecycle Workflow History Summaries
2323

24-
Lifecycle Workflows introduce a history feature based on summaries and details. These history summaries allow you to quickly get information about for who a workflow ran, and whether or not this run was successful or not. This is valuable because the large set of information given by audit logs might become too numerous to be efficiently used. To make a large set of information processed easier to read, Lifecycle Workflows provide summaries for quick use. You can view these history summaries in three ways:
24+
Lifecycle Workflows introduce a history feature based on summaries and details. These history summaries allow you to quickly get information about for who a workflow ran, and whether or not this run was successful. This is valuable because the large set of information given by audit logs might become too numerous to be efficiently used. To make a large set of information processed easier to read, Lifecycle Workflows provide summaries for quick use. You can view these history summaries in three ways:
2525

26-
- **Users summary**: Shows a summary of users processed by a workflow, and which tasks failed, successfully, and totally ran for each specific user.
26+
- **Users summary**: Shows a summary of users processed by a workflow. Successfully, failed, and total ran information for each specific user is shown.
2727
- **Runs summary**: Shows a summary of workflow runs in terms of the workflow. Successful, failed, and total task information when workflow runs are noted.
2828
- **Tasks summary**: Shows a summary of tasks processed by a workflow, and which tasks failed, successfully, and totally ran in the workflow.
2929

30-
Summaries allow you to quickly gain details about how a workflow ran for itself, or users, without going into further details in logs. For a step by step guide on getting this information, see [Check the status of a workflow (Preview)](check-status-workflow.md)
30+
Summaries allow you to quickly gain details about how a workflow ran for itself, or users, without going into further details in logs. For a step by step guide on getting this information, see [Check the status of a workflow (Preview)](check-status-workflow.md).
3131

3232
## Users Summary information
3333

@@ -113,7 +113,7 @@ Task detailed history information allows you to filter for specific information
113113
- **Completed date**: You can filter a specific range from as short as 24 hours up to 30 days of when the workflow ran.
114114
- **Tasks**: You can filter based on specific task names.
115115

116-
Separating processing of the workflow from the tasks is important because, in a workflow, processing a user certain tasks could be successful, while others could fail. Whether or not a task runs after a failed task in a workflow depends on parameters such as enabling continue On Error, and their placement within the workflow. For more information, see [Common task parameters](lifecycle-workflow-tasks.md#common-task-parameters-preview).
116+
Separating processing of the workflow from the tasks is important because, in a workflow, processing a user certain tasks could be successful, while others could fail. Whether or not a task runs after a failed task in a workflow depends on parameters such as enabling continue On Error, and their placement within the workflow. For more information, see [Common task parameters (preview)](lifecycle-workflow-tasks.md#common-task-parameters-preview).
117117

118118
## Next steps
119119

@@ -123,4 +123,3 @@ Separating processing of the workflow from the tasks is important because, in a
123123
- [taskProcessingResult resource type](/graph/api/resources/identitygovernance-taskprocessingresult?view=graph-rest-beta&preserve-view=true)
124124
- [Understanding Lifecycle Workflows](understanding-lifecycle-workflows.md)
125125
- [Lifecycle Workflow templates](lifecycle-workflow-templates.md)
126-

0 commit comments

Comments
 (0)