Create Contact activity

An activity that creates a contact in Microsoft Outlook.

Configure the Create Contact activity

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

Good to Know

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
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?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
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?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the Exchange Server tab.
On the Exchange Server tab, drag the Create Contact activity onto your process.

General Configuration

Specifies the basic settings for the Create Contact activity.

Good to Know

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

Fields

Field Name	Definition
Display Name	Description: Specifies the activity name that shows in your process. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts 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	Description: Specifies an optional text description for your activity. Allowed Values: More than one line of text. Default Value: None Accepts Variables: No

Field Name

Definition

Display Name

Description:

Specifies the activity name that shows in your process.

Allowed Values:

One line of text (a string).

Accepted:

Letters
Numbers
Spaces

Default Value:

None

Accepts 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

Description:: Specifies an optional text description for your activity.
Allowed Values:: More than one line of text.
Default Value:: None
Accepts Variables:: No

Create Contact Configuration

Specifies the configuration to create a contact.

Fields

Field Name	Definition
Exchange Server	Description: Specifies the access token that connects to your Exchange Server. Allowed Values: A list of access tokens configured for your environment. Default Value: None Accepts Variables: No
Create	Opens this Screen: Access Token for Exchange Server Function of this Screen: Configure an access token to connect to Exchange Server.
First Name	Description: Specifies the first name of the user. Allowed Values: One line of text that can have spaces. A process data variable Default Value: None Accepts Variables: Yes
Last Name	Description: Specifies the last name of the user. Allowed Values: The last name of the user. A process data variable Default Value: None Accepts Variables: Yes
Email ID	Description: The user's e-mail address. Allowed Values: One line of text (a string) in email address format. Default Value: None Accepts Variables: Yes
Email Display Name	Description: Specifies the name to show as an alternative to the e-mail address of the user. Allowed Values: One line of text (a string) in email address format. A process data variable Default Value: None Accepts Variables: Yes
Mobile	Description: Specifies the user's mobile number. Allowed Values: The user's mobile number. A process data variable Default Value: None Accepts Variables: Yes
Business Phone	Description: Specifies the business phone number of the user. Allowed Values: The business phone number of the user. A process data variable Default Value: None Accepts Variables: Yes
Company Name	Description: Specifies the name of the user's organization. Allowed Values: One line of text that can have spaces. A process data variable Default Value: None Accepts Variables: Yes
Department	Description: Specifies the user's department. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts Variables: Yes
Store Contact ID in this Variable	Description: Specifies the process data variable that contains the contact ID from Exchange Server. Allowed Values: A process data variable that accepts an alphanumeric string with no spaces. Default Value: None Accepts 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?