Yes, I know I can change the name of a flow anytime. Just can't remember if that is dynamically changed... meaning, if I change the flow name, is it changed in the other flows that reference it or do I need to go in an reselect the flow from the drop down list as I'm working in Architect?
Also, do you have any documentation regarding using Archy? This is the first I've heard of it. When trying to keep our code in sync between orgs and divisions, I've been exporting from our prod org to an i3 format, then importing the i3 file to our lower environment to make a new flow. Then I have to make about 100 changes manually to support the lower environment. We have two lower environments that I need to support this way. The process is very time consuming and prone to errors from the manually changes. I wish our vendor had developed the code in a more portable way so I could easily move code from one org/division to another.
Thank you,
Jackie
------------------------------
Jackie Maher
Health Equity
------------------------------
Original Message:
Sent: 08-29-2022 17:38
From: Melissa Bailey
Subject: Cleaning up old obsolete flows - suggestions need for best practice on this
Sorry, you can change the name of a flow any time.
The UI does not currently import .yaml files but you can use Archy to either create a new flow with config from the .yaml file or create a new version of an existing flow with it.
------------------------------
Melissa Bailey
Genesys - Employees
Original Message:
Sent: 08-29-2022 17:35
From: Jackie Maher
Subject: Cleaning up old obsolete flows - suggestions need for best practice on this
@Melissa Bailey - Can you restate your last comment. I'm not following. I'm thinking you are saying to rename a flow, but I'm not sure.
Also Melissa, if I export it as.yaml. Can I import it back into Genesys as a inbound call flow or secure call flow, if there was some obscure reason I had to? I thought only i3 format was importable as usable code.
Thank you,
Jackie
------------------------------
Jackie Maher
Health Equity
Original Message:
Sent: 08-29-2022 17:23
From: Melissa Bailey
Subject: Cleaning up old obsolete flows - suggestions need for best practice on this
I'd export them as .yaml instead of .i3 format. If you want to know what's in a .i3 file, you would need to create a new flow and import the config. You can look directly at a .yaml file and see what's in it (disclaimer: I'm not saying it will be as easy to understand as the UI).
Just making sure, you know you can the name of a flow any time you want, right? And that you can see the dates each version of a flow was published?
------------------------------
Melissa Bailey
Genesys - Employees
Original Message:
Sent: 08-29-2022 16:13
From: Jackie Maher
Subject: Cleaning up old obsolete flows - suggestions need for best practice on this
Hi All,
We have many old inbound and secure flows in Architect that we no longer used. I'm thinking of exporting them as a i3iboundCallFlow and i3SecureCallFlows files to a network drive, just to have as a back up, but then deleting the source code from Architect. Not sure if this is the best process to follow, but I don't see any other way within Genesys to archive old flows. I know Genesys does its own versioning of flows, but we have change the flows names to correspond to the release dates of the flows, so the build in does not help us with this clean up effort.
I'm looking for suggestions on how others manage their old, obsolete flows. Thank you,
Jackie
#Unsure/Other
------------------------------
Jackie Maher
Health Equity
------------------------------