Architects prevents deletion if the item is a flow used by another flow or prompt. You cannot delete an item if it is a resource dependency for another item. For example, let’s assume Flow A includes a transfer to Flow B. If a flow author tries to delete Flow B, Architect returns an error message and fails the deletion attempt.
If you encounter a deletion error, perform a dependency search on the resource to determine if it is associated with another item. Remove the dependencies (in the example above, remove the Transfer to Flow B action from Flow A), and then delete the resource.
Every year, Genesys® orchestrates more than 70 billion remarkable customer experiences for organizations in more than 100 countries. Through the power of our cloud, digital and AI technologies, organizations can realize Experience as a Service℠, our vision for empathetic customer experiences at scale. With Genesys, organizations have the power to deliver proactive, predictive, and hyper personalized experiences to deepen their customer connection across every marketing, sales, and service moment on any channel, while also improving employee productivity and engagement. By transforming back-office technology to a modern revenue velocity engine Genesys enables true intimacy at scale to foster customer trust and loyalty.