Operations HubOperations Hub Release Notes
This topic provides a list of product changes in Operations Hub for this release.
Version: 2022.4.1
What's New
| Description | Tracking IDs |
|---|---|
Enhancements to the Trend Card widget:
|
F64020 |
| Introduced Favorite Organizer widget. | F63934 |
| Provision for Auto-login configuration. | F64022 |
| Enhancements to SQL queries with multiple result sets. See Use the Relational Database Query in the Designer | F64156 |
| New plugins in Operations Hub: Button, Check Box, Radio Button, Slider, Text Area, Text Box, Toggle, Chart LineChart Pie, Gauge Bar, Gauge Circular, Gauge Linear, Image, Simple Indicator, List, Text. |
Known Issues and Limitations
| 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 |
| 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. |
Fixed Defects
| Description | Tracking ID |
|---|---|
| Previously, the output returned by the Dropdown integration widget was incorrect if the query had two similar Select output field values. This issue has been resolved. | SF00991349 |
| Previously in the end app, the size of the Dropdown native widget appeared larger than the other widgets (for example, Input) set to the same size. This issue has been resolved. | SF00993323 |
| Previously, the dropdown selection did not revert to default when switching between pages in an end app. This issue has been resolved. | SF00986712 |
Previously, Dropdown label name appeared for a dropdown in the
end app even when no label was given. By default, the dropdown integration widget
populates a label if the Label property is empty. This issue
is fixed by setting the default label value to a blank value. |
SF01000424 |
| Previously in the end app, images were not appearing in the size set in the Datagrid widget. This issue is fixed by providing an option to set an image/icon size for datagrid Rows property. | SF00991337 |
| Previously, if an administrator renamed a favorite created by a non-admin user, the favorite was inaccessible to the non-admin user. This issue has been resolved. | SF00991863 |
| Previously, output variables lost their global status if the entity was renamed. This issue has been resolved. | SF00996685 |
| Previously, the Trend widget appeared with missing text if the browser language was set to Dutch. This issue has been resolved. | SF00997200 |
| Previously on the Trend chart, values with decimals appeared as whole numbers on the y-axis scale if the option AUTOFETCH LIMITS was disabled. This issue has been resolved. | SF01000873 |
| Previously, SQL queries with multiple result sets cannot be added on the same page. This issue has been resolved. Multiple instances of a query with multipe result sets, each with different inputs per query can be added to the page. | SF00965428, SF01002841 |
| Previously in Operations Hub page designer, a query with an identical input and output name added to a page led to data issues in the end app. This issue has been resolved. | SF00984121 |
| Previously in the end app, the values in a dropdown loaded inconsistently. This issue has been resolved. | SF00990033 |
| iFIX Color and String lookup tables were not working in Operations Hub mimics. Animation with Exact Match did not work for analog tags (AI, AA). This issue has been resolved. | SF00990809 |
| Previously in the dropdown plugin, a default label name appeared in the end app even if no label name was provided. This issue has been resolved. | SF01000424 |
| Previously on importing an app with Operations Hub screens resulted in the entities being overwritten. This issue has been resolved. | SF00998136 |
| Previously in Datagrid and Pivot grid, there was no option to disable data export at runtime. This issue has been resolved by providing the Allow Export property. | SF01004560 |
Previously, multiple pivot tables overlapped at runtime if the plugin height
was set to 0. This issue has been resolved. |
SF01004570 |
| Previously, the pivot grid table disappeared on using the export option at runtime. This issue has been resolved. | DE176354 |
| Previously, the DateTime Range Picker design was not user-friendly. This issue has been resolved. | SF01004753 |
| Previously in Interactive Map, some images were lost after exporting and importing the app. This issue has been resolved. | SF01004368 |
| Previously, if a hidden condition was applied to a container with a paginated table, the table data was not populated as expected at runtime. This issue has been resolved. | SF00990614 |
| Previously with Historian extension queries, the data calculation based on daylight saving time led to varied output values. This issue has been resolved. | SF00995370 |
Previously, Historian extension queries did not support the special character
/ (slash) in Historian tag names. This issue has been resolved by
modifying the code to handle more special characters including /
(slash). |
SF00996737 |
| Previously, errors occurred on upgrading from Operations Hub 2.1 to 2022. The upgrade related errors have been resolved. | SF01004243 |
| Previously on upgrading to Operations Hub 2022, error logs indicated plugin transformation errors for some of the widgets. This issue has been resolved. | SF01004995 |
| Previously, date and timestamp format error occurred on switching to the Japanese language in Chrome. This issue has been resolved. | SF01006938 |
| Previously, an unknown error occurred on importing an app as a duplicate. This issue has been resolved. | SF01005341 |
| Previously, issues were observed with the alignment of the Date Picker widget at runtime. This issue has been resolved. | SF01005133 |
| Previously in Analysis App trend configuration section, the specification limit labels were missing if Chrome browser language was set to Norwegian. This issue has been resolved. | SF01010682 |
| Import log file displayed errors on importing an asset model to Operations Hub. This issue has been resolved. | SF01009452 |
| Random errors occurred in Operations Hub from time to time. This issue has been resolved. | SF01009316 |
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 |
| 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 and greater |