Skip to content

Commit b821473

Browse files
authored
Merge pull request #175951 from yoelhor/patch-204
Update subjourneys.md
2 parents fd60cb0 + bc0fa10 commit b821473

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/active-directory-b2c/subjourneys.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: CelesteDG
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: reference
11-
ms.date: 12/11/2020
11+
ms.date: 10/15/2021
1212
ms.author: kengaderdus
1313
ms.subservice: B2C
1414
---
@@ -20,8 +20,6 @@ Sub journeys can be used to organize and simplify the flow of orchestration step
2020

2121
A sub journey is a grouping of orchestration steps that can be invoked at any point within a user journey. You can use sub journeys to create reusable step sequences or implement branching to better represent the business logic.
2222

23-
[!INCLUDE [b2c-public-preview-feature](../../includes/active-directory-b2c-public-preview.md)]
24-
2523
## User journey branching
2624

2725
Sub journeys behave like [user journeys](userjourneys.md), as both are represented as an orchestration sequence that must be followed through for a successful transaction. User journeys can be invoked on their own and require a SendClaims step to execute. Sub journeys are components of user journeys and cannot be invoked independently, and are always called from a user journey.
@@ -136,4 +134,4 @@ For the complete list of orchestration step elements, see [UserJourneys](userjou
136134

137135
## Next steps
138136

139-
Learn about [UserJourneys](userjourneys.md)
137+
Learn about [UserJourneys](userjourneys.md)

0 commit comments

Comments
 (0)