Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Related Pages: Field Validation

Table of Contents

...

Type

Usage

Illustration

Full page request (HTTP)

Partial page request (AJAX)

401 Unauthorized - See reference

Bad, missing, or expired token. Specifically for use when authentication is required and has failed or has not yet been provided (e.g Login has timed out)

N/A

Redirect to login page. Once login is completed, redirect back to originating page

Redirect to login page. Once login is completed, redirect back to originating page

403 Forbidden - See reference

For use when the user does not have the necessary permissions for a resource (e.g An administrator only page)

Render the LUX template (VerinTop© and navigation) but the full content area should render the error message

Render the LUX template (VerinTop© and navigation) but the container area should render the error message

404 Not Found - See reference

Page or resource not found. For use when a URL or API is called that the server finds no page or resource for.

Do not render the LUX template (VerinTop© and navigation) but the full page should render the error message

Render the LUX template (VerinTop© and navigation) but the container area should render the error message

5XX Server Error - See reference

Server Infrastructure errors. For use when the server is unable to respond for any number of server issues

Do not render the LUX template (masthead VerinTop and navigation) but the full page should render the error message

Do not render the LUX template (masthead VerinTop and navigation) but the full page should render the error message

Generic

Catch all. For use when none of the system errors above are suitable

Do not render the LUX template (VerinTop© and navigation) but the full page should render the error message

Render the LUX template (VerinTop© and navigation) but the container area should render the error message

...

  • The system error is centered vertically and horizontally on the full page or container area.

  • The illustrations are of ??fixed width and height??.

Interaction

System errors are mostly non interactive with the exception of optional helper operations (e.g. ‘Back’). The rest of the surrounding application should remain intractable when a system error is embedded in a container area.

...

Don’t use

General

  • Minimize the potential for system errors

    • Do not show links or operations to a user that they do not have authorization for.

    • When a resource expires or is deleted, the original URL should redirect to its replacement or new resource where possible.

...

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.

Design

Zeplin link

Screen thumbnail

<<Screen with 200 width>>

...