Release Notes

QualityChecks Release Notes - v1.7.0

Release Status

Version 1.7.0 introduces configurable submission visibility by role. Administrators can now choose whether each role sees all submissions or only its own submissions for each submission type.

This release includes:

• Added per-role All or Own visibility controls for Cover Design Reviews, Intros, Finalizing, Proofer Changes, and Association Changes.
• Made an All setting take precedence when a user has multiple roles.
• Applied Finalizing own visibility using the Finalizer assignment.
• Added the role visibility settings to production alongside the configured development settings.
• Strengthened build-version cache recovery so active sessions refresh onto a complete deployment before lazy routes load.
• Added a user-selected default landing page preference that respects accessible routes.
• Improved submission-table pagination on smaller screens.
• Preserved active submission and evaluation form values during automatic cache-refresh recovery.

Summary

QualityChecks v1.7.0 gives administrators precise control over which submission records each role can view, while preserving full access for administrators.

Included in v1.7.0

Role-Based Submission Visibility

• Each non-administrator role detail page includes Submission Access controls for five submission types.
• Each submission type can be configured as All, which shows records from every designer, or Own, which limits records to the assigned designer.
• For Finalizing, Own is based on the Finalizer assignment rather than the designer.
• The setting applies consistently to the type-specific submission queues and the combined My Submissions queue.

Multi-Role Access Resolution

• A user with multiple roles receives All access for a submission type whenever any assigned role is configured as All.
• When no assigned role has All access, the user receives Own access for that submission type.
• Missing or invalid visibility settings fall back to Own access.

Role Administration

• The Roles table remains focused on role identity and timestamps; visibility settings are configured only on the relevant role detail page.
• Administrator role details omit Sidebar Access and Submission Access because administrators always have full access.
• Role detail pages show five assigned users before paginating.

Deployment Cache Recovery

• The app checks the deployed build version before mounting routed content.
• When an active session detects a newer deployment, it reloads through a cache-busted URL while preserving the signed-in Microsoft session.
• Build-version checks are bounded so a static-host outage cannot delay application startup indefinitely.
• Missing same-origin lazy-loaded JavaScript or CSS assets continue to trigger cache-busted recovery as a fallback.
• Active submission and evaluation form drafts are flushed to session storage before a cache-busted reload and restored after the updated app loads.

User Default Landing Page

• Users can select a default page from the profile menu, using only pages available through their assigned roles and sidebar access.
• The preference is stored on the user record and is used only when the app opens at its root route.
• Explicit URLs, including submission previews and type-specific queue links, always take precedence over the saved preference.
• The app no longer chooses a landing page from a hard-coded role mapping.

Submission Table Pagination

• Submission queues retain dynamic pagination while showing at least five records before pagination begins.
• Sorting a submission table resets to the first page only when the sort order changes.
• Pagination controls use stable page bounds after sorting, preventing intermittent Next and Previous failures on multi-page tables such as Cover Design Reviews.

Regression Coverage

• Added visibility-policy coverage for all five submission types.
• Added coverage for cross-role All precedence and Finalizing Finalizer ownership.

Upgrade Notes

• The roles table now includes five visibility fields, one for each supported submission type.
• Existing production visibility settings have been synchronized with the configured development settings.
• The users table now includes default_landing_page for the user-selected preference.
• No Power Automate changes are required.

---