When you create a new element, it is locked automatically for you.

In order to lock an element, you must have Write access rights to it. For details, see Assigning and Managing Permissions for Elements.

When you lock an element, Designer obtains and locks the latest version of the element that has been saved on the webMethods Integration Server.

Elements generated by a service (including an adapter service) are not locked automatically.

When you select multiple elements to lock, some elements in the selection may not be available to lock because they may be system locked, locked by another user, elements to which you do not have Write access, or elements that cannot directly be locked. Designer will notify you that these elements cannot be locked and will lock the rest.

When you lock an adapter notification, Designer also locks its associated publishable document type. You cannot directly lock the publishable document type associated with an adapter notification.

When you lock a folder or package, you only lock existing, unlocked elements within it. Other users can still create new elements in that folder or package.

When you lock a Java or C/C++ service, Designer locks all other Java or C/C++ services within the folder. This means that other users cannot create Java and C/C++ services in a folder or package that contains the Java or C/C++ services. To create these services, all existing Java and C/C++ services in the folder must be unlocked and the user must have Write access to all Java and C/C++ services in the folder. For details, see Guidelines for Locking Java and C/C++ Services.

You cannot lock a listener or connection element.