Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

What resources are not exported in CX as Code

  • 1.  What resources are not exported in CX as Code

    Posted 06-05-2025 18:29

    alex7 | 2024-02-02 20:26:27 UTC | #1

    For genesyscloudtfexport, what CX entities are not supported? I already know that flows are not.

    Is there a list?

    Zino_Onokpise | 2024-02-05 18:37:37 UTC | #2

    Hi alex7,

    The flow definition is exported, but the actual flow file (.yaml) is not, you have to manage that using Archy. Script (.json) and user prompt (.wav) files are automatically exported by the CX as Code genesyscloudtfexport resource. As for what's exported, please see: https://registry.terraform.io/providers/MyPureCloud/genesyscloud/latest/docs,

    alex7 | 2024-02-06 21:28:40 UTC | #3

    I looked through that earlier and couldn't find any such list. But I assume it is any resource listed except for the flow implementation/yaml.

    John_Carnell | 2024-02-06 21:36:03 UTC | #4

    Hi Alex,

    Any resource currently available n CX as Code is exportable. However, as ZIno was eluding too:

    • Architect Flow Configuration will be exported from CX as Code but the actual architect flow will not. You will need to use the Archy CLI.
    • You can export integration credentials, but Genesy Cloud does not allow you to export the actual token or user/password in the credential.
    • We have several resources not yet implemented in CX as Code. As those resources become available they should be exportable.

    Thanks, John Carnell Director, Developer Engagement

    system | 2024-03-07 21:36:23 UTC | #5

    This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 24462



Related Content