We will have a quick look at the locking mechanism of Orchestrator.
For locking workflows, we need a workflow that we can use to lock, primarily, a workflow that calls other actions or workflows. If you don't have one in hand, use the 06.06.01 Using Asynchronous Workflows
example workflow.
There are only two options in the locking system.
To lock a workflow, action, or package, follow these steps:
Notice that the little lock icon on the item you have locked; you will not be able to edit this workflow anymore. However, you are still able to run it.
Locking locks the edit mode of a workflow, which marks it as not accessible. Anyone with Admin rights can place or lift a lock.
A lock disables Edit, Delete, Synchronize, and Move. Locks cannot be exported.
Workflow locking actually has nothing to do with the locking system (see the Using the locking system recipe in Chapter 8, Better Workflows and Optimized Working). Workflow locking locks workflows and actions, whereas the locking system locks resources.
Locks can be useful in a production environment where one wants to make sure that an important production workflow can't be altered.
The Using the Locking System recipe in Chapter 8, Better Workflows and Optimized Working.