Reply To All activity

An activity that creates a message and addresses it to the sender and all recipients of the original message in Microsoft Outlook.


Reply To All activity

Configure the Reply To All activity

To configure the Reply To All 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 Process Builder, in the Activity Library, open the Exchange Server tab.

    Open Exchange Server tab
  3. On the Exchange Server tab, drag the Reply To All activity onto your process.

    Drag Reply To All activity

General Configuration

Specifies the basic settings for the Reply To All 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

Reply To All Configuration

Specifies the configuration that creates a message and addresses it to the sender and all recipients of the original message in Microsoft Outlook.

Figure: Reply To All Configuration screen

Reply To All 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.

Message ID

Function:
Specifies the ID of the Exchange Server message to which to reply.

The message ID comes from Exchange Server.

Accepted Values:
  • A valid message ID.
  • A process data variable.

    You can use Process Data screen to specify 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?

Reply Body

Function:
Specifies the content of the message.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data Variables:
Yes

Store Status of Message in this Variable

Function:
Specifies the process data variable that stores the status of the e-mail message such as reply sent or failed.
Accepted Values:
A process data variable that accepts an alphanumeric string that can have spaces.
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?