Error pages

Error pages can be divided into business errors and platform errors.

Platform errors

Platform errors are errors that appear when an error occurs on the application that is handled by the platform by default, e.g. a session expiration error.

In the above situation an error page is displayed containing textContent set in the platform configuration errorPagesConfiguration

The configuration is set globally in the platform. We do not have the ability to update it low-code in the designer. If changes are needed, contact the administrators.

Example configuration:

<code_default>
    <content>error_page_default-*</content>
</code_default>
<code_serverSessionExpired>
    <content>error_page_serverSessionExpired-*</content>
    <retryButtonAvailable>true</retryButtonAvailable>
    <styleName>spider-night</styleName>
</code_serverSessionExpired>
<code_formLimitExceeded>
    <content>error_page_formLimitExceeded-*</content>
</code_formLimitExceeded>

Business errors

Business error is a situation in which a user's action, a system process or an interaction with an external system violates accepted business rules — even though from a technical point of view the operation could be performed.

Examples:

  • Attempting to withdraw an amount exceeding available funds.

  • Submitting an application with a client's account inactive.

  • Accessing the application as an unauthenticated user, even though login is required

How to invoke?

Business error it can be invoked in script services and script validators. It is best to use the method throwBusinessException and getErrorPageDefinitionBuilder.

Methods that can be called on the context object:

Sample script with descriptions:

Last updated

Was this helpful?