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

Lookup - execute search when hitting enter while in any of the criteria text fields

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.0-m1, 2.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-11917Commas are added to search criteria of the Lookup Operators page
      KULRICE-1715When passing searchable attribute values to Document Search in the URL they are not displayed in the search criteria fields
      KULRICE-3924Doc Search ignores invalid or manually entered doctype during first search
      KULRICE-12012Parameter Lookup - Selecting a component from search results does not populate “Component” search criteria field
      KULRICE-9076Fix Criteria Masking on Lookups with encrypted fields
      KULRICE-12744Quickfinder Lookup doesn't populate criteria fields with data from calling field
      KULRICE-9022Behavior change in date fields in lookup criteria from KNS to KRAD
      KULRICE-4168Don't render text areas in lookup criteria
      KULRICE-6091Exception in document search when searching with invalid criteria
      KULRICE-10364Lookup feature to hide search criteria when displaying results, add button in footer for new search
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Lookup - execute search when hitting enter while in any of the criteria text fields. Currently any direct lookups will be triggered instead of executing search, need to change this on LookupCriteriaInputField's. Might have to ass script on the criteria fields.

        Issue Links

          Activity

          Hide
          Jerry Neal (Inactive) added a comment -

          Samuel and Claus,

          Couple of comments on this. One keyboard support is a Phase 3 item: KULRICE-8860. So I am going to link this so we can roll this solution into the general solution once it is there.

          Second I am wondering about the triggerOnEnter. Looks like you would have to set that to true on each input in order to get the enter action regardless of the field? Since this will likely be replaced by the full keyboard support, I wondering for now if we should just add some onload script to the lookup view that will make the default enter key action the search.

          thanks,
          Jerry

          Show
          Jerry Neal (Inactive) added a comment - Samuel and Claus, Couple of comments on this. One keyboard support is a Phase 3 item: KULRICE-8860 . So I am going to link this so we can roll this solution into the general solution once it is there. Second I am wondering about the triggerOnEnter. Looks like you would have to set that to true on each input in order to get the enter action regardless of the field? Since this will likely be replaced by the full keyboard support, I wondering for now if we should just add some onload script to the lookup view that will make the default enter key action the search. thanks, Jerry
          Hide
          Samuel Holtzkampf (Inactive) added a comment -

          Jerry,

          There is a triggerOnEnter flag on the LookupView that is true by default so no need to set on each input. You would only set the flag on input fields if you want to exclude certain input fields - maybe you still want the default enter behaviour on a specific control.

          We would not want to make search the default enter key action for the view as the user might have tabbed focus to another action button and it would be confusing if enter then triggers search.

          Samuel

          Show
          Samuel Holtzkampf (Inactive) added a comment - Jerry, There is a triggerOnEnter flag on the LookupView that is true by default so no need to set on each input. You would only set the flag on input fields if you want to exclude certain input fields - maybe you still want the default enter behaviour on a specific control. We would not want to make search the default enter key action for the view as the user might have tabbed focus to another action button and it would be confusing if enter then triggers search. Samuel
          Hide
          Jerry Neal (Inactive) added a comment -

          Hey Samuel,

          My concern is I think this will get replaced by the general keyboard support when it comes, and instead of having a property that everyone starts using thought we could just put in something now that masks the problem until the support is there (which should be 2.3).

          Not sure if that makes sense. We can talk more about it in one of the standups this week.

          thanks,
          Jerry

          Show
          Jerry Neal (Inactive) added a comment - Hey Samuel, My concern is I think this will get replaced by the general keyboard support when it comes, and instead of having a property that everyone starts using thought we could just put in something now that masks the problem until the support is there (which should be 2.3). Not sure if that makes sense. We can talk more about it in one of the standups this week. thanks, Jerry

            People

            • Assignee:
              Samuel Holtzkampf (Inactive)
              Reporter:
              Samuel Holtzkampf (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel