Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

Templates make streamlining and standardizing the management of configurations more effective. The goals of templates are:

  • Efficiency: Simplify the creation and maintenance of configurations by providing predefined templates that reduce manual effort and ensure consistency.

  • Scalability: Enable organizations to manage complex systems by using templates to replicate proven configurations across multiple units or projects.

  • Compliance: Ensure all configurations adhere to company policies and standards through the controlled use of templates and protocols.

Managing Templates

Template Types

  • Unit Templates: Units with a concept type marked as IsTemplate: true.

  • Configuration Templates: Configurations of concept types that are also marked as templates

Template Usage

  • Users can select templates to create new configurations.

    • Specific configuration items can be excluded from the template. Reasons for exclusions are documented in the Template Usage Protocol.

Configuration Creation Features

  • Creation Options:

    1. New, empty configuration.

    2. Configuration from a template.

    3. Copy of an existing configuration.

  • Details on Template Use:

    • Properties and configuration items are inherited from the template.

    • All changes or customizations are recorded in a template usage protocol.

Superstates and Rules

  • Templates and configurations can be associated with superstates (Closed Baseline, Template).

  • Superstate associations cannot be changed once persisted.

  • No labels