C
Coral reef Boa
I have been struggling with proper workflow maintenance and testing. My customers are all on Workflow A, but if I want to make a feature update or troubleshoot an odd issue, I would need to update the 'Production' workflow. With that brings the potential to break the live version and any execution that may occur while I'm working on the workflow.
The Clone function is recommended by documentation, but does not fit this use-case for a couple of reasons.
  1. If I clone to the same Org, it only copies the top-level parent workflow. If I need to make changes to a sub-workflow, I would also need to clone that. This creates multiple versions that then need to be maintained and cleaned-up. For example, I now have 5x of one type of workflow after I cloned back-and-forth one too many times without knowing the consequences.
  2. If I clone to a 'Test' Org, that is going to break specific permissions that may be setup where the workflow needs to run from the Parent Org. While these can be individually adjusted as a workaround, it's not clean and creates a lot more overhead to get to a place of testing.
There needs to be a way to completely sandbox the workflows, with proper versioning and functionality to promote changes to the Production workflow.