Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0-m1, 2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-5156Validate client side flag on view not being looked at for client side validation
      KULRICE-4708Support for client side field validation
      KULRICE-7026Alter behavior of client side validation
      KULRICE-9032cancelling a document with client side validation disabled
      KULRICE-12622KRAD Demo: Client side validation for search criteria
      KULRICE-7339Adhoc routing for completion - client side validation
      KULRICE-14261Enable client side validation in dialogs (backport KULRICE-12235)
      KULRICE-12301View flag for disabling growls should disable client side growls as well
      KULRICE-11729Selectively disable client side validation on KRAD collections
      KULRICE-13010Investigate client side collection rendering
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      The following issues were discovered with client side validation:

      1) Validation when '-' is not allowed (or invalid date format) is inconsistent. Likely issues with validation triggering. See related issue KSENROLL-557

      2) Validation pop up not appearing for add line. See related issue KSENROLL-574

      These issues can be seen at http://dev2.ks.kuali.org/portal.do

        Issue Links

          Activity

          Hide
          Miki Harmath (Inactive) added a comment -

          KSENROLL-605 > TimePatternConstraint
          KSENROLL-557 > BasicDatePatternConstraint

          Show
          Miki Harmath (Inactive) added a comment - KSENROLL-605 > TimePatternConstraint KSENROLL-557 > BasicDatePatternConstraint
          Hide
          Jerry Neal (Inactive) added a comment -

          Comment from UserGroup:

          If you enter an invalid date, you get the following message:
          "Must be a date in the following format(s): MM/dd/yy, MM/dd/yyyy, MM- dd-yy, MM-dd-yyyy"
          But the JQuery textbox does not allow you to type in hyphens so the last two formats are never allowed.
          Should the other validation patterns should be removed?

          Show
          Jerry Neal (Inactive) added a comment - Comment from UserGroup: If you enter an invalid date, you get the following message: "Must be a date in the following format(s): MM/dd/yy, MM/dd/yyyy, MM- dd-yy, MM-dd-yyyy" But the JQuery textbox does not allow you to type in hyphens so the last two formats are never allowed. Should the other validation patterns should be removed?
          Hide
          Daniel Seibert (Inactive) added a comment -

          Fixed validation issues with Datepicker widget.
          Other issues can be resolved with setting datepicker options.

          There are also choices of validation techniques: using datepicker widget constraints, and/or krad constraints.

          Documentation is needed to better explain the options to users.
          Several examples have been added to the kitchen sink to demonstrate different options.

          Summary of specific related issues:
          1- You can NOT enter a dash in the Date fields when using a datepicker (KSENROLL-557 and others)
          The "constrainInput" option on the jquery datepicker widget controls allowable keys as they are entered.
          When set to true (the default), it restricts input to characters allowed by the "dateFormat" option of the datepicker (default:"mm/dd/yyyy"). So a default datepicker will expect a "mm/dd/yyyy" format and only allow "/" as a delimiter. To allow "/" or "-", set constrainInput to false.

          2. Required validation message not clearing after date is selected - fixed.

          3. BasicDatePatternConstraint not behaving as expected. - fixed.

          Show
          Daniel Seibert (Inactive) added a comment - Fixed validation issues with Datepicker widget. Other issues can be resolved with setting datepicker options. There are also choices of validation techniques: using datepicker widget constraints, and/or krad constraints. Documentation is needed to better explain the options to users. Several examples have been added to the kitchen sink to demonstrate different options. Summary of specific related issues: 1- You can NOT enter a dash in the Date fields when using a datepicker ( KSENROLL-557 and others) The "constrainInput" option on the jquery datepicker widget controls allowable keys as they are entered. When set to true (the default), it restricts input to characters allowed by the "dateFormat" option of the datepicker (default:"mm/dd/yyyy"). So a default datepicker will expect a "mm/dd/yyyy" format and only allow "/" as a delimiter. To allow "/" or "-", set constrainInput to false. 2. Required validation message not clearing after date is selected - fixed. 3. BasicDatePatternConstraint not behaving as expected. - fixed.

            People

            • Assignee:
              Daniel Seibert (Inactive)
              Reporter:
              Jerry Neal (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel