Documentation Index

Fetch the complete documentation index at: https://docs.unqork.io/llms.txt

Use this file to discover all available pages before exploring further.

Express View Page

Prev Next

The Express View page loads an application or module in the same front end that end-users use, with an additional preview bar visible only to Creators. This article explains the preview bar controls, describes how Express View handles data, and covers the difference between a Creator's Express View and the end-user's experience.

Express View Preview Bar

The preview bar displays at the top of the Express View page. It is visible to Creators only and does not appear for end-users.

The Express View preview bar at the top of the page, showing the Preview as and Preview Style controls.

The preview bar provides the following controls:

Control

Description

Preview Runtime as

Switches the runtime engine used to render the application. Options are Vega (2.0) and .

Preview as

Lets Creators select which Express role to preview the application as. Options include the available Express roles configured in the environment (for example, Administrator, Authenticated, Anonymous, No Access). Selecting a role loads the application with that role's permissions and data access applied. Creators can test restricted scenarios without logging in as a separate account. Learn more about creating end-user roles in Express Role Administration.

Preview Style

Controls the style applied to the application in Express View.

Remove

Hides the preview bar completely, showing the application exactly as end-users see it.

Hide

Collapses the preview bar while keeping it accessible.

How Data Is Captured

In Express View, data submitted or entered by a Creator is stored as real submission data in the environment. Express View does not use a sandbox or isolated data store. Any form submissions, record saves, or data writes made in Express View create or update actual records in the environment.

Creators should use test accounts or clearly labeled test data when working in Express View to avoid creating records that affect production reports, workflows, or downstream processes.

Creator Express View vs. End-User Experience

The table below summarizes the differences between what Creators see in Express View and what end-users see in the production application.

Feature

Creators in Express View

End-Users in Production

Preview bar

Visible at the top of the page.

Not visible.

User selector

Can switch to any Express user account.

Does not see their account or others.

Console Tools

Can run debugging commands in the browser console.

Cannot access console tools.

Data changes

See saved changes immediately after saving in the platform.

Always see the last saved state of the application.

Unsaved changes

Express View reflects the last saved version of the module. Save changes in the Module Builder before opening Express View to see updates.

Always see the last saved state.

Data written

Writes real submission data to the environment.

Writes real submission data to the environment.


Changelog

Date

Change

2026-08-28

Accuracy pass: fixed "Unsaved changes" row; fixed description opener; corrected internal link ; removed slop note (EN-8063).

2026-05-11

Initial publication.