Update Record (Data Entities) activity

An activity that changes a record in AgilePoint NX entity.

Configure the Update Record activity

To configure the Update Record activity, do the procedure in this topic.

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX Private Cloud or AgilePoint NX OnPremises v7.0 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.
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:
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?

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 Data Entities tab.
On the Data Entities tab, drag the Update Record activity onto your process.

General Configuration

Specifies the basic settings for the Update Record 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 Record Configuration

Maps request data from your process to the AgilePoint NX entity field when you change a record. You can work with standard entities or custom entities.

Fields

Field Name	Definition
Standard Entities / Custom Entities	Function: Specifies whether to show standard (out-of-the-box) entities or custom entities in the Entity Name list. Accepted Values: Standard Entities - Shows standard (out-of-the-box) entities in the Entity Name list. Custom Entities - Shows custom entities in the Entity Name list. Default Value: Standard Entities
Entity	Function: Specifies the name for your entity from the list. Accepted Values: An entity name from the list. Default Value: None Example: Refer to: (Example) Store Data from an eForm in Data Entities with a Data Entities Activity
Record ID / Unique Record Field Value	Function: Specifies an ID or a value of the primary field for the record to change in an AgilePoint NX entity. Accepted Values: A record ID or a value of the primary field for the record from an AgilePoint NX entity. Default Value: None Accepts Process Data Variables: Yes Limitations: The Unique Record Field Value option is available in these releases: AgilePoint NX OnDemand (public cloud) AgilePoint NX Private Cloud or AgilePoint NX OnPremises v8.0 or higher.
Request Mapping	Function: Connects your process schema to the entity fields. Accepted Values: Click the Schema Mapping button to open the Schema Mapper screen. Use this screen to connect the request to the data model for your process. Default Value: None Example: Refer to: (Example) Schema Mapper
Store Record ID in This Variable	Function: Specifies the process data variable that stores the ID of a record you create or change. 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