Edit a complex library structure

If updating a library version requires a series of invalid interim changes to accomplish the desired final result, you must lock the parent version before making the changes.

When you lock a version, it prevents other users from making changes to the structure of the version or changes to the objects in the version that would result in changes to the version's structure. The following operations are not available when a version is locked:

• Refactor
• Remove from
• Update to
• Create new instance
• Add to

For example, when the version is locked, users cannot add an object such as a topic to the version or remove it, but can edit the topic or add it to a map already in the version.

Once the version is locked, you can perform the operations needed to accomplish the desired final result, and then you release the version. Before the changes are released to the repository, the final results are verified for:

• Version conflicts
• Key changes
• Invalid objects
• Status changes

If any errors are discovered, a dialog box displays the issues that must be resolved before the release can proceed. If no errors are found, all versions affected by the changes are locked, all the changes are applied including status changes and key changes, and the container is updated.

When you need to use the Library Dependency Editor to perform a series of invalid interim changes to accomplish a desired final result, you must look at the changes you need to make and identify the parent version common to all the versions being edited and open that parent as the focus library in the Library Dependency Editor. For example, in the following figure the parent version containing the proposed changes is the Prod Y v1 version and, therefore, should be opened in the Library Dependency Editor as the focus library.

To lock a version:

1. In the Dynamic Release Management view, right-click the version you need as the focus library and select Open With > Library Dependency Editor.
2. Right-click the library version and click Lock.
3. Make the required changes.
4. Right-click in the Library Dependency Editor and click Release all.

   If errors are found in the result, they are displayed in the Release All Libraries dialog box. These errors must be resolved before the version can be released. To assist in resolving the errors, you can click the following:

   • Save: to save the list of errors in a tab-separated (TSV) file.
   • Locate: to open the list of errors in the Search Results view.
   • Copy: to copy the name and ID of the selected version.
   • Show In Graph: to display a dependency graph of the results.
5. If no errors are discovered, the Validation Graph opens and displays all the changes that will occur once the version is released. Click Next.
6. In the Release dialog box, add a comment describing the change and click OK.