Industrial graphic requirements for CONNECT

Graphics created in the Industrial Graphic Editor must meet specific requirements to run in CONNECT. These requirements ensure that graphics behave consistently in CONNECT, meet security expectations, and provide reliable performance. CONNECT is a secure, browser-based application. The cloud environment differs from the desktop environments that existing industrial graphics may have been designed for.

Supported graphic types

Only Graphics Toolbox (GTB) graphics are supported. Object graphics are not supported.

Supported System Platform IDE versions

System Platform IDE 2023 and later are supported.

Supported standalone InTouch HMI versions

InTouch HMI 2023 and later are supported.

Unsupported components

CONNECT only supports industrial graphics that are compatible with web runtimes. Graphics that contain unsupported components are rejected during ingestion. Unsupported components include:

• Web widgets

• Client controls originally built for desktop (WinForm or WPF controls)

• Custom script libraries

These components rely on unrestricted system access or non-web technologies and cannot operate in the cloud environment.

File size limits

CONNECT supports .aaPKG files up to 256 MB. Each industrial graphic in the .aaPKG file can be up to 2 MB.

For information about reducing file size, see the Reducing file size section in Best practices for designing CONNECT-ready graphics.

Web compatibility expectations

Desktop-only features or components without a browser equivalent must be removed. All visual elements should be compatible with creating and viewing visualizations in CONNECT.

DataPointReference custom property name

If you are using any statistic other than Current, there is a custom property that by default is named DataPointReference. You may alter this property name by adding a number after it, e.g. DataPointReference03, but do not otherwise make changes to it. This property only works in CONNECT if it is named DataPointReference or DataPointReference<number>.

Script security compliance

Scripts must follow the CONNECT security guidelines described in the Script security policy section.

General security compliance

The graphic is scanned for security risks when the visualization is saved in CONNECT. If it fails the check, the visualization is not saved.