Cisco Cisco Process Orchestrator 3.0 User Guide

For information about the property fields, see the online help.

Click Save 

 to save your changes.

Multiple users might be working together to develop processes that they plan to group into an automation 
pack. The Process Locking feature is designed to enforce limits on access to a process. You can lock one 
or more processes from the Process Orchestrator console.

Process Locking also includes these features:

The UI provides a filter for the process definition view to view processes locked by me, or processes 
locked by someone else.

The columns for these views show whether a process is locked, who has the lock, and since what 
date / time the lock has been held.

Locked processes:

Are read-only to other users.

Cannot be enabled or disabled by other users.

Can be added or removed from automation packs by other users because this action does not 
modify the configuration of the process itself.

That are locked by another user can be unlocked if you have Break Lock permissions (see 

During the editing process:

If User A attempts to edit a process that is currently locked by User B, User A receives a warning 
message and the process displays in Read-only mode.

If User A is editing a process, which is then locked by User B, User A receives an error message 
when attempting to save the process.

User A cannot delete a process that is currently locked by User B.

A confirmation dialog displays if you close the Process Orchestrator and there are still locked 
processes remaining.

Team content development is:

A way for users to lock processes when they are developing content along with other process authors

A new environment-wide setting which forces users to lock processes when editing them

Team content development is not:

Locking other object types