Find Contact activity

An activity that finds a contact in Microsoft Outlook.


Find Contact activity

Configure the Find Contact activity

To configure the Find Contact activity, do the procedure in this topic.

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In the Process Builder, in the Activity Library, open the Exchange Server tab.

    Open Exchange Server tab
  3. On the Exchange Server tab, drag the Find Contact activity onto your process.

    Drag Find Contact activity

General Configuration

Specifies the basic settings for the Find Contact activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

  • Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field NameDefinition

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

Find Contact Configuration

Specifies the configuration to find a contact.

Figure: Find Contact Configuration screen

Find Contact Configuration screen

Fields

Field NameDefinition

Exchange Server

Function:
Specifies the access token that connects to your Exchange Server.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None
Accepts Process Data Variables:
No

Create Add Token icon

Opens this Screen:
Access Token for Exchange Server
Function of this Screen:
Configure an access token to connect to Exchange Server.

Search By

Function:
Specifies how to search the contact in Exchange Server.
Accepted Values:
  • Contact ID - Searches the contact by the contact ID.
  • Email ID - Searches the contact by the e-mail address.
Default Value:
Contact ID
Accepts Process Data Variables:
No
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use 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, or 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?

Email/Contact ID

Function:
Specifies the e-mail address or contact ID of the user.

The contact ID comes from Exchange Server.

Accepted Values:
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use 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, or 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?

First Name

Function:
Specifies the process data variable that stores the first name of the user.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes

Last Name

Function:
Specifies process data variable that stores the last name of the user.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes

Email ID

Function:
Specifies the process data variable that stores the e-mail address.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes

Email Display Name

Function:
Specifies the process data variable that stores the name to show as an alternative to the user's e-mail address.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes

Mobile

Function:
Specifies the process data variable that stores the user's mobile number.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes

Business Phone

Function:
Specifies the process data variable that stores the business telephone number of the user.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes

Company Name

Function:
Specifies the process data variable that stores the name of the user's organization.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes

Department

Function:
Specifies the process data variable that stores the user's department.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes

Contact ID

Function:
Specifies the ID of the contact in Exchange Server.
Accepted Values:
A valid contact ID.
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use 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, or 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?