Editing objects in CCMS Web

In the IXIA Dynamic Release Management module, IXIA CCMS Web automatically forks in some situations so that users do not need to decide whether to fork or edit.

When editing objects in CCMS Web, the behavior of CCMS Web can depend on the following factors:

Situation in CCMS Web Effect
The status of the object If an object is already in an end status (for example, Authoring:done), it might automatically fork if users move it back to Authoring:work in a Development or Maintenance Branch.
The status of the Branch Branches in Delivery or Closed status do not allow editing or objects to change status. Objects in Branches restricted through content level security also prevent editing.

Changes to objects shared with these Branches cause the objects to automatically fork in other Branches.
The context of the object Objects have a context when you access them through an assignment or a map. Objects found through search or Dependencies view do not have a context map except when already checked out.

If there is no context map, you have to pick one. An object automatically forks only if:

  • There is only one editable map to make changes in
  • The context map is in a Branch that might require it, for example a Maintenance Branch
The access rights of the user If users have the access rights to edit across multiple branches, they are given more options for branching and can branch in several branches at once.

If users do not have the access rights, they can only fork objects and make changes in one Branch. Objects usually fork automatically unless there is no context map and more than one editable Branch.

By default, writers have these access rights while contributors and reviewers do not. This simplifies working with DRM for contributors and reviewers.