ORDER DESK / LOCAL · REAL BACKEND · SAMPLE DATA
An order tool with a saved result.
Create an order, make a change and reload. This product-owned example uses the actual React runtime, real application sign-in and the AutoTable backend with MongoDB and Redis.
ORDER DESK / ACTUAL REACT UI
LOCAL DEMO · REAL BACKEND · SAMPLE DATA
Actual local application with synthetic sample records. No API response interception or injected session was used. There is no public app instance to sign in to from this page.
THE TASK
From a form to a saved change.
The browser signs in as an application user and requests the saved page configuration. Record operations run through the real HTTP API.
ORDER DESK / ACTUAL REACT UI
LOCAL DEMO · REAL BACKEND · SAMPLE DATA
1. Create: order number, customer and total 240. Status and ownership are supplied on the backend.
ORDER DESK / ACTUAL REACT UI
LOCAL DEMO · REAL BACKEND · SAMPLE DATA
2. Edit and reload: the total is 275. An independent GET and a full reload confirm the persisted value.
- Sign in as an application user
- Create an order through the form
- Read the saved record independently
- Edit the total from 240 to 275
- Reload and check the same record
- Verify a second user cannot read or edit it
WHAT WAS VERIFIED
Real calls. Real persistence. A clearly scoped example.
This is local integration evidence for the exact configured example. It is not a customer deployment or a claim that every possible application works automatically.
| Check | Observed result |
|---|---|
| Configuration | Schemas, users, policies, saved page and before-create workflow installed through actual management HTTP and read back. |
| Sign-in | Actual browser application login and cookie session; no fake session injection. |
| Create/default | Real POST returned a server record ID; backend assigned owner and persisted Draft. |
| Edit/readback | The 240 → 275 change passed independent GET and browser reload checks. |
| Access | Fresh second-user browser and direct GET/PATCH were denied for the first user’s record. |
| Logout | Actual logout returned the private application route to sign-in. |
Verified 2026-11-02. Sample values are demonstration data, not customer metrics. The current website does not offer this as a ready-to-use template or an automatically hosted app.
CONFIGURATION AND HOSTING
The pieces behind the working interface.
Use Tenant Panel to configure the project. The backend runs data and access logic; the separately configured React runtime presents the application.
Project setup
An orders schema, unique/searchable order number, application accounts, backend owner policies, enabled routes and a before-create default workflow.
Application setup
A saved all-grid page with Records/New order tabs, a schema table, create/edit form and navigation. Configure the real API origin and session behavior.
Delivery setup
Transaction-capable MongoDB, Redis, the AutoTable service and a separately deployed React runtime. Configure HTTPS, cookie/CORS origins and verify the hosted flow before calling it a live demo.
This walkthrough does not demonstrate payment processing, fulfillment, bulk transactions or a live dashboard. Saved pipelines/charts and template cloning require their own configuration and acceptance.
From a data model to a working product.
A connected foundation for the things you want to build.