Publishing a screen
A screen inside the studio is useful to the people who open the studio. Published as its own extension, it appears on the record page where the work already happens — for people who will never open the designer.
On this page
Why publish a screen#
The studio is a workspace: you go to it. A published screen is the opposite — it comes to the user, as a tab on a service call, a panel under an equipment record, or a tile on the Shell home screen.
Nothing is redeployed to do this. One deployment serves every extension you publish, so the tenth costs exactly what the first did.
Minting one#
- Open the screen in the admin area of EasyScreenViewer and choose to create an extension from it.
- Name it. This is what the tab or tile will be called in FSA.
- Choose the outlets — where in FSA it should appear. You can pick several in one install.
- Copy the install link and add it in Foundational Services → Extensions, exactly like any of our products.
The link is short and permanent. The manifest behind it is generated and signed for that specific screen.
Where it can appear#
Eighteen outlet placements across FSA, plus the Shell home screen. The useful ones in practice are the record tabs and the detail-page panels, because those are where a scoped screen earns its keep.
Small outlets are tight, so a published screen sheds non-essential chrome below a certain height and offers an expand control that opens it full size in a Shell modal. You do not configure this; it adapts.
It knows which record it is on#
A screen placed on a record scopes itself to that record automatically, with no configuration by the person using it — and follows along when they move to the next one.
To control which field is filled and whether it is locked, see auto-filling from the host record.
Revoking and deleting#
Every published extension is listed in the extensions manager with its install link. Each can be revoked, reactivated or deleted on its own — the others carry on untouched.
A revoked link stops serving immediately, and a tenant that has it installed sees a card explaining that rather than a broken frame.
Categories, and mobile#
You can publish a whole category of screens as one extension, which appears as a chip rail of related screens rather than a single one — useful when a role needs four screens rather than one.
Each published extension can target web, mobile, or both. On mobile it appears in the Web Container alongside the products; see mobile setup.