Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-9586

Need to avoid required validation checks on addLine

    Details

    • Similar issues:
      KULRICE-7532required validation fails in StackedCollectionSubSection addLine
      KULRICE-11813Update Collection Addline in Lightbox AFT to check validation tooltip
      KULRICE-7110Conditional requirement bug in a Collection's addline
      KULRICE-6666Validation causes Javascript error with an addLine containing a checkbox or radio
      KULRICE-9595Avoid running scripts on non-visible content
      KULRICE-12203Elements - Action - Validation Message needs to describe validation is “required field”
      KULRICE-12581addViaLightBox validating addLineGroup when the light box is not rendered
      KULRICE-3475for client app db imports, rice dbs project needs to be checked out under the client app dir to avoid scheduling conflicts
      KULRICE-8541Validation errors are shown when a refresh happens within a group that has a field that was progressively hidden with an error
      KULRICE-10179Setting required="true" on field with file indicator does not require upload client side
    • Epic Link:
    • Rice Module:
      KRAD
    • Application Requirement:
      KS
    • Sprint:
      2.5.0-m3 Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      In KS, we noticed that in a collection addLine, if the field is required field, the framework always performs required validation checks when the focus is changed from a required field in addLine to other, which leads to the error display on the screen. Although the error does not prevent users from saving the page, it would be better to avoid required validation checks on addLine till users explicitly click add button.

        Issue Links

          Activity

          Hide
          Jerry Neal (Inactive) added a comment -

          Bonnie,

          the other side to this though is if the user is actually adding the line wouldn't it be better to show them the error as they are filling it out, rather than clicking the add button and getting errors about the line?

          Jerry

          Show
          Jerry Neal (Inactive) added a comment - Bonnie, the other side to this though is if the user is actually adding the line wouldn't it be better to show them the error as they are filling it out, rather than clicking the add button and getting errors about the line? Jerry
          Hide
          Garey Taylor added a comment - - edited

          Added link to KS issue. Contains screenshots. https://jira.kuali.org/browse/KSENROLL-6184

          Show
          Garey Taylor added a comment - - edited Added link to KS issue. Contains screenshots. https://jira.kuali.org/browse/KSENROLL-6184
          Hide
          Christie Heitkamp (Inactive) added a comment -

          UX architect comment from KRAD prioritization sheet:
          From the screenshots in the associated jira https://jira.kuali.org/browse/KSENROLL-6184, the type of validation currently being used seems to create an ineterruption and unexpected UX. Recommendation is to use subtle inline validation while the user is completing the row. Refer to this article: http://alistapart.com/article/inline-validation-in-web-forms

          Show
          Christie Heitkamp (Inactive) added a comment - UX architect comment from KRAD prioritization sheet: From the screenshots in the associated jira https://jira.kuali.org/browse/KSENROLL-6184 , the type of validation currently being used seems to create an ineterruption and unexpected UX. Recommendation is to use subtle inline validation while the user is completing the row. Refer to this article: http://alistapart.com/article/inline-validation-in-web-forms
          Hide
          Richard Slabach added a comment -

          Great article, Christie. The reactions recorded in the section titled "After method helps users to complete forms more quickly" are particularly appropriate to the way it acts now – "It’s frustrating that you don’t get the chance to put anything in [the field] before it’s flashing red at you.”

          Show
          Richard Slabach added a comment - Great article, Christie. The reactions recorded in the section titled "After method helps users to complete forms more quickly" are particularly appropriate to the way it acts now – "It’s frustrating that you don’t get the chance to put anything in [the field] before it’s flashing red at you.”
          Hide
          Jerry Neal (Inactive) added a comment - - edited

          It actually does give you a chance to fill out the field before. No validation messages are shown until you have entered the field and left. In addition, the errors shown follow the inline validation recommendations. Just the field is highlighted, only when you hover over to you see the tooltips. Also there is an option in the framework to show the message with the field instead of the tooltip.

          Also, note in the related Jira the screenshots are misleading. You don't get errors like this on cilent side validation, only when the page is submitted.

          This jira is just to skip the messages on the add line, because users might be tabbing through without the intention of adding the line. We should keep the scope to that, and address other error issues with different Jiras. Although our current error handling has been vetted multiple times and was outlined by a consulting group.

          Show
          Jerry Neal (Inactive) added a comment - - edited It actually does give you a chance to fill out the field before. No validation messages are shown until you have entered the field and left. In addition, the errors shown follow the inline validation recommendations. Just the field is highlighted, only when you hover over to you see the tooltips. Also there is an option in the framework to show the message with the field instead of the tooltip. Also, note in the related Jira the screenshots are misleading. You don't get errors like this on cilent side validation, only when the page is submitted. This jira is just to skip the messages on the add line, because users might be tabbing through without the intention of adding the line. We should keep the scope to that, and address other error issues with different Jiras. Although our current error handling has been vetted multiple times and was outlined by a consulting group.
          Hide
          Brian Smith (Inactive) added a comment -

          Good article, glad to know the framework is providing the exact thing described (ie, after validation on first pass)

          Show
          Brian Smith (Inactive) added a comment - Good article, glad to know the framework is providing the exact thing described (ie, after validation on first pass)
          Hide
          Tadas Paegle (Inactive) added a comment -

          Validation has been updated. The validation of addLine fields is skipped until the add button is clicked or if the user enters a value in the field.

          Show
          Tadas Paegle (Inactive) added a comment - Validation has been updated. The validation of addLine fields is skipped until the add button is clicked or if the user enters a value in the field.

            People

            • Assignee:
              Tadas Paegle (Inactive)
              Reporter:
              Bonnie Huang (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 hours
                4h
                Remaining:
                Time Spent - 3 hours Remaining Estimate - 1 hour
                1h
                Logged:
                Time Spent - 3 hours Remaining Estimate - 1 hour
                3h

                  Agile

                    Structure Helper Panel