Operations Hub Release Notes

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

Version: 1.7

Table 1. Enhancements and New Features

The following enhancements and new features have been added.
Description Tracking IDs
This release of Operations Hub contains the following features:
  • UAA Group based access to Queries, Pages, and End Apps
  • Improved End App and Page Load Performance
  • Relational Database Support: Support for Stored Procedures from Microsoft SQL Server
  • Critical Security Fixes
  • Support for 300 concurrent users, with a hardware configuration of 32G and an 8-core CPU
  • F52254, F52256, F52258
  • F52236
  • F52261
  • F49212, F49213, F49214, F50728, F52862
  • F32385
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, previous Operations 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
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
If you install Historian 7.x 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

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.x first, and then Operations Hub 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
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 13+ annotations do not seem to work. The workaround is to use the Chrome browser on the iPad. DE136597
When not connected to the Internet, there are a couple of icons (the certificate lock icon and view password icon) in the UAA/LDAP tool which may not display. These icons require an Internet to display. N/A
Table 3. Fixed Defects

The following fixed defects have been addressed with this version of Operations Hub.
Description Tracking ID

A Google Maps display issue caused issues with viewing locations in the map widget. There were also issues working within the layout or style provided. This issue was resolved in version 1.7.

 N/A
When you imported an app, the update process replaced the old app with a new one - which meant any users from the old app would need to be re-added to the new app. Users were not imported as part of the operation. This issue was resolved in version 1.7. DE132173
When importing and exporting apps, information from app user assignments was not included. One side effect of this issue was that when you imported a new version of an existing app, the old app was replaced with the new app, and no users were assigned to the app. Previous user assignments were lost, and had to be added again after the import. This issue was resolved in version 1.7. N/A
Sometimes a race condition would occur when you installed Operations Hub. Because of this, you were not be able to log in; the log in page was blank. To resolve this issue, you needed to restart the IQP Tomcat Webserver service. This issue was resolved in version 1.7. DE131187
UAA/ LDAP Tool: Ability to skip SSL verification and allow search depth. This issue was resolved in version 1.7. US413742
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
  • Historian 8.1
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.x. Install Historian 8.x prior to Operations Hub.
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.
Plant Applications
  • Version 8.1
  • Version 8.0, SIM3 (for Integrated Process Apps)
Proficy Workflow Version 2.6, SP1
User Authentication and Authorization (UAA) service Version 4.30.0 or later