Introduction
The app tells you when it has changed, in three places, and gives you one way to tell somebody when something is wrong.
Two of them find you: a warning strip and a Highlighted block, both on your daily overview. The third you go looking for — the full release notes, one entry per version, under Release notes in the main menu. The fourth is the feedback form, which is how a problem gets from your desk to the people who can fix it.
You will use this when:
- a screen has moved and you want to know whether that was deliberate
- a colleague says "that changed last week" and you want the detail
- something is broken and you need to report it properly
Words this screen uses
| The screen says | It means |
|---|---|
| Highlighted | Short notices pinned to your home screen by the supplier |
| Release type | How big the change was: Major, Minor, Patch or Hotfix |
| Executive summary | The one-paragraph version, before the detail |
Steps
Before you start: nothing here needs special rights — every signed-in member of staff sees the same notices and the same release notes. Nothing you do on these screens changes any booking or any figure; they are read-only.
- Start on your daily overview and read the warning strip, if one is showing. It is the supplier's way of saying something behaves differently from today.
- Read the Highlighted block underneath it, and click an entry to open the full text.
- For the whole story, open Release notes from the main menu.
- Narrow the list with the search boxes above Release version and Release name, or by Release date and Release type.
- Click a row to open that version's note.
- Move between versions from the Other release notes panel beside it, using Load More to reach older ones.
What a release note is made of. Each one opens with its version, type and date, then runs through the same sections in the same order.
| Section | What is in it |
|---|---|
| Executive summary | The short version — only printed if somebody wrote one |
| What's New | Features that were not there before |
| Improvements | Things that already existed and now work better |
| Bug Fixes | Faults that have been repaired |
| Breaking Changes / Known Limitations | Where you will have to do something differently |
| Closing remarks | Anything that did not fit above — again, only if written |
A missing section is a deliberate choice. Each of the four middle sections is switched on per release note, so a note with no Bug Fixes heading is not a note that forgot them: whoever wrote it turned that section off. Look for the heading before concluding nothing was fixed.
You only ever see finished notes. A note stays invisible while it is being drafted, waiting for approval, or approved but not yet published. It appears in your list the moment it is published, so a version you have already been running for a week can turn up in the list today.
The warning strip cannot be dismissed. It shows whenever the supplier has a live warning out, it says the same thing to everybody at every company, and it goes away only when they withdraw it. Clicking it does nothing and there is no "seen it" button — so if one has been sitting there for days, that is expected, not a fault.
The list is one row per released version. Each row carries the version, the name, the date it went out and its type, and the newest work is not always at the top — sort or search rather than assuming the first row is the latest. A Major release is one that changes how something works, Minor adds to it, and Patch and Hotfix are repairs — a hotfix being the urgent kind that did not wait for the next planned release.
Getting help when something is wrong. The app carries a feedback form: a Subject, a Description, and an Email box that appears only when the form is set up to ask for one. Open it from the feedback button in the app frame — exactly where that sits depends on how your app is put together.
The form keeps what you typed. Subject, description and email are already saved as soon as you type them, not when you send. Close the form halfway through writing and it is all still there when you come back. That is convenient until it is not: Cancel does not throw a half-written report away either. Use Clear when you want a genuinely blank form.
Send a picture with it. Take Screenshot grabs the screen you were on, and there is an annotation tool for drawing on it — a red circle round the wrong number saves several paragraphs. Upload attaches a file instead. Submit sends the lot.
What to do next: if the release note explains a change you now have to work around, tell the rest of your shift before they find out one at a time. If it does not explain what you are seeing, that is worth a feedback report — with a screenshot and the booking number in the description.
Tips and common issues
- There are two menu entries that look the same. Release notes is the reading list everyone gets. A second, near-identical entry is the editing screen and only administrators have any business there — if what you opened lets you create and delete release notes, back out and take the other one.
- A version you know shipped is not in the list. It has not been published yet. Nothing you can do at your end brings it forward; it will appear on its own.
- The Highlighted block has vanished. It only shows while at least one notice exists. An empty block is hidden rather than shown empty, so nothing is broken — there is simply nothing pinned at the moment.
- You cannot find where a change was announced. Breaking changes are listed twice: as a warning strip when they are current, and permanently in the Breaking Changes / Known Limitations section of the release note for that version. The strip goes; the note stays.
- Your feedback report came back with a question you cannot answer. Fill in the Email box if the form offers it. Without a way back to you, a report that needs one clarification stalls.
- The screenshot is of the wrong screen. It captures the screen the form was opened from. Go back to the screen that is wrong, then open the form from there, rather than opening the form first and navigating afterwards.