WebStudio Reference

WebStudio has both a development and a user mode. In development mode, compilations can be created using a wide variety of widgets and developer tools. The user mode allows interactive access to widgets and compilations without changing the underlying model.

This section of the documentation is primarily aimed at providing technical reference material for the development mode in WebStudio. As such, it is not designed to be read from end-to-end but provides extensive information on all of the tools and widgets that WebStudio has to offer.

With developer tools enabled for a compilation, click the DevToolsButton icon in the menu bar of WebStudio to enable access the Widget Model Editor for all widgets.

For a more user-friendly walkthrough of how to use WebStudio and examples of compilations, refer to the "Getting Started" section instead.

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

Item Description

Loading WebStudio

Load WebStudio in a browser

Compilation Model

WebStudio compilation model.


Interaction actions.

Generic Widgets:

Advanced Form

Display an advanced form with more configurability than the basic Form.


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://HOSTNAME: PORT/apps/webstudio/

  • 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: Set the theme to dark or light. The compilation will load with the indicated theme pre-selected. This setting overrides the user selection. The theme toggle button is hidden when this option is used. Also see compilation options.theme

Loading WebStudio compilation from the system

There are various ways to load a compilation from the system into WebStudio. In all cases, the developer tools will be hidden by default. For more information, see the Developer Tools section.

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": 96,
        "numberOfRows": 12,
        "stacking": "none",
        "showDevTools" : true,
        "padding": {
            "x": 0,
            "y": 2
        "spacing": {
            "x": 2,
            "y": 2
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 viewport. By default the numberOfColumns is set to 96 when you create a new compilation. In case you are wondering why 96 and not 100, it is because 96 has the most factors, allowing the columns to be divided into more equal width groups ( 2, 3, 4, 6 …​ etc) that 100. That said, the column count should be adjusted to suite the layout needs for your compilation.


Optional property, which can be assigned one of three values:

  • auto: see numberOfRows.type = "square" below.

  • <number>: This option is deprecated and should be avoided. For the time being it is still available to provide backward compatibility. It sets the height of grid rows to a specific number of pixels. The same can be achieved by setting the numberOfRows.type field to height and assigning the pixel height to the numberOfRows.value field.

  • Nested properties: See below

If the property is omitted the auto behavior is assumed.


The numberOfRows.type field determines how the number of rows, and more specifically the row height for grid rows is calculated. Options are:

  • height: The height of each grid row is set to a fixed number of pixels, taken from the value property. In this configuration the grid rows don’t scale with the size of the viewport.

  • count: The row height is calculated by dividing the compilation viewport height by the number assigned to the value field, which now denotes the count of rows. In this mode, the row height scales proportionally to the viewport height. Use this option to create compilations which always fit exactly into the available compilation window.

  • square: The value field is ignored, and the row height is set equal to the calculated columns width, resulting in square gid cells. Consequently, the grid cells scale proportionally, based on the viewport width. This is the default behavior when the numberOfRows is not defined in the model.


The values is interpreted as either the row height or number of rows, depending the type selected.


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 access to developer tools in the UI, which allow compilations to be created, edited and inspected. It can be set to true for example to allow editing of compilations served from the back end, or false to prohibit editing at any time.

If the property is not provided, Webstudio enforces the following default:

  • Devtools and edit buttons are shown when creating and loading compilations locally

  • They are hidden when retrieving compilations from the back end.

Note: this setting takes precedence over the dev URL query parameter, which is to say, if the showDevTools property is set to false, this will override the query parameter and prevent the development tools from being shown.


This is an optional property used to set the number of pixels between the edge of the canvas and the content. The x value sets the padding at the left and right edges of the canvas, while the y value sets the padding at the top. Since compilations can be taller that the height of the canvas, the there is no padding applied to the bottom of the view.If the property is omitted a default value of 5 is applied to the x and y properties. When a new compilation is created, the padding is explicitly set to x=0 and y=2.


This is an optional property used to set the spacing between widgets on the canvas. The x and y values determine the horizontal and vertical spacing. If the property is omitted, the widget spacing defaults to 10. When a new compilation is created, the spacing is explicitly set to x=2 and y=2.Note: The numberOfColumns property places a limit on the pixel size of each grid cell. The widget spacing is achieved by reducing the area within the grid cell occupied by the widget. This in turn means that the spacing cannot be set larger than the dimensions of one cell. A side effect of this is that the higher the numberOfColumns the smaller the maximum spacing can be between widgets.


Optional parameter forcing the compilation to be shown with either the light or dark themes. When applied, the theme toggle button is removed preventing users from changing the setting at runtime. This value takes precedence over the user’s selection and the url setting.


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