Post Message activity

An activity that posts a private message to a specified user or a community.

Configure the Post Message activity

To configure the Post Message 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 Viva Engage tab.
On the Viva Engage tab, drag the Post Message activity onto your process.

General Configuration

Specifies the basic settings for the Post Message 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

Post Message Configuration > Send Private Message tab

Configures a message to send to a specified user.

Post Message to Yammer Configuration Send Private Message tab — Figure: Post Message Configuration > Send Private Message tab

Fields

Field Name	Definition
Viva Engage	Description: Specifies the access token that connects to Viva Engage. Allowed Values: A list of access tokens configured for your environment. Default Value: None Accepts Variables: No
Create	Opens this Screen: Access Token for Viva Engage Function of this Screen: Configure an access token to connect to Viva Engage.
Network Name	Description: Specifies the name of your Viva Engage network. Allowed Values: Read only. When you select the Viva Engage access token, the associated network name shows in the Network name field. Default Value: None 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?
Select Users	Function: Specifies the users from the user list.
Message	Description: Specifies the content of the message. Allowed Values: More than one line of text. Default Value: None Accepts Variables: Yes
Add File URL	Description: Specifies the location of the attachment file. Allowed Values: An absolute path and file name on the AgilePoint Server or SharePoint Server. Only one attachment is supported. Default Value: None Accepts Variables: Yes Example: c:\My Documents\sample1.doc ${HomeDirectory}\sample2.doc http://demo3:8000/DocumentLib1/sample3.doc
Store the Response Thread ID in Custom Attribute or Schema	Description: Specifies the name of the process data variable that is used to store the response thread ID. Allowed Values: A process data variable. 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?

Post Message Configuration > Post in a Community tab

Sets up a message to send to a specified community..

Post Message to Yammer Configuration Post in a Group tab — Figure: Post Message Configuration > Post in a Community tab

Fields

Field Name	Definition
Viva Engage	Description: Specifies the access token that connects to Viva Engage. Allowed Values: A list of access tokens configured for your environment. Default Value: None Accepts Variables: No
Create	Opens this Screen: Access Token for Viva Engage Function of this Screen: Configure an access token to connect to Viva Engage.
Network Name	Description: Specifies the name of your Viva Engage network. Allowed Values: Read only. When you select the Viva Engage access token, the associated network name shows in the Network name field. Default Value: None 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?
Community Name	Description: Specifies a community. Allowed Values: A valid community name from the list. Default Value: None Accepts Variables: Yes
Message	Description: Specifies the content of the message. Allowed Values: More than one line of text. Default Value: None Accepts Variables: Yes
Add File URL	Description: Specifies the location of the attachment file. Allowed Values: An absolute path and file name on the AgilePoint Server or SharePoint Server. Only one attachment is supported. Default Value: None Accepts Variables: Yes Example: c:\My Documents\sample1.doc ${HomeDirectory}\sample2.doc http://demo3:8000/DocumentLib1/sample3.doc
Store the Response Thread ID in Custom Attribute or Schema	Description: Specifies the name of the process data variable that is used to store the response thread ID. Allowed Values: A process data variable that accepts an alphanumeric string with no spaces or special characters. 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?