Operations Hub Release Notes
This topic provides a list of product changes in Operations Hub for this release.
Version: 2022.06
What's New
Description | Tracking IDs |
---|---|
Share favorites with other users using Favorite Organizer. | F65368 |
Enhancements to DataGrid:
|
F65148 |
Enhancements to Trend Card:
|
|
Performance improvements for handling import/export of asset models in Operations Hub. | F56941 |
Enhancements to App import/export in Operations Hub. | F65104 |
Known Issues and Limitations
Description | Tracking ID |
---|---|
In a trend chart, if you add a tag that is identical to the one that is already plotted but the case of the tag name does not match the case of the tag name in Historian, a straight line appears in the trend chart. To resolve this issue, modify the tag name to match the case of the tag name in Historian. | DE123833 |
During Operations Hub installation, when
you provide the tenant user ID, the following conditions apply:
|
DE123770 |
When you create a data source, you can provide a certificate only in the base-64-encoded format. A DER-encoded certificate is not supported. | DE116706 |
Operations Hub uses Kafka, which generates a large number of logs in the following location: C:\tmp\kafka-logs\. To avoid consuming too much space for these logs, we recommend that you periodically delete the logs, especially if the system has low disk space. | N/A |
If you encounter intermittent responsiveness issues with the Operations Hub runtime environment when using the Safari browser on your mobile device, it is recommended that you use the Chrome browser instead. | DE131011 |
When adding environment variables to Windows System Variables, be aware that environment variables are case-sensitive. If your environment variables in Operations Hub do not match the case of the ones used by the target Historian Server, the data source will fail when tested. Be sure that you use the same case when configuring data sources in Operations Hub. A data source target in Operations Hub should match the case in the environment variables, as the variables are case-sensitive. | DE130896 |
Historian REST response time increases exponentially when there are over 30 users logged into Operations Hub accessing an End app that utilizes Historian REST queries. | DE134904 |
When using Safari 13+ on iOS, trend card functionality like adding tags to the trend, favorites, and annotations perform inconsistently. The workaround is to use the Chrome browser on the iPad. | DE136597, DE149433 |
If a Historian data point being trended transitions to a bad quality (such is the case when a collector goes down or loses communications), the trend card displays a flatline for the last known good value. If you experience one or more flatlines in your trends, and all the various requests from the same source, you should check the communication chain for an issue with Historian, a collector, or a SCADA driver, for instance. | DE138128 |
There are currently some page printing issues. For instance, if you have iframe that spills over to a second page, that can cause an issue. | DE146462 |
The uaa-provisioning.log file generates in a new folder if the
location path provided during Operations Hub installation contains a space in it.
For example, C:\Custom Logs. |
DE148827 |
As a workaround to address VC++ (x64) failure, follow these steps to install
Task Client on Operations Hub 2.1.
|
DE161643 |
If the Data Distributor service started at a time when the datasource was offline, reload the end application. | DE158762 |
For REST connection, if you enter an IP address instead of the hostname in the
Auth URL field, it results in a 404 error. You must add the
IP address to the list of supported subdomains/zones. To do this:
|
DE153631 |
When importing a model containing a second CIMPLICITY namespace table, it
overwrites the values in the first namespace table. Workaround: Combine the server and namespace information from the two namespace tables into one namespace table, and then import the model again. |
DE47669 |
The inline mimic write operations performed in Operations Hub are indicated as
successful even if the entries did not meet the criteria of these CIMPLICITY
attributes.
The values do not get updated to the CIMPLICITY point control panel. |
DE156030 |
Error message does not appear when you perform a write operation on a CIMPLICITY tag value that is outside of a given range. | DE157698 |
If you select Acknowledge All in Operations Hub to acknowledge 5000 iFIX alarms, an internal error occurs in the iFIX application. | DE161742 |
Only a single instance of the CIMPLICITY HMI Webspace widget per app is supported. If using multiple instances of webspace widgets across multiple pages, you may encounter access error messages when navigating between pages that contain webspace instances. After confirming the message, the widget loads as expected. | |
The typeName parameter in the custom widget’s
manifest.json file does not support special characters. |
DE162893 |
For Operations Hub 2022 release, Proficy Authentication server validation fails while installing Workflow Task Client. As a workaround to fix this issue, please refer to Resolving Proficy Authentication Issue During Workflow Task Client Install. | DE174960 |
In Operations Hub 2022.4.1, line chart legend is not updating based on the updated parameters for the chart. The line chart always shows only the initially fetched data for a query. | |
If an App uses multiple nested containers and a large number of queries, it impacts the page load performance. | DE170644 |
Events do not trigger after they work properly for a while. Restart the
following services to fix the issue:
|
DE178533 |
MQTT slow response impacts page load performance. | DE183156 |
While using the trend card on iOS 15 Safari browser, the tags in a drop-down menu are not displaying properly. This occurs when there is more than one page in an App. | DE184797 |
The following issues are noticed in Operations Hub on Android device:
|
DE184895, DE184901 |
If you create a display condition for a widget (or container), the widget (or container) is hidden regardless of the condition not being met. Condition always defaults to true at runtime. | DE184491 |
Some times on a trend chart, the AXIS LOW limit is not
being returned if the duration of the trend is modified. The values are auto scaled
based on the property data for the current duration. For example, consider a tag with a low/high of 0-100, and with actual data values ranging from 40-60. In this case, when you change the duration of the trend, the y-axis for this series might switch to show 35-100, instead of 0-100. Except for the low-range value returned by Historian, all the other data values appear on the trend. Workaround: On modifying the trend duration, go to each tag and reset its AUTOFETCH LIMITS. To reset, first turn off the toggle, and then turn it on to fetch low/high limits appropriately. |
DE185861 |
Fixed Defects
Description | Tracking ID |
---|---|
Previously, exporting an asset model remained unsuccessful with errors. Upgrading to Operations Hub 2022.4.1 resolved the issue. | SF01008750, SF01011692 |
Previously, configuration issues occurred while upgrading from Operations Hub
2.1 to 2022. Re-uploading the service provider’s metadata.xml file
resolved the issue. |
SF01021840 |
Previously, if source values came from another source/dropdown for
GEDateTimeRangePicker , then the values were not being passed down
to the target globals. This issue has been resolved |
SF01021950 |
During app import, the system only checks for duplicate conflicts due to same name. The system does not highlight if a conflict item contains a renamed artifact. Choosing to replace a conflict item in such scenarios may lead to binding loss. This message is highlighted in the confirmation screen for app import. | SF00997849 |
Previously, custom dashboards stopped working due to data source related error. This issue has been resolved | SF00998439 |
Previously, MES dashboard logos disappeared after a reset. This issue has been resolved by providing a fix to allow anonymous access to the image URLs. | SF00997558 |
Previously, no warning or error message appeared when there is a mismatch between the Host and the Port. This issue has been resolved. | SF01012233 |
Previously, the Analysis app failed on adding/removing tags to the GETrendCard. This issue has been resolved. | SF01010449 |
Previously, DataGrid was not displaying data coming from SQL. This issue has been resolved. | SF01013847 |
Previously, restoring an Operations Hub backup led to errors. This issue has been resolved. | SF01010402 |
Previously, upgrading from Operations Hub 2.1 to 2022 led to asset model import releated issues. This has been fixed. | SF01021839 |
Previously, upgrading to Operations Hub 2.0 SIM8 remained unsuccessful. This issue has been resolved. | SF01021972 |
The security vulnerabilities detected in the previous version of Operations Hub have been resolved in the latest release. | SF01021430 |
Previously, print previews displayed a blank output. This issue has been resolved. The exact output from an app can be successfully printed via browser. | SF01014982 |
Previously, duplicating an app led to loss of images in interactive maps. Code has been modified to resolve this issue. | SF01030700 |
Compatibility Matrix
Product | Required Version |
---|---|
Proficy Historian |
Note: Historian REST APIs are required for REST integration between Operations Hub and Historian 8.x and above. Historian REST APIs are installed automatically when you install Historian web-based clients. |
Proficy Plant Applications | Plant Applications 2022, Plant Applications 2022 SIM1 |
Proficy Authentication (UAA) | UAA 2022 |
Proficy iFIX |
Note: Mimic and model publish to Operations Hub 2.1 and greater is supported only with iFIX 6.5 with
latest SIM and iFIX 2022. |
Proficy CIMPLICITY |
Note: Mimic and model publish to Operations Hub 2.1 and greater is supported only with CIMPLICITY
11.1 and CIMPLICITY 2022. |
Proficy Workflow | Workflow 2.6 SP1 SIM4 |
GE Common Licensing | Version 20.2.2002 or greater |