WebStudio Reference

This part of the documentation is primarily aimed at providing technical reference material and as such isn’t designed to be read end to end. While this may well be a good exercise to undertake in terms of getting to know all the tool has to offer, it is likely to be a rather dry read…​ For a more user friendly walk-through of how to use WebStudio and examples of compilations, refer to the "Getting Started" section instead.

Refer to the tables below to jump to specific reference section.

Item Description

Loading WebStudio

Load WebStudio in a browser

Compilation Model

WebStudio compilation model.


Interaction actions.

Generic Widgets:


Display rich text editor.


Display entries to collect user input.


Embed other web content.


Display an image.

Markdown Viewer

Display Markdown content including Mermaid graphs.


Display and edit tabular data. Supports (multi) select.


Displaying multiple compilations within a main compilation.


Display text.

Time Period Table

Table with start and end time pickers.


Display hierarchical node structure.


Display a video.

Specific Widgets:

Batch Table

Display batch (BPR) headers.


Display trend chart with multiple axis support.

Event Table

Display A&E events.


Display actual system object values.

File Grid

Display info and content of multiple files (GridFS).

Report Viewer

Display reports with export support.

Development Widgets:

Message Debugger

Inspecting action pipeline messages.

Transform Editor

Test transform actions.


Example Compilations

Examples of the widgets and their interaction.

Loading WebStudio

WebStudio is shipped with the system Setup. The installation of the Web API also includes the WebStudio web app. WebStudio can be loaded into the Browser by:


  • PROTOCOL: http or https

  • HOSTNAME: Hostname of the web server from where to load WebStudio from. Can be the Web API.

  • PORT: TCP/IP port number of the web server.

Typically with a default installation you can open the Browser, on the machine where the Web API is installed, and visit:


By providing query parameters in the URL you can auto connect and load WebStudio compilations.

Connection parameters

  • hostname=HOSTNAME: Hostname of the Web API.

  • port=8002: TCP/IP port number of the Web API.

  • ssl=true: Using secure connection to the Web API.

Security parameters

Adding credentials in the URL:

  • credentials=: Base64 encoded 'username:password'.

  • authority=builtin: Possible values builtin(default), ad, machine

Using Integrated Windows Authentication:

  • secp=iwa:

Loading options

  • logo=false: removes the vendor logo.

  • theme=light: Setting the theme to dark (default) or light.

Loading WebStudio compilation from the system

If the compilation is loaded from a URL, WebStudio automatically hides the development tools. If the user, typically an engineer, wants to edit a hosted compilation, the query parameter dev=1 can be added to the URL. Also refer to the showDevTools option below which can be set directly on the compilation to control the visibility of the toolbar icons.

Development Tools are:

  • Add widget

  • Import compilation

  • Export compilation

  • Edit compilation model

  • Edit widget model

Loading from custom Advanced Endpoint

Model can be loaded by calling an Advanced Endpoint. See Web API - Advanced Endpoint docs for more details.

  • lib=MY_LIBRARY: Lua library name. Script can return function or a Lua table.

  • func=MY_FUNCTION: Function name in case the library returns a Lua table.

  • farg=: Function argument data. Typically Base64 encoded in case of JSON data.

  • ctx=/System/Core/MyFolder: (Optional) Alternative script context.



Loading from object’s Custom Property

WebStudio compilations can be loaded from Custom Properties of objects by adding two query parameter in the URL.

  • obj: object path or id. (Note: if not provided the Web API default context path will be used.)

  • name: name of the Custom Property.




The WebStudio configuration, in which widgets along with their display attributes and dynamic behavior are defined, is collectively referred to as a compilation.

The compilation and contained widgets within are described using JSON objects. Throughout this documentation the term "model" refers to the structure of the various JSON fragments used to describe the elements within the compilation as well as the compilation as a whole.


The version is for future changes to be able to support new definition of the model.

    "version": "1",
    "widgets: [] // List of widget objects.

See widget doc model description for the widget model.


    "options": {
        "background": {},
        "numberOfColumns": 24,
        "numberOfRows": 12,
        "stacking": "none",
        "showDevTools" : true
name description


Used to set the compilation background color and image. These settings are actually nested within a style object. Refer to the example below to see them in action


style options for the background


load an image as the canvas backdrop.


Set the display options for the backgroundImage. The options derived from CSS styles and are:

auto : The loaded image native size is used and it is tiled to fill the whole canvas area. This is the default options

cover : The image height is stretched to that of the canvas. If it has a wider aspect ratio than that of the browser window, the image will be clipped. Also note the if the image height is larger than that of the canvas, it will be clipped at the bottom of the frame

contain: The image is repeated either horizontally or vertically, depending on which of its dimensions divides the most into the canvas width or height. In other words, if the background image is about the same width as the work area, but much shorter in height, it is repeated vertically and vise versa.

<n>%: This option behaves the same as auto except that the image is scaled by the specified percentage (For example 50% )

<n>px or <n>px <m>px: Sets the size of the image in pixels. If only one value is provided it is applied to the width of the image. For example 100px is equivalent to 100px auto

<n>.<m>em: Specify the size in EM units. 3.2em for example


can be set to any valid CSS color name or RGB value


Defines the number of vertical columns the grid is divided into. The absolute column width in pixels, will scale proportionally to that of the compilation.


The naming of this property is a bit misleading in that it is used to set the height of grid rows to a specific number of pixels rather than dividing the canvas into equally sized rows. By setting this property, the row height is fixed and no longer scales when the canvas width is resized. If the property is omitted each cell in the grid is as many pixels high as it is wide. The width being determined by the canvas width divided by the numberOfColumns. In this case the row height does scales with the column width.


Defines how the widgets can be positioned. Options are:

none: Widgets can be dragged around freely and positioned on any gid cell. Default

vertical: Widgets are stacked vertically starting from the top of the screen.

horizontal: Widgets are stacked horizontally starting at the left of the screen.


As the name suggests, this parameter is used to control the availability of developer tools in the UI. It would be set to true for example to allow editing of compilations served from the system, or false to prohibit editing at any time.Note: this setting takes precedence over the dev URL query parameter described above. In other words, if showDevTools is set to false, this will override the query parameter and prevents the development tools from being shown.


To set the maximal grid width with e.g. 500.

Example to have an image as the compilation background:

    "options": {

        "background": {
            "style": {
                "backgroundColor": "#001b01",
                "backgroundImage": "url(\"https://transparenttextures.com/patterns/45-degree-fabric-light.png\")",
                "backgroundSize": "contain"


name description


Refers to the system and/or the Web API.


Object’s path or the object ID.

Read other parts of the docs to get familiar with the system capabilities.