Skip to content

Commit e7f8a50

Browse files
authored
Added clarification on validation technical profile execution
1 parent 8702752 commit e7f8a50

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/active-directory-b2c/self-asserted-technical-profile.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -192,6 +192,9 @@ The validation technical profile can be any technical profile in the policy, suc
192192

193193
You can also call a REST API technical profile with your business logic, overwrite input claims, or enrich user data by further integrating with corporate line-of-business application. For more information, see [Validation technical profile](validation-technical-profile.md)
194194

195+
> [!NOTE]
196+
> A validation technical profile will only be triggered when there is some input from the user. It is not possible to create an _empty_ self-asserted technical profile that exists to call validation technical profiles only e.g. to take advantage of the **ContinueOnError** attribute of a **ValidationTechnicalProfile** element. These validation technical profiles must be called from a self-asserted technical profile that solicits some input from the user, or called from an orchestration step in a user journey.
197+
195198
## Metadata
196199

197200
| Attribute | Required | Description |

0 commit comments

Comments
 (0)