Working with Resource Locks
In Studio, a resource can be opened, locked, and modified starting with a right-click on the resource name in the Studio resource tree.
You can also lock and unlock all resources in TDV using a single configuration parameter. When Studio resource locking is enabled with this configuration parameter, resources must be unlocked before they can be edited. Studio resource locking is disabled by default. See the TDV Administration Guide for more information.
When a resource is locked, other developers working on the same TDV Server instance (or active cluster) can see that a lock has been placed on a resource or a resource tree node.
Note: Resource locking is not intended as a security feature. An administrator can protect defined resources by managing rights and privileges.
Administrators with the Modify All Users right, and resource owners, can revoke the Write privilege (modify) for specific resources, thereby preventing anyone from modifying those resource definitions.
Constraints on new resources in locked containers include the following:
• Only the user who locked a resource can modify that resource or save changes to it.
• Only the lock owner can create or destroy resources within a locked container.
• All resources within a locked container inherit the lock from the parent container, which in turn belongs to the original lock owner.
This section includes: