Grid Viewer Actions
Grid Studio provides a set of Grid Viewer specific actions that allow dashboards and control interfaces to interact with Grid Viewer clients.
These actions enable interfaces to control how viewer clients behave, for example by navigating between frames, controlling display states, or triggering viewer-specific functionality.
Viewer actions can be triggered from widgets, events, or other logic within Grid Studio.
Action Types
Grid Viewer actions are available in two different scopes:
The main difference between these two types is how the action is targeted and executed.
Session-Based Actions
Session-based actions operate independently of a specific Grid Viewer object.
When triggered, the command is executed by the viewer instance from which the action was initiated, regardless of which Grid Viewer object exists in the project.
This approach is typically used when an interface should control its own viewer session without targeting a specific endpoint.
Viewer Object Actions
Viewer object actions are tied to a specific Grid Viewer object in the project.
When triggered, the action is executed only on the viewer instance connected to that specific object.
This allows interfaces to control other viewer endpoints within the system.
For example, one viewer can trigger actions that affect another viewer running on a different device.
Example: Navigate To
The Navigate To action loads a new frame within the Grid Viewer interface.
The behavior depends on how the action is configured.
Session-based action
If the action is created as a session-based command, the currently active viewer session will load the specified frame. The command is executed locally by the viewer where the action was triggered.
Viewer object action
If the action targets a specific Grid Viewer object, only the viewer instance connected to that object will load the new frame.
This makes it possible for one viewer to remotely control the interface of another viewer device.
Last updated