Skip to main content

Publishing

An app is built in versions. Each version is a snapshot of the app with its own prompts, resources, roles and notes. Users always run the published version, so you can keep building the next version without disturbing the app people are using.

The lifecycle at a glance​

TermWhat it means
Build sessionAn active editing context for a draft version. Only one person can be in a build session on a version at a time. Sessions time out after 8 hours.
SaveKeeps everything done in the current build session.
DiscardThrows away everything done in the current build session.
VersionA snapshot of the app. Every version has a status: Draft, Published or Archived.
PublishMakes a version the one users run.
ArchiveRetires a version. Archived versions are kept and can be viewed, but not built on.

A new app starts with version 1 as a draft. Only a Draft version can be built on. Published and archived versions are read-only, so to change a published app you create a new version.

Save and discard​

Save keeps the work from the current build session. Click the arrow next to Save to choose what happens afterwards:

  • Save and continue to build (the default) keeps the build session open so you can keep prompting.
  • Save and exit Build Mode ends the build session.

Discard ends the session and throws away everything it produced, including the conversation. Both buttons ask you to confirm.

Unsaved-changes reminder​

After a few prompts with no save, a banner appears above the prompt box: You have unsaved changes. Press Save to keep your progress. Close it and it comes back after 30 minutes if you still have unsaved work. If you try to leave the editor with unsaved work, you are asked to confirm first, because leaving loses that work.

caution

Unsaved work is lost if the session ends or you discard it. Save before stepping away.

Versions​

Use the version selector at the top of the editor to switch between versions. Each entry shows the version number, its status, who created it and when. The selector is locked while a build session is open.

Create a new version​

  1. Open the version selector and click New Version.
  2. Add a description for the version.
  3. Choose what to bring along. For each of resources, assets and roles you can copy them from the version you are on, or start fresh. For roles you can also copy the role assignments (who has which role).
  4. Create the version, then click Build to start a build session on it.

The published version stays live while you work on the new one.

Version notes​

Use Notes in the version's actions menu (the three dots next to Build) to describe what changed. Notes are for builders and are not shown to users of the app.

Other version actions​

The same menu also lets you look at a version's Resources, Assets, In-app Roles, Build Prompt history and Feedback. See Build prompt history and Application feedback.

Publish a version​

  1. Select the version you want to publish and make sure no build session is open. Save or discard first.
  2. Click Publish, add an optional note and confirm.

Publishing makes that version the one users run. The Apps list then shows the published version and who published it.

  • Only one version is published at a time.
  • You can publish any version that is not already published, including an older one. This is how you roll back.
  • Archive retires a version you no longer need. It is not available while a build session is open.

Both Publish and Archive need the Deploy permission. See Who sees which action.

tip

Test your app with accounts for each in-app role before publishing. In the preview you can also use Simulate Roles to check what each role sees.

The Apps list​

App Builder opens on the Apps list. For each app it shows:

  • Published: the published version and who published it and when, or No published version.
  • Version: the latest version, its status and how many versions the app has.
  • Created by and Modified by, with dates.

Click a row to open the app: users run the published version, and builders with Write access open the editor when there is nothing published yet. See Manage your apps for search, labels, filters, favourites and copying.

Who sees which action​

Each row has an actions menu.

ActionWhat it doesWho sees it
Start appRuns the published versionEveryone who can see the app, when it has a published version
Edit latest versionOpens the editor on the latest version (the menu shows which, for example Continue editing v3)People with Write access to the app
Copy appCreates a new app from a copy of this onePeople with Write access to the app
Delete appPermanently deletes the app, after you confirmPeople with Write access to the app

Inside the editor, Publish and Archive need Deploy access. With only Write access they are greyed out, so a builder can finish the work and hand publishing to an app owner. See Concepts & Architecture for the permission levels.

Typical workflow​

  1. Build in a draft version: prompt, review the preview, Save.
  2. Publish the version.
  3. For the next significant change, create a new version, build and save, then publish it. The previous version stays available if you need to go back.

Further reading​

Last updated on