OPUS Release Notes - August 2026

We are pleased to share the latest version of OPUS, released on Thursday 13 August 2026. This update contains a lot of improvements, so let's start it right away with the major changes:

This document outlines the new features, enhancements, and resolved issues included in the August 2026 OPUS platform release. It covers the web dashboard, mobile applications, analytics, and backend infrastructure components.

Highlights of this release include a brand new OPUS Content Hub for publishing company articles and documents.

Major Features

📚 New: OPUS Content Hub

OPUS now includes a dedicated Content Hub for publishing and distributing internal content — documents, posts, urgent notices, and videos — to a company's workforce across stores, regions, or the whole organisation, without needing to attach that content to a checklist or job. The module name shown to users is configurable per company, defaulting to "Content Hub".

Content is organised into Folders, with each item also tagged with a Category and Sub-Category for filtering. A new Content Folders admin screen manages this structure, and a Content Hub grid handles the content itself, with bulk actions and filters. Creating an item only requires a Folder and Title — Category, Sub-Category, Short Description, and Content body are all optional — and attachments up to 10MB are supported, with video content stored as an external link rather than an uploaded file.

On the web, content is browsed through a redesigned Articles page — a filterable grid rather than a folder drill-down, sortable by newest, oldest, urgent, or A–Z, with search across title and short description. Each item is shown as a card with its type, title, and Folder › Category › Sub-Category breadcrumb, and opens as a pop-up. Mobile keeps a Folder → Category → Sub-Category drill-down navigation and has its own search. A Content Hub card has also been added to the web dashboard's Overview Page, showing Recent Content, Folders, and a shorter Quick View grid.

Visibility is controlled through the same site-role links used elsewhere in OPUS, rather than a separate content-specific permission — content with no role selected is visible to everyone, and a sub-company automatically inherits visibility through the site role it's linked to, rather than needing a separate sub-company setting.

Users are notified by push notification when new content is published, and tapping the notification opens the article directly, whether the app is closed, open, or the notification is picked from the in-app list. Attachments now open in the device's own viewer — PDFs in Adobe, images in the gallery app — rather than an in-app equivalent.

A bulk importer is available for administrators migrating an existing document library into Content Hub from a spreadsheet — matching by title to update existing content rather than creating duplicates. The Folder, Category, and Sub-Category referenced by each row must already exist before the import is run.

Cover images, scheduled publish/archive dates, calendar events, and AI-powered search are on the roadmap for a future release but are not part of this one.

Minor Enhancements

Web Dashboard

• Site Services Tags: Sites can now be tagged with the services they offer directly from the Site edit screen, using the same tagging framework already used elsewhere in OPUS. This makes it possible to record and report on which services are available at each site.
• Scheduled Custom Reports: Custom reports can now be configured to automatically email on a recurring schedule (daily, weekly, or monthly) to a specific user or to everyone linked to a site role, without needing to be run manually each time.
• Overdue Job Notifications: Overdue job notifications can now be sent to a user or site role independently of the job's operator, rather than only ever notifying the operator.
• Workflow Duplicate Job Avoidance: The criteria used to prevent duplicate jobs being generated by a workflow have been refined, so a source job being adjusted and signed off again can still correctly generate a fresh destination job where required.
• Analytics Dashboard Date Handling: Date parameter handling in the Blazor-based Analytics Dashboard has been corrected, resolving inconsistencies that could occur compared to the previous WebForms version.
• Custom Report Time Zone Handling: Custom reports using the analytics database now correctly account for the difference between the server's UTC clock and the SAST time zone, so date-range filters no longer cut off early or include the wrong day's data.
• Transactions Grid Performance: The Transactions grid has been optimised for faster loading and filtering.

Bug Fixes

Web Dashboard

• Documents in the Documents page were not being limited to the sites linked to the user, meaning some roles could see documents created by every site rather than just their own. This has been corrected.
• Deleting a question from an unpublished or cloned checklist could freeze the screen and fail with a generic error, caused by a missing database index. The underlying index has been added and deletion now completes as expected.
• The job audit log was not always displaying the correct "created by" user name. This has been resolved.
• Linked jobs on the Job Details page were not sorted in date order. They now display in the correct order.
• The Operators grid filter for checklists with no checklist tags ("Untagged") was not returning results. This has been corrected.
• Custom filters on the Transactions grid were not working — the filter spinner would run and stop without returning results. This has been resolved.
• Editing changes made to a job on the web or in admin were not always reflected back on the job when opened on mobile, due to a missing sync trigger. The app now correctly detects and syncs these changes.

Mobile Applications

• A workflow-generated job could occasionally be signed off twice if the app was closed while a sync was in progress, resulting in duplicate downstream jobs being generated. This has been resolved.
• An image attached to a repeating subsection's child question could fail to upload with a foreign key error if the parent answer had not yet been confirmed as uploaded. This has been corrected.
• Recurring jobs configured to send to "Unassigned" on a daily basis were not always appearing the following day despite the recurrence being set up correctly. This has been resolved.
• An intermittent connection error when viewing a document-type question could prevent a job from being signed off, blocking downstream workflow jobs from being generated. This has been resolved.