Industrial graphic requirements for CONNECT visualization

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

Unsupported components

CONNECT visualization 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 visualization supports ZIP files up to 10 MB. Each industrial graphic in the ZIP file must be less than 2 MB.

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

A ZIP file can contain multiple separate industrial graphics; however, only the first industrial graphic and any embedded graphics within it are imported. Any additional graphics in the ZIP file are ignored, unless they are embedded inside the first graphic. The order of the graphics within the ZIP file is determined by the selection order used during export.

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 visualization.

Script security compliance

Scripts must follow the CONNECT visualization 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 visualization. If it fails the check, the visualization is not saved.