Loading...
Loading...
Loading...
This article describes all releases of the AWS Lambda data actions integration.
Administrators can now view relationships and dependencies between Genesys Cloud objects, including integrations, data actions, and Architect flows. This feature helps administrators understand the impact of changes and determine whether an object can be safely modified or removed: View Genesys Cloud object dependencies for integrations, data actions, and flows.
Administrators can now configure the execution timeout setting for data actions. The timeout can be set between 1 and 60 seconds, with a default of 60 seconds. When an HTTP request runs longer than the configured time, the data action returns a timeout response. This feature helps improve control over data action timeouts, prevents long-running processes, and reduces unnecessary concurrency usage: Add configuration to custom actions for integrations and How many seconds before a data action times out?.
Administrators can now use the esc.jsonEncode and esc.jsonDecode to escape JSON’s reserved characters in the output: Velocity macros and URI (URL) form encoding for data actions.
Genesys Cloud now limits the depth of JSON objects to 50 levels within data action requests and responses. This limitation helps to maintain the performance of the data action service: Add configuration to custom actions for integrations and Request configuration for data actions.
Administrators can now visualize the performance and failure rates of data actions: Data Actions Performance Summary view, Data Actions Performance Detail view and Data actions integration performance analysis.
Administrators can now select the HTTP DELETE method to remove data from the integrated service: Add configuration to custom actions for integrations.
Administrators can now use the successTemplateUtils.moveKeysIntoArrayOfObjects macro to convert data into a format that is compatible with Architect: Velocity macros.
The AWS Lambda integration now supports cross-region invocations. Administrators can invoke Lambdas that exist in a different AWS region from their Genesys Cloud organization as data actions. For more information, see the AWS Lambda tab in Add configuration to custom actions for integrations.
Added documentation to explain how to use example code for a AWS Lambda function and a data action that executes the function: Example AWS Lambda function with a data action.
On July 29, 2020, Genesys ended the ability to connect to Genesys Cloud with the TLS 1.1 protocol. Data actions can still connect to REST endpoints with the TLS 1.1 and TLS 1.3 endpoints: Deprecation: TLS 1.1 protocol.
On July 29, 2020, Genesys will remove the ability to connect to Genesys Cloud with the TLS 1.1 protocol: Deprecation: TLS 1.1 protocol.
On April 1, 2020, Genesys ended support of the TLS 1.0 protocol for data actions: Deprecation: TLS 1.0 for data actions.
Updated documentation to clarify the use of various escaping methods: Velocity macros for data actions and Request configuration for data actions.
On April 1, 2020, Genesys will no longer support the TLS 1.0 protocol for data actions: Deprecation: TLS 1.0 for data actions.
The AWS Lambda data actions integration now automatically adds an invocation context object on data actions: Add configuration to custom actions for integrations.
Updated documentation to explain how to securely use AWS Lambda data actions in Genesys Cloud to retrieve data from on-premises solutions and then use that data in various Genesys Cloud applications: Data actions with on-premises solutions overview, Workflow for data actions with on-premises solutions, and Example AWS Lambda data action with on-premises solution.
Administrators can now configure input and output contracts for actions through a simple user interface: Add contracts to custom actions for integrations.
Added documentation about error codes in data action responses during testing: Data action fails during testing.
Administrators can now configure requests for actions through a simple user interface: Add configuration to custom actions for integrations.
The AWS Lambda data actions integration allows you to create custom actions that you can then use throughout Genesys Cloud to directly invoke AWS Lambda functions in your AWS account: About the AWS Lambda data actions integration.
Get user feedback about articles.