Important: You do not have the latest version of Operations Hub! You are missing out on the newest capabilities and enhanced security. For information on all the latest features, see the Operations Hub product page. For more information on upgrades, contact your GE Digital sales agent or e-mail GE Digital Sales Support. For the most up-to-date documentation, go here.

Operations Hub

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

Version: 1.6

Table 1. Enhancements and New Features
The following enhancements and new features have been added.
Description	Tracking ID
This release of Operations Hub contains the following features REST API Support: PUT, POST, DELETE Japanese Language Support	F49620 F49626

Table 2. Known Issues and Limitations
The following known issues and limitations exist.
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: If you are installing Operations Hub for the first time, do not provide StudioAdmin as the tenant user ID because it is used by Operations Hub. If you want to use a shared UAA to work with Operations Hub, do not provide the user ID of an existing user of the UAA instance. If you do so, the installation fails. If you are installing Operations Hub after uninstalling it without purge, do not provide a tenant user ID that matches any previously used user ID (including any previously used tenant ID). This is because after you uninstall Operations Hub without purge, previousOperations Hub users (along with tenant administrators, their groups, and privilege assignments) still exist in the database.	DE123770
You can create multiple data sources with the same URL. After you restart the services, the Data Distributor service uses the most recently saved System API authentication settings for the URL. Therefore, if the most recently saved credentials do not work, you cannot connect to the data source. To fix this issue, modify the data source to specify working credentials, and then test the data source. We recommend that you do not save the data sources that do not pass the test or data sources with the same URL.	DE123040 DE116737
If you install Historian after installing Operations Hub on the same machine, sometimes, the Operations Hub login page does not appear. This is due to a conflict between the ports used by the two applications. To avoid this issue, perform one of the following workarounds: Stop the Historian Tomcat instance, restart the IQP Tomcat instance, and then start the Historian Tomcat instance. While installing Operations Hub, provide a different port number for the IQP HTTP port so that it does not conflict with the port used by Historian.	DE122500
Some widgets, such as a table, do not work as expected when used with a REST query. In particular, features which require additional queries to fetch more data (such as pagination), as well as features limiting data (such as row limits) may not work.	DE118883
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
While it is not recommended to install Historian and Operations Hub on the same computer, if you must install them together the order of install matters. Install Historian 8.0 first, and then Operations Hub 1.6 second. When installing the Historian Web Client, use the fully qualified domain name (FQDN) and the local machine name (separated by commas). Without the computer name as part of the generated certificate, the UAA Provisioner will fail when it attempts to add information to the UAA, and you cannot directly modify the certificate after it is added.	DE124584
Live preview for Mobile and Tablet devices opens at the bottom of the page after an object is deleted. Even though Live Preview should not open in the first place, it is cut off and there is also no way to close it. As a workaround, refresh the page.	DE121922
Image names should not contain spaces or non-English characters. If they do, an import or export of an app bundle with fail.	DE131122
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
Sometimes a race condition can occur when you install Operations Hub. Because of this, you will not be able to log in; the log in page is blank. To resolve this issue, restart the IQP Tomcat Webserver service.	DE131187
When you import an app, the update process replaces the old app with a new one - which means any users from the old app will need to be re-added to the new app. Users are not imported as of the operation.	DE132173
When importing and exporting apps, information from app user assignments is not included. One side effect of this issue is that when you import a new version of an existing app, the old app is replaced with the new app, and no users will be assigned to the app. Previous user assignments are lost, and must be added again after the import.	N/A

Table 3. Fixed Defects
The following fixed defects have been addressed with this version of Operations Hub.
Description	Tracking ID
When you exported an application that contained an image widget, the images used in the widget were not exported. You had to manually place the images in the target Operations Hub instance. This issue is resolved in version 1.6.	US383459
When you imported an application, if an application with the same name existed, the new one was given a unique name. This was to avoid replacing the existing application with the new one. If, however, you wanted to replace the application with the new one, you specified the same name for both the applications. This also applied to the queries and entities that were imported along with the application. However, in some scenarios, queries and entities were copied even if you wanted to replace. This issue is resolved in version 1.6.	DE120745

Table 4. Compatibility Matrix
The following products are compatible with Operations Hub.
Product	Required Version
Historian	Historian 7.0 with the latest SP Historian 7.1 with the latest SP Historian 7.2 with the latest SIM Historian 8.0 Note: While it is not recommended to install Historian and Operations Hub on the same computer, if you must install them together the order of install matters for Historian 8.0. Install Historian 8.0 prior to Operations Hub.
Plant Applications	Version 8.0, SIM3, for Integrated Process Apps
User Authentication and Authorization (UAA) service	Version 4.30.0 or later