Find Task activity

An activity that finds a task in Microsoft Outlook.

Configure the Find Task activity

To configure the Find Task 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 Find Task activity onto your process.

General Configuration

Specifies the basic settings for the Find Task activity.

Good to Know

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

Fields

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

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 Task Configuration

Specifies the configuration to find a task in Microsoft Outlook.

Fields

Field Name	Definition
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	Opens this Screen: Access Token for Exchange Server Function of this Screen: Configure an access token to connect to Exchange Server.
Task ID	Function: Specifies the ID of the task in Exchange Server. The task ID comes from Exchange Server. Accepted Values: A valid task 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?
Task Subject	Function: Specifies the process data variable that stores the subject of the Exchange Server task. Accepted Values: A process data variable. Default Value: None Accepts Process Data Variables: Yes
Task Body	Function: Specifies the process data variable that stores the body of the Exchange Server task. Accepted Values: A process data variable. Default Value: None Accepts Process Data Variables: Yes
From Date	Function: Specifies the process data variable that stores the start date and time of the Exchange Server task. Accepted Values: A process data variable. Default Value: None Accepts Process Data Variables: Yes
To Date	Function: Specifies the process data variable that stores the date and time the Exchange Server task completes. Accepted Values: A process data variable. Default Value: None Accepts Process Data Variables: Yes
Task Status	Function: Specifies the process data variable that stores the status of the Exchange Server task. Accepted Values: A process data variable. 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?