Error Message - 405
Use the Error Message screen to display backend-enforced restriction messages. This modal appears when the app receives a 405 HTTP status code, typically due to permission rules or entitlement conditions set by the insurer or the app's backend.

This screen includes:
- A backend-provided message explaining the action restriction.
- An OK button to dismiss the modal.
- Conditional display based on status code 405.
- A read-only interface with no input fields.
- A modal layout that overlays the current screen.
Workflow
- The app receives a 405 status code from the backend.
- The Error Message modal opens automatically.
- The modal displays a descriptive message, optionally including contact guidance.
- The user selects OK to acknowledge the message.
- The modal closes and the app returns to the previous screen.
Validations
- The modal appears only in response to a 405 status code.
- Input fields are not present.
- The message content and formatting are rendered directly from backend logic.
Actions
- Cancels the blocked operation based on backend policy.
- Displays the modal with the server-defined message.
- Allows the user to dismiss the message by selecting OK.
- Logs the event if session logging is active.
- Maintains the session state and returns to the prior screen after dismissal.
SDK and API References
- SDK Reference
- API Reference
GET
/error-message
This SDK endpoint displays the error modal when a request returns a 405 (Method Not Allowed) response. The message provides details from the backend regarding the restriction and offers a single OK action to close the modal.
Displays an error modal when the server returns a 405 Method Not Allowed response. The modal shows backend details about the restriction and includes a single OK button to dismiss the message.
UI Element Types
Level | Reference | Type | Value | Placement |
---|---|---|---|---|
1 | error-message | Regular | The operation cannot be completed, policy not found. For more details, please contact 0 | |
1 | ok | Button | Ok |
API details planned.