The Advanced Exceptions From the Audit option was added in 188.8.131.52 to allow uAchieve Self-Service users to create more powerful exceptions at the requirement and sub-requirement level. Main advantages of creating advanced exceptions from the audit include the following:
- Ability to select any exception type (not just the six original ones)
- The new COM setting allows the user to determine which pseudo to pick, by default
Enter Exception Mode
Proceed to Enter Exception Mode () on the HTML audit to access Advanced Exceptions:
Navigate to the requirement or sub-requirement of interest on the audit side (left side) of the exceptions page. The Advanced Exceptions button will appear as a lightning bolt button at the requirement level and sub-requirement level:
- Requirement's Advanced Exceptions button () in dark brown
- Sub-requirement's Advanced Exceptions button () in orange
Choose an Exception Type by clicking an Advanced Exceptions button at either the requirement or sub-requirement level; a Choose an Exception Type page is generated:
Review the list of exception types, descriptions, and exception codes to find the type of exception you would like to create. Click either the Description or the Exception Code to create the new exception:
The exception screen will reappear. The audit side (left side) will highlight the specific sub-requirements you are working with. The exceptions side (right side) displays a series of fields specific to the exception type selected (e.g., Add Action R test):
The More button () is an orange wand icon that designates those fields in the exception area that were pre-populated (autocompleted) from the audit. The More button facilitates creation of many additional complex exceptions that were unavailable in releases previous to 184.108.40.206. Hover with the mouse to view more information:
Certain fields on the exception form can be automatically populated:
- DPMask: is not pre-populated, by default; can select from drop-down menu. DPMask may or may not be set in the HTML, depending upon whether the audit was originally requested with a dpmask.
- Dprog: is pre-populated from the audit
- Requirement Name (RNAME): is pre-populated from the audit
- Auth Code: is always pre-populated since the exception will not apply if the auth code was not set (even if the field is not showing to the user)
Except Action of U and Action of $
Is pre-populated to the default pseudo, but user can change this to a different preferred pseudo
If you backspace out of the pre-populated Pseudo Course (in this example, TRANSCRIP), a list of all available pseudos that apply to the sub-requirement based on the encoding will appear in a drop-down menu for alternate selections:
The list of all available pseudos can be especially useful when working with complicated pseudo groupings, providing the user a time-saving advantage since groupings will not have to by manually entered. All available pseudos will appear in the Select From line are automatically set to begin, but users can key in others if encoding changes are anticipated.
Configure the default pseudo in exceptions from the audit using the server's new COM setting AUDITEXCPS .