usertasks
All documentationStart free beta
Documentation hub

Feature guide

Application pages

Compose internal operational applications from forms, data, reports, workflows, agents, and navigation.

On this page

Complete feature description

Understanding application pages in UserTasks

Application Pages are composable internal applications built from UserTasks assets. A page can combine operational data, reports, forms, workflow launchers, task navigation, kanban, agent chat, custom web components, and presentation content around a specific job or business context.

Pages use parameters and bindings to load the correct records and pass context into actions. A page parameter such as case_id can feed object lookups, report filters, form prefill values, and workflow variables. Component and lifecycle rules then control visibility, values, navigation, overlays, and messages.

Publishing validates the page schema and referenced assets before the page becomes available. Published pages can be linked directly, grouped into projects, or placed into Space navigation so different teams receive focused operational experiences.

When to use this feature

  • A team needs one workspace around a case, process, or operational role.
  • Users need to act on data rather than only view a report.
  • Several forms, workflows, reports, and external sources should feel like one application.
  • A purpose-built experience is clearer than sending users across multiple admin screens.

What you can build

  • Case and request workspaces
  • Operations command centers
  • Self-service portals for internal teams
  • Executive and team dashboards
  • Workflow launchpads
  • Agent-assisted knowledge and action pages

Production design notes

  • Choose a small number of stable page parameters and document their meaning.
  • Use objects or references as reusable data contracts instead of embedding source-specific assumptions in every component.
  • Design loading, empty, permission-denied, and source-error states.
  • Validate dependencies before publishing and test the page with the permissions of its intended audience.

Core concepts

Sections and components

Responsive sections contain inputs, tables, charts, reports, content, launchers, agent chat, and custom components.

Data bindings

Bind components to objects, tables, integration references, reports, forms, workflows, or page parameters.

Actions and rules

Buttons and component events can navigate, open overlays, launch forms, start workflows, or apply page rules.

Publishing

Validate and publish pages for authenticated use, projects, and space navigation.

Before you start

Have these permissions, assets, and design decisions ready.

  • Permission to create pages
  • The data, report, form, workflow, or agent assets the page will expose
  • A clear target audience and navigation location

Detailed input and result reference

These are the values designers configure and the results available after execution. Exact fields can vary by operation, but the runtime contract follows these patterns.

Bind data table

Display operational or external data in a sortable page component.

Inputs

sourcecustom table | object | referencerequired

The list operation that supplies rows.

columnsarrayrequired

Visible field, label, width, and formatter definitions.

parametersmappings

Page parameters or values passed into the source.

selectableboolean

Whether users can select rows for downstream actions.

Expected results

rendered rowstable

Data displayed according to bindings and column formatters.

selected rowpage state

Current selection available to actions and rules.

load errorcomponent state

Source or mapping failure shown without crashing the page.

Launch workflow

Start a workflow from a button or component event.

Inputs

workflow_idUUIDrequired

Workflow definition to start.

variable mappingsobject

Maps page parameters, component values, or selected rows to workflow variables.

navigation behaviorconfiguration

Stay, show confirmation, navigate, or open another surface after start.

Expected results

workflow runrecord

Created synchronous or queued run.

run ID / statuspage state

Available for confirmation and follow-up navigation.

Launch form

Open a reusable form with page context and initial values.

Inputs

form_idUUIDrequired

Published form template.

initial valuesmappings

Prefill values from parameters, selected data, or page state.

display modepage | overlay

How the form appears.

Expected results

submissionrecord

Validated form data and submission identifier.

configured submit actioneffect

Workflow start, navigation, data update, or confirmation.

Navigate

Move users between pages, records, tasks, or external URLs.

Inputs

targetpage | task | URLrequired

Navigation destination.

parametersobject

Values passed to the target page.

open modesame view | overlay | new tab

Presentation behavior.

Expected results

navigation stateclient state

Destination opens with resolved parameters and history behavior.

Run page rules

Apply lifecycle and component rules based on page state.

Inputs

triggerpage load | value change | clickrequired

Event that evaluates the rule.

conditionsarray

Predicates over page parameters and component values.

actionsarrayrequired

Set value, show/hide, enable/disable, navigate, or show a message.

Expected results

updated page statestate

Components and navigation reflect the matching rule actions.

Step-by-step implementation guides

Build an operations case workspace

Expected outcome: A page shows case data, documents, open tasks, and actions for one case ID.

  1. 1

    Define page parameter

    Add case_id as a required page parameter.

    Result: Every data binding and action can reference the current case.

  2. 2

    Bind the case object

    Add a data display bound to the object get operation with case_id.

    Result: Core case fields load from the governed source.

  3. 3

    Add related work tables

    Bind tasks and documents filtered by case_id.

    Result: Operators see the active work and evidence in one view.

  4. 4

    Add actions

    Configure buttons to launch a follow-up form, start an escalation workflow, and open a task.

    Result: Users act without leaving the case context.

  5. 5

    Publish and place in a space

    Validate references, publish, and link the page into the team space.

    Result: The intended team receives a focused operational application.

Actions and capabilities

What designers and operators can do in this product area.

Application pages actions

The main operations available in Application pages.

Application pages actions

Add components

Place inputs, content, data tables, charts, saved reports, kanban, agent chat, and custom web components.

Example: Build an operations console that shows live cases and launches a remediation workflow.
Configuration inputs
  • Permission to view and edit the relevant application pages assets.
  • The target page and its component, binding, rule, or navigation target.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Pages from the main navigation.
  2. 2.Create or open the relevant asset and choose “Add components”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The published application page reflects the configured behavior for authorized users.
  • Failures remain visible with enough context to correct configuration or retry safely.

Application pages actions

Bind a data source

Choose a custom table, object, report, or integration reference and map its fields.

Example: Build an operations console that shows live cases and launches a remediation workflow.
Configuration inputs
  • Permission to view and edit the relevant application pages assets.
  • The target page and its component, binding, rule, or navigation target.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Pages from the main navigation.
  2. 2.Create or open the relevant asset and choose “Bind a data source”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The published application page reflects the configured behavior for authorized users.
  • Failures remain visible with enough context to correct configuration or retry safely.

Application pages actions

Launch a form or workflow

Configure button actions with parameters, initial values, and post-action navigation.

Example: Build an operations console that shows live cases and launches a remediation workflow.
Configuration inputs
  • Permission to view and edit the relevant application pages assets.
  • The target page and its component, binding, rule, or navigation target.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Pages from the main navigation.
  2. 2.Create or open the relevant asset and choose “Launch a form or workflow”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The published application page reflects the configured behavior for authorized users.
  • Failures remain visible with enough context to correct configuration or retry safely.

Application pages actions

Navigate and overlay

Open other pages, task views, external links, or modal-style overlays.

Example: Build an operations console that shows live cases and launches a remediation workflow.
Configuration inputs
  • Permission to view and edit the relevant application pages assets.
  • The target page and its component, binding, rule, or navigation target.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Pages from the main navigation.
  2. 2.Create or open the relevant asset and choose “Navigate and overlay”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The published application page reflects the configured behavior for authorized users.
  • Failures remain visible with enough context to correct configuration or retry safely.

Application pages actions

Add lifecycle rules

Run page-load, component, and navigation logic with validation and dependency checks.

Example: Build an operations console that shows live cases and launches a remediation workflow.
Configuration inputs
  • Permission to view and edit the relevant application pages assets.
  • The target page and its component, binding, rule, or navigation target.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Pages from the main navigation.
  2. 2.Create or open the relevant asset and choose “Add lifecycle rules”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The published application page reflects the configured behavior for authorized users.
  • Failures remain visible with enough context to correct configuration or retry safely.

Application pages actions

Publish

Run reference validation and expose the page through direct links, projects, or spaces.

Example: Build an operations console that shows live cases and launches a remediation workflow.
Configuration inputs
  • Permission to view and edit the relevant application pages assets.
  • The target page and its component, binding, rule, or navigation target.
  • Any required mappings, recipients, filters, variables, permissions, or lifecycle settings shown by the designer.
How to use it
  1. 1.Open Pages from the main navigation.
  2. 2.Create or open the relevant asset and choose “Publish”.
  3. 3.Complete the required fields, map dynamic values, and review access to every referenced asset.
  4. 4.Use preview, test, or validation where available; correct errors before publishing or executing.
  5. 5.Run the action and inspect its status, output, history, or audit record.
Expected results
  • The published application page reflects the configured behavior for authorized users.
  • Failures remain visible with enough context to correct configuration or retry safely.

Potential use cases

Patterns you can adapt to your own operating model.

Operations console

Give a team one page for workload, exceptions, reports, and common actions.

Saved report cards
Filtered data table
Launch workflow button
Open task overlay

Case workspace

Assemble case data, documents, conversation, forms, and actions around one identifier.

Page parameter
Object binding
Document list
Task message component
Action buttons