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

Document search by document type doesn't allow wildcards or case insensitive searches

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-4165Search on document description should be case insensitive
      KULRICE-5249Case Insensitive flag ignored in KNS
      KULRICE-85implement case-insensitive searching
      KULRICE-7171Document type field on document search seems to be case sensitive in Rice 2.0
      KULRICE-14020Analysis: Wildcard fields are case sensitive for permissions
      KULRICE-6425Notification Search link does not populate document type name for search
      KULRICE-13110lookup searches do not ignore case even though forceUppercase=true
      KULRICE-3208case sensitivity on doc search (was: Doc type is case sensitive in document search and returns an error when lower case is entered)
      KULRICE-6687Person lookup isn't case-insensitive in Rice 2.0
      KULRICE-3533Document Search - Clear out Searchable attributes when Doc Type changes and loses tab focus. Ajax stuff
    • Rice Module:
      KEW
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      In KR 1.0.3, wildcards are allowed when searching for documents by document type name. However, now in KR 2.0, the error message "No Valid Document Type Found for document type name 'eDoc.Example1.ParentDoctyp*'" is displayed on the top of the screen instead.

      Also, in KR 1.0.3, if you use the full document type name when searching, the search is case insensitive so both eDoc.Example1.ParentDoctype and EDOC.Example1.ParentDoctype would return the same number of documents. Now in KR 2.0, the error message is also thrown if the exact name is not used.

      Would it be possible to allow wildcards and make both types of searches be case insensitive?

        Issue Links

          Activity

          Hide
          Sona Sona (Inactive) added a comment -

          Created a review. Will commit after its over.

          Show
          Sona Sona (Inactive) added a comment - Created a review. Will commit after its over.

            People

            • Assignee:
              Sona Sona (Inactive)
              Reporter:
              Shannon Hess
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel