Update Email Design activity

An activity that changes an email design in Twilio SendGrid.

Configure the Update Email Design activity

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX Private Cloud or AgilePoint NX OnPremises v8.0 Software Update 2 or higher.

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 Twilio SendGrid tab.
On the Twilio SendGrid tab, drag the Update Email Design activity onto your process.

General Configuration

Specifies the basic settings for the Update Email Design 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

Update Email Design Configuration

Specifies the information about an email design to change in Twilio SendGrid.

Fields

Field Name	Definition
Twilio SendGrid	Function: Specifies the access token that connects to your Twilio SendGrid service. Accepted Values: A list of access tokens configured for your environment. Default Value: None
Create	Opens this Screen: Access Token for Twilio SendGrid Function of this Screen: Configure an access token to connect to Twilio SendGrid.
Email Design Name Or ID	Function: Specifies the name or ID of the email design to change in Twilio SendGrid. Accepted Values: An email design name from the list. When you select the access token from the Twilio SendGrid field, this field shows the email design names associated with the access token. An alphanumeric string that represents an email design ID. The email design ID comes from Twilio SendGrid. 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?
Design Name	Function: Specifies the name of the email design to create in Twilio SendGrid. Accepted Values: One line of text (a string) that can have letters, numbers, spaces, and 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. 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?
Subject	Function: Specifies the subject line for your email design. Accepted Values: One line of text (a string) that can have letters, numbers, spaces, and special characters. Default Value: None Accepts Process Data Variables: Yes
HTML Body	Function: Specifies the content for the email design in HTML format. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: Yes
Generate Plain Text Body	Function: Specifies whether to enter the text to create an email design in plain text format. Accepted Values: Deselected - Specifies the text to use to create the email design in plain text format. Selected - Creates the email design in plain text format from the content specified in the HTML Body field. Default Value: Selected
Plain Text Body	Function: Specifies the content for the email design in plain text format. To Open this Field: On the Create Email Design Configuration screen, deselect Generate Plain Text Body. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: Yes
Categories	Function: Specifies one or more categories for the email design that are used to count or track emails in Twilio SendGrid. Accepted Values: One line of text (a string) that can have letters, numbers, spaces, and special characters. The line of text represents one or more categories, separated by semicolons (;). If the categories entered in this field do not exist in your Twilio SendGrid environment, when this activity runs, the activity creates the categories and adds them to the email design. 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?