If you've replaced a microflow with newer functionality, how can you test the new version without deleting the old one?

Testing a new version of a microflow while keeping the old one intact can be accomplished in different ways. One effective method is to exclude the old microflow from the project. By doing this, you can ensure that it is not executed, allowing you to test the new functionality without interference from the previous version. This means you can assess how the new functionality performs under the same conditions without having to delete or alter the original microflow significantly.

Excluding the microflow ensures that it does not clutter your testing process and makes it straightforward to revert back or switch between versions if necessary. It allows for a clean testing environment where the functionality of the new version can be fully evaluated.

Other options, such as disabling or archiving the old microflow, may not provide the same level of flexibility during testing. Disabling the old microflow will stop it from being executed but still keeps it in the project, which may lead to confusion or the potential for accidental re-enablement. Archiving is typically used for keeping versions for historical purposes, yet it could also be cumbersome when it comes to quick testing iterations. Renaming the old microflow would still leave it in the project and running if mistakenly called, which might not provide a clear testing scenario for the new