Known Issues and Limitations
This topic outlines the known issues and limitations applicable to this release of Operations Hub.
| Description | Tracking ID |
|---|---|
| Compatibility Requirement for Same Box Installation: When Proficy Authentication and Operations Hub are installed on the same machine, both applications must be upgraded to the same version (2025) to ensure proper functionality. Upgrading only Common components to version 2025 while Proficy Operations Hub remains on version 2024 can cause runtime failures, specifically impacting the End App functionality. |
970332 |
In Classic Operations Hub, Users with iqp.developer
Role Can Modify User Permissions:In the classic layout of
Operations Hub, users assigned only the This behavior is inconsistent with expected role-based access control and differs from how permissions are enforced in the new Operations Hub layout. |
957321 |
| Slider Value Resets to 0 When Same Global is Used for Input and
Output: The slider is trying to read a value (input) and write a
new value (output) to the same global at the same time. On page load,
this creates a conflict. The slider does not know which value to keep, so
it defaults to Workaround: Avoid using the same global as input and output in the Slider widget. Instead:
This ensures the slider works as expected and does not reset to zero. |
937281 |
| External Libraries Not Supported in Scripts: The scripting editor only supports native Python and does not allow external libraries such as NumPy, Pandas, Flask, or TensorFlow. | 913128 |
| 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 screens to Operations Hub using a remote Proficy Authentication (UAA) instance. | DE197305 |
| 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 |