Skip to main content
Version: 3.1

The app link

Beta: open an App Studio app on its own, full screen, from a link people can bookmark, and keep shared stations signed in as the right person.

Where
Run page, Apps menu, after publishing
Who
Anyone who may run the app
Shared stations
Sign out asks who signs in next
Beta

App Studio is in release 3.0 as Beta: a paid add-on that no edition includes by default.

Every published app gets a link that opens only the app: no MaestroHub menus, rail, search or notifications. People use it as "the line 3 app" on a station, in a browser bookmark, or on a tablet. It is the same isolated app as on the Run page, with the same permissions; only the MaestroHub around it is gone.

On the app's Run page, in the app's menu on the Apps list, and in the builder's message after publishing: Copy app link and Open as app. The link keeps the address the app already has (/<workspace>/apps/<app>/kiosk), so bookmarks and paired displays keep working; the screens call it the app's link, and only the address keeps the word "kiosk".

The link is built from MaestroHub's public address when an administrator has set one (System Management → Email → Public address). Without it, the link uses the address in your browser; if that is localhost, MaestroHub says the link works only on this computer.

What is on the screen​

The app, and one slim strip that is always visible, also in full screen:

  • left: the app's name, who built it, and "not part of MaestroHub";
  • right: who is signed in, Sign out, full screen, and Open MaestroHub (to the app's Run page).

A second line appears only while the workspace is in maintenance mode ("Maintenance under way: values in this app may not update until it ends."), and, for people, in the last three days before the license ends ("MaestroHub's license ends in 2 days. Tell your MaestroHub administrator."). On a paired display, the strip shows the display's name instead of a person, with no Sign out, no Open MaestroHub and no license line.

A dashboard has the same kind of page: Dashboard only, full screen in its view options opens it with the same strip (its name, Sign out, full screen, Open MaestroHub, and the same notices).

Who can open it​

Opening the link needs the same access as the Run page. Someone signed out is sent to sign in, with a password or through single sign-on, and comes back to the app. Someone who may see the app but not open it gets, still without menus, the same Your access panel as the app's page on the Apps page: with Advanced Access Control, Request access (then the request's state, Cancel request, or when they may ask again); without it, which roles open apps here and who can give them. A paired display reads only that an administrator can share the app with it. Someone who may not even see the app sees "This app doesn't exist or you don't have access to it."

If MaestroHub cannot be reached for a moment, the app keeps running and the strip says "Can't reach MaestroHub. Retrying." If it cannot be reached when the page opens, the page says "MaestroHub is not answering. This screen retries by itself." and asks again by itself, every 2 seconds at first and at most every 30; a person also gets a Reload button. A workspace address's list of apps does the same. If the app is switched off, unpublished or deleted, or the person loses access, the app stops and the page says why.

Shared stations: the next person signs in as themselves​

On a station several people use, Sign out on the strip makes sure the next sign-in asks who is there, even with single sign-on:

  • the next single sign-on asks the identity provider for a fresh sign-in (or for the account chooser, with Google);
  • if the identity provider still returns the person who just signed out, MaestroHub asks before signing anyone in: "You're signed in as name again." with Continue as name and Use another account;
  • after signing in, the station comes back to the app it was showing.

Administrators can set the identity provider's sign-out return address to MaestroHub's sign-in page; once MaestroHub's public address is set, the single sign-on form suggests it (without one, the form says where to set it). A SAML sign-out ends on MaestroHub's sign-in page.

Paired displays​

Paired displays use the same page and stay read-only. A display whose pairing ended shows the pairing code page with "This screen (name) is no longer paired (its pairing ended or was removed). An administrator pairs it again under Identity & Access → Devices."

Embedding MaestroHub elsewhere​

Embedding

MaestroHub's own pages can no longer be shown inside another website's frame. A page that embedded MaestroHub (an intranet portal, a SCADA web panel) must link to it instead, or open the app's link in its own window.