Conditional Error Behavior Scenarios
When triggered, conditional errors appear as close as possible to the issue they are associated with, ensuring that users do not need to navigate back and forth from the error to determine what changes need to be made. Multiple conditional errors can be triggered at one time.
Conditional client-side error
IF…A user takes an action on a page that causes progress to be blocked. ANDThe user navigates away from the area where the action was taken.
THEN…The conditional error alert appears.
UNTILThe user corrects the error
THEN…The conditional error message disappears.
THEN…The conditional error alert appears.
UNTILThe user corrects the error
THEN…The conditional error message disappears.
Conditional server-side error
IF…A user takes an action on a page that causes progress to be blocked. ANDThe user selects the progress button to attempt to continue.
THEN…The Red Sticky Bar is displayed with the message “Please correct the <#> issues on this page in order to continue. View next”If there is only one error, the number of issues does not appear, and there is no jump link to navigate the user between errors. (“Please correct the issue on this page in order to continue.”)ANDThe conditional error alert appears.
UNTILThe user corrects the error
THEN…The red sticky bar and conditional error message disappear.
THEN…The Red Sticky Bar is displayed with the message “Please correct the <#> issues on this page in order to continue. View next”If there is only one error, the number of issues does not appear, and there is no jump link to navigate the user between errors. (“Please correct the issue on this page in order to continue.”)ANDThe conditional error alert appears.
UNTILThe user corrects the error
THEN…The red sticky bar and conditional error message disappear.