Jump to main content

Guide to IXIASOFT CCMS 7.0 Dynamic Release Management (DRM) for Information Architects

Guide to IXIASOFT CCMS DRM for Information Architects
IXIASOFT CCMS Desktop User Guide
User FAQs
Glossary
Notices

Home
Guide to IXIASOFT CCMS DRM for Information Architects
A user guide for information architects using IXIA CCMS 7.0 with the the IXIA Dynamic Release Management (DRM) module. It contains information to work with branches and setup the information architecture for documentation in a DRM deployment of IXIA CCMS.
Managing the documentation structure
About Content Level Security
The following section examines how Content Level Security works with content defined within the IXIA Dynamic Release Management environment.

Guide to IXIASOFT CCMS DRM for Information Architects
A user guide for information architects using IXIA CCMS 7.0 with the the IXIA Dynamic Release Management (DRM) module. It contains information to work with branches and setup the information architecture for documentation in a DRM deployment of IXIA CCMS.
- About the IXIASOFT Dynamic Release Management module
  The IXIA Dynamic Release Management (DRM) module allows technical publication teams to easily manage the documentation for multiple products across multiple release cycles.
- Managing the documentation structure
  - Open the DITA perspective
    The DITA perspective is the default working environment for IXIA CCMS.
  - Displaying the IXIA Dynamic Release Management view
    The IXIA Dynamic Release Management view lists the products, libraries, releases, and versions that are configured for your deployment.
  - Open the Information view
    The Information view shows all the DRM versions for the selected object.
  - Associate DRM files with an XML editor
    When you create a product, library, release, or version, IXIA CCMS creates an XML file that defines that product, library, release, or version.
  - Set up the documentation structure
    Before writers can add objects (maps, topics, images, resources) to IXIA CCMS, the documentation structure must be set up.
  - Rename a version
    You can change a product or library's DRM version name to a new unique name.
  - Clone a version (branch a documentation set)
    You clone a version when you want to use the content of a version as a starting point for the next version.
  - Close a version
    If all of the work for one version is complete, you can close the version. This prevents anyone from accidentally creating or changing content for that version.
  - Reopen a version
    You can reopen any version that is closed If you need to change the content in it.
  - Editing objects in CCMS Web
    In the IXIA Dynamic Release Management module, IXIA CCMS Web automatically forks in some situations so that users do not need to decide whether to fork or edit.
  - Managing libraries
    You can edit libraries or their dependencies if the organization or structure of your libraries needs to change.
  - Show the container associated to the version
    The Locate Containers feature is used to find the container and container parts associated to a version.
  - Change your documentation structure (Refactor)
    You can change a product into a library or a library into a product using Refactor.
  - Export the Dynamic Release Management tree view
    You can export the Dynamic Release Management tree view to a tab-separated-value (TSV) file.
  - Understanding the Version tag feature
    A version tag is an object that captures the contents of a product version or library version at a particular point in time. It is like a snapshot for an entire version.
  - About Content Level Security
    The following section examines how Content Level Security works with content defined within the IXIA Dynamic Release Management environment.
    - Understanding Content Level Security
      Content Level Security (CLS) is a feature that controls who has access to edit or read content.
    - Setting Content Level Security on a Version
      You can restrict the access of users to content in IXIA CCMS Web by setting Content Level Security (CLS) on a Version in IXIA Dynamic Release Management in IXIA CCMS Desktop.
    - Examples of access restrictions from Content Level Security
      Content Level Security controls whether users in a specific group can view, create, and edit content in IXIA CCMS Web.
    - How Content Level Security and Dynamic Release Management interact
      Content Level Security (CLS) has default settings for new Versions, allows access in cases of mixed security settings, and has restrictions that ensure visibility across parent-child Libraries.
- Add the documentation to versions
  When the documentation structure is set up, writers can add content to versions.
- Notices

About Content Level Security

The following section examines how Content Level Security works with content defined within the IXIA Dynamic Release Management environment.

Generated by IXIA CCMS oXygen Webhelp