Healthcare - CSR Help Desk - Active Directory - User Functions API - Subflow
The Healthcare - CSR Help Desk - Active Directory - User Functions API - Subflow takes account management actions on users.
Purpose
The Healthcare - CSR Help Desk - Active Directory - User Functions API - Subflow accepts a user identifier and an action (enable, disable, or get user account information) as inputs. It finds the user using the identifier, then performs the specified action.
Structure
This flow is divided into sections using teleport nodes:
- Identify the CSR action from the input schema.
-
Uses a PingOne node to identify the user, then uses a function node to set flow variables. A function node then branches the flow based on the desired action, and the flow progresses to the portion of the User Functions section that corresponds with the desired action.
- User Functions
-
Performs an action corresponding to the action input:
-
If the action is getUserAccountStatus, the flow uses a PingOne node to retrieve user information, then uses a function node to determine the correct account status button text. The flow then progresses to the Return Success section.
-
If the action is disableUser, the flow uses a PingOne node to disable the user. The flow then progresses to the Return Success section.
-
If the action is enableUser, the flow uses a PingOne node to enable the user. The flow then progresses to the Return Success section.
-
- Return Success
-
Sends a success JSON response, indicating that the flow completed successfully.
- Return Error
-
Sends an error JSON response, indicating that the flow completed unsuccessfully.
Input schema
This flow has the following inputs:
| Input name | Required | Description |
|---|---|---|
|
No |
The action to be taken during the flow. |
|
No |
The identifier to be used in user lookup. |
Output schema
This flow has the following outputs:
| Output name | Description |
|---|---|
|
The user’s PingOne user name. |
|
The email address associated with the user’s PingOne account. |
|
A Boolean indicating whether the user’s email address is verified. |
|
The user’s PingOne account status. |
|
The date when the user’s password was last changed. |
|
The button label that should be displayed for the user’s account status. |
|
The action that the button should take based on the user’s account status. |
|
An object containing additional error parameters. |
|
The action that was attempted during the flow. |
|
The identifier used in user lookup. |