Limitations of the Genesys Cloud Function data actions integration

Genesys Cloud Function data actions offer flexibility but with significant limitations regarding security, support, and access to internal resources. Developers must carefully consider these limitations when designing and implementing custom functions. Thorough testing and robust error handling within the Lambda functions are crucial due to the limited support options.

Limitations of Genesys Cloud Function data actions are listed for your consideration:

  • Code security and support
    • No code scanning or anti-virus: Uploaded code is not subject to any security scans or anti-virus checks.
    • No warranties or support: Genesys provides no warranties regarding code safety or quality. Support for custom code is not provided.
    • Limited support options: For troubleshooting, enable Flow Playback data to recreate input scenarios in the data action test mode.
  • Code management and access
    • No code download: Uploaded code cannot be downloaded due to environmental security controls.
    • Limited access: Only the Functions service within your Genesys Cloud account can access and invoke your Lambda functions.
    • Limited access to AWS resources: Functions are restricted to internal processing and external internet access. They cannot directly access other AWS resources like DynamoDB, S3, or SQS.
    • Context limitations: Functions rely solely on the information provided in the data action request headers and body for context.
    • Genesys Cloud access: Access to Genesys Cloud is achieved through the public API, requiring developers to manage their own authentication within the Lambda function.
  • CX as Code implications
    • Support for CX as Code: Though there is no initial support for CX as Code, it will be supported in a future release.
    • Support for external code repositories: Due to restrictions on code downloads, future implementation may involve external code repositories such as GitHub and Bitbucket.
  • Network and security considerations
    • No static IP addresses: Functions do not have static IP addresses.
    • VPC and IP lists: Functions operate outside the traditional VPC, making static IP lists for data actions inapplicable.
    • mTLS support: Functions do not have access to Genesys Cloud data actions client certificates. For mTLS, you must implement your own certificate management within the Lambda function.