You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In very specific custom submission setups, it is possible errors shown on top of the submission sections are not displayed at all, when they should be present. In those cases, the section is also marked as valid when it shouldn't.
To Reproduce
First, set up the project with the following conditions in the backend:
In item-submission.xml, configure a submission definition containing two steps with type "submission-form" (e.g. "traditionalpageone" and "traditionalpagetwo")
Modify (or configure a different) MetadataValidation to add section-wide errors (/sections/{sectionId}). By default, this validation will only allow metadata field errors, but this bug requires section-wide errors.
Next, start a submission in the configured form and:
In one of the two "submission-form" sections, fill in any value of any of the fields
In the other section, perform an action that would result in the custom section-wide error
If the setup is correct, this should result in NO section-wide error (at the top of the section) being displayed for the relevant section.
If the other section is left empty, the error does display.
Expected behavior
The error should always display when the conditions are met, regardless of the other sections within the submission.
The text was updated successfully, but these errors were encountered:
Describe the bug
In very specific custom submission setups, it is possible errors shown on top of the submission sections are not displayed at all, when they should be present. In those cases, the section is also marked as valid when it shouldn't.
To Reproduce
First, set up the project with the following conditions in the backend:
item-submission.xml
, configure a submission definition containing two steps with type "submission-form" (e.g. "traditionalpageone" and "traditionalpagetwo")MetadataValidation
to add section-wide errors (/sections/{sectionId}
). By default, this validation will only allow metadata field errors, but this bug requires section-wide errors.Next, start a submission in the configured form and:
If the setup is correct, this should result in NO section-wide error (at the top of the section) being displayed for the relevant section.
If the other section is left empty, the error does display.
Expected behavior
The error should always display when the conditions are met, regardless of the other sections within the submission.
The text was updated successfully, but these errors were encountered: