# Pascal Work Surfaces

Source: https://www.trypascal.io/platform/work-surfaces

Build software around your business.

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

## Capabilities

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

## Connected context

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.

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

## Controls and permissions

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.

## Example

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.

## Workflow

### Build on the business model

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

### Inspect the working preview

- Open the interface and follow a lithium work item before applying the source. The preview lets the team review how the work fits together.

### Use the reviewed application

- Factory Control 1.0.0 is active after engineering acceptance and explicit activation. Its three queue items remain available after reload.

### Keep operating decisions explicit

- The linked Logistics Exception Desk preview still shows pending Compliance. An application release does not approve a change to shipment policy.

## Next steps

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

- [Contact sales](https://www.trypascal.io/contact)
- [Logistics](https://www.trypascal.io/solutions/logistics)