Does User Exist activity

An activity that is used to check whether a user exists in Active Directory.

Configure the Does User Exist activity

To configure the Does User Exist activity, do the procedure in this topic.

To send an e-mail notification, click Advanced > E-mail Notifications .
For more information, refer to Configure E-mail Notifications for Any Activity.
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

On the Application Explorer screen, do one of these:
- Open a Process.
- Create a Process.
Do one of these:
- Add an activity:
  1. In the Process Builder, in the Activity Library, open the Active Directory tab.
  2. On the Active Directory tab, drag the Does User Exist activity onto your process.
- Change an activity:
  1. In your process, double-click your activity.

Specifies the basic settings for the Does User Exist activity.

Field Name	Definition
Display Name	Function: Specifies the activity name that shows in your process. Accepted Values: One line of text that can have spaces. Default Value: None Accepts Process Data Variables: No Example: This is a common configuration field that is used in many examples. Refer to: Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.
Description	Function: Specifies an optional text description for your activity. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: No

Field Name

Definition

Display Name

Function:

Specifies the activity name that shows in your process.

Accepted Values:

One line of text that can have spaces.

Default Value:

None

Accepts Process Data Variables:

Example:

This is a common configuration field that is used in many examples. Refer to:

Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Configures the user check in Active Directory.

Field Name	Definition
Active Directory	Function: Specifies the access token that connects to your Active Directory. Accepted Values: A list of access tokens configured for your environment. Default Value: None Accepts Process Data Variables: No
Add Token	Opens this Screen: Access Token for Active Directory. Function of this Screen: Configure an access token to connect to Active Directory.
User Name	Function: Specifies the name of a user to check if the user exists in Active Directory. Accepted Values: One line of text that can have spaces. Default Value: None Accepts Process Data Variables: Yes
Group Name	Function: Specifies the name of the Active Directory group. Accepted Values: A valid Active Directory group name. When you select the access token from the Active Directory field, a list of group names shows in this field. Default Value: None Accepts Process Data Variables: Yes
Store the Response in Custom Attribute or Schema	Function: Specifies a process data variable that stores a Boolean value of true or false. Returns true if the user exists in Active Directory, false if not. Accepted Values: A process data variable that accepts a Boolean value, or the text true or false. Default Value: None Accepts Process Data Variables: Yes