All,

Hoping the experts here have a solution for this.

We discovered that it seems when using Common Modules, the calling architect flow takes a snapshot of the Common Module version at the time of publish (the Architect calling flow publish). Work with common module flows - Genesys Cloud Resource Center 

If later you modify the Common Module, ANY flow that references a Common Module continues to leverage the previous/same Common Module. It does not dynamically update to the latest Common Module version published. Is this correct? If so, are there are work arounds? If we have 50 flows that call a common module, do we really have to republish each of them every time we update the common module?

Hoping there is a work around on this or we're incorrect. :)

Thanks all,

Shane

Yes, no*, yes.  There's an idea for that: https://genesyscloud.ideas.aha.io/ideas/SSA-I-363

*It's not a workaround, but you can use archy if you don't want to click buttons in the UI.  Export the calling flow, then publish it.  Archy will insert the updated common module during the publish.  Use a loop to do it for all 50 of your flows.
https://developer.genesys.cloud/devapps/archy/

------------------------------
Melissa Bailey
Genesys - Employees

Original Message:
Sent: 02-23-2024 11:48
From: Shane Jenkins
Subject: Common Module behavior confirmation

All,

Hoping the experts here have a solution for this.

We discovered that it seems when using Common Modules, the calling architect flow takes a snapshot of the Common Module version at the time of publish (the Architect calling flow publish). Work with common module flows - Genesys Cloud Resource Center 

If later you modify the Common Module, ANY flow that references a Common Module continues to leverage the previous/same Common Module. It does not dynamically update to the latest Common Module version published. Is this correct? If so, are there are work arounds? If we have 50 flows that call a common module, do we really have to republish each of them every time we update the common module?

Hoping there is a work around on this or we're incorrect. :)

Thanks all,

Shane

#ArchitectureandDesign
#Routing(ACD/IVR)

------------------------------
Shane
------------------------------

All,

Hoping the experts here have a solution for this.

We discovered that it seems when using Common Modules, the calling architect flow takes a snapshot of the Common Module version at the time of publish (the Architect calling flow publish). Work with common module flows - Genesys Cloud Resource Center 

If later you modify the Common Module, ANY flow that references a Common Module continues to leverage the previous/same Common Module. It does not dynamically update to the latest Common Module version published. Is this correct? If so, are there are work arounds? If we have 50 flows that call a common module, do we really have to republish each of them every time we update the common module?

Hoping there is a work around on this or we're incorrect. :)

Thanks all,

Shane

Yeah, this is a big problem for us. We have a lot of work for a small change in one big flow.

Att,

All,

Hoping the experts here have a solution for this.

We discovered that it seems when using Common Modules, the calling architect flow takes a snapshot of the Common Module version at the time of publish (the Architect calling flow publish). Work with common module flows - Genesys Cloud Resource Center 

If later you modify the Common Module, ANY flow that references a Common Module continues to leverage the previous/same Common Module. It does not dynamically update to the latest Common Module version published. Is this correct? If so, are there are work arounds? If we have 50 flows that call a common module, do we really have to republish each of them every time we update the common module?

Hoping there is a work around on this or we're incorrect. :)

Thanks all,

Shane