Document cycles, states, and status types

IXIA CCMS has a formalized document cycle that ensures that content development stays on track as various users exchange topics, maps, and images until the content is ready for publication.

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

Cycles

Cycles establish the larger framework for document development. For example, organizations typically have an authoring cycle and might also have a localization cycle that applies to maps, documents, and images.

A typical document cycle might follow this sequence:

  1. Authors or contributors create content
  2. Subject matter experts (SMEs) review and approve the content
  3. An editor might revise the content
  4. A translation coordinator might submit source content to a language service provider (LSP) for localization, review the resulting translations, and import them back into the CCMS
  5. A user publishes the content and its possible translations as output of various types

States and status

States identify the status of an object at each point in the cycle.

A document's cycle and state, written together, define its status, such as Authoring:review.

Users move content within objects from one status to another as a status promotions or demotions within the cycle.

Figure: Sample documentation process cycles and states