Main Windows in Sym3 Web

Overview

Sym3 Web supports Main Windows - allowing you to design and display custom windows in the web client exactly as they appear in the PC client. Main Windows are project windows that have been flagged as a “Main Window” and are accessible directly through unique URLs.

This provides a seamless experience between the PC and web clients, enabling users to access the same interface regardless of their platform.

How It Works

Flagging a Window as Main Window

In Sym3 Operator Editor:

  1. Open your project (.s3o file)
  2. Select the window you want to make available in the web client
  3. Flag it as a “Main Window” in the window properties

Accessing Main Windows

Once a window is flagged as a Main Window and you published the project:

  1. Navigate to the Windows page in the Sym3 Web Administration section
  2. All Main Windows are listed with their unique URLs
  3. Click on a window or use its URL to open it in the web client

The window will render with all configured controls (Buttons, Panels, Alarm Displays, etc) as designed in the project file.

Limitations

Authentication Requirement

Unlike the PC client, which can start in anonymous mode, Sym3 Web requires users to be logged in to access Main Windows. Anonymous access to functional windows is disabled for security reasons.

Unsupported Actions

The following actions are not supported in Sym3 Web:

Action Reason
Execute External Program Web browsers cannot execute local programs for security reasons
Exit Application Not applicable to web applications
Open Login Form Authentication is handled by the web application framework
Open Speed Tuning Dialog PC client-only feature for configuring Product Tracking. For the web, please use the Speed Tuning tool in Sym3 Web Client.
Edit Alarm’s User Properties Not needed - the Alarm Display control has native inline editing support. Enable the User Can Edit User Properties property to allow users to edit values directly in the grid

For a complete list of supported actions in Sym3 Web vs PC Client, see Actions.

Control Visibility

All controls support platform-specific visibility settings. When designing your windows, you can control whether a control appears in the PC client, web client, or both:

  • Is Visible On PC Clients - Control appears in the desktop application
  • Is Visible On Web Clients - Control appears in the web browser

This allows you to:

  • Hide controls that use unsupported actions in the web client
  • Provide alternative controls optimized for web or desktop
  • Create platform-specific user experiences within the same window

See individual control documentation for more details on visibility properties:

Best Practices

  1. Design for Both Platforms: When creating Main Windows, consider which platform your users will primarily use and test on both
  2. Use Visibility Settings: Hide controls with unsupported actions in the web client using the “Is Visible On Web Clients” property
  3. Provide Alternatives: If a feature requires an unsupported action (like Execute External Program), consider providing a web-compatible alternative
  4. Test Authentication: Ensure your users have appropriate roles and permissions to access Main Windows in the web client