Designing at the platform

At the platform

With the scope switcher on the platform, the Runtimes lens designs the runtimes of the platform's own applications — the applications a platform domain holds in Domains (under Settings). What you build here is what a package carries: when a capability version carries the application, it carries the runtime's published version, with its workspaces, its navigation and its default workspace, and the platform's A_EntityViews of the application.

1. Under Create a platform runtime, choose one of the platform's applications and press Create runtime. The runtime starts with an empty draft version 1.
2. Press Open on the runtime. Under Add a workspace, give a key and a name; for an Explorer workspace choose the platform entities it opens with and whether people can add a column and see relations. Add as many workspaces as the application needs.
3. Choose the Default workspace — the one the application opens on — and press Make default.
4. Under Add a navigation item, give a key and a label, choose the workspace it opens (or none, for a group) and where it goes (top level or under another item). A new item goes after its siblings; Move up and Move down change the order. How the navigation reads shows the result.
5. Press Publish version N. To change a published version, press New draft version: it starts as a copy of the published one, and the published version keeps running until the draft is published.

The application's A_EntityViews are listed under the runtime and made in the Workflow & EntityView Designer's A_EntityView tab, also at the platform.

The Actions lens defines the platform's actions: every tenant runs them on its records, a platform workflow's effects run them, and a package carries those its workflows and entities use. Defining needs application.write, publishing application.publish, at the platform.

Keep in mind Only the platform's own applications can get a platform runtime, and only Explorer workspaces run today: a version with another workspace type is refused at publish, and the list says so.

Tip At the platform, viewing requires application.read, authoring application.write and publishing application.publish, all at the platform. Tenant runtimes are designed in each tenant and are not listed at the platform.