Loading...
Loading...
Loading...
This article describes all releases of the web services 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 use a mTLS certificate associated with the location of a Genesys Cloud organization in Singapore or Mexico: mTLS support for data actions.
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 a mTLS certificate associated with the location of a Genesys Cloud organization in Osaka, Zurich, or UAE: mTLS support for data actions.
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.
Administrators can now configure web services data actions to utilize a client certificate signed by Digicert as the certificate authority in the mTLS process: Add a data actions integration and Is the mutual TLS (mTLS) certificate publicly trusted?.
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.
Added documentation for errors that can occur when non-JSON type is used as Accept header: Data action returns a 400 error, Data action fails during testing and Add configuration to custom action integrations.
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 a mTLS certificate associated with the location of a Genesys Cloud organization in Mumbai: mTLS support for data actions.
Administrators can now use the successTemplateUtils.moveKeysIntoArrayOfObjects macro to convert data into a format that is compatible with Architect: Velocity macros.
Added FAQ about list of trusted root certificates for web services data actions: Which root certificates are trusted for web services data actions?.
Added documentation about certificate errors when testing web services data actions: Data action fails during testing.
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.
Administrators can now use a mTLS certificate associated with the location of a Genesys Cloud organization in Canada, Seoul, or London: mTLS support for data actions.
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, Request configuration for data actions, How to use the User Defined credential type, and How to use the User Defined (OAuth) credential type.
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 data actions service now supports the use of mTLS authentication for increased security: mTLS support and Security.
Administrators can now retrieve and add IP addresses to allowlists: IP addresses for the firewall allowlist.
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.
Data actions are now configurable with translation map defaults: Response configuration for data actions.
Data actions can now be reused across Genesys Cloud organizations by exporting contracts and configuration from one data action for import into another data action: Import or export a data action.
Added documentation about custom actions failing due to transfer encoding: Custom action fails for unexpected reason.
Updated documentation about required port: Requirements.
Updated documentation about the successTemplateUtils.firstFromArray macro: Velocity macros.
Added list of all relevant content for the integration: Content list.
The integration now supports different credential types and authentication workflows for your web service: Credential types.
Added documentation about Velocity macros that you can use in templates for data actions: Velocity macros.
The web services data actions integration allows you to create custom actions that you can then use throughout Genesys Cloud to interface with JSON-based web services. If you currently use the web services data dip connector that runs on the Genesys Cloud Bridge Server, consider switching to this new integration that runs as a Genesys Cloud service: web services data actions integration.
Get user feedback about articles.