Skip to content

Commit 029781b

Browse files
authored
Merge pull request #28362 from microsoftgraph/owinfreyATL-FixedExamples-Workflows
Fixed Lifecycle workflow activate with scope examples
2 parents c47aa95 + 6e623ea commit 029781b

2 files changed

Lines changed: 165 additions & 2 deletions

File tree

api-reference/beta/api/identitygovernance-workflow-activatewithscope.md

Lines changed: 85 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,9 @@ If successful, this action returns a `204 No Content` response code.
6060

6161
## Examples
6262

63-
### Request
63+
### Example 1: Activate a workflow with a specific scope of 2 users
64+
65+
#### Request
6466

6567
The following example shows a request.
6668

@@ -104,7 +106,88 @@ Content-Type: application/json
104106

105107
---
106108

107-
### Response
109+
#### Response
110+
The following example shows the response.
111+
<!-- {
112+
"blockType": "response",
113+
"truncated": true
114+
}
115+
-->
116+
```http
117+
HTTP/1.1 204 No Content
118+
```
119+
120+
121+
### Example 2: Activate a workflow with a specific scope of 2 users who don't exist
122+
123+
#### Request
124+
125+
The following example shows a request.
126+
127+
<!-- {
128+
"blockType": "request",
129+
"name": "lifecycleworkflows_workflowthis.activatescope_invalid"
130+
}
131+
-->
132+
```http
133+
POST https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/2f0dcb02-65d9-4369-bad5-a3174538c5ff/activatewithscope
134+
Content-Type: application/json
135+
136+
{
137+
"scope": {
138+
"@odata.type": "microsoft.graph.identityGovernance.activateProcessingResultScope",
139+
"processingResults": [
140+
{
141+
"id": "abc12345-265a-4e8f-8d61-94a2dcd2d395_1_78799042-265a-4e8f-8d61-94a2dcd2d395_638927021459371237_0cdd8963-aaaa-4632-a1f2-aaaa7230aaaa"
142+
},
143+
{
144+
"id": "abc12345-265a-4e8f-8d61-94a2dcd2d395_1_78799042-265a-4e8f-8d61-94a2dcd2d395_388131231459357126_aaaa8963-1c30-4632-aaaa-ac96723069cb"
145+
}
146+
],
147+
"taskScope": "allTasks"
148+
}
149+
}
150+
```
151+
152+
#### Response
153+
The following example shows the response.
154+
<!-- {
155+
"blockType": "response",
156+
"truncated": true
157+
}
158+
-->
159+
```http
160+
HTTP/1.1 406 NOT Acceptable
161+
```
162+
163+
### Example 3: Activate a workflow with a specific processing result scope
164+
165+
#### Request
166+
167+
The following example shows a request.
168+
169+
<!-- {
170+
"blockType": "request",
171+
"name": "lifecycleworkflows_workflowthis.activatescope_processingresultscope"
172+
}
173+
-->
174+
```http
175+
POST https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/2f0dcb02-65d9-4369-bad5-a3174538c5ff/activatewithscope
176+
Content-Type: application/json
177+
178+
{
179+
"subjects": [
180+
{
181+
"id": "abc12345-265a-4e8f-8d61-94a2dcd2d395_1_78799042-265a-4e8f-8d61-94a2dcd2d395_638927021459371237_0cdd8963-aaaa-4632-a1f2-aaaa7230aaaa"
182+
},
183+
{
184+
"id": "abc12345-265a-4e8f-8d61-94a2dcd2d395_1_78799042-265a-4e8f-8d61-94a2dcd2d395_388131231459357126_aaaa8963-1c30-4632-aaaa-ac96723069cb"
185+
}
186+
]
187+
}
188+
```
189+
190+
#### Response
108191
The following example shows the response.
109192
<!-- {
110193
"blockType": "response",

api-reference/v1.0/api/identitygovernance-workflow-activatewithscope.md

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,8 @@ If successful, this action returns a `204 No Content` response code.
6262

6363
## Examples
6464

65+
### Example 1: Activate a workflow with a specific scope of 2 users
66+
6567
### Request
6668

6769
The following example shows a request.
@@ -116,3 +118,81 @@ The following example shows the response.
116118
``` http
117119
HTTP/1.1 204 No Content
118120
```
121+
122+
123+
### Example 2: Activate a workflow with a specific scope of 2 users who don't exist
124+
125+
#### Request
126+
127+
The following example shows a request.
128+
129+
<!-- {
130+
"blockType": "request",
131+
"name": "lifecycleworkflows_workflowthis.activatescope_invalid"
132+
}
133+
-->
134+
```http
135+
POST https://graph.microsoft.com/v1.0/identityGovernance/lifecycleWorkflows/workflows/2f0dcb02-65d9-4369-bad5-a3174538c5ff/activatewithscope
136+
Content-Type: application/json
137+
138+
{
139+
"subjects": [
140+
{ "id": "2ea4c363-4b85-4529-b2ec-53b64308f39f"},
141+
{ "id": "44fc5392-9485-4348-871e-2ea17cc0a1b8"}
142+
]
143+
}
144+
```
145+
146+
#### Response
147+
The following example shows the response.
148+
<!-- {
149+
"blockType": "response",
150+
"truncated": true
151+
}
152+
-->
153+
```http
154+
HTTP/1.1 406 NOT Acceptable
155+
```
156+
157+
### Example 3: Activate a workflow with a specific processing result scope
158+
159+
#### Request
160+
161+
The following example shows a request.
162+
163+
<!-- {
164+
"blockType": "request",
165+
"name": "lifecycleworkflows_workflowthis.activatescope_processingresultscope"
166+
}
167+
-->
168+
```http
169+
POST https://graph.microsoft.com/v1.0/identityGovernance/lifecycleWorkflows/workflows/2f0dcb02-65d9-4369-bad5-a3174538c5ff/activatewithscope
170+
Content-Type: application/json
171+
172+
{
173+
"scope": {
174+
"@odata.type": "microsoft.graph.identityGovernance.activateProcessingResultScope",
175+
"processingResults": [
176+
{
177+
"id": "abc12345-265a-4e8f-8d61-94a2dcd2d395_1_78799042-265a-4e8f-8d61-94a2dcd2d395_638927021459371237_0cdd8963-aaaa-4632-a1f2-aaaa7230aaaa"
178+
},
179+
{
180+
"id": "abc12345-265a-4e8f-8d61-94a2dcd2d395_1_78799042-265a-4e8f-8d61-94a2dcd2d395_388131231459357126_aaaa8963-1c30-4632-aaaa-ac96723069cb"
181+
}
182+
],
183+
"taskScope": "allTasks"
184+
}
185+
}
186+
```
187+
188+
#### Response
189+
The following example shows the response.
190+
<!-- {
191+
"blockType": "response",
192+
"truncated": true
193+
}
194+
-->
195+
```http
196+
HTTP/1.1 204 No Content
197+
```
198+

0 commit comments

Comments
 (0)