Version Control
If your use case is already published, here's how you can make edits without modifying the existing experience.
![Launch Process Launch Process](/static/fd4c2fef195fa2c4f6c2871d3ffa1e3d/c6bbc/launch-process.png)
Editing your use-case
- Take your live use-case & add yourself to the blocklist. The blocklist will prevent you from seeing the use-case in production. The blocklist can be found under the "Launch" tab in Queries, Paths, and Events workspaces
Make all your staging edits to this duplicated use-case.
![Launch Block Launch Block](/static/3b7fc6302fd74beb7c677f16a1c2ec6b/c6bbc/version_control_block.png)
- Rebuild your use case exactly as the original and only allowlist yourself. Add a
[Dev]
tag in front of the name.Make all your staging edits to this duplicated use-case.
![Launch Block Launch Block](/static/258b9627304d57f49113c1c9c2a8ba0f/c6bbc/version_control_dev.png)
- Deploy your use case, allowlisting ONLY yourself.
![Launch Block Launch Block](/static/6bb92c2ec6d9f7e97aa58a0f12403e61/c6bbc/version_control_blocklist.png)
Once your edit is complete, disable the old flow & launch your updated one.
In future releases, Moveworks will make it easier for you to duplicate existing use-cases.