Locking elements

We will have a quick look at the locking mechanism of Orchestrator.

Getting ready

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.

How to do it...

There are only two options in the locking system.

Locking workflows

To lock a workflow, action, or package, follow these steps:

  1. Right-click on a workflow, action, or package.
  2. Navigate to Locking | Lock or Locking | Lock with dependencies. The Lock with dependencies option will lock all subworkflows and subactions that are used in this workflow.

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.

Unlocking workflows

Unlocking should be obvious now. However, note that there is no unlock with dependencies option, which means that you have to unlock each element by itself:

  1. Right-click on a locked workflow, action, or package.
  2. Navigate to Locking | Unlock.

How it works...

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.

See also

The Using the Locking System recipe in Chapter 8, Better Workflows and Optimized Working.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset