Versions
What this step is for​
Every change you make in the wizard is first saved as a draft. A draft is your private working copy: people who connect the application keep using the last committed version until you decide that the draft is ready.
This step lets you compare the draft with a committed version, edit the draft directly as text, and commit it, which makes it the new version that users get.
What you see on the page​
The page shows two editors side by side. Both show the whole application as text (JSON): basic information, credentials form, scripts, context questions and so on. Above each editor there is a drop-down where you choose which version to show.
| Drop-down choice | What it shows |
|---|---|
| draft | Your working copy, with all the changes you made in steps 1 to 5. |
| latest | The newest committed version, the one users currently get. |
| 0.0.9, 0.0.8, 0.0.7, ... | Earlier committed versions, newest first. |
By default the left editor shows latest and the right editor shows draft, so you see what you have changed. You can choose any two versions to compare, for example 0.0.7 with 0.0.9 to see what changed between two releases, or an old version with the draft before you go back to it.
| Part | What it is |
|---|---|
| "Both editors have the same content" | A note that appears while the two texts are identical, for example when the draft has no changes compared to latest. When they differ, the editors show the difference. |
| Commit draft | A switch. See below. |
Editing the draft​
The draft is the version you can change. Show it in either editor and edit it as text. You can change it in two ways, and the result is the same:
- in the wizard steps 1 to 5 (the usual way);
- directly in the editor that shows the draft, which is handy for copying a configuration from another application or making a quick fix.
Keep the text valid JSON. If the text is broken, the page cannot save it. The logo is stored inside the text as a long encoded string; leave that part as it is unless you replace the whole logo.
Commit draft​
| Switch | What happens when you press Save & Continue or Save & Exit |
|---|---|
| Off | The draft is saved. Users still get the previous committed version. |
| On | The draft is saved and committed: it becomes the new version, and users get it from now on. |
Why use the draft at all:
- You can test a new version of the scripts without breaking the application for people who already use it.
- If you are not happy with the changes, you can leave the draft uncommitted and continue later, or go back to the committed version.
Commit only after you have tested the Authentication and Authorization steps with the Test tab.
Buttons​
| Button | What it does |
|---|---|
| Save & Continue | Saves (and commits, if Commit draft is on) and opens Step 7. Access. |
| Save & Exit | Saves (and commits, if Commit draft is on) and leaves the wizard. |
| Cancel | Leaves without saving the changes of this page. |
Good to know​
- Who can use the application is set in Step 7. Access. That setting applies to committed applications only, so commit the application at least once before you set it up.
- Applications that users already connected are not changed by a draft. They get a new committed version when it is published.
Tips​
- Commit often enough that the committed version is a safe point you can return to.
- Before you commit, show the draft and read it from top to bottom once, especially the scripts, or compare it with latest.