Operations Hub

This topic provides a list of product changes in Operations Hub for this release.

Version: 1.0.1

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The Operations Hub documentation now contains information on the purpose and usage of the following widgets:
  • Event settings
  • Interactive map
  • Gauge
  • Map
  • Repeater
  • Upload devices
  • Upload excel
  • US333114
  • US333113
  • US333112
  • US333111
  • US333110
  • US333109
  • US328739

Version: 1.0

Table 2. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
Operations Hub has been introduced in this release. Operations Hub is an end-to-end solution for developing, managing, and delivering applications to leverage the capabilities of big data analytics and internet of things. Using Operations Hub, you can perform the following tasks without the need to use programming skills:
  • Create database components of an application such as tables (called entities) and queries without the need to understand SQL.
  • Specify alarms (called events) that can automatically send dynamic emails, run queries, or send commands to devices.
  • Design applications with multiple pages and dashboards used to monitor and control assets and workflows. You can use baseline or custom page components in the applications.
  • Send or receive data from devices such as sensors or controllers, and analyze the data in the applications.
Table 3. Known Issues

The following issues are unresolved in this release.

DescriptionTracking ID
While creating or modifying a query, when you select Save And Exit or Save As New, if the query contains invalid conditions, instead of displaying an error message, the query is saved in an invalid state. The workaround, to ensure that a query is validated, is to select Save.DE93603
If you use the Auto Sync query submission option to retrieve data from a custom entity, the data is not automatically updated. This issue occurs if the entity is updated by an external source using the REST Insert Entity data API. The workaround for this issue is to use the Auto Update query submission option to retrieve data.DE93360
In the ENTITIES workspace, in each row containing a custom entity, the Last Updated column incorrectly specifies that the entity was updated 0 days ago even if it was updated prior to the current date. The entities, however, are correctly sorted in the order in which they have been updated.DE93118
In an application, if you use a variable from the Globals > Custom section to show or hide map markers, the condition is not updated when the value of the variable changes unless you navigate away from the page and return to it.DE92593
If you create a query to retrieve data from a field of the Boolean data type, and if you specify <> true in the Conditions section, the query results do not include the data for which the field value is null. The workaround for this issue is to ensure that Boolean fields always contain a value.DE92215
If you export and import an application many times, an error occurs. This is because each time a theme is imported, the name of the theme is appended with the text _transfer_UUID, thus resulting in a lengthy name. The workaround for this issue is to modify lengthy theme names before exporting the application.DE82960
In a query, in the Output Data section, you cannot select the same field from the same entity twice (for example, you want to retrieve the minimum, maximum, and average values of a field). The workaround for this issue is to use separate queries to retrieve the data.DE75180
If you use variables from the Globals > System > Geolocation section to retrieve the latitude and longitude values in a page that does not contain a map, the values are incorrect.DE72552