Annikenkbrathen
commented
1 week ago We need to map out different cases for presenting errors to the users an consider how to solve them. We have different types of errors. Should these have different patterns based on case/content?
for example:
- validation errors (errors in fields)
- Operation errors
- Not direct field errors, but usage errors that will break the app (binding, lack of content)
Description
The handling of errors in configuration on the "Lage page" and other places in Altinn Studio should have a consistent design and structure for how to notify that there are errors in the application.
This specifically applies to error messages that arise from changes made outside Altinn Studio or from changes made in other parts of the studio that cause these errors.
For example, should we mark the accordion in red where there are errors? Should there be an alert box, or a red border around the field that has an error (when it is not opened in edit mode) + a message?
How should we handle this consistently?
Additional Information
No response
Tasks
No response
Acceptance Criterias
No response