OMI Apps and Widgets: System Platform Enterprise 2023 Limitations

Product Component

Feature

Current Limitations

Web Client

The Share feature in the Web Client is only supports the HTTPS protocol.

ViewApp

Access Level

Not Supported

Layout

AutoFill

Not Supported: AutoFill in nested Layout

Initial State

Not Supported

Layout Pane Divider

If the Interactive pane divider property is set to false to disable panes from being resized, layout panes can still be resized during runtime.

Layout scripting

Layout scripting is not supported for applications designed to run on the web with the Web Client.

Object Wizard

Object Wizard

Not Supported

App

Current Limitations

HistoricalTrend control

A HistoricalTrend app is not supported by an OMI Web Client application.

MapApp control

Only the following MapApp control properties support reference values in an OMI Web Client application:

• InitialLatitude

• InitialLongitude

• InitialZoom

• CurrentLatitude

• CurrentLongitude

• CurrentZoom

• Asset

• ZoomLayers

MapApp control

To manually set an asset, set the FollowCurrentAsset property to false and add a reference for the Asset property. This is a kind of Owning object that enables a user to set the map’s focus to other assets. This will help with layouts where the Owning Object has been set.

MapApp control

The MapApp control ZoomLayers property can support dynamic changes in an OMI Web Client application.

Widget

Current Limitations

MapApp widget

When embedding the MapApp widget into a graphic, it does not appear correctly during runtime when placed in an AVEVA OMI ViewApp.

The following issues are present:

1. The map does not show the current value when setting the current value (current zoom, current latitude, current longitude) as a reference type, pane & zoom in/out under Map page.

2. The map does not show the correct asset level when selecting an asset from the navigation tree of the ViewApp. The map does not zoom to the correct zoom level, longitude, and latitude

MapApp widget

Embedding the MapApp widget into a layout is not yet supported. It does not work during runtime when placed in an AVEVA OMI ViewApp

MapApp widget

Only the following MapApp widget properties support reference values:

• InitialLatitude

• InitialLongitude

• InitialZoom

• CurrentLatitude

• CurrentLongitude

• CurrentZoomAsset

• ZoomLayers

MapApp widget

The MapApp widget ZoomLayers property can support dynamic changes in an OMI Web Client application.

All widgets

Property writing

Use action scripts to write a value such as
WIDGET1.Prop1 = “NewValue”;

Use property binding. For example, create one custom property, then bind a widget’s property to this custom property.

All widgets

Property reading

Use action scripts to read values such as
Text1.Text = WIDGET1.Prop1

OMI Runtime does not support Use Property binding.

All widgets

Property data changes

Do not support receive data change event notifications when trigger WIDGET1.Prop1 changed.

OMI runtime applications do not receive any notification Use Property binding when a data change script is triggered.

Teamwork widget

The Teamwork widget CredentialName property is not currently supported. Users must use the SSO method to automatically log on to Teamwork.

TitleBar widget

• Minimize, Maximize, restore commands are disabled in the Web Client.

• The StylesLibraries property is not supported for OMI ViewApps. Multiple galaxy styles are not supported

• Not Supported: Keyboard component

• Sign out: User must use sign out from the Web Client app bar.

GraphicRepeater widget

In an AVEVA OMI ViewApp running on the web, the background graphic of the Graphic Repeater does not stretch to cover the full width and height of the pane in which it has been placed.

DataGrid widget

DataGrid widget works only if the JSON data is enclosed in square brackets []. Square brackets encapsulate a list/array and curly brackets {} encapsulate an object with key/value pairs. Thus a list/array can be included in a value of a key/value pair.

An example of correct JSON syntax:

[{"name":"Afghanistan","iso2":"AF","long":65,"lat":33},{"name":"Albania","iso2":"AL","long":20,"lat":41},{"name":"Algeria","iso2":"DZ","long":3,"lat":28}]

App/Widget

Current Limitations

MapApp widget and MapApp control

The MapApp widget always shows the initial value of a reference when loading. For a Map Control and Map Widget embedded in a graphic shown in an OMI Web Client application, the following behaviors occur.

With an Asset

• For Common Layout, the first loading will show map with layer's zoom, asset's location; the second loading will show map with layer's zoom, asset's location even manually pan and Zoom in/out.

• For a linked layout,the first loading will show the map with the layer's zoom, asset's location. The second loading shows the map and retains the last pan and Zoom in/out map change.

  Without an Asset

• If both the initial value(initialzoom/longitude/latitude) and current value(CurrentZoom/ Longitude/Latitude) as static, the Map shows the initial value as first loading and shows current as second loading.

• If initial value as reference and current value as static, the MapApp will show the initial value as first loading and show the current value as second loading.

• If initial value as static and current value as reference, the MapApp shows the initial value as first loading and current value as second loading.

• If both the initial value and current value are set as references, the MapApp shows the initial value as first loading and the current value as the second loading.

Manually setting an asset

Set the FollowCurrentAsset property as false and add a reference for the Asset property. This is a kind of Owning object so that a user can set the map’s focus to other assets. This will help with layouts when the Owning Object has been set.

Script Method

Current Limitations

ShowGraphic() method

Scripts that include the ShowGraphic() method have the following limitations for applications designed to run in the web using the Web Client.

• Do not support Identity(only support is ShowSymbol using the graphic name as the identity).

• Do not support the Name property.

• Do not support the Owning Object property.

• Do not support ResizeWindow property.

• Do not support the HasTitleBar property. By default, applications always show a tittle bar.

• Do not support the HasCloseButton property. By default,screens always show a close button.

• Do not support the WindowTitle property.

• Do not support using the same interface element to open several graphics.

• Do not support ScalePercentage property.

• Center is the only supported value of the Position property.

ShowGraphic() method popup behavior

When the ShowGraphic() method produces a popup window, the following limitations are present:

Relative To Symbol:

• The size of a popup window is always the same as the graphic's original default width and height with scaling at 100 percent.

• If a graphic's original default size is larger than the screen, the popup window appears in full screen mode as well as relative to the desktop.

• The placement of a popup window is always at the center of screen.

  Relative To Desktop:

  A popup window is always shown in full screen mode.

  Custom Width and height:

  The width and height of a popup window cannot be customized.

HideGraphic() method

The name of a graphic is used as the hide identity.

ShowContent() method

The ShowContent() method does not support the Name property.

Security Mode

Current Limitations

OS Group based security

Nodes do not appear in a ViewApp Navigation tree based upon their specified access levels configured for a Read-Write user belonging to an OS Group based security group.