Hyperview 1.5

December 22 2020

This page covers significant new features, enhancements, and bug fixes in Hyperview 1.5.x since version 1.4.x.

BACnet/IP and Modbus TCP support

Hyperview now supports the BACnet/IP and Modbus TCP protocols.

Manage BACnet/IP definitions and relevant sensors

Administrators can use the new BACnet/IP Definitions page (Settings → BACnet/IP Definitions) to manage BACnet/IP definitions. Additionally, you can click on the Numeric Sensors tab to manage numeric sensor definitions associated with a certain BACnet/IP definition.

Manage Modbus TCP definitions and relevant sensors

Administrators can use the new Modbus TCP Definitions page (Settings → Modbus TCP Definitions) to manage Modbus TCP definitions. Additionally, you can click on the Numeric Sensors tab to manage numeric sensor definitions associated with a certain Modbus TCP definition.

New Monitoring section while adding a new asset

A Monitoring Profile field has been added to the Add New page (Assets → Add New or via right-click in Asset Hierarchy → Add New Asset; only accessible by Power Users and above). Possible values are: “Discovered” (default), “BACnet/IP”, and “Modbus TCP”. Selecting either “BACnet/IP” or “Modbus TCP” will surface relevant protocol-specific fields.

Enhanced Monitoring page

Power Users and above can now use the Monitoring page (browse to asset → Information → Monitoring) to update an asset’s monitoring profile (Discovered, BACnet/IP, or Modbus TCP). You can also refresh the device data using the latest device definition, where applicable. Saving the page will create individual Change Log events per new or updated monitoring property.

Enhanced user management

User-related features have been significantly enhanced to support external login-only access on a per-user basis, and to allow for applying asset access policies across groups of people.

External login enforcement

Administrators can now force users to access Hyperview using their external login provider from the Users grid (Account → Profile → Users).

From a user’s standpoint, attempting to log into an external login enforced-account using a Hyperview username and password will throw an error. Additionally, the “Manage your account” page (Account → Profile) will no longer feature Password, External Logins, and Two-Factor Authentication links.

User groups

Administrators can use the new Groups page (Account → Profile → Groups) to manage groups. For example, you can create groups for specific teams in your organization, such as developers, business analysts, managers, and so on.

Administrators can use the Users page (Account → Profile → Users) to add a new user to existing groups, or update an existing user’s group memberships. Users can see what groups they belong to from their Profile page (Account → Profile → Profile).

Users grid enhancements

The Users grid (Account → Profile → Users) features four new columns:

  • Two Factor Auth (indicates if 2FA is turned on)
  • External Logins (indicates configured external login providers; only Microsoft is currently supported)
  • External Login Required (lets you toggle the external login requirement)
  • Groups (lists groups the user belongs to)

Distinct Application Log entries for external logins

The Application Log (Logs → Application Log) now distinguishes between external login events and Hyperview login events, citing the external login that was used (currently only Microsoft is supported).

Asset access enhancements

Access policy groups

Administrators can now use the Access Policies page (Settings → Access Policies) to specify groups that a certain access policy will apply to. Allowed groups for an access policy will appear in an asset’s Access Control page (browse to asset → Access Control), provided the same access policy is currently selected.

Access Policies grid enhancement

The Access Policies grid (Settings → Access Policies) now features an Associated Groups column, which indicates the number of groups associated with a given access policy.

Other notable enhancements

  • The Hierarchy tree has been renamed to Asset Hierarchy for ease of reference.
  • Asset labels in Rack Elevation views are now more legible.
  • IxOS discoveries now return Model and Serial Number values for ports.

API changes

All API changes are reflected in the corresponding Open API (aka Swagger) interfaces, which can be accessed from the Help menu.

The following endpoints have been added in the Hyperview API. In addition, various object definitions have been improved for the Hyperview and Data Collector APIs. No Data Collector API endpoints have been added or updated.

New /accessPolicyGroups endpoints

  • /api/v1/setting/accessPolicyGroups returns groups of users that can be associated with an asset access policy.
  • /api/v1/setting/accessPolicyGroups/{accessPolicyId} retrieves groups associated with a specific access policy.

New /bacnetIpDefinitions endpoints

  • /api/v1/setting/bacnetIpDefinitions lets you retrieve a list of BACnet/IP definitions, or create one.
  • /api/v1/setting/bacnetIpDefinitions/{bacnetIpDefinitionId} lets you retrieve, delete, or update a specific BACnet/IP definition.
  • /api/v1/setting/bacnetIpDefinitions/bacnetIpNumericSensors/{bacnetIpDefinitionId} lets you retrieve numeric sensor definitions associated with a BACnet/IP definition, or create such a numeric sensor definition.
  • /api/v1/setting/bacnetIpDefinitions/bacnetIpNumericSensors/{bacnetIpDefinitionId}/{bacnetIpNumericSensorId} lets you delete or update a numeric sensor definition associated with a BACnet/IP definition.

New /modbusTcpDefinitions endpoints

  • /api/v1/setting/modbusTcpDefinitions lets you retrieve Modbus TCP definitions, or create one.
  • /api/v1/setting/modbusTcpDefinitions/{modbusTcpDefinitionId} lets you retrieve, delete, or update a specific Modbus TCP definition.
  • /api/v1/setting/modbusTcpDefinitions/modbusTcpNumericSensors/{modbusTcpDefinitionId} lets you retrieve numeric sensor definitions associated with a Modbus TCP definition, or create such a numeric sensor definition.
  • /api/v1/setting/modbusTcpDefinitions/modbusTcpNumericSensors/{modbusTcpDefinitionId}/{modbusTcpNumericSensorId} lets you delete or update a numeric sensor definition associated with a Modbus TCP definition.

New /monitorOnlyCommunicationSetting endpoints

  • /api/v1/asset/monitorOnlyCommunicationSetting/{assetId} lets you retrieve or update the monitoring setting for a specific asset (note: see AS-8338 under Known Issues).
  • /api/v1/asset/monitorOnlyCommunicationSetting/{assetId}/refreshSensors refreshes the asset monitoring sensors for a given asset from “monitor only” definitions.

Deprecated endpoints

No endpoints were deprecated in this release.

Known issues

  • AS-7654 Panduit Gen3 (Unite/Sinetica based) rack PDU appears as an environmental monitor.
  • AS-7879 The All location in the Asset Hierarchy does not always expand by default.
  • AS-8160 While attempting to bulk delete Advanced Search rows, the operation remembers row selections from previous queries.
  • AS-8164 The Add New modal crashes while adding a rack, rack PDU or PDU with missing model data.
  • AS-8166 Often cannot add assets to shelves due to inactive Add button.
  • AS-8180 You are able to set the RackU size of a rack to 0, which is incorrect.
  • AS-8321 The View button is unavailable while editing a location layout in Map Mode.
  • AS-8338 (API only) PUT /api/v1/asset/monitorOnlyCommunicationSetting/{​​assetId}​​ does not correctly update the monitoring state for assets that are set to a Discovered monitoring profile.
  • AS-8354 While editing a BACnet/IP or Modbus TCP definition, the breadcrumb trail link for the same opens the All assets page.
  • AS-8442 Users cannot clear an asset’s Lifecycle fields after saving them.

Notable bug fixes

  • AS-6161 The Rack Space KPIs widget for location dashboards no longer repeats legend values.
  • AS-7631 SSH key discoveries work with new keys.
  • AS-7846 Fixed sorting issue with asset types listed in the Assets By Type widget for locations.

Changes in version 1.5.1

Bug fixes

  • AS-8446 The Definition field on the Information → Monitoring page was blank for assets that have Monitoring Profile set to “BACnet/IP” or “Modbus TCP”. Definition selection options for the field were also unavailable. Both issues have now been addressed.