[Index]

Model: data/RuleModelDeviceSelectionType

Network Device List Selection Rules

If an administrator at a hierarchy has access to more than one Network Device List (NDL), the option to choose a specific hardware group or list may be needed in order to provision a set of devices. The Network Device List Reference (NDLR) does not offer such a choice.

The Rule Model Device Selection Type model provides a solution to this problem and instances of it are a set of rules for views and relations at a hierarchy level. A particular NDL can then be selected from a pop-up form before the Add form of these model types are shown. In this way the administrator can then select the specific required NDL. Refer to diagram below for an illustration of this functionality.

When an instance of the Rule Model Device Selection Type model is added, the target relation or view is specified and more than one a set rules can be added for it - one for each relevant Hierarchy Node Type.

In addition, a Default GUI Rule that is applied to the Relation or View is reflected as the Default value for the Permitted Hierarchy Node Type.

In addition to this behavior, the following rules apply:

• The NDL selection is only available for Devices, Relations and Views.
• Device form fields will be filtered according to the device listed in the selected NDL.
• More than one type of device is supported for the selected NDL.
• Any Provisioning Workflow Network Device Filters (NDF) override a selected NDL device choice.
• Only the Add operation supported.
• NDL selections are controlled by GUI Rules at hierarchy levels for model types. The device selection given GUI Rules, NDLs, NDLRs and Device Selection Rules are shown in the table below.

The Rule Model Device Selection Type model also provides the following functionality:

• The NDL device meta is available to the context in Provisioning Workflows. For example:

  "device_meta": {
          "ndl": {
              "name": "NDL1",
              "pkid": "54dc76c82afa4327de0d218e",
              "data/CallManager": {
                  "pkid": "54dc76c72afa4327de0d217f",
                  "bkey": "[\"10.120.2.175\", \"8443\", \"P.C\"]"
              },
              "bkey": "[\"NDL1\", \"P.C\"]",
              "data/UnityConnection": {
                  "pkid": "54dc76be2afa4327de0d210b",
                  "bkey": "[\"172.29.41.72\", \"443\", \"P.C\"]"
              }
          }
   }
  

• NDL device meta namespace device_meta is available in macros as: {{ device_meta.??? }}, for example:

  device_meta.ndl.name
  device_meta.ndl.data/CallManager.pkid
  

• The [ndl] macro is available for use in GUI Rules - similar to [hierarchy].

• An API parameter is available for the selected NDL when a GET request is sent for the Add form of a Relation. The value of [ndl] in the example below will be a valid PKID for the NDL. For example:

  GET /api/relation/UserCucmCucRel/add/?
   hierarchy=[hierarchy]&
   ndl=[ndl]&
   schema=true&
   schema_rules=true
  

  This parameter will be transformed in the subsequent Add calls to devices to a device parameter.

This defines a rule for adding a model type using specific device selection type

Model Details: data/RuleModelDeviceSelectionType