Open mahalakshme opened 4 months ago
If no forms have been filled, we can allow the change.
@petmongrels in cannot change the type, we should provide the name of the form element with group name - if the error message is going to be near the place where change has happened, pin-pointing might not be needed. AC is to mention it nearby and hence didn't mention in the message.
I understand the message is different from AC. But applies.
Fixed form validation server side error messages to include more information of the offending elements. Kept webapp error message as-is.
Reference video :
Issue:
During testing or when self-service organisations change the form element configuration(Single to Multi-select, repeatable to non-repeatable) of question type(Coded or QuestionGroup) without knowledge, the app breaks.
Analysis:
Should not allow to change them since anyways 'app designers' can always create new form elements and migrate the data to it.
AC:
Example mockup for showing error message:
Out of scope:
Introducing new data types that will support switching between types.
Analysis notes:
Suggestion: