Triggers for CCMS Web

Triggers are sets of code that automatically invoke when a CCMS Web user performs a given action or when there is a change in status.

Note: In a dedicated SaaS deployment, submit a support ticket to request that IXIA CCMS Customer Support perform this task for you.
There are two types of triggers:
  • CCMS action triggers automatically invoke when a user performs an action such as Release, Lock, or ChangeStatus. For example, you can use a trigger to automatically remove tracked changes from all related topics when a user moves a document to its final state, such as Authoring:complete.
  • Status triggers automatically invoke with a status change. For example, you can use a status trigger to 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 when the object status changes to a lower state 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. See Automatically increment revisions.
Important: Make configuration changes in a test environment and confirm they work before copying them to a production environment.

You can enable or disable a trigger in the triggerswebplatform.xml file.

For example, the following code shows how you could define a trigger to validate the scope of internal map references, but this particular example remains commented out, so remains disabled until you uncomment it.

<!-- Validates the scope of the internal map references -->
<!--<class applyOn="changeStatus" className='com.ixiasoft.application.command.triggers.ValidateLinksTrigger' > 
    <parameters> 
        <param name="initial-status" value="Authoring:work"/> 
        <param name="end-status" value="Authoring:*"/> 
    </parameters> 
</class>-->