As a user, I want to have the ability to lock or checkout flows so that other user will not be able to overwrite the flow the I am updating.
I have several instances where the latest update in the flow was overwritten by other users since they are the one who last updated their script which is using the flow that I am updating.
Instead of checking out and locking a flow, which is not great for multi-user collaboration, mabl allows anyone with edit permissions to start editing a test and will warn users about conflicting changes upon save. If you see a save conflict warning you can either proceed with your changes or decide to save your edits to a test branch first. Release notes
Changes saved to a test branch can be merged later, once you've had a chance to review other what changes have been made to the test prior to your edits. In general, we consider working with branches to be a better collaboration mechanism than locking artifacts during editing, which comes with its own set of challenges such items remaining in a locked state.