Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.
  • 1.  Architect Flows: Unable to renumber identifiers

    Posted 07-18-2024 09:29
    No replies, thread closed.

    Hello,

    We're looking to use the action IDs in Architect flows. It says here that we can renumber IDs but I'm not seeing that option in our environment. Do I have to assign role/permission to myself or is there a global setting in the org?

    Thank you,


    #ArchitectureandDesign
    #Implementation
    #Unsure/Other

    ------------------------------
    Dianne
    ------------------------------


  • 2.  RE: Architect Flows: Unable to renumber identifiers
    Best Answer

    Posted 07-18-2024 09:35
    No replies, thread closed.

    That functionality was never released, the help doc page will be updated.



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



  • 3.  RE: Architect Flows: Unable to renumber identifiers

    Posted 07-18-2024 09:39
    No replies, thread closed.

    Hi Melissa,

    Thank you for your reply.

    Would you happen to know if there's a way to grab action IDs and use it within Architect?



    ------------------------------
    Dianne
    ------------------------------



  • 4.  RE: Architect Flows: Unable to renumber identifiers

    Posted 07-18-2024 10:17
    No replies, thread closed.

    No.  What are you wanting to use them for?



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



  • 5.  RE: Architect Flows: Unable to renumber identifiers

    Posted 07-22-2024 15:29
    No replies, thread closed.

    Dianne / Melissa,

    Firstly, I think it's important to understand that the numbers are merely unique identifiers, they don't dictate flow (like line numbers in old-school BASIC, for example) so there really shouldn't be a need to renumber per-se.

    However, what would be useful is to be able to grab the identity of the current, or the previous step (like you could in Handlers.) This would allow for steps used for logging result (like failures) to reference themselves (or their preceding, that presumably threw the error) without having to worry when Flows are exported / imported / copied, which can result in the IDs changing. (Currently, you have to hard-code them all and if you use the numeric IDs, go back in and edit everything if they change...)

    Just my 10 cents..



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