plmcgrn | 2024-10-30 15:12:23 UTC | #1
We often have a design pattern where logic is in an Inbound Flow reusable task, but we later desire to be a common module so we can use it in multiple flows. Is there a way to migrate a flow task to a module task, short of manually copying every architect step configuration by hand?
crespino | 2024-10-30 16:07:31 UTC | #2
Today the only way I can think to make this process less tedious is to use our Archy developer tool to export the flow as a YAML file, cut out what you don't need, and then import what's left as a Common Module.
I would also suggest that you open an Idea on the Genesys Cloud Ideas Portal and suggest that UI functionality be added to save a Reusable Task as a Common Module.
plmcgrn | 2024-10-30 18:34:09 UTC | #3
Bummer, OK. Yeah, I was hoping it wouldn't be the case, but understood. Thankfully the flow I'm currently working on only had about 15 architect steps that needed copying, but I will assess doing manual YAML moves and open an idea on this on Aha if one doesn't exist. I'll edit this comment with a link to that idea either way.
Edit: Idea here https://genesyscloud.ideas.aha.io/ideas/SSAAOB-I-218
system | 2024-11-30 18:29:24 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 30127