Related Pages: Field ValidationEmpty States
| Table of Contents |
|---|
Description
System errors are application and server errors which occur from a failure of communication between the client application and its server.
<< Most communicative screenshot of the component >>
Types
There are many different types of system errors that can occur during the hosting and operation of modern web applications. These take the form of the list of HTTP status codes attached to every client\server request. With LUX, we have created specific designs and illustrations occur when the application encounters a problem, such as with authentication or server communication.
...
Types
This full list of HTTP status codes shows all of the potential server request response codes.
LUX has specific designs for the 5 most common types of these system errors (including one for a ‘catch all’ situation), plus an additional generic design for rarer instances.
Type | Usage | Illustration |
‘Regular’ HTTP request flow
AJAX request flow with target container area
AJAX request flow without target container area
Icon | Full page request (HTTP) | Partial page request (AJAX) |
Bad, missing, or expired token, causing an authentication failure (e.g login has timed out). | N/A |
Redirect to login page. Once login is completed, redirect back to originating page
- redirect | N/A - redirect | Redirect to |
Login page. |
complete, redirect back to originating page. | Redirect to |
Login page. |
complete, redirect back to originating page. |
The user does not have permission to access a resource (e.g an administrator-only page). |  |  |  Render the LUX frame, including the VerinTop. |
with the error message. |  Render the |
permitted areas of the interface. |
User closable toast error message
within the container area. |
Page or resource not found |
Do not render the LUX template (masthead and navigation) but the full page should render the error message
Render the LUX template (masthead and navigation) but the container area should render the error message
User closable toast error message
5XX Server Error - Server Infrastructure errors
Do not render the LUX template (masthead and navigation) but the full page should render the error message
Do not render the LUX template (masthead and navigation) but the full page should render the error message
Do not render the LUX template (masthead and navigation) but the full page should render the error message
Generic - Catch all
Do not render the LUX template (masthead and navigation) but the full page should render the error message
Render the LUX template (masthead and navigation) but the container area should render the error message
User closable toast error message
Usage & Behavior
General guidelines
...
. Use when a URL or API is called that the server finds no page or resource for. |  | N/A |  The full page should be replaced by the error message. Do not render the LUX frame. |  Render the LUX frame, including the VerinTop. | |
Resource is unavailable at that time because there is a load on the network or service. |  |  |  The full page should be replaced by the error message. |  Render the permitted areas of the interface. | |
Service is not responsive or denies access. |  |  |  The full page should be replaced by the error message. |  Render the permitted areas of the interface. | |
Server infrastructure errors. Use when the server is unable to respond for various reasons. |  |  |  The full page should be replaced by the error message. |  The full page should be replaced by the error message. | |
Generic | Catch all. Use when none of the system errors above are suitable. |  |  |  The full page should be replaced by the error message. |  Render the LUX frame, including the VerinTop. |
Usage & Behavior
General Guidelines
Structure
A system error generally consists of:
A an illustration which visualises and contextualises the error.
a title which describes the high level basic nature of the error. This may also contain the error code.
A description paragraph that summaries (in a little more detail) the reason(s) why the application entered the error state.
An illustration that attempts to visualize and contextualize error.
Examples:
Placement and Positioning
<<Where should the component be located on the screen. See example: Pagination placement and positioning>>
Default State
<<When there is more than one state for control or area. Including default values> see example: Numeric stepper default state >>
Content
<<Including labels, microcopy, number of items, order of items etc… See example: Buttons content >>
Interaction
<<for example, how to change value – type, arrows, use slider. See example: Numeric stepper interaction>>
Best practices
<Whenever a recommendation (not a must) is provided>>
Use:
<…>
<…>
Don’t use
<…>
<…>
General
<…>
a description that provides more detail on why the error has occurred.
action options such as Back or Retry, to help the user recover from the error state. (Optional).
Example:
...
Placement and Positioning
The system error is centered vertically and horizontally on the full page or container area.
Interaction
System errors are mostly non-interactive, with the exception of action options such as Back, where shown.
When a system error is embedded in a container area, the rest of the application should remain interactive.
Best practices
Don’t use:
as a substitute for form field validation.
General
Minimise the potential for system errors.
Do not show links or options which the user does not have authorisation for.
When a resource expires or is deleted, the original URL should redirect to its replacement or a new resource, where possible.
Accessibility Compliance
Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.
Download
| View file | ||
|---|---|---|
|
Design
Zeplin link | Screen thumbnail |
|---|
<<Short Zeplin link. You
Use this 
>>
<<Screen with 200 width>>
Code
...
Code
...