Using CCMS Web with concurrent localization

If you edit content in CCMS Web but use the CCMS Desktop concurrent localization model, you need to enable CCMS Web to create a new revision when a map moves from its final state to an earlier state in the workflow.

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 CCMS Desktop localization models.

In CCMS Web, this is not the case. No new revision is automatically created when you change the status of a map from a final state to a former status in the workflow. This design is to avoid creating revisions when there is no actual change to the map's structure or content.

If you are using CCMS Web with the concurrent localization model (meaning that you edit content in CCMS Web but localize in CCMS Desktop), you can configure CCMS Web to create the new revision by activating the optional RevisionBumpTrigger trigger in your system configuration.

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 parameter 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 the following objects in Localization:

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 TopicB correctly—it references zyx123_00005.xml instead of xyz123_00006.xml.

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

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

and this solves the problem for concurrent localization.