Fixed Defects
This topic provides a list of defects that were fixed in this version of Operations Hub.
| Description | Tracking ID |
|---|---|
| Previously, custom plug-ins did not respond to screen size changes in the designer as they did in runtime. Upon inspection, it was found that the screen resize event was missing, preventing plug-ins from resizing dynamically. This issue has now been resolved. | - |
| Pie chart colors were not consistent and sometimes changed unexpectedly
when data was updated. To resolve this, a manual color configuration feature has been introduced, allowing you to define default colors or assign specific colors to data tags for consistency. Your colors now remain unchanged until you manually refresh the page. See Pie Chart |
01116031 |
| Custom HMI graphics with animations did not function correctly inside a Repeater when using certain query types. While Extension Queries worked as expected, SQL Queries updated text but did not change animations, and Entity Queries did not work at all. This issue has now been resolved. | 01121170 |
| The trend chart title property did not update dynamically when the associated Global changed. It remained set to the first selected favorite and did not change with subsequent selections in the Favorite Organizer widget. This issue has now been resolved. | 01151307 |
| Previously, when duplicating a page with Globals in the Operations Hub new layout, selecting Duplicate Globals did not copy the page. The page was only duplicated when Attempt to reuse Globals was selected. This issue has been resolved through a code update. | 01134412 |
In the Operations Hub Classic layout, apps locked by one user could not
be unlocked by other users, even if they were members of the
iqp.tenantAdmin group. This issue affected both domain
and non-domain accounts, preventing administrators from unlocking apps when
the original user was unavailable. This issue has been resolved through a
code update. |
01143639 |
| Previously, on importing an App, renaming it, and then re-importing the
original zip file with the Replace option, images in Interactive Map were lost. This issue has been resolved to ensure that images in Interactive Maps remain intact, even after renaming and re-importing an App. |
01141963 |
| When using the Gauge Bar widget with an Input
Value containing multiple tags, the displayed tag order
varied randomly over time. The order depended on the server response and
changed on page refresh. This issue has been resolved. The widget now maintains the initial order of tags as defined in the input parameter, ensuring consistency across data updates and page refreshes. |
01108286 |
| In the Operations Hub new layout, there was an issue with the Indicator widget where attempting to add a range caused the widget to crash unexpectedly. This issue has been resolved. | 01156111 |
| Previously, Datagrid color animation did not work when the value was
greater than 100. The system was comparing values as strings instead of
converting them to numbers or dates, leading to incorrect animation
behavior. This has been resolved by updating the logic to convert configuration and query data to appropriate types before comparison. |
01135278 |
| Previously, the connection between Operations Hub and Historian would periodically break. A timing issue during startup caused the system to try connecting before the connection channel was fully ready. This issue has been resolved. | 01139122 |
| Previously, a dialog box showing a license issue would appear when editing a page. An incorrect license validation was triggered during page edit. This issue has been resolved. | 01128389 |
| Previously, permissions for individual favorites in the Favorite Organizer widget did not work unless the item was drag-and-dropped. Items added to the tree after initial load did not have the necessary click listener, preventing permission changes. This issue has been resolved. | 01150335/01152598 |
| In the Trend Card widget, the Trend Type – Output
property, which is supposed to reflect whether the chart is showing realtime
data or historical data, did not return a value when a favorite saved in
realtime mode was loaded. A coding issue in the logic prevented the system
from recognizing the initial mode and publishing it to the output. The issue has been resolved, and the output now correctly reflects the chart’s mode when a favorite is selected. |
01156853 |
| The Line Chart widget did not display data the first time the Show Trend toggle was turned on, even though the query returned valid data. The code attempted to process data without checking if it was available, which could cause errors when the chart tried to render. Code has been modified to fix the issue. | 01159261 |
| The chart title in the Trend Card widget did not update correctly when chart controls were hidden. It either showed as blank or displayed null. The code used to update the title only handled the visible chart controls and did not account for the different title element used when controls were hidden. Code has been modified to fix the issue. | 01156268 |
| The DatePicker for historical mode in the Trend Card widget did not
display correctly in Mozilla Firefox when a Favorite Organizer was also
present on the page. A layout conflict affected how the calendar rendered in
Firefox after the Favorite Organizer was added. The issue has been resolved by adjusting the logic to better handle screen size variations. |
01153172 |
| In Live mode, the Trend Card legend did not show the tag
description if the tag had no engineering units (EGU), even though
the description existed and was visible in the trend configuration
panel. The issue has been resolved by updating the logic to include the description whether or not units are present. |
01156100 |
| Previously in Operations Hub, the QR code for the App was not generated, even when internet access was available on the machine. The QR code relied on a Google API that is no longer available. This issue has been resolved. | 01147589 |
| When retrieving current values for Historian tags using the REST API,
the query returned no results if even one tag had no data, despite other
tags having valid values. The issue has been resolved by improving the handling of incomplete data sets, ensuring that valid tag values are still returned even if some tags have no data. |
01153922 |
| For a REST query using a Plant Applications data source, the POST method returned an internal server error in Operations Hub, even though the same request worked in Postman. This issue has been resolved. | 01159092 |
| A 'Datagrid Configuration Error' appeared intermittently in Operations
Hub when loading a custom tab in the Activities page, preventing data from
being displayed. Investigation pointed to missing data in the query tag,
which requires corrected input from the customer. The defect was closed
after engaging Customer Support to follow up for the correct
data. Workaround: Reload the page. |
01137750 |
| Previously, a coding error prevented the containers with gauges from being displayed, even when the visibility condition was met. This issue has been resolved. | 01158139 |
Operations Hub was using jQuery v1.11, which is no
longer supported. To resolve this, jQuery has been updated
across Operations Hub to a supported version. |
01131574 |
| App pages created in the new layout of Operations Hub could be opened
and edited using the Classic layout. This allowed users to save the page in
an incompatible format, leading to page corruption. Once corrupted, the page
could no longer be edited in the new layout, and attempts to import the App
would fail. To prevent this, the system was updated to block editing of new layout pages in the Classic layout. This ensures page compatibility is preserved and avoids data corruption during export or import. |
01161163 / 01153882 |
In the Operations Hub new layout, the Current Datetime
(Local) system global did not refresh automatically, even when a
query on the page was set to run periodically. This behavior worked as
expected in the Classic Operations Hub.The issue has been resolved, and system globals now update automatically. |
01159749 |
| In the Trend Card, the property to display trend legend could not be
dynamically controlled using a global set outside the widget. A coding
oversight prevented the trend chart from properly responding to global value
changes. The issue has been resolved, and the legend can now be shown or hidden dynamically using an external global. |
01161177 |
| The Line Chart did not reflect time-based spacing between data points.
Regardless of whether the timestamps were 5 minutes or 12 hours apart, the
points appeared evenly spaced on the chart, misrepresenting the actual time
intervals. The issue has been resolved, and the Line Chart now adjusts spacing to reflect the true time intervals between data points. |
01165467 |
Chart tooltips were not visible when hovering over bars, as they
appeared behind the chart. The tooltip was rendered inside the body element,
while the chart plugin had a higher z-index, causing it to
overlap the tooltip in coordinate layout.The issue has been resolved, and tooltip values are now visible properly when hovering over chart elements. |
01161122 |
When Operations Hub was registered within Configuration Hub, users were
unable to adjust the transparency (alpha channel) of color settings in the
designer. The color was applied using only the hex value, which does not
support transparency. The opacity (alpha) was not applied because the
required RGBA format was not used.The issue has been
resolved by switching to the |
01161161 |
| A license error message appeared in Operations Hub if left idle for some
time, even though the license had not changed. A temporary loss of
connection between the browser and server caused the system to misinterpret
the reconnection as a license update. The message has been removed from the user interface and will now appear only in the browser console during debug mode for diagnostic purposes. |
01149429 |
| Containers with Gauges were not displaying when expected due to a timing issue during page load. The widget tried to subscribe to query fields before the query was ready. This has been handled to ensure gauges appear correctly when the condition is true. | 01158139 |
| In new Operations Hub, data binding from a Dropdown to a SQL Query was
lost at runtime after duplicating the page into another App. Although the
binding appeared intact in design mode, the input value was not passed
during runtime. The issue has been resolved. Direct bindings between UI widgets and query inputs are now retained and function correctly after duplicating pages. |
01166282 |
| In new Operations Hub, input binding for dropdown selection did not work
correctly after duplicating a page. Although the dropdown displayed options,
its target input field had to be manually re-added and the App re-saved for
values to display properly. The issue has been resolved. Duplicated pages now retain the dropdown input bindings as expected, without requiring manual reconfiguration. |
01161248 |
| When a favorite includes a Historian tag with missing data during the
chart’s timeframe, an error appears on the Trend Card. The widget treats
missing or offline tag data as an error and displays a persistent banner
message each time the trend updates. The banner can be manually dismissed,
but it reappears on update. There is currently no setting to disable or
suppress it. The behavior is working as designed and there is scope for enhancement. |
01170245 |
A page failed to display the correct indicator when a Historian tag had
bad quality and returned NULL, causing conditional
visibility logic to fail. The issue was related to how the
HasNoValue condition handled tag values with bad or
uncertain quality.The issue has been resolved. It is recommended to consider using the Indicator widget, which supports defined ranges and image mapping with fewer plug-in instances. |
01158093 |
| Previously, the trend card widget in historical mode did not support dynamic updates to reflect future data as time progressed. This has been resolved. | 01174101 |
| In the Trend Card widget within the Analysis App, decimal values could
not be entered in the Add Tag Query Criteria fields.
The input field was restricted to whole numbers, preventing decimal
entry. The issue has been resolved. Tag query criteria fields now accept decimal values as expected. |
01173242 |
| After installing SIM 6, certain HMI graphics with color animation appeared completely black and no longer responded to tag-driven color changes. An undefined opacity variable in one part of the code disrupted color animation for non-group SVG elements. The issue has been resolved. Color animation now works correctly for all affected HMI graphics. | 01177225 |
| Previously, the Value Display widget did not align properly when placed
inside a layout framed with Line Connectors. A CSS scope issue caused the
Renaming the
|
01175650 |
In Operations Hub new layout, when you set the grid’s Min Cols
and Min Rows to a higher value (like 20), the settings appear to save
but are lost after reopening the page. The values reset to 5. This happened
because a null check was missing, which caused the settings
not to be stored correctly. The issue is now resolved by adding the missing
check, and the grid settings are saved and restored as expected. |
01175068 |
| Previously, after upgrading to a SIM version, SVG color animations no longer worked in Operations Hub. While data values continued to update correctly, the color animation remained black. This issue affected all SVG elements using color animation, not just text. The issue has now been fixed, and color animations work as expected. | 01173896 |
| The Datagrid widget was not showing row color animations on configuring the Add Animation property. While Add Cell Animation still worked, it only applied to individual cells, not the entire row. The issue occurred when using a page global set to a number, the animation did not trigger as expected. This happened because a condition for handling number-type data was missing. The issue has now been fixed, and row color animations work as expected. | 01172303 |
| Previously in Operations Hub queries, some stored procedures were not returning all expected output fields. This was due to a limitation applied during query execution, which affected how results were processed. The issue has now been fixed, and all output fields are returned as expected. | 01162943 |
| The Text Display widget was ignoring the Align property at runtime, always aligning content to the left. The alignment worked correctly in preview mode but not when the App was run. This was caused by a CSS issue and has now been fixed. The widget now respects the alignment setting as expected at runtime. | 01139090 |
| When using the DateTime Range Picker to drive trend charts, the widget took up too much space on the page. Scrollbars appeared unless the widget was stretched, and the panning buttons were placed above and below the widget instead of neatly to the side. This was due to incorrect CSS. The CSS has now been updated to improve the widget layout, making it more compact and usable. | 01169366 |
The Toggle widget did not output the correct value when bound to a
global variable of type Boolean. When switched off, it returned an empty
string ("") instead of "false", while
"true" was returned correctly when switched on. This
caused issues in logic expecting a proper boolean value. The issue has now
been fixed by updating the widget's HTML property to support Boolean values
correctly. |
01167364 |
In the Analysis App, boolean tags from a Historian data source were
displayed as 1.00 or 0.00 in the Tabular
view, instead of showing 1 or 0 as stored
in the Historian. This happened because boolean values were treated as
numbers, and the display formatting always applied two decimal places. The
issue has now been fixed so that boolean values appear correctly as
1 or 0 in the Tabular view. |
01172230 |
| Previously, there was no option to control the Y-Axis position (Left or
Right) for individual pens in the Trend chart, which limited customization
for dual-axis trends. To address this, a dropdown was added for each pen configuration to let users choose the Y-Axis position - Left or Right. This behavior is supported in both Classic and new Operations Hub. |
01177127 |
| In compact view mode, pens in the Trend Card widget were difficult to see, especially at smaller sizes. This made it hard to read trend data in limited space. As the trend was not originally designed for such small sizes, improvements were made to increase the visibility of the trend area in compact layouts, making the data easier to interpret. | 01180123 |
| Importing an App sometimes failed with an error. This occurred when using the Image widget in Classic Operations Hub Apps and switching between data source options (from File to URL and back to File). In this case, the image data was lost during save, which caused the import to fail. The issue has been fixed by adding a null check during import and updating the Classic layout to correctly restore the image data when toggling between source types. | 01180329 |
| The Pie Chart widget was showing incorrect results when multiple queries were executed in succession. Instead of showing fresh results each time, the chart displayed a merged result from previous queries. This happened because the chart was retaining values across commits to address an earlier sorting issue, but the values were not cleared properly when new data was received. The issue has now been fixed, and the Pie Chart displays correct results for each query execution. | 01184834 |
The Solid Gauge widget did not perform as expected, making the
application page difficult to use. The gauge displayed at only half of its
intended size, and the title did not resize dynamically with the container.
This was caused by incorrect font sizing using em units
instead of px, and the plot height was not adjusting
properly when the widget size was smaller. The issue has now been fixed by
correcting the gauge height, title clipping, and font size behavior for both
the title and current value. |
01179490 |
| When attempting to duplicate a page from one App to another in Operations Hub, an error occurred. A coding error caused a null pointer exception. The issue has been resolved by updating the logic to skip conflict checks for globals. | 01182743 |
| After updating SIM version, the QR code URL was incorrect for Apps with names written in Japanese. While the QR code was successfully generated, scanning it led to an invalid or malformed URL. The issue has been resolved. QR codes now generate the correct URL for apps with Japanese characters in their names. | 01171325 |
| Previously, when a Chart Line widget was configured as a bar chart,
tooltips were not displayed for bars with very small values (0 or
near-zero). Bars with values below screen resolution were rendered with zero
dimensions, making them unresponsive to hover actions. The issue has been resolved by expanding the hover-sensitive area around the start of the bar, allowing tooltips to be shown even when the bar itself is not visibly drawn. |
01185298 |
| In a bar/line chart using two Y-axes, the left Y-axis auto-scaled to
include negative values, even though the data (KPI percentages) was strictly
non-negative. Additionally, the chart displayed two X-axes, causing visual
misalignment. The issue has been resolved. The Y-axis now scales appropriately based on the actual data range, and both series align with a single shared X-axis as expected. |
01180711 |
| The Dropdown widget did not show a scrollbar when there were more items
than could fit in the visible list, preventing users from selecting options
near the bottom. The list height was set in a way that caused it to overflow
the parent popup container, resulting in clipped entries. The issue has been resolved. A scrollbar is now shown as expected, allowing users to view and select all options in the list. |
01185290 |
| The Value Display widget did not reflect updated threshold values from a
query after a manual refresh. It loaded its configuration only once during
initialization and did not reapply changes when query results were updated.
The issue has been resolved. The widget now updates its thresholds and state configuration dynamically when the associated query is refreshed. |
01181941 |
When importing an App using Replace (instead of Duplicate), any
data sources with matching names are replaced. However, pre-existing queries
that reference those data sources retain outdated UUIDs, leading to broken
references and errors like InvalidDataSource.The import process has been updated to ensure that queries referencing replaced data sources are also updated with the correct UUIDs. This applies to both SQL and REST queries. |
01185555 |
| Previously, the Text Display widget always rendered text as
left-aligned, regardless of alignment settings. This issue has been resolved. The widget now respects the selected alignment setting. For right-aligned content, appropriate scroll behavior is added to handle overflow within a parent container when needed. |
01189116 / 01185301 |
| Previously, the dropdown widget accepted and displayed preselect values
that were not part of the predefined options list when using Pre-select
mode: Data. This caused invalid values to appear as selected, potentially
confusing users. This issue has been resolved. The widget now validates that preselect values exist in the configured list of key/value pairs. If the value is not found, the dropdown remains unselected. |
01185294 |
| Previously, the dropdown widget input displayed and applied preselect values that did not match the defined list. Invalid values from the data source were incorrectly shown as selected, instead of defaulting to no selection. This issue has been resolved. | 01184967 |
| Previously, the toggle widget did not reflect the iFIX value on App load because it did not interpret numeric values correctly, treating neither 0 nor non-zero values as valid boolean inputs. This was fixed by updating the toggle to support numeric input, where 0 is treated as false and any non-zero value as true. | 01183641 |
| In Operations Hub new layout, sorting the Apps by modification date did not work correctly when the browser language was set to Portuguese. The sorting order appeared inconsistent or incorrect. This issue has been resolved. Both the Modification Date and Creation Date columns can now be sorted in ascending and descending order across different browser languages, including Portuguese. | 01153915 |
| Previously, certain authentication test endpoints allowed users to gain access by submitting only a valid username, without requiring password verification. This bypassed proper authentication controls and introduced a critical security risk. This issue has been resolved. Only fully authenticated sessions are now allowed access. | 01163408 |
| Previously, Line Chart X-axis displayed overly long date strings after DateTime rendering was introduced. Dates appeared as long, unformatted strings on the X-axis, impacting readability. This issue has been resolved. | 01179297 / 01179295 |
| Previously, when multiple charts were used within a Trend Card, the trend title display was inconsistent at runtime. This issue has been resolved. | 01181954 |
| Previously in Operations Hub new layout, the Trend Card's Details panel did not upgrade properly. As a result, users were unable to access or configure Trend Card properties. This issue has been resolved. | 01173863 |
| Margin behavior (right-side margin persists) is expected to be resolved with the release of End App V2. | 01174815 |
On iOS 18.0.2, Apps created with Operations Hub new layout could not be
scrolled in Safari or Chrome. While navigation through the menu worked, page
scrolling was blocked. A workaround was applied by stopping
touchmove event propagation on mobile devices, restoring
scroll functionality on iOS. |
01192734 |
| After upgrading to SIM10, some Apps in Operations Hub 2024 could no longer be accessed at runtime. Attempting to open these Apps resulted in failures or blank pages. This issue has been resolved. | 01197926 |
| In Apps containing trend charts, the chart displays correctly on the
initial page load. However, after reloading the page, the trend chart may
appear collapsed. Adjusting sizing settings, cards, or layouts did not
resolve the issue. A script handling the trend chart was encountering a null pointer exception during navigation, disrupting proper rendering of the chart on subsequent page loads. A null check was added to the script to prevent the exception. After this fix, the trend chart maintains the correct size across all page navigations. |
01188125 |
| In Classic Operations Hub layout, a user with sufficient permissions
could add pages to an App locked by another user. In the new layout,
however, the same user is unable to unlock or modify the locked application,
despite having the necessary permissions. This issue has been resolved. The logic for verifying Tenant Admin permissions was missing in the new layout. Authorized users can now unlock and modify locked Apps after receiving the proper confirmation prompt. |
01190909 |