OPUS Release Notes - September 2025

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

Major Features

✅ Sub-Company Checklist Management for Parent Companies

Sub-company admins under Parent Companies now have the ability to remove non-critical checklists from their company’s job flow.

This update provides greater operational flexibility, allowing sub-companies to opt out of non-mandatory checklists that may not be relevant to their specific formats or workflows.
Critical checklists remain locked to ensure compliance, while non-critical ones can now be disabled as needed by sub-company admins.

📅 Checklist Frequency & Run Status Indicators

OPUS now supports the ability to assign frequency settings to checklists and to display run status indicators on mobile — helping users track whats already been completed per period and what is still pending.

🔧 New Frequency Settings

Checklists can now be tagged with one of the following frequency options:

Daily
Weekly
Monthly

This allows better alignment with operational routines that require ad hoc initiation by users without pre-scheduled jobs.

📱 Mobile Indicators: Has This Job Been Done?

For ad hoc jobs that are expected to be run on a recurring schedule:

The mobile app will now indicate if a checklist has already been run for the selected frequency period (e.g., today for daily, this week for weekly, this month for monthly).
If the job has been completed for all linked sites, the checklist will be marked as “done” for the period.
Users can still re-run the checklist if needed — the indicator is purely informational to avoid duplication or oversight.

🔎 Visibility of Checklist Frequency & Priority

To support planning and prioritization:

Checklist frequency and priority are now visible:
- When creating, editing, or viewing a job (on both web and mobile)
- In the mobile checklist selection screen
- In the job grid on web

Prioritization uses OPUS’s existing priority table:

🟥 Critical, 🔶 High, 🟨 Medium, 🟩 Low, and ⚪ None.

🔁 Improved Speed of OPUS Mobile app

To improve performance and reduce unnecessary data syncing, a new setting has been added at the checklist level:

✅ Only Sync on Sign Off

When enabled, the checklist will not auto-sync when navigating back to the start page or through other parts of the app.
Instead, syncing will only occur:
- Manually, when triggered by the user
- Automatically, when the checklist is signed off

Alongside the checklist-level controls, we’ve also made a key improvement to the site sync model:

Sync logic for Sites now uses the last sync date, instead of syncing all sites on publish.
This significantly improves performance during sync operations by only syncing sites that have changed since the last successful sync.

🔒 Granular Access Control for Checklist Job History

To strengthen data security and align with real-world permission models, OPUS now supports context-sensitive access control for job histories — moving beyond the existing all-or-nothing user-level model.

🚫 Previous Limitation

Access to job history was governed solely by a global user setting.
Users with history access could view all jobs, regardless of:
- Checklist
- Site
- Job type
No fine-grained control was available to limit access to specific categories or scopes of job history.

🧩 New Capability: Checklist-Level Job History Access

Admins can now define permissions at the checklist level to control who can view the history of jobs related to that checklist.
This enables role-based, site-specific and checklist-scoped visibility into job records, aligning with operational security needs.

🔍 Consideration for OPUSmedia

The logic used to hide documents in OPUSmedia (based on visibility and access control) is under review to align with this new job history permission model.
Future updates may bring unified handling of job-related media visibility alongside job history access.

🚚 Multi-Leg Stock Order Process

A new multi-leg stock order workflow has been introduced to support complex stock movements across 2–3 stages, allowing for more flexible and accurate inventory operations.

Previously, stock workflows in OPUS were limited to single-leg transitions (e.g., Ordered → Intake). This enhancement enables multi-stage flows such as:

Request → Ordered → Intake

This supports suppliers, warehouses and internal transfers, enabling seamless tracking from order to use.

Other Enhancements

🆔 Workflow Action: Auto-Generate Employee Number

A new Workflow Destination Action has been introduced to automatically generate an Employee Number (reference) for the context user on a job if none is currently set.

🔄 Enhanced Sage 300 People Integration

This release introduces powerful new workflow automation capabilities to support HR and onboarding processes, particularly when integrating with Sage 300 People.

🧩 New Workflow Condition: Sage 300 People Employee Check

A new workflow condition allows OPUS to check for the existence of an employee in Sage 300 People, based on checklist answers.
This ensures validation of employee records before proceeding with downstream actions.

🛡️ Refined Access Control: Limited Sites Role & Checklist Visibility (Sub-Companies)

Enhancements have been made to how site roles and checklist restrictions interact within sub-companies to provide clearer, more intuitive access control for users — especially those assigned to Limited Sites Roles.

📷 Enhanced Configuration for Photo Option Questions

We’ve added greater flexibility to how “Photo” questions using option types can be configured — with a focus on clarity and control over optional vs required behavior.

✅ New: Optional Setting at Question Level

You can now set Optional = true at the question level for option-type questions with photos.
When set, users will always be allowed to take a photo, even if no specific option is selected.

🛑 Option-Level Rules Still Take Precedence

If any individual option within the question has Required = true, that requirement overrides the question-level optional setting.
This ensures that mandatory photo capture logic remains enforced where needed.

🏗️ Hierarchical Site Roles (Parent–Child Relationships)

Site roles can now be arranged in parent–child hierarchies to better reflect real-world organizational structures.

Each site role can optionally have a parent role.
Supports multi-level hierarchies (e.g., Company Admin → Regional Manager → Store Manager).

Bug Fixes and Minor Improvements

Minor Improvement: Updated holdings labels and headers to match new UI design.
Minor Improvement: Renamed restaurant owner site roles and updated access/overview links.
Minor Improvement: Checklist user access queries now consider site restrictions via NoLock.
Minor Improvement: Added <section.name> to questions in Blazor alerts grid for clarity.
Minor Improvement: Audit logging added to Job Import functionality.
Minor Improvement: Custom EF errors now include DB connection info for Slack workflows.
Minor Improvement: Hyperlinks in mobile summary/text fields are now clickable if a URL is detected.
Minor Improvement: Resolved issue where OPUS4manager did not display sites on second selection in Site Holdings.
Minor Improvement: Site field now shows “optional” text when no site is required on job creation.
Minor Improvement: Moved “Done” button to bottom of screen after photo capture for improved usability.
Minor Improvement: Site tags on jobs-checklist grid now respect limited sites user settings.
Minor Improvement: Document jobs set as “not visible in history” are now hidden on mobile.
Minor Improvement: User search now returns results when combining first and last names.
Minor Improvement: Checklist selector in sub-companies now hides tags/brands and adds description text filter.
Minor Improvement: Jobs grid now shows “Job Closed – Not Started” and “Job Closed – In Progress” statuses.
Minor Improvement: Job Importer now supports multiple job tags.
Minor Improvement: Job description is now searchable in the reference field on jobs grid.
Minor Improvement: Operator grid now respects limited site roles in job-checklist site list.
Minor Improvement: Dashboard category selection now uses DisplayName instead of Name.
Minor Improvement: SA ID number validation now works correctly when using number-type questions on mobile.
Minor Improvement: Auto-closed jobs now display a distinct label in job history to avoid confusion with manual sign-off.
Minor Improvement: Item Ordered quantity defaults "#" so as to force a quantity to be captured
Minor Improvement: Changed orange “Enter text…” placeholder on read-only fields to avoid user confusion.
Fix: Pull Inbox search now works as expected and displays job descriptions on mobile.
Fix: Stock items marked as “X” now correctly display as rejected in movement transfer jobs.
Fix: Date Format in Job Descriptions now respects question format Settings
Fix: Added side-by-side historical score comparison for cloned store audits and KPIs on mobile.
Fix: Enhanced context user change logic to properly update job-level references on mobile.
Fix: Spinner now appears correctly in Chrome on item holdings grid button clicks.
Fix: Sub-company job wizard now only displays operators from the correct company scope.
Fix: Clone jobs now handle undefined item transaction types gracefully, excluding invalid items.
Fix: Audit log now correctly captures permanent job deletions.
Fix: Document grid statuses now show accurate state representations.
Fix: Jobs grid “Last week” filter now includes weekend dates.
Fix: Transactions grid now shows results for limited sites user roles.
Fix: ‘Show in Job History’ checkbox now copies correctly when updating document checklists.
Fix: Eliminated double scrollbars on dashboards on smaller screens.
Fix: Job description column in jobs grid now links correctly to job detail page.
Fix: Improved error handling for overly long prompts entered in reports.
Fix: Improved spacing on multi-line job descriptions and ensured three-dot icon does not overlap text.
Fix: Resolved blank user list when selecting context users in APP