Build software around your business.

Work Surfaces. Create internal applications on your business data, objects, and actions. Bring the queue, context, and next decision into one place for your team.

Scope a Work Surface

Illustrative workflow with synthetic data.

Work Surfaces: reviewed source to active application. Pascal product walkthrough. — Product walkthrough · Illustrative example
Read the transcript and visual descriptions

Work Surfaces. Bring the business into your software.

Build around the operation

Author internal interfaces with React routes, scoped CSS, and Pascal components. Choose a layout for the records, context, and actions the team needs.

Connect to workspace resources

Declare the application’s data and action bindings in the project. Use generated handles to connect the interface to those resources.

Present useful data states

Use native tables and status components to show the records available, their freshness, selection, and the context behind a result.

Work with Codex on the change

Prepare source changes in a Code Task. Inspect the files and diff before applying the working copy to the project.

Preview the applied project

Open the project preview to review the interface after Apply. Keep it distinct from the task’s working copy and the released application.

Follow the project to release

Build from the project and use its release workflow to make the application available. Connected data and actions retain their current workspace permissions.

Explore Pascal

From a working copy to a working application.

Follow Factory Control through its implementation and release, then see the separate operating review that remains open.

Factory Control uses native components and project-local bindings to connect work items, requirements, and reviews.

Build on the business model. Native product view with illustrative data.

In practice

Meridian needs a work queue that connects requirements, implementation, and reviews. Factory Control gives the team that application on Pascal’s existing objects and workflows. The active application can be used while the lithium policy change follows its own approval path.

Example operation.Explore the solution

Work Surfaces in your operation.

Connect it to the rest of your work.

Build on records from Data and Ontology, processes from Compass, and reusable functions from Forge. Keep implementation and review connected to the team in Workrooms.

What you work with

Work Surfaces

React routes, styles, and project configuration
Declared data, process, and action bindings
Code Tasks, applied source, previews, and releases

Stay in control as the work moves.

Review the source, preview the application, and follow the build through release. Connected data and actions retain their own permissions. Releasing the interface does not approve the business decisions made through it.

Where you work

Work Surfaces

The internal application library
Code Task Files and Changes
The project preview and released application

Build the interface the operation is missing.

Choose one user, one recurring workflow, and the business objects and actions the application should bring together.

Scope a Work Surface Logistics