Open Subject Allocation
Go to Exam → Subject Allocation. The existing Subject Allocation guide remains available. Classic opens first unless you saved another choice. Try the new layout and View old layout switch both ways; Make this my default or Make old layout my default saves your own institute-specific preference. Explicit layout links override it for the visit, and a failed save preserves the previous default with Retry. Layout changes retain the same mounted scope and unsaved subject drafts; switching does not save them.
Load and change subjects
Choose Campus, Class, optional Sections and student Status, then Show. Changing draft selectors alone keeps the loaded class and its edits. Show with unsaved changes retains the original discard confirmation. Only subjects offered for the loaded class can be added; original stray-subject removal and row All clearing remain.
Two different scopes
Header subject checkboxes and header All act on the currently filtered visible page only. A row checkbox changes that student. Save Changes writes ALL edited students in the loaded class, including edits hidden by search, paging or column visibility. Each saved subject list replaces that student’s whole subject list; rows restored to their original list are no longer edits. The original update permission, confirmation, validation, no-op response and PATCH payload remain.
Review, settings and native Print
Existing substring search, column filters, sorting and saved column order/visibility retain their original behavior. Browser Print uses the displayed table page with original page content. No Excel/PDF export or new dedicated Print action is added. The existing guide explains the original allocation rules; this guide covers only layout choice and review scope.
Pending and Retry
Loading/saving or failed scope/student/grid-setting queries block stale selectors and checkboxes and hide stale print content. Retry repeats the failed original scope, students or grid-setting query; it does not save subjects. Existing Exam::Subject Allocation access stays authoritative; layout choice grants no access and adds no sends.