How forking affects assignments

In IXIA Dynamic Release Management (DRM), when you fork an object, it might change how users are assigned to the original instance.

Note: If you fork an object, it is not automatically assigned to you in the new instance. You are never assigned to a new instance unless you were already assigned the original object.

Assignments for objects without context maps

Assignments do not change when you fork objects that do not have context maps. The assignments on the original object are copied to the new instance. Any users who were assigned to the original object are automatically assigned to the new instance as well as the original instance.

Note: For objects that cannot be given context maps, such as images and ditavals, the assignments are always copied.

For example, Emma is assigned to Topic B without a context map, and Mia is assigned to Topic B in Context Map 1 as part of a different assignment. Emma forks Topic B in the Branch that contains Context Map 1. Emma is now assigned to the new instance of Topic B as well as the original instance of Topic B. Mia is assigned to only the new instance of Topic B in Context Map 1.

Assignments for objects with context maps

After you fork an object with a context map, assignments can change. When you fork an object, the following happens:

  • If you were assigned to the object in the same Branch as where the new instance is created, the assignment switches to the new instance, but you are no longer assigned to the original instance of the object.
  • If you were assigned to the object in a different Branch from where the new instance is created, you remained assigned to the original instance of the object.

For example, Martin is assigned to Topic A in Context Map 1, and Arata is assigned to Topic A in Context Map 2. Martin forks Topic A in the Branch that has Context Map 2. Arata is assigned to the new instance of Topic A in Context Map 2. Martin is still assigned to the original instance of Topic A in Context Map 1.