Post Attachment activity

An activity that posts an attachment to a specified user or a group.

Configure the Post Attachment activity

To configure the Post Attachment activity, do the procedure in this topic.

Good to Know

To send an e-mail notification, click Advanced > E-mail Notifications .
For more information, refer to Configure E-mail Notifications for Any Activity.
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?
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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

On the Application Explorer screen, do one of these:
- Open a Process.
- Create a Process.
Do one of these:
- Add an activity:
  1. In the Process Builder, in the Activity Library open the Yammer tab.
  2. On the Yammer tab, drag the Post Attachment activity onto your process.
- Change an activity:
  1. In your process, double-click your activity.

General Configuration

Specifies the basic settings for the Post Attachment activity.

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

Post File Attachment to Yammer Configuration > Send Private Attachment

Specifies an attachment and a recipient.

Fields

Field Name	Definition
Yammer	Function: Specifies the access token that connects to Yammer. Accepted Values: A list of access tokens configured for your environment. Default Value: None Accepts Process Data Variables: No
Add Token	Opens this Screen: Access Token for Yammer Function of this Screen: Configure an access token to connect to Yammer.
Network Name	Function: Specifies the name of your Yammer network. Accepted Values: Read only. When you select the Yammer 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, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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.
Add File URL	Function: Specifies the location of the attachment file. Accepted Values: An absolute path and file name on the AgilePoint Server or SharePoint Server. Only one attachment is supported. Default Value: None Accepts Process Data 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	Function: Specifies the name of the process data variable that is used to store the response thread ID. 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, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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 File Attachment to Yammer Configuration > Post in a Group

Specifies a group to send an attachment..

Fields

Field Name	Definition
Yammer	Function: Specifies the access token that connects to Yammer. Accepted Values: A list of access tokens configured for your environment. Default Value: None Accepts Process Data Variables: No
Add Token	Opens this Screen: Access Token for Yammer Function of this Screen: Configure an access token to connect to Yammer.
Network Name	Function: Specifies the name of your Yammer network. Accepted Values: Read only. When you select the Yammer 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, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?
Group Name	Function: Specifies a group. Accepted Values: A valid group name from the list. Default Value: None Accepts Process Data Variables: Yes
Add File URL	Function: Specifies the location of the attachment file. Accepted Values: An absolute path and file name on the AgilePoint Server or SharePoint Server. Only one attachment is supported. Default Value: None Accepts Process Data 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	Function: Specifies the name of the process data variable that is used to store the response thread ID. Accepted Values: A process data variable that accepts an alphanumeric string with no spaces or special characters. 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, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?