AVEVA OMI issues

Issue

Description

OMI preview issue

Warnings appear in the logger when OMI Preview is launched when using Object Wizards/Symbol Wizards in a seven-level containment relation, using the maximum template length (32 characters).

Show graphic issue

The title of a show graphic is cut off in the OMI web client when using long object names (> 32 characters).

Localized character issue

Localized characters do not display in the component column of the Logger in the Operations Management Console when using long object names (> 32 characters).

Incomplete tooltip issue

The Tooltip for an instance graphic is displayed incompletely in the Japanese language version when long object names (> 32 characters) are used.

AutoComplete issue

When used with long object names (> 32 characters), the autocomplete text is not fully shown in the Graphic or Layout editors, or in the Edit Animations dialog, that is, the text is cut off on the left side.

Graphic alignment issue

When long names are used for TagName, Hierarchical Name, and Contained Name, graphics are shifted to the right when displayed using the Value Display animation at run time.

Issue Number

Description

IMS 1212168

On Windows 10 operating systems, layouts created in System Platform 2020 with non-English OS/regional settings show a warning and do not open when migrated to System Platform 2020 R2 or 2020 R2 SP1.

Workaround: Before migrating the galaxy, make sure the operating system locale is set appropriately by following these steps:

1. Open the Windows Control Panel and select Region.

2. Select the Administration tab when the Region popup opens. The Administration tab contains two buttons:

   • Copy settings

   • Change system locale

3. Select Copy settings and then mark the checkboxes to copy current settings to "Welcome screen and system accounts", and "New user accounts".

4. Select Change system locale and then choose the applicable locale from the dropdown list.

TFS 1369154

Under certain circumstances, an instance derived from a template with an invalid reference will not show a warning during design time. This can occur if the following occurs:

5. A symbol is added to the Graphic Toolbox with an undefined relative reference, for example, “Me.Attribute001,” where Attribute001 has not been created yet.

6. The symbol is then added to a layout.

7. The layout is linked to a UDO (User Defined Object) template. When the template is saved, no warning is displayed.

8. When an asset is derived from the template, no warning is displayed for the instance either.

   Result: Although no warnings are issued during design time, when you create and then deploy a ViewApp with the linked layout, and show the linked layout in any screen, an error message will be displayed at run time (or in Preview Mode) that will allow you to troubleshoot and correct the error. The message will be similar to:

   "Element ‘TEXT1’ in Symbol ‘UDO_001.S1’ has Configuration error: Invalid reference ‘Galaxy1:Me.Attribute001’ with owning object ‘UDO_001’ does not exist."

Missing NavTree

After upgrading or migrating an AVEVA OMI ViewApp from 2017, a warning message states that the NavTree entity could not be found. In 2017 Update 1, this navigation object has changed and is now called “NavTreeControl.”

Workaround 1: To replace the NavTree object in a ViewApp or Layout when upgrading from System Platform 2017:

9. Open the ViewApp or Layout that shows the warning.

10. In the ViewApp or Layout editor, look in the Actions list for all references to “NavTree.” An icon showing “Content not available” will be displayed for these references.

11. To see the entire action list for a ViewApp, toggle the Actions for Primary switch to show Actions for Home (does not apply to the Layout editor).

    1. Replace the NavTree object with the new NavTreeControl.

    2. Search for NavTreeControl under the Toolbox tab.

12. Drag the NavTreeControl onto the pane to replace the NavTree.

13. Confirm that you want to replace the content, then save the ViewApp or Layout and close the editor.

14. Verify Layouts and ViewApps no longer show any warnings related to the NavTree.

15. Deploy the ViewApp.

Workaround 2: To replace references to NavTree when importing packages from System Platform 2017:

16. Launch the IDE and open the “Find” dialog.

17. Search for “NavTree” using the default search settings.

    If the package file contains the obsolete NavTree object, it will be listed in the search results.

18. Double-click the NavTree search result, which will select the NavTree object in the Graphic Toolbox.

19. Delete the NavTree object from the Graphic Toolbox.

20. Use Workaround 1 to replace the NavTree object with the new NavTreeControl object.

TFS 774717

When an AVEVA OMI application (View.exe) that uses one of the following web controls is run in 4K mode or on multiple 1080p monitors, under certain circumstances the application may stop responding:

• InSightApp

• MapApp

• WWWebAppControls

Workaround: When running a ViewApp that uses a web control on a 4K monitor, set the monitor resolution to 2560 x1440 or less. When running the ViewApp on 1080p monitors, do not attempt to span multiple monitors.

TFS 777504

The GetCPQuality() scripting method is not supported in AVEVA OMI. If used in a ViewApp, it always returns quality = 0 (bad quality). This is similar to issue L00150114, listed above.

TFS 781006

If an invalid custom property is added to a symbol, no warning is logged in the Operations Control Management Console, even though no value is displayed for the custom property.

TFS 781620

The Height and Width properties of a group with text elements do not change in accordance with changes made to the label font size, and are not rendered correctly.

TFS 784470

Tooltip animations that contain multiple lines of text with line breaks may not display properly in deployed ViewApp.

TFS 784474

A tooltip may partially cover the element with which it is associated in the deployed ViewApp.

TFS 787192

When OSGroup security mode is used, if you first attempted to perform the VerifiedWrite without having the correct security credentials, then the VerifiedWrite dialog is not displayed when you modify the value of a VerifiedWrite attribute from a combo box.

TFS 789958

On some high resolution tablet devices, such as the Surface Pro 4, object names in the System Platform IDE may have insufficient line spacing between items, which can make it harder to read object names.

TFS 794383

When a custom property is changed from public to private, the change does not have any affect, and the value of the private custom property is shown at run time (private values should not be shown). Similar situations occur when:

• An override values for a custom property that is later made private. The override is also shown at run time.

• An override is applied to a custom property, and later the custom property is locked (can no longer be overridden). When the ViewApp is redeployed, the override value is still shown.

Workaround: Manually validate the outermost symbol and then deploy the ViewApp.

IMS 1989484

After galaxy migration, if a linked symbol information is unavailable, the layout validator cannot process the linked symbol. This can result in the layout in warning state. Immediately connecting to the galaxy will display a warning state and empty symbol preview for the specific unprocessed linked symbol.

Workaround: After the migration completes, connect to the galaxy and open the layout in warning state. Identify the symbols showing empty previews, validate those symbols only, then validate the layout to resolve the issue. You do not need to validate all symbols, only those symbols with missing previews in the layout.

IMS 1989662

Some alarm field localizations might not appear in the Alarm Control in InTouch HMI and AVEVA OMI when running in Historical Alarms and Events client mode.

When running the Alarm Control, either as an embedded symbol in InTouch HMI or in AVEVA OMI, or as an AlarmApp in AVEVA OMI configured to run in Historical Alarms, Historical Events, or Historical Alarms and Events modes, some alarm field localizations may not load even if present in the galaxy translation files. This occurs when the control is configured to display alarms from the History Blocks database. Following are the known cases (Alarm/Event types) where the localizations fail to load at runtime:

• For user write operations (User.Write) and events, the AlarmComment field is only partially localized in an Alarm App configured to view Historical Alarms and Events.

• For a Boolean alarm (Alarm.Set, Alarm.Clear) events, the AlarmComment, Limit and Value field localizations are not displayed in an Alarm App configured to view Historical Alarms and Events,.

• For Boolean write operations from an I/O reference (Application.Write) events, the AlarmComment and Value field localizations are not displayed in an Alarm App configured to view Historical Alarms and Events.

IMS 1991749

After installing and configuring System Platform 2023 or rebooting the system, the following message will be logged in the Operations Control Logger, "AnnounceOnline could not announce to local discovery service due to communication error," when the InTouchIDataService is unable to connect to the Discovery Service. This can occur if the InTouchIDataService starts before the Local Discovery Service. This message will not be logged after the Discovery Service starts. There is no functional loss once all services have started.

IMS 2918856

In some cases, in the OMI web client, the Trend Pen graphic element and the HistoricalTrendApp OMI ViewApp cannot retrieve historical data. There are two reasons for this:

• The Historian Server node name and port are not set in the application settings file for the proxy server on the WebViewEngine platform.

• The Historian Server does not use the security certificate from the System Management Server. This means the web client does not have a trust relationship with the Historian Server and will not accept data from it.

Perform workaround 1 to correct the first issue. For the second issue, perform one of the two procedures in workaround 2.

Workaround 1: Update the application settings file for the WebViewEngine:

21. On the WebViewEngine node, in a text editor, open the file C:\Program Files (x86)\Common Files\ArchestrA\Services\proxyserver\appsettings.json.

22. Find this section of the file:

    "history-data": {

    "HttpRequest": {

    "Version": "1.1",

    "VersionPolicy": "RequestVersionExact"

    },

    "Destinations": {

    "destination1": {

    "Address": "https://localhost:32573/"

23. Change localhost to the name of the node where the Historian Server is installed. If Historian is not using the default port of 32573, also set the correct port number. Save and close the file.

Workaround 2: To fix the security certificate issue, you have two choices.

• Install each Historian's certificate on every remote node that will use the OMI web client. You do not need to shut down or disable Historian to do this, but each node or remote device must have the Historian certificate installed before it can use the OMI web client.

• Change the Historian Server node to use the certificate of the System Management Server. You need to shut down and disable the Historian during the change, but this method requires changes only on the Historian Server node.

Decide on the method you wish to use and follow the appropriate procedure below. You need to follow only one of these procedures.

To install Historian certificates on Windows nodes or remote devices

Note: Depending on your organization's network configuration, your IT department may be able to install the certificate on all devices remotely. Users would not then need to perform this procedure.

24. For each web client node, in a supported web browser, go to https://<historian_node>:32573/.

    (If Historian is not using the default port of 32573, use the Historian port number for your installation.)

25. Select the Not secure message, then, in the dialog box that opens, select Certificate is not valid.

26. On the Certificate Viewer dialog box, on the Details tab, under Certificate Hierarchy, select the line that ends in ... CA.

27. Select Export.

28. Save the Historian certificate to a file. You can place it in any folder and give it any name, but do not change the file type.

29. Install the certificate. You can do this either by executing the certificate file you just created, or by opening the Windows Certificate Manager from the Start menu. Once you have started the process, follow the wizard prompts and place the Historian certificate in your Trusted Root Certification Authorities store.

30. Close, and re-open your browser. You should now be able to open the OMI web client, start the ViewApp, and see historical data.

Note: For remote devices which use an operating system other than Windows, see the manufacturer's instructions for installing a certificate.

To change the certificate on the Historian Server node

31. On the Historian Server node, use the OCMC to stop and disable the Historian:

    1. Start the OCMC and expand the Historian node in the left pane until you see the Historian Server node name.

    2. Expand the node name. Right-click Management Console, select All Tasks, and select Shutdown (and disable) Historian.

    3. On the Shutdown and Disable Historian dialog box, make sure the node name is correct and select OK.

32. From the Windows start menu, select AVEVA, then Configurator.

33. Under AVEVA Historian, select Server. Select Rest Configuration.

    The Rest Configuration dialog box opens.

34. For Certificate Source, select Provided by IT.

35. In Certificate, select <hostname> ASB, where <hostname> is the name of the node where the Historian Server is installed.

36. Select OK, then select Configure.

37. Select Close to close the Configurator.

38. In the OCMC, restart the Historian:

    1. Expand the Historian node again.

    2. Right-click Management Console, select All Tasks, and select Enable (allow to run) Historian.

IMS 2968494

Basic translation is supported for trend controls using an SQL connection. This translates the descriptions of tags as well as the user interface of the trend control. However, you can more fully use the translation capabilities to the trend control by connecting to the Historian using the REST oData interface. Using the REST oData interface expands the translation capabilities to include the translation of descriptions, engineering units and Boolean on/off messages.