Genesys Cloud - Main

Hi Community,

How do your teams manage version control for Architect flows?

Do you:

• Export flows regularly?
• Keep documentation outside Genesys Cloud?
• Use Git to store exported configurations?

I'm interested in understanding different governance approaches.

#ArchitectandDesign

------------------------------
Fausto Brito
------------------------------

Hi Fausto,

Great question.

In our environment, we mainly rely on Architect's built-in version history for tracking changes. For major updates, we also export the flow before publishing so we have a rollback copy if needed.

At this stage, we don't use Git for Architect flows, so I'd be interested to hear how other organizations manage version control and governance for larger Architect environments.

------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------

Hi Fausto,

I do a manual backup every 3 monthes. With every change on a Flow I update the beginning of the name of the flow to the current year and month (for example: "2607 Testflow"). With that I exactly know which flows I have to backup.

------------------------------
Christoph Domaschke
Produktmanager Kunden-Dialog-Center
------------------------------

Hello Fausto,

We are managing it from 2 aspects:

1. Rely on Architect's built-in version history for tracking changes.
2. Since we use CX as Code,  we are also using GitHub versioning feature to keep the copies.

Regards

Jyoti

------------------------------
Jyoti Sharma
Senior Design Consultant
------------------------------

We use TFE VCS/Github, however I keep versioning in flows name in TF code (easy rollback by flow association). With Terraform if you have to redeploy (various reasons) the versioning increases on Genesys side with no real impact. In flows you can add comments per version.

------------------------------
Bogdan Simaciu
------------------------------

Hello, Fausto!

At the moment, we primarily rely on the native versioning capabilities available in Genesys Cloud Architect, which work well for maintaining history and restoring previously published versions.

However, I have been considering adopting external version control with Git, using GitHub or Bitbucket, mainly for two reasons:

1. Genesys Cloud still does not provide a native and practical way to compare changes in detail between two flow versions.

2. With Archy, storing YAML files in a Git repository would make it easier to manage artifacts, review changes, and deploy specific versions across different environments or organizations.

I believe a hybrid approach would be the most appropriate: using Architect's native version history for operational management and rollback, while Git would provide an additional layer of governance, traceability, collaboration, and deployment automation.

__________________________________________________________________________________________________________________________________________________________________

Olá, Fausto!

Atualmente, utilizamos principalmente o versionamento nativo do Genesys Cloud Architect, que atende bem ao controle e à recuperação das versões publicadas.

No entanto, tenho avaliado a adoção de um versionamento externo com Git, utilizando GitHub ou Bitbucket, principalmente por dois motivos:

1. O Genesys Cloud ainda não oferece uma forma nativa e prática de comparar detalhadamente as alterações realizadas entre duas versões de um fluxo.

2. Com o uso do Archy, manter os arquivos YAML em um repositório Git facilitaria o controle dos artefatos, a revisão das mudanças e o deploy de versões específicas entre diferentes ambientes ou organizações.

Acredito que uma abordagem híbrida seja a mais adequada: manter o histórico nativo do Architect para operação e rollback, enquanto o Git seria utilizado como camada adicional de governança, rastreabilidade e automação de deploy.

------------------------------
Matheus Mendonca
------------------------------