Content workflows

During the process of creating, editing, reviewing, and approving a Authoring:work. Each status requires input from users with different roles.

Each status represents a corresponding stage in the process of creating a document.

The status of an object can identify the following:

  • Location within your documentation process
  • Next workflow stage
  • User currently responsible for the object
  • Possible workflow stages that remain before completion

Every object has a status that reflects the object's current workflow stage. Objects change status according to the workflow defined in your deployment. For example, a topic could move from the initial Contribute status to the final Done status using the example workflow.

Figure: Example of a workflow
Sample workflow

Roles and workflows

Each user acts in one or more roles, such as Contributor, Writer, and Reviewer, depending on your configuration and your assignments.

For example, a subject matter expert (SME) could provide a rough draft of content to a technical writer to refine. In this case, the assigned role for the SME is the Contributor role, and the assigned role for the technical writer is the Writer role. After completing the content edits provided by the SME, the technical writer assigns the SME the Reviewer role and sends the content back for comment and verification of accuracy.

A user has the responsibility to work on objects at a status related to the user's assigned role. A writer or other user can change the status of the object to permit users with the specified role to work on the object.

Object dependencies and workflows

An object cannot be further along in its workflow than its dependencies. For example, if a topic references images, the topic cannot move to a Done status before all related images also move to a Done status. A topic cannot move to a Done status if it references unfinished conrefs that are still have a Work status.

Note: When you move an object to a different status, IXIA CCMS Web will automatically move any dependencies of the object that need to move as well. If something prevents a dependency from changing status, you must resolve the issue with the dependency before you can move the object.