Release notes for the Microsoft Dynamics 365 data actions integration

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.

Limitation for JSON objects depth

Genesys Cloud now limits the depth of JSON objects to 50 levels within data action requests and responses. This limit helps to maintain the performance of the data action service: Add configuration to custom actions for integrations and Request configuration for data actions.

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.

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.

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.

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.

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.

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.

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.

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.

mTLS authentication
The data actions service now supports the use of mTLS authentication for increased security: mTLS support and Security.

IP addresses for outbound data action traffic
Administrators can now retrieve and add IP addresses to allowlists: IP addresses for the firewall allowlist.

Application registration changes
Updated documentation about enabling the application to be a public client: Register the integration in Azure Active Directory.

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.

Error codes in data action responses
Added documentation about error codes in data action responses during testing: Data action fails during testing.

Action configuration interface updated
Administrators can now configure requests for actions through a simple user interface: Add configuration to custom actions for integrations.

Translation map defaults
Data actions are now configurable with translation map defaults: Response configuration for data actions.

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.

Velocity macros
Updated documentation about the successTemplateUtils.firstFromArray macro: Velocity macros.

Content list
Added list of all relevant content for the integration: Content list.

Velocity macros
Added documentation about Velocity macros that you can use in templates for data actions: Velocity macros.

Initial release of the Microsoft Dynamics 365 data actions integration
The Microsoft Dynamics 365 data actions integration runs as a Genesys Cloud service. The integration provides static actions and allows you to create custom actions that you can use to act on data in Microsoft Dynamics 365. The integration replaces the previous Microsoft Dynamics CRM data dip connector that ran on the Genesys Cloud Bridge Server: Microsoft Dynamics 365 data actions integration.