Operations Hub Release Notes
This topic provides a list of product changes in Operations Hub for this release.
Version: 2024
What's New
| Description | Tracking IDs |
|---|---|
| High availability enabled through on-premises Windows clustering. | F74492 |
| HMI screens can now adapt to different screen sizes. You can preserve aspect
ratios while defining custom values for positioning and sizing of page
elements. See Coordinate Card. |
F72586 |
Several enhancements for improved functionality, flexibility, and user
experience:
|
F70676 |
Updates to the Trend card:
|
F70676 |
Updates to SVG Request Handling:
|
F70676 |
Updates to Plug-in/Widget functionality:
|
F70676 |
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 |
| Missing page globals after importing a page that has been renamed in the
system: When you rename an existing page in the Operations Hub system that was previously exported and then reimported to the same Operations Hub system, globals bound to the renamed page disappear in the Operations Hub designer layout. However at runtime, the renamed page displays the global values. This issue occurs because the page globals are not duplicated for each page. Instead, both pages (renamed and original) reference the same global via the page ID assigned to the global when it was originally created. To address this issue:
|
503735 |
| Attempting to install the Historian Web-based Clients on Windows cluster nodes
may fail, resulting in the rollback and deletion of some existing files, including
Java Runtime Environment (JRE) and PostgreSQL files. This issue can lead to the
unexpected shutdown of the Proficy Authentication (UAA)
service. Workaround: Do the following:
|
DE212736 |
| At times, the common components (Proficy Authentication and Configuration Hub)
may encounter installation issues on installing from the Operations Hub integrated installer
package. Although the installation process may appear successful, the common
components are not properly installed. This issue is intermittent and arises due to
untranslated product names, resulting in the display of string
placeholders. Workaround: To ensure the correct installation of common components, simply run the installer again. |
DE211900 |
| Limitation in Marker Shape Customization in Interactive Map
Designer: Currently there is a limitation in the capability to alter marker shapes seamlessly within the Interactive Map Designer. In the Interactive Map Designer properties, if you attempt to change the shape of the marker from round to square, the expected change does not occur. |
DE208208 |
| 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 |
| 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 |
| 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, the camera functionality was provided by a native widget. However, it was unclear how to retrieve the image captured by the camera plug-in. To address this, a new camera plug-in has been introduced. This plug-in includes an Image (base/64 encoded) output and features Image ID generation. When this property is enabled, a unique ID can be included when submitting the image. This ID can then be used to retrieve and display the image using the image plug-in. | 01069645 |
| Previously, when two different datalinks were used in plug-ins, both referencing the same source tag but using different queries, only plug-ins linked to one data source were refreshing in the run mode. This issue has been resolved. | 01076961 |
| Previously in Trend Card, when providing a JSON input for Historical data, the control rapidly switched between 'Live' and 'Historical' modes, causing some parts of the header to flash between two states. The trend itself never appeared. This issue occurred specifically with Historical JSON input, while it worked fine with Live JSON input. The issue has been resolved. | 01081841 |
| Previously, in Pivot Grid, the horizontal scrollbar was missing when the list
was long. Users had to scroll down to the end of the list to get the horizontal
scrollbar. This issue occurred when there was a long list and many columns,
requiring both vertical and horizontal scrolling. From Operations Hub 2023.1 onwards, plug-ins will not honor the JSON manifest height & width. Instead, use the widget properties. |
01083314 |
| There was an issue with rounding values in Pivot Grid when the query used to
populate the plug-in returned both numeric and string values. The problem occurred because we tried to round values in the Pivot Grid using its built-in format feature, which includes setting the "precision" parameter to specify the number of decimal places. However, this parameter only works with numbers. When the query returned numeric values as strings, the precision setting did not work. This issue has been resolved. |
01083372 |
Error messages appear for users belonging to the
iqp.studioAdmin group after logging into Operations Hub. Removing
the user from this group resolves the issue.By design, users logging into
Operations Hub should not be added to the |
01083439 |
| Previously in Favorite Organizer, when dragging a favorite from the
'Unorganized' folder and attempting to drop it into another folder, the focus of the
favorite remained in the 'Unorganized' folder. This issue occurred when working with
long lists that required scrolling. To temporarily resolve the issue, a right-click context menu is added to allow users to cut/paste favorites as a workaround. |
01068335 |
| Previously in Datagrid, the horizontal scrollbar was missing when the list is long. The scrollbar only appeared when scrolling down to the end of the list. This issue occurred due to the way the Datagrid height is set. if the height is set in pixels and is larger than the card height itself in the designer, the browser scroll takes over. This means that without scrolling to the bottom, you will not see the horizontal scrollbar. To fix the issue, a menu has been introduced. Users can right-click on the column header and fix any column to the left or right. | 01078908 |
| Previously, while exporting applications from one server and importing them into another led to loss of images. This issue occurred due to missing application and image mappings in the database, resulting in the application not exporting all the images used within it. This issue has been resolved. | 01086089 |
| Previously, the Trend card was losing the visibility settings for individual tags configured through the eye icon in the legend when switching from normal trending to stacked trending. This issue has been resolved. | 01072257 |
| When using a data query with the tag display format parameter defined as input field (not fixed value) for Color animation link, a warning was displayed in Run mode even if the tag display format input was defined. This issue could be worked around by defining the tag display format parameter as fixed value at the data query definition. | 01076959 |
Adding a UAA user with the iqp.studioAdmin group mapping did
not bring the user to the Operations Hub designer as expected. This issue has been
resolved. |
01081867 |
| Previously, the Button widget did not work properly to set the value of a global using the formula option (as data source). This issue has been resolved. | 01088159 |
| Previously, animations were not working properly because of how the program handled 'False' or the number '0' values. Instead of recognizing 'False' as a specific value, the program interpreted it as 'undefined', which led to the incorrect behavior. This issue has been resolved. | 01091391 |
| Previously, the Sparkline widget was not adjusting its size to fit the available space in the browser window, regardless of the browser size. This issue has been resolved by upgrading to the latest version. | 01089088 |
| Previously, the plug-in upgrade process was not correctly passing the command line arguments to the console program, resulting in the program not receiving any inputs. This issue has been resolved. | 01091554 |
| Previously in Trend card, when trying to create a Historical trend, it took a very long time for the data to load. This made the web browser slow down or even crash, especially when using Google Chrome or Firefox. This issue has been resolved. | 01091823 |
| Previously, the Datagrid displayed incorrect values if an alias with a dot in its name is used along with Column Cell Animation. This issue has been resolved. | 01092998 |
| Previously, when displaying the last updated or modification date for applications, the timezone abbreviation was assumed to be 3 characters long. This assumption caused issues when displaying timezones with abbreviations that were 4 characters long, such as those in Europe. Code has been modified to correctly handle timezone abbreviations with 4 characters, ensuring that the dates are displayed accurately regardless of the timezone abbreviation length. | 01094598 |
| Previously, the line connectors were not scaling properly causing misalignment of line connectors with other objects on the page when the application is opened in a different browser window size or on a different screen. This issue has been resolved. | 01094596 |
| Previously, when using Solid Gauge with the text position set to 'Center' and an Engineering Unit added, the text is not centered, and the Engineering Unit is displayed below the value instead of on the right side. This issue has been resolved. | 01091268 |
| After importing multiple .csv files to the Asset model in Operations Hub 2023.1 server, the customer is unable to export assets (full export). The error messages indicate issues with GET requests to certain endpoints, resulting in HTTP status codes 404 and 503, indicating "Not Found" and "Service Unavailable" respectively. This issue has been resolved. | 01102688 |
| When multiple rows are selected in the Datagrid, and then one or more rows are unselected, the output global does not update correctly. It retains the ID of the last unselected row instead of removing it. This issue has been resolved. | 01098558 |
| Previously, the radio button was not functioning correctly. This is fixed now. | 01106068 |
| The Datagrid widget is not cleared when moving between pages, even when nothing is selected in the dropdown. This issue has been resolved. | 01106079 |
| Previously, graphical objects were not displaying correctly in Operations Hub. This issue has been resolved. | 01078488 |
| When there are multiple charts on the same page, such as a Trend Card and a Histogram, their configuration interfaces appear on the same layer as the chart. This can result in the configuration interface hiding below the other chart. This issue has been resolved. | 1086298 |
| When two pages within Operations Hub use equal OPC UA write queries connected to input visuals, only one page works correctly at a time. The other page displays an exception error. This issue has been resolved. Each page's 'Page Data' is independent of other pages, even if they use the same queries. | 01098726 |
| Previously, there was a discrepancy between the update of the input field's global value and its displayed value. This issue has been resolved. | 01098711 |
| Adding more than six trend charts on a page enables vertical scroll bars, even when there is sufficient space to display the charts without scrolling. This issue has been resolved allowing for a better display of multiple charts on a page. | 01100338 |
| After importing an application into a different system and selecting the 'Replace' option, the query configuration within the application is lost. Although the query appears under the Query tab, selecting or opening it results in an empty page. This issue has been resolved. The import process replaces the query configuration as part of the application import, ensuring that the query is correctly configured in the new system. | 01096584 |
| After upgrading to Operations Hub 2023.1 SIM1, the solid gauge widgets were not appearing as expected in the application. This issue has been resolved. | 01099341 |
| Previously, images were lost during the export/import operations between the production and test servers in Operations Hub. This issue has been resolved. | 01086089 |
| When the pie chart widget has a larger number of labels, the labels overlap, making it impossible to read all of them. This issue has been resolved. | 01102683 |
| Previously, clicking the help icon on the Trend Card widget did not lead to the correct page on the online help. This issue has been resolved. | 01102080 |
| After upgrading to SIM2, several issues have been identified with the Dropdown widget. This issue has been resolved. | 01106003 |
| Previously, the Dropdown widget would set a "null" value to the global if used as a target. This impacts the conditions applied to pages, as a condition may require the global to have a value. However, with the current behavior, the condition renders true since "null" is considered a value. This issue has been resolved. | 01106267 |
| Previously, users with the freemium tier were incorrectly forced into demo mode with 2-hour time limits. This issue has been resolved. | 01109852 |
| Previously, users were incorrectly forced into demo mode after updating to the latest sales demo 2023.1 key. This occurred when the new sales demo key contained new licensing tiers such as canvas, insights, or ultimate. This issue has been resolved. | 01110391 |
| Upgrading Operations Hub to the latest version resolves port starvation issues. | 01114544, 01072610 |
When attempting to execute a PUT request that requires the Content-Type header
to be set to application/vnd.ge.mes.v1.full+json, the request fails
to be processed as expected. The issue has been resolved by updating the request
processing logic to correctly handle the Content-Type header parameters for PUT
requests. |
01090895 |
| When attempting a partial export of assets, the process sometimes lasted for several hours, with the export process appearing to hang intermittently. This behavior was inconsistent, with export times varying between one to two hours. The issue has been resolved by identifying and addressing the root cause of the extended export times and hang-like behavior. Partial exports now complete in a reasonable amount of time, providing a smoother experience. | 01100372 |
| After attempting to import an application exported from the Operations Hub within the Configuration Hub system using the import function, the import process fails. This issue has been resolved by identifying and addressing the root cause of the import failure. | 1112337 |
| After applying the SIM4 patch to Operations Hub 2022.6, the application no longer supports the Dropdown widget version 1.0.0. Attempts to upgrade the widget to version 1.0.1 using the application upgrade utility were unsuccessful. The issue was resolved by updating the Dropdown widget specification in SIM5, allowing the application to properly support and utilize the upgraded version of the widget. | 01117814 |
| When attempting to import an application in Operations Hub 2022.06 SIM4, an error message appears: "Error while publishing application: null." This issue is related to the server not finding the image file in the images folder, causing an exception and halting the import process. The fix implemented for this issue catches the error, logs it, and allows the import process to continue and complete successfully. | 01119819 |
Widgets in applications developed in Operations Hub Classic did not render
properly, exhibiting issues such as:
This issue has been resolved. |
01105598 |
| The issue affects the functionality of show/hide conditions assigned to visual objects in the new layout in Configuration Hub (Classic Operations Hub does not have this issue). When a show/hide condition includes a constant on the right side of the equation (e.g., 'Flow1.value >= 1200'), the condition works as expected. However, when the condition includes a flow on the right side (e.g., 'Flow1.value >= Flow2.value'), the condition never works, and the object always remains hidden. This issue has been resolved by implementing a fix that ensures show/hide conditions work correctly in all scenarios, including when flows are used on the right side of the equation. | 01107773 |
| Currently, errors returned by an Extension query are not displayed on the page at runtime unless a plug-in from the Integration suite is present on the page. This behavior has been identified and resolved in the latest update, ensuring that Extension query errors are always displayed on the page for improved visibility and troubleshooting. | 01117522 |
| When a map is configured on a page, the marker icon and position settings are automatically reset every time the page reloads. This issue has been resolved in the latest update, ensuring that the marker icon and position settings are retained even after the page is reloaded. | 01118631 |
| When using a repeater to generate check boxes, the array length generated by there repeater for check boxes varies inconsistently. This led to unexpected behavior when used as input for SQL parsing. Code has been modified to resolve the issue. | 01118937 |
| When multiple Dropdown widgets are present on a page, changing the value of one Dropdown widget does not reset the subsequent dropdowns to a blank state as intended. To resolve this issue, a new property called 'Dependency' has been introduced. This property allows us to link all the dependencies to a particular dropdown, ensuring that when the value of that dropdown changes, the subsequent dropdowns are reset to a blank state. | 01106844 |
| When using the 'Historical By Interval-Calculated Mode' query in a page to calculate a minimum value in a time interval, the configuration was not getting saved in Page Data. Code has been modified to fix the issue. | 01123540 |
| Users were incorrectly forced into demo mode with a 2-hour time limit on the Freemium Tier. Code has been modified to fix the issue. | 01109852 |
| Creating and editing a custom graphic in the new Operations Hub caused the page to crash. This issue has been resolved. | 01113884 |
| Previously in Trend card, selecting 'Stacked Y-Axis' mode does not work as expected. Instead of splitting into multiple trends with each having its own tag, it behaves the same as 'Trend Card' mode, showing just one trend with all the tags. This issue occurs in both Live and Historical modes. This issue has been resolved. | 01120966 |
| When attempting to set the input query to 'none' after it has been previously set to a specific query, an error occurs. The input query reverts back to the previously selected query. This issue has been resolved. | 01119329 |
| Widgets and graphics were not displaying while editing a page. This issue has been resolved. | 01124748 |
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 |
|
| Configuration Hub | Configuration Hub 2024 |
| Proficy Authentication (UAA) | Proficy Authentication 2024 |
| Proficy iFIX |
|
| Proficy CIMPLICITY |
|
| Industrial Gateway Server | IGS OPC Server 7.68 and later |
| Proficy Workflow | Workflow Task Client 2.6 SP2 |
| GE Common Licensing | Version 20.7.2423 and later |