This document describes the template & patterns for a generic “Error Page” in PASIprep for the PASIprep Page Layout Guidelines.
The page retains most of the Components defined in the Page Layout Guidelines except:
The 403 page is the typical way that web applications handle Forbidden error messages.
Suggested scenarios where this error page should be used:
This page will have the following information:
{Error Title} | Access Denied/Forbidden |
{Error Message} | You don't have the correct permission(s) to perform the action that you have just requested. |
The 404 page is the typical way that web applications handle Not Found error messages.
Suggested scenarios where this error page should be used:
This page will have the following information:
{Error Title} | Page Not Found |
{Error Message} | The page you have requested does not exist. This can be caused by using a bookmark that refers to a page that no longer exists, or you are trying to access PASIprep with an incorrect URL. |
The 500 page plus any other http error code is the typical way that web applications handle Internal Server Errors. Essentally a ‘catch all’ error page to handle unexpected errors.
This page will have the following information:
{Error Title} | Unexpected Error |
{Error Message} | PASI is not able to process your request due to an unexpected error. Any changes that you might have been trying to save could be affected. Time: {timestamp when error occured} |
PASIprep will persist the error internally in the PASI database (as part of the Audit record) and provide a {timestamp when error occurred} incorporated into the message. This enabled the Help to ask users for screenshots of the page with a visible timestamp for the technical team to get more information as needed.