Invoke Function (AWS Lambda) activity

Configure the Invoke Function activity

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v9.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.
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 AWS Lambda tab.
On the AWS Lambda tab, drag the Invoke Function activity onto your process.

General Configuration

Specifies the basic settings for the Invoke Function 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:

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

Invoke Function Configuration > Request Mapping tab

Connects the request payload from AWS Lambda to the process schema.

Fields

Field Name	Definition
Amazon Web Services	Opens this Screen: Access Token for Amazon Web Services Function of this Screen: Configure an access token to connect to Amazon Web Services.
Create	Opens this Screen: Access Token for Amazon Web Services Function of this Screen: Configure an access token to connect to Amazon Web Services.
Function	Description: Specifies the name of the AWS Lambda function to execute. Allowed Values: A function name from the list. When you select the access token from the Amazon Web Services field, this field shows the function names associated with the access token. 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?
Enter Request Payload / Get Request Payload From This Variable	Description: Specifies how to connect the request data from AWS Lambda to the AgilePoint process schema. Allowed Values: Enter Request Payload – Specify a payload to use to connect to the process schema. In the text field, specify a payload in JSON format. Click Map Schema button to open the Schema Mapper screen. Use this screen to connect the payload values to the AgilePoint process schema. Get Request Payload From This Variable – Specifies a process data variable that stores the payload. The value of the process data variable must be in a valid JSON format. Default Value: Enter Request Payload 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?

Invoke Function Configuration > Response Mapping tab

Specifies where to store the response from AWS Lambda.

Fields

Field Name	Definition
Amazon Web Services	Opens this Screen: Access Token for Amazon Web Services Function of this Screen: Configure an access token to connect to Amazon Web Services.
Create	Opens this Screen: Access Token for Amazon Web Services Function of this Screen: Configure an access token to connect to Amazon Web Services.
Function	Description: Specifies the name of the AWS Lambda function to execute. Allowed Values: A function name from the list. When you select the access token from the Amazon Web Services field, this field shows the function names associated with the access token. 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?
Enter Response Payload / Store Response In This Variable	Description: Specifies where to store the response from AWS Lambda. Allowed Values: Enter Response Payload – Specifies a payload to use to map the response to the AgilePoint process schema. Click the Map Response button to open the Schema Mapper. Use this screen to connect the response to the data model for your process. . Store Response In This Variable – Select this option if you want to store the information from AWS Lambda to a variable in the AgilePoint NX app. In the text field, specify a variable that accepts an alphanumeric string in JSON format. Default Value: Enter Response Payload 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?