Create Exceptions From the Audit
To create an exception from an audit, staff can Enter Exception Mode to create exceptions directly from the HTML audit without requiring extensive knowledge of exceptions.
If you are looking for information on creating regular exceptions via the Exceptions menu instead, click here. |
For More Info... Create Exceptions From the Audit FAQs |
Exception Mode is available from an opened HTML audit in uAchieve Self-Service (Audits<Manage). If a menu option for Exceptions is displayed, then you will have access to Exception Mode on the audit.
NOTE: |
Make sure you run a new audit with the new server before attempting to use Exception Mode. Audits run against a pre-4.2 version of the server will not have the exception buttons since those are new to 4.2. |
Enter Exception Mode
If available, click Enter Exception Mode button () on the HTML audit.
The Exception Mode screen consists of two areas
- The left side of the screen is the Audit area
- The right side is the Exceptions area
Exception buttons are aligned down the center:
NOTE: |
Exception Buttons
Exception buttons are ordered next to corresponding audit requirements down the center of the screen between the audit Requirements (on the left) and the Exceptions table (on the right). Three exception buttons are available:
Exception Button | Description |
---|---|
![]() |
Force Requirement Complete |
![]() |
Edit Requirement |
![]() |
(new in 4.3.0.4) |
Where are my Exception Buttons?
|
Exit the Exception Mode screen at any time by clicking the Exit Exception Mode button.
NOTE: |
Audit Area
The Audit area displays an abbreviated version of the HTML audit on the left side of the screen. The audit is still interactive, but with charts and graphs removed and the hierarchy collapsed (by default).
NOTE: |
Running an exception from the audit always generate an HTML audit (not a What-if audit), as indicated on the Completed Audit Request page:
Exceptions Buttons
Exception buttons in the center of the Exception Mode page represent the six unique exception types available at different levels.
The easiest way to view exception buttons in Exception Mode is to Open All Sections on the audit side (left side) of the screen. This will expand the closed sections to view the buttons associated with each level
- Requirement (highest level)
- Subrequirement
- Courses
- Subrequirement
Close All Sections | Open All Sections |
---|---|
![]() |
![]() |
Exception buttons are color-coded to the level of the audit applied:
Audit Level | Color |
# of Exception Types at This Level |
Exception Type | Button | |
---|---|---|---|---|---|
Requirement | Brown |
2
|
|
|
|
Sub-Requirement | Orange | 3 |
|
|
|
Course ("Select From:" line) |
Green | 3 |
|
|
Click on an Exception button to be directed to a gray exception box to key in details of the exception and save it. As soon as an exception is saved, it immediately affects the student record and appears in the uAchieve Self-Service Client.
Control Codes (Ctlcd) set in the Self-Service Admin area control which specific exceptions that a user can create. See functional documentation on setting Control Codes.
The six unique exception types available in Exception Mode are detailed below.
Force Complete
(Applicable to Requirement and Sub-Requirement)
The Force Complete exception forces a current Requirement or a Sub-Requirement to completion, no matter what. Staff simply need to okay the Force Complete with no further action required.
Requirement Force Complete Exception |
||
![]() |
Exceptions made will not be reflected on the audit until a new audit is run.
|
|
Subrequirement Force Complete Exception |
||
![]() |
The Force Complete area is the same for Sub-Requirements as it is for Requirements (above).
|
Edit
(Applicable to Requirement and Sub-Requirement)
The Edit exception modifies a Requirement or a Sub-Requirement.
Requirement Modification Exception |
||||
|
Tab 1. Requirement Modification
Any edits away from default values render an action button:
|
|
Tab 2. Verify & Save
Exceptions made will not be reflected on the audit until a new audit is run.
|
|
Subrequirement Modification Exception |
||||
![]() |
Tab 1. Subrequirement Modification
Any edits away from default values render an action button:
|
![]() |
Tab 2. Verify & Save
Exceptions made will not be reflected on the audit until a new audit is run.
|
Force Course
(Applicable to Sub-Requirement only)
Force Course Exception |
||||||
![]() |
Tab 1. Force Course
|
![]() |
Tab 1. Force Course (continued)
Any additions away from default renders an action button:
Undo a course addition into the Course Forcing: box using the Delete button ( |
![]() |
Tab 2. Verify & Save
Exceptions made will not be reflected on the audit until a new audit is run.
|
Add Course
(Applicable to Course only)
Add Course Exception |
||||
![]() |
Tab 1. Add Course
Any additions away from default renders an action button:
Undo a course addition into the Course Adding: box using the Delete button (
|
![]() |
Tab 2. Verify & Save
Exceptions made will not be reflected on the audit until a new audit is run.
|
Remove Course
(Applicable to Course only)
Remove Course Exception |
||||||
![]() |
Tab 1. Remove Course
|
![]() |
Tab 1. Remove Course (continued)
Any removals away from default renders an action button:
Undo a course removal into the Course Removing: box using the Delete button ( |
|
Tab 2. Verify & Save
Exceptions made will not be reflected on the audit until a new audit is run.
|
Swap Course
(Applicable to Course only)
Swap Course Exception |
||||||
![]() |
Tab 1. Swap Out
Any swapping away from default renders an action button:
Undo a course swap into the Swapping Out: box using the Delete button ( |
![]() |
Tab 2. Swap In Select a course from the list to swap into the Swapping In: box using the add button ( Undo a course swap into the Swapping In: box using the Delete button (
Any swapping away from default renders an action button:
|
![]() |
Tab 3. Verify & Save
Exceptions made will not be reflected on the audit until a new audit is run.
|
Exceptions Area
The Exceptions area is the list of exceptions currently applied to this particular student audit, by ctlcd, Note, Auth by, and Auth Date.
Control Codes (Ctlcd) set in the Self-Service Admin area control which specific exceptions that a user can create. See functional documentation on setting Control Codes. |
Advanced Exceptions From the Audit
If users have permissions allowed, they may create more advanced exceptions at the requirement and sub-requirement levels.
Exit Exception Mode
Click Exit Exception Mode to exit the exception mode (creating exceptions from the audit).
The Staff member will return to the student audit:
Click on the Exceptions tab in the menu bar to view new changes or additions.