We would like to have an option in HelloID to trigger the update process after the create process in the account cycle.

In some scenarios, a department or other property is not known or cannot be set in the initial create account request. In cases like this, we would like to trigger the Update script to update the account with that department or other properties. The reason we prefer this approach is to keep the create script clean with only the create action, and use the update process for all other HTTP requests that update properties.

We would like only to execute the initial HTTP create request to create the user in the create script and use the update script for the other actions that are required. We still would also like to distinguish whether the account is correlated in the update after the create lifecycle.

In the past, in Target v1, we sometimes misused the account reference to create this functionality. In v2, we misused the $accountcorrelated = $true variable to trigger the update action, but this is not the intended use of this variable.

Example Target Systems we would like to use this feature on (may not be a complete list):

KPN-Bart (Set account reference)

KPN-Lisa (Set workspace ID)

Zermelo (set departments)

Ozo (set title)

Arda Online (update account)

Capp12 (set positions/set departments)

Entra (in development)

Paxton Net2 (set department)

Fierit ECD (Update user)

Multiple Azure connections

Powershell AD connector on roadmap