Resolve ambiguous status changes

Sometimes, when a parent object must move to a lower status, there can be more than one eligible status available. You can set a rule to indicate which status should be the target.

About this task

CAUTION: Use extra caution when editing this file. Be sure you understand the effects of your changes.

Let's say that your map workflow includes the work state at level 2 and the review state, at level 3. You have a map at done (level 10) with all its topics necessarily at done (level 10) as well. You move one of those topics back to work (level 3), which requires that the map move back as well, due to the workflow dependencies rule. However, the map could move to either work or review; both states satisfy the rule.

In cases of ambiguity like this, you can specify that the CCMS always move the parent back to the highest state possible (in this example, review) or the lowest state possible (in this example, work).

Important: Make configuration changes in a test environment and confirm they work before copying them to a production environment.

Procedure

  1. In the TEXTML Administration perspective, connect to your server.
  2. Locate the fallthroughmanager.xml file in the repository's /system/conf collection.
  3. Check out the file and open it for editing.

    By default, the CCMS is set to move the object back to the highest level possible. This is generally preferred.

  4. To select the lowest level possible option, comment out the first <manager> element and uncomment the second <manager> element.

    Only one other the other <manager> can be active at a time.

  5. Save, close, and check in the file.
  6. Inform users of the changes.
    The changes are automatically applied once users close and then reopen their IXIA CCMS Desktop. Users can also apply the changes without restarting their CCMS Desktop by clicking IXIA CCMS > Synchronize Configuration.