Viewing and Previewing Applications

The Unqork platform provides two ways to view and preview a module or application during development, without deploying to another environment. Viewing keeps Creators inside the Module Builder; previewing opens the full end-user experience in a separate browser tab.

UI View

UI View loads the module inline inside the Module Builder using an embedded frame. No new tab opens. The preview displays in the editor itself.

To open UI View, select UI View from the view selector at the top of the Module Builder. Select any other view (Config View or Logic View) to exit. For a full reference of UI View features, see UI View.

UI View is the fastest way to check rendering and run Console-based debugging. For testing that depends on submission IDs, application routing context, or the browser network tab, use Express View instead.

Express View

Express View loads a module or application in a new browser tab at the same URL an end-user would visit. A preview bar displays at the top of the page with debugging controls and user-selection tools that end-users cannot see. Changes saved in the platform reflect in Express View immediately.

Opening Express View

On a module that belongs to an application, the Play button (directly left of Save in the module header) opens a menu with two destinations:

Modules without an owning application and revisions opened from History open Express View directly — no menu appears. An API module has no Play button — choose View in Express from the (ellipsis) menu instead.

From the Explorer panel

Select the (ellipsis) next to any module or application in the Explorer panel, then select View in Express. Express View opens in a new browser tab.

Express View and End-Users

Express View and the production application share the same URLs. Creators see the preview bar at the top; end-users see only the application. Below the preview bar, the application looks and behaves the same for both. For preview bar controls and data handling, see Express View Page.

Testing with Express Roles

Express View reflects the role-based access control configured for end-users. Creators access Express View as themselves, so they might see data or features that a restricted end-user would not.

To test how the application behaves for a specific end-user, use the user-selection controls in the Express View preview bar. Selecting a specific end-user account loads the application with that user's role and data access applied.

Express roles, Express groups, and Express users are managed in Administration:

• Express Role Administration — create and manage roles that control what end-users can access

• Express Group Administration — create and manage groups that control data access scope based on role hierarchy

• Express User Administration — create and manage end-user accounts and their role assignments