Operations HubOperations Hub Release Notes
This topic provides a list of product changes in Operations Hub for this release.
Version: 2023.1
What's New
| Description | Tracking IDs |
|---|---|
Page and Layout Enhancements
See Coordinate Card, Flexbox Card, Grid. |
F69489, F69492 |
Screen Building Tools for working with Page Elements
See Display Panel. |
F67512 |
| License enforcement for data sources, widgets, and layouts. See Understanding Operations Hub Licensing Tiers, Add Plant Applications Data Source (Classic). |
F69493, F69494 |
| Partial model deletion | US586352 |
| Trend enhancements for batch processing. | US580224 |
| Added Convert Datetime feature to enable conversion of the SQL Datetime from UTC to browser's local time when displaying data, and input Datetime parameters to be converted from the browser's local time to UTC. See Create SQL Query (Classic). | 2023 SIM2 |
Known Issues and Limitations
| Description | Tracking ID |
|---|---|
| Changes made to the tag query criteria condition are not reflecting in the
trend plot. Workaround: To resolve the issue, do the following:
|
530223 |
| Applies to the following plug-ins when importing applications from an older
version of Operations Hub Classic to Operations Hub 2023. Issue: When you import an App to the new system, the plug-in’s image
source settings are altered.
Workaround: Access the Image/Indicator plug-in in the imported App and change the altered Type back to its original type settings. The original source information (if exists) is retrieved. |
DE198548 |
| 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.
|
DE161643, DE161690 |
| 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 |
| 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 |
| In Histogram, when X-axis range is provided manually, the bins towards the left and right end of the chart get truncated. | DE186605 |
| Unable to publish iFIX / CIMPLICITY screens to Operations Hub using a remote Proficy Authentication (UAA) instance. | DE197305, DE197304 |
| Unable to publish model from CIMPLICITY project to Operations Hub using a remote Proficy Authentication (UAA) instance. | DE197366 |
| Currently in Operations Hub page designer, every undo and redo action causes a redraw of all the elements on the page. | DE196399 |
| New Designer - When a large number of Solid Gauge plug-ins are added and configured within a layout, a performance issue arises, resulting in higher response times. This issue is particularly observed when configuring the Solid Gauge with "Preview Data ON" condition. | DE202270, DE199246 |
| Currently, the date format received from the server can only be parsed by the client without considering the time zone, resulting in the client displaying its own time zone time. | DE123419 |
| During a load test on the Auto Sync application, which uses OPC UA as the data source, a significant number of failures (8-9%) occur, particularly during peak load. The majority of these failed calls/APIs are related to the login process, resulting in a '503 Service Unavailable' error. | DE160706 |
Batch widgets - To ensure compliance with 21CFR11 regulations for e-signatures,
the full user name (not just the user account name) needs to be logged when calling
the addsecurityevent function. |
DE175035 |
| When attempting to add or perform any operation on the Batch plug-ins, a server error dialog appears. | DE189081 |
| New Designer - At runtime, the actions 'Next Page' and 'Previous Page' do not work as expected. | DE190509 |
| New Designer - If you switch from the Details panel to Components panel, the plug-in selection is lost. The current workaround is to select the plug-in again, which will refresh the Details panel and show the relevant information properly. | DE195533 |
| When designing a page with multiple cards using the fit option for the grid layout, and subsequently changing the page width and height at runtime, the gutter space between the cards scales along with the page. | DE197417 |
| The behavior of the 'Undo' functionality on the Display Panel does not work as expected. | DE197540 |
| When you make changes on a page, the save button is highlighted prompting to save the modifications. However, if those changes are reversed, effectively returning the page to its previously saved state, the save button continues to remain highlighted. The absence of changes does not deactivate the save button, as there are no pending modifications to be saved. | DE199776 |
| New/Classic Designer - Actions defined for the Interactive Marker are not working properly in the end app. | DE199825 |
| The Toggle plug-in's appearance differs between the runtime environment and the page designer. | DE199838 |
| New Designer - There is no cancel button to discard changes made on a page. | DE199847 |
| The Hidden property is not functioning correctly for plug-ins within a repeater. Despite being marked as 'hidden', plug-in/s continue to be visible at runtime. | DE200150 |
| Operations Hub 'About' section version information does not reflect the SIM1 version. | DE200665 |
| The 'Undo' button undoes the most recent keystroke instead of reverting to the original state of the HMI graphic. The problem also extends to other properties, as changing them and using the undo button may require multiple undo actions before reaching the original value. | DE200918 |
| When you import an app and choose the 'replace' option, the UUIDs (Universally Unique Identifiers) of the queries in the imported application are different from the UUIDs present on the page. | DE200978 |
| When an undo operation is performed, the preview of the plug-ins may not load
properly. Workaround: Select the refresh icon on the toolbar to display previews properly. |
DE201052 |
| Copy pasting multiple instances of plug-ins on a page does not increment the plug-in IDs. As a result, multiple plug-ins can have identical IDs. | DE201197 |
| The Dropdown plug-in ID is not reflected or paired with the dropdown name on the Page Visuals Tab. | DE201198 |
| Performance delays occur when multiple operations are performed within a span of 5 to 10 seconds in Operations Hub Page Designer. The application becomes slow or unresponsive. | DE201452 |
| When a line connector width is modified, the arrow attached to the line is not getting updated proportionally to match the line width. | DE201514 |
| While updating plug-in properties using multi-selection on a page, some properties remain unchanged. | DE201824 |
| If you modify the default properties of the page grid layout in an app, the default grid layout properties do not appear anymore for any additionally added pages. Instead, the settings from the previously created page are carried over to the newly created pages. | DE201934 |
| New Designer - The query output binding view feature is not available. In the classic designer, users can select a query output and view where it was used on the page. It was also possible to easily unbind a query, if needed. | DE202013 |
| Entering the plug-in height and width values less than the defined minimum values does not trigger a warning message. Min Height and Min Width field value validations are not working for all plug-ins on both the flex and coordinate layouts. | DE202207 |
| Using the line connector tool, if you attempt to draw a line from any corner of a rotated plug-in, then the line is positioned differently and does not honor the desired starting position. The line should originate from the exact location where the user intended to draw it, regardless of the rotation of the plug-in. | DE202225 |
When dealing with a large tag database, the tag browser pop-up dialog is
challenging to use due to the following reasons:
|
DE202265 |
| When plug-ins and line connectors are added to the page, selecting multiple
elements and hiding the lines retains the selection properly. However, when hiding
plug-ins, the selection is lost. The selection of both lines and plug-ins is not consistent when hiding and un-hiding elements from the page visuals. When hiding a plug-in and then un-hiding it, the selection is automatically restored. However, when performing the same actions with lines, the selection is not automatically restored upon un-hiding. |
DE202416 |
| The Camera plug-in will only work in runtime for keys enabled for custom plug-ins. | DE202984 |
| Attempting to modify the Generate ID property in the Camera plug-in leads to an error. | DE202991 |
Fixed Defects
| Description | Tracking ID |
|---|---|
| Previously, values on the X-axis of a trend chart could not be rounded to have fewer decimals, resulting in overlapping and unreadable labels on the graph. This issue has been resolved by allowing to round values on both the X and Y axes. | SF01047164 (DE191940) |
|
Previously, Pareto chart exhibited inconsistent behavior setting the right axis to 120%. This issue has been resolved by providing an option to disable aligning the tick marks. A new property called Align Tick Marks is introduced in the Pareto chart with a check box option. By unchecking this box, the tick marks on the right axis would no longer be automatically aligned to the size of the bars on the left axis. Note: Classic Operations Hub apps containing Pareto chart
plug-ins will automatically have this property enabled upon upgrade and for new
plug-ins after installing SIM1. Existing Operations Hub apps (via Configuration
Hub) containing Pareto chart plug-ins will not contain this property upon upgrade.
Only newly added Pareto chart plug-ins will contain the new property and will be
enabled by default.
|
DE199581 |
| Previously, the Line chart lacked the capability to manually set the range limits for the Y-axis. The Y-axis would automatically adjust based on the received data, which made it challenging to compare the data with other graphs. This issue has been resolved. | DE199580 |
| Previously, markers on an Interactive Map were visible in the designer mode, but would disappear on transitioning to the runtime environment. An "Unknown Error" dialog would appear upon running the app. Clicking the "Dismiss" button on the error dialog would display the page, but none of the Interactive Maps on that page would show any markers, even though the page contained three Interactive Maps with multiple markers. This issue has been resolved. | SF01070099 (DE200862) |
| Previously, when using the Trend Chart and exporting the data to a CSV file, an issue occurred where the column headings in the exported file were not correctly reflecting the tag names. Instead, the column headings would display identical tag names, regardless of the actual tags plotted on the chart. This issue has been resolved. | SF01068322 (DE200760) |
| Previously, when viewing the application on an iPad device, an issue occurred where the check mark within the check box appeared shifted beyond the bounds of the check box. This issue has been resolved. | SF01074749 (DE200761) |
| Ops Hub 2023 - Visual Inputs linked to OPCUA Write data queries & HMI visuals (e.g. Pump) using Color animation linked the OPCUA write functionality does not work. | SF01074108 (DE200450) |
| Previously, while attempting to install a new certificate, a 'pad block corrupted' error was encountered. This error prevented the installation of the certificate. Despite verifying the certificate's validity with KeyStore Explorer, the installation process remained unsuccessful. This issue has been resolved. | SF01052705 (DE194695) |
| Previously, "scoped CSS" setting was not enabled for the new designer, which led to issues. This has been fixed now by modifying the Scoped CSS support for the HTML widget to be universal to address Custom plug-in issue in the new designer. | SF01081234 (DE201757) |
Previously, EMBED.getGlobalData function failed to retrieve
the global value set in the plug-in, causing unexpected behavior and impacting the
functionality of the product. It was found that the issue was in the
getPluginPrivateData function, which has been fixed to address
the problem. |
SF01068027 (DE197971) |
| Previously in Visualization widget (bar chart), after zooming in and moving the X-axis, the box that includes time and value appeared far from the area where the mouse pointer was positioned. This issue has been resolved. | SF00907369 (DE150562) |
| Previously, 'GE Operations Hub Httpd Reverse Proxy' was creating large log files that are not automatically deleted. This issue has been resolved. | SF01065078 (DE197539) |
| Previously, the rotation feature was not successfully applied, resulting in the plug-in becoming locked and unable to be rotate further. This has been fixed bow. | SF01078409 (DE202065) |
| Previously, when all servers for monthly maintenance were restarted, alerts with recent timestamps appeared in the system, even though these alerts were actually generated before the restart. On inspecting the Historian data in Historian Admin, it was found that there were no corresponding values and timestamps on Historian tag for those alerts. This inconsistency between the system's alerts and the corresponding Historian data has caused confusion and potential data integrity issues. This issue has been resolved. | SF01035338 (DE193329) |
Compatibility Matrix
| Product | Required Version |
|---|---|
| Proficy Historian |
Note: Historian REST APIs are required for REST integration between Operations Hub and Historian.
Historian REST APIs are installed automatically when you install
Historian web-based clients. |
| Proficy Plant Applications | For feature-specific compatibility, refer to the table below.
|
| Configuration Hub | Configuration Hub 2023 |
| Proficy Authentication (UAA) | Proficy Authentication 2023 |
| Proficy iFIX |
|
| Proficy CIMPLICITY | CIMPLICITY 2022 |
| Industrial Gateway Server | IGS OPC Server 7.68 and later |
| Proficy Workflow | Workflow Task Client 2.6 SP1 SIM5 |
| GE Common Licensing | Version 20.5.2217 and later |
The following table lists feature-specific compatibility for Plant Applications version.
| Operations Hub 2023 Features | Plant Applications 8.2 | Plant Applications 2022 | Plant Applications 2023 |
|---|---|---|---|
Classic Designer Layout:
|
Yes | Yes | Yes |
Classic Designer Layout:
|
Yes | Yes | Yes |
New Designer Layout:
|
No | No | No |
New Designer Layout:
|
Yes | Yes | Yes |