November 5, 2026 Release - Version 5.14.0 (Web), v1.15.0 (Admin v2) and v2.13.0 (Client v2)

Created by Joon-Agmer Merdegia, Modified on Thu, 5 Nov at 5:30 PM by Joon-Agmer Merdegia

Inspection themes and scores on the Home Dashboard


This release adds two ways to read inspection results: by theme, across the sections of a form, and as scores on the Home Dashboard.


ComponentVersion
Web / Serverv5.14.0
Admin v21.15.0
Client v22.13.0


Inspection themes


A theme is a subject, such as hygiene or safety, that cuts across an inspection form's sections.

  • Themes page in Admin. Under Inspections, owners and admins keep the account's list of themes: add, rename, translate, reorder, and retire one that is no longer used. Everyone else can see the list.

    The Themes page in Admin, subtitled "Group inspection questions by subject, across sections", listing twelve numbered themes with drag handles, such as Package integrity, Temperature control and Health and safety, under an Add theme button.
  • Give a question a theme. In the App Builder, a multiple-choice question has a Themesetting, applied when the App is published. In an Inspection App's Field Library, you can set or clear the theme of many questions at once, and see which questions still have none.

    The lower part of the Set a theme dialog: Management is selected (10 will change, 1 already has it) below Health and safety, Security and HR, each marked 11 will change; a summary reads 10 have no theme yet and 1 already has it, above Cancel and Set on 10.
  • Read inspections by theme. On the web, an Inspection App's list switches betweenSections and Themes, with one score column per theme. The list remembers your choice for each App.

    An Inspection App's list on the web with Themes selected in the Sections, Themes and Dashboard switch. Nine inspections show their ID, Status and Compliance, then fifteen theme columns such as Package integrity, Environment and Management. Completed inspections score between 88% and 100% on ten of the themes; five themes and the inspections in progress show a dash. The theme scores are illustrative.


Scores on the Home Dashboard


A Home Dashboard filtered to all Sites and Created Date Year to Date, last refreshed today: Latest audit and Average score cards side by side for three Inspection Apps, at 95 and 94 percent, 88 and 86 percent, and a dash for an App with no score, above a plain Actions card with 0 Records.
  • Latest score and Average score cards. In Admin's dashboard builder, Add widget offers aLatest score card and an Average score card for any Gen 2 Inspection App. On the web, the card shows the score as a percentage, coloured by the App's compliance ranges, or says why there is none (for example No audit in the period).
  • Filter by date and Site. A dashboard with App, Domain or score cards has a filter bar: a created-date filter, a Site filter that picks whole Regions or single Sites, a refresh button and the time of the last refresh. The cards follow the filters, and a copied link keeps them.
  • New default period. Home Dashboard counts now cover Year to Date by default, instead of the last 6 months. Choose another period in the filter bar.
  • Last Year. Record lists' and App dashboards' date menus also offer Last Year.


Bug fixes


Gen 2 — Admin v2

  • Duplicating an Inspection App produced a copy in which no inspection could be started.
  • Files made by App Export could not be imported back.
  • Apps with more than 500 fields did not show all of them.
  • Paging through the list of dashboards showed the same dashboards on every page, and the page size could not be changed.


Gen 2 — Web / Server

  • Editing a submitted inspection as an admin did not raise the automatic Action when an answer was changed to one that should raise it.
  • A Record with a Reference field could not be updated.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article