Operations HubOperations Hub Release Notes
This topic provides a list of product changes in Operations Hub for this release.
Version: 2022
| Description | Tracking IDs |
|---|---|
| Added the following widgets in Operations Hub: |
F62194 F62193 F60132 F62159 F60533 F60531 F60530 F60131 F62852 F62477 F62195 F60119 |
| Introduced widgets for batch execution process. | F62860 |
| Provision to install Dataflow Editor along with Operations Hub installation. | F63238 |
| Operations Hub support on Azure and AWS environment. | F62898 |
| Provided support for third party OPC UA write operations. | F60577 |
| Introduced back/forward navigation icons on end application. | F62071 |
| Ability to perform backups and restore the Operations Hub database. | F62392 |
| Ability to perform dynamic translation of Operations Hub app and page names. | F62391 |
| Single Box support for Operations Hub, Historian, Scada (iFix, Cimplicity). | F62507 |
| Set up email notification for Operations Hub certificate expiry. | F62667 |
| Enhanced mimics to support publishing target name to a global. |
| Description | Tracking ID |
|---|---|
| When you save a favorite in a trend chart, if you include a special character in the name, the error message that appears does not specify the issue. | DE123967 |
| 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 |
| Description | Tracking ID |
|---|---|
| Previously on the big data widget, only a portion of data appeared, and not the complete existing data. The third-party library has been upgraded to resolve this issue. | SF00907357 |
| Previously, data source with a name containing the backslash special character got created successfully but remained unusable. The data source could not be modified or deleted from Operations Hub. This issue has been resolved. | SF00949690 |
| Previously in the dropdown widget, the results for a dropdown selection were not working as expected. This issue has been resolved. | SF00957547, SF00951042 |
| Previously, images coming from an image widget were not visible if you were part of only the iqp.user group. This issue has been resolved. | SF00945585 |
| Previously, HTML widgets were not returning the query results properly. This issue has been resolved. | SF00945676 |
| Previously on importing applications, images used in an interactive map widget were lost. This issue has been resolved. | SF00968247 |
| Previously asset import/export failed on an upgraded system. This issue has been resolved. | SF00923728 |
| Previously in Operations Hub, there was no way to delete applications created by a user deleted from the system. This issue has been resolved. | SF00945516 |
| Previously, modifying existing user account details led to the creation of new user accounts. This issue has been resolved. | SF00945610 |
| Previously, when runnning extension or REST queries on a table or grid widget, the paging function did not work. This issue has been resolved. | SF00951421 |
| Previously, applications exported from Operations Hub were not getting imported resulting in publishing errors. This issue has been resolved. | SF00956970 |
| Previously when exporting data to CSV, decimal point was being used as a separator for non-English languages. This has been fixed to use the decimal comma. | SF00953929 |
| Previously, Operations Hub administrators were not able to access favorites created by other users. This issue has been resolved. | SF00964124 |
| Previously in the Indicator widget, the decimal precision did not work as expected when set to 0. This issue has been resolved. | SF00964625 |
| Previously in Operations Hub, some specific applications were not getting exported. This issue has been resolved. | SF00956055 |
| Previously, asset models of a larger size were not getting imported to Operations Hub. This issue has been fixed to support model import up to 13MB. | SF00940548 |
| Previously in the end app, the Logout button on the Access Denied page did not work as expected. This issue has been resolved. | SF00963066 |
| Previously for German language, the date picker option in the input widget did not work properly. This issue has been resolved. | SF00964478, SF00984397, SF00984115 |
| Previously, tagnames with special characters were not being parsed properly in JSON API Call. This issue has been resolved. | SF00931668 |
| Previously, data distributor error occurred on upgrading from Operations Hub 2.0 to 2.1. This issue has been resolved. | SF00966648 |
| Previously, queries could not be added, modified, or deleted from application pages. This occurred because the plug-in manifest had old schema structure. This issue has been resolved. | SF00983175 |
| Previously, plug-ins were not getting imported to Operations Hub. This issue has been resolved. | SF00967193 |
| Previously, the Datagrid widget was not displaying images at runtime. This issue has been resolved. | SF00984119 |
| Previously, conditions set on a repeater widget were not working as expected. This issue has been resolved. | SF00987714 |
| Previously, Operations Hub 2.1 SIM1 installation failed due to the absence of an install-time created “response” file. This issue has been resolved. | SF00982456 |
| Previously, you were not able to add page globals if the global variable was already added on another page. As a workaround, make sure to give unique names to globals in an application. | SF00984358, SF00968869 |
Previously, the Spring.log file was getting very bigger in
size. This issue has been resolved. |
SF00968885 |
| Previously in Datepicker widget, the dateTime input parameter for flows was not working properly. This issue has been resolved. | SF00990262, SF00991574, SF00991575 |
| Previously, the toggles that controlled mimics were not working as expected. This issue has been resolved. | SF00987424 |
| Security vulnerabilities concerning SQL injection attack were detected in Operations Hub. This issue has been resolved. | SF00984843 |
Previously, logs were huge and growing endlessly. To resolve this,
The configuration settings can be modified by an administrator. |
SF00989117, SF00992619 |
| Previously, the admin user was not able to unlock applications created by other users. This issue has been resolved. | SF00992802 |
| Previously, default applications were getting selected while exporting an app. The tag binding was also lost on importing an exported app. This issue has been resolved. | SF00993932 |
Previously in the OPC UA data source, special characters were not allowed in
the User Name field to specify domain users for authentication.
This issue has been resolved. |
SF00996520 |
| 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 |
| Proficy Authentication (UAA) | UAA 2022 |
| Proficy iFIX |
Note: Mimic and model publish to Operations Hub 2.1 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 is supported only with CIMPLICITY 11.1
CIMPLICITY 2022. |
| Proficy Workflow | Workflow 2.6 SP1 SIM4 |
| GE Common Licensing | Version 20.2.2002 |