Release notes for the Genesys Cloud data actions integration
This article describes all releases of the Genesys Cloud data actions integration.
February 21, 2024
- Velocity macros to escape JSON’s reserved characters
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.
August 9, 2023
- Limitation for JSON objects depth
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.
April 5, 2023
- Data actions performance summary view
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.
January 19, 2022
- Delete data actions support
Administrators can now select the HTTP DELETE method to remove data from the integrated service: Add configuration to custom actions for integrations.
February 24, 2021
- Velocity macro for dynamic keys
Administrators can now use the successTemplateUtils.moveKeysIntoArrayOfObjects macro to convert data into a format that is compatible with Architect: Velocity macros.
January 6, 2021
- FAQ about using data actions to perform actions on conversations
Added FAQ about the inability to use data actions to perform actions on conversations: Can I use Genesys Cloud data actions to perform actions on conversations?.
July 29, 2020
- TLS 1.1 protocol deprecation removal
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.
May 13, 2020
- TLS 1.1 protocol deprecation
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.
April 1, 2020
- TLS 1.0 protocol deprecation removal
On April 1, 2020, Genesys ended support of the TLS 1.0 protocol for data actions: Deprecation: TLS 1.0 for data actions.
March 18, 2020
- Escaping strings in data actions
Updated documentation to clarify the use of various escaping methods: Velocity macros for data actions and Request configuration for data actions.
February 19, 2020
- TLS 1.0 protocol deprecation
On April 1, 2020, Genesys will no longer support the TLS 1.0 protocol for data actions: Deprecation: TLS 1.0 for data actions.
August 7, 2019
- Action contracts interface updated
Administrators can now configure input and output contracts for actions through a simple user interface: Add contracts to custom actions for integrations.
February 27, 2019
- Error codes in data action responses
Added documentation about error codes in data action responses during testing: Data action fails during testing.
November 21, 2018
- Action configuration interface updated
Administrators can now configure requests for actions through a simple user interface: Add configuration to custom actions for integrations.
August 29, 2018
- Translation map defaults
Data actions are now configurable with translation map defaults: Response configuration for data actions.
April 18, 2018
- Import or export 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.
January 10, 2018
- Velocity macros
Updated documentation about the successTemplateUtils.firstFromArray macro: Velocity macros.
January 3, 2018
- Content list
Added list of all relevant content for the integration: Content list.
December 13, 2017
- Velocity macros
Added documentation about Velocity macros that you can use in templates for data actions: Velocity macros.
October 18, 2017
- Initial release of the Genesys Cloud data actions integration
The Genesys Cloud data actions integration provides static actions and allows you to create custom actions that use the Platform API. The Genesys Cloud data actions integration uses a Genesys Cloud OAuth client to authorize access to the Platform API (Genesys Cloud Developer Center).