Automatically increment revisions

If you use the legacy concurrent localization model, you might require a new revision of a map each time you move it from a final status to a prior status in the workflow, such as moving it from Authoring:done back to Authoring:work.

Important: This trigger applies only for concurrent localization in CCMS Desktop

In CCMS Desktop, when you change the status of a map from a final state to a former status in the workflow, a new map revision is automatically created, which is essential for the concurrent localization model. See Comparison of the two localization models.

You can use the RevisionBumpTrigger in CCMS Web to similarly create a new revision when a map moves from a final Authoring status, such as Authoring:done, to a former or lower status, such as Authoring:work. If the topic has a cross-reference, a parameter in the trigger allows your users can determine whether to increase the revision number when it is set to true, or leave it as it is when it is set to false.

Why is this trigger necessary in some scenarios? Consider TopicA (abc123.xml, rev. 3) with a cross-reference to TopicB (xyz123.xml, rev. 5, done)

When these topics are localized in CCMS Desktop, you have:

TopicA (abc123_00003.xml, rev. 2, done) with a cross-reference to TopicB (xyz123_00005.xml, rev. 2, done)

After the status change in Authoring without the revision increment, you have:

TopicA (abc123.xml, rev. 3, done) with a cross-reference to TopicB (abc123.xml, rev. 6, work)

At this point, if you set TopicB to done and localize it, you have a problem. TopicA in Localization will never reference it—it references zyx123_00005.xml instead of xyz123_00006.xml.

By setting the process-crossReferences paremeter to true, you have:

TopicA (abc123.xml, rev. 4, done) --> TopicB (xyz123.xml, rev. 6, work)

and this solves the problem for Localization.

You can enable or disable the RevisionBumpTrigger in the triggerswebplatform.xml file.
Important: Make configuration changes in a test environment and confirm they work before copying them to a production environment.
Note: In a dedicated SaaS deployment, submit a support ticket to request that IXIA CCMS Customer Support perform this task for you.

To automatically increment revisions for concurrent localization:

  1. Locate the triggerswebplatform.xml file.
  2. Check out the file, open it and uncomment RevisionBumpTrigger to activate it. 
    Increase the revision of map and its cross-references
<class applyOn="changeStatus" class="com.ixiasoft.cms.triggers.RevisionBumpTrigger">
	<parameters>
		<param name="process-crossReferences" value="true"/>
	</parameters>
</class>
  3. Optional: Set the "process-crossReferences" parameter value to false if you do not want to increase the revision of the cross-references or change their status.
  4. Save, close, and check in the files.
  5. Test your implementation.
  6. Inform users of the change and synchronize the Web server.