Genesys Cloud - Main

 View Only

Discussion Thread View
  • 1.  Common Module behavior confirmation

    Posted 02-23-2024 11:48

    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
    ------------------------------


  • 2.  RE: Common Module behavior confirmation

    GENESYS
    Posted 02-23-2024 12:11

    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
    ------------------------------



  • 3.  RE: Common Module behavior confirmation

    Posted 02-23-2024 15:45
    Edited by Paul Simpson 02-26-2024 10:05

    There are two problems with the mass re-publish approach.

    Firstly, there is the problem of quantity of work, which as Melissa has said, can potentially be mitigated using Archy.

    Secondly, and perhaps more significantly, there is the problem that if any flow that calls the Common Module is in a state of current development, you may not be in a position to want to republish it at the current time.

    Please review the Idea Melissa linked to and comment / vote. Personally, I prefer the wording of the Merged Idea https://genesyscloud.ideas.aha.io/ideas/INB-I-1689 as I don't think the publishing of dependent flows should even enter into the discussion!



    ------------------------------
    Paul Simpson
    Views expressed are my own and do not necessarily reflect those of my employer.
    ------------------------------



  • 4.  RE: Common Module behavior confirmation

    Posted 02-23-2024 12:44

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

    Att,



    ------------------------------
    Breno Canyggia Ferreira Marreco
    https://www.linkedin.com/in/brenocfm-40b62182/
    ------------------------------



  • 5.  RE: Common Module behavior confirmation

    Posted 02-26-2024 10:49

    All,

    Thanks for the quick responses. Sounds like while Archy is a possible work-around to republish flows that leverage the common module, it still indeed requires a re-publish of any flow that uses a common module. I did up-vote the Idea for common module handling/improvement.

    Hopefully something can be done soon to make this process more graceful. 

    Thanks again,

    Shane



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



Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources