Profiles

Profiles are used to provision devices and mapped to one or more scopes in the hierarchy. Profiles can be created as Local or Shared elements. Profiles are logically grouped into Profile Categories with a modular layout and comprised of three components:

Properties

Properties are used to define configuration parameters. Profiles compatible with two or more device functions include an option called Device Specific Parameters. These parameters are exclusive to a specific device function.

Note:

Mandatory parameters are marked with an asterisk.

Figure 1: Properties

Figure 2: Device Specific Parameters

References

References are created when parameters are defined using configuration elements in the library.

Figure 3: References

Overrides

Overrides are represented by a icon. Any configuration node is able to override configuration elements inherited from its parent configuration, regardless of whether the parent node initially accessed the element as local or shared. The process of element overriding begins when an administrator edits the properties of an inherited element.

  • From UI flow, when an element is overridden, a copy of that element, along with the edits, will be created as a local element for the configuration node.

  • From API flow, when an element is overridden, payload which is provided as input in the API will be created as a local element for the configuration node.

Once a local element is generated for the configuration node, it becomes an independent entity and is no longer connected to the parent copy of the element. Any changes made to the parent element will not be automatically transferred to the local copy in the overridden nodes.

At any given time, a scope can either have a shared element or local element for a specific configuration module and configuration module instance.

Note:

Shared Profiles created by users at higher scopes are being inherited by lower scopes and remain editable at those lower levels. Additionally, when a user creates a local profile at a higher scope, this profile is also inherited by lower scopes, where it can be modified.

For example, If site scope is assigned to a profile, then at any given point, the profile can either be a local configuration or a shared configuration. If both local and shared configuration is created for a profile, then the local configuration takes precedence and the shared configuration is unassigned from the scope.