Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0-m9
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-843Improve wildcarding on all search screens
      KULRICE-5616PersonServiceImpl.findPeopleInternal no longer supports search wildcards (including "!", "?", and "*")
      KULRICE-7452Unable to use wildcards on custom doc search fields
      KULRICE-14020Analysis: Wildcard fields are case sensitive for permissions
      KULRICE-4843Add an "all" option for search type results
      KULRICE-3351Test changes for the flag to disable wildcards for lookup fields in JPA
      KULRICE-6802Person lookup doesn't support % wildcard
      KULRICE-13126Add enter key support to inline edit
      KULRICE-13167Person lookups not ignoring case while doing wildcard searches
      KULRICE-5365Uif Framework - Collections: Need support for read only after add
    • Rice Module:
      KNS
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Rice KNS / KRAD supports wildcard characters in lookup fields and does so in most places. But isn't working on some places, for example, see fiscal officer lookup in the KNS L&F section of the portal. Also isn't working in the 4 lookups in the financial category in the portal.

      Recommend we fix this wildcard/support bug.

      This is due to some fields being numeric, or date, which the current framework does not support.

        Issue Links

          Activity

          Hide
          Jessica Coltrin (Inactive) added a comment -

          Candace - the wildcard only works on strings, could you list the fields that it's not working on so we can determine it's an issue. Please respond with specific steps.

          Show
          Jessica Coltrin (Inactive) added a comment - Candace - the wildcard only works on strings, could you list the fields that it's not working on so we can determine it's an issue. Please respond with specific steps.
          Hide
          Candace Soderston (Inactive) added a comment -

          I would expect the wildcard to work on any field, text-string and numerics. But if all the places where I found this was "broken" are numeric fields, I'll change this from a bug to a task (future).

          To see if all the lookup fields in the financial category in the portal are numerics, I came across potentially 2 other problems. Before I log these 2 additional problems, I think it would be faster if Jerry could check these & advise first. Using these strategies I was unable to check on whether these fields are numeric:

          – I get an error message when I search on the lookup fields in the financial category in the portal (blank fields) saying "the system has encountered an error". Does search only work on text/string fields? (If yes, I'll log another JIRA task for this.)

          – When I select the inquiry icon (on a blank field) I get an inline validation message that states: "Please enter a value in the appropriate field". It doesn't tell me whether the value must be numeric. (If not broken, I'll log another JIRA task for this. Message should be specific.)

          Show
          Candace Soderston (Inactive) added a comment - I would expect the wildcard to work on any field, text-string and numerics. But if all the places where I found this was "broken" are numeric fields, I'll change this from a bug to a task (future). To see if all the lookup fields in the financial category in the portal are numerics, I came across potentially 2 other problems. Before I log these 2 additional problems, I think it would be faster if Jerry could check these & advise first. Using these strategies I was unable to check on whether these fields are numeric: – I get an error message when I search on the lookup fields in the financial category in the portal (blank fields) saying "the system has encountered an error". Does search only work on text/string fields? (If yes, I'll log another JIRA task for this.) – When I select the inquiry icon (on a blank field) I get an inline validation message that states: "Please enter a value in the appropriate field". It doesn't tell me whether the value must be numeric. (If not broken, I'll log another JIRA task for this. Message should be specific.)
          Hide
          Candace Soderston (Inactive) added a comment -

          See comments in the JIRA.

          Show
          Candace Soderston (Inactive) added a comment - See comments in the JIRA.
          Hide
          Candace Soderston (Inactive) added a comment -

          If this problem (wildcard and blank field search not working in the financial lookups in the portal and in the fiscal officer lookup in the KNS L&F forms) is related to a planned design that it work only on text fields, could we assume all fields are text strings when searching in lookups (without changing the underlying data type)?

          Show
          Candace Soderston (Inactive) added a comment - If this problem (wildcard and blank field search not working in the financial lookups in the portal and in the fiscal officer lookup in the KNS L&F forms) is related to a planned design that it work only on text fields, could we assume all fields are text strings when searching in lookups (without changing the underlying data type)?
          Hide
          Jessica Coltrin (Inactive) added a comment -

          moving all non-critical or blocker jiras from 2.0.0-b2 to 2.0.0-b3 due to the short time frame for b2 & KD taking up one of the two weeks.

          Show
          Jessica Coltrin (Inactive) added a comment - moving all non-critical or blocker jiras from 2.0.0-b2 to 2.0.0-b3 due to the short time frame for b2 & KD taking up one of the two weeks.
          Hide
          Jerry Neal (Inactive) added a comment -

          Candace,

          We need more information on this. For example, what screens and fields did not have the wildcard support, where was it different and so on.

          thanks,
          Jerry

          Show
          Jerry Neal (Inactive) added a comment - Candace, We need more information on this. For example, what screens and fields did not have the wildcard support, where was it different and so on. thanks, Jerry
          Hide
          Candace Soderston (Inactive) added a comment -

          Jerry and I discussed the locations and agreed this should be fixed. The current framework doesn't support searches using wildcards in numeric fields. It is not a bug, but an enhancement needed. We agreed to change from bug to enhancement, and recognize that it won't fit into 2.0 workload.

          Show
          Candace Soderston (Inactive) added a comment - Jerry and I discussed the locations and agreed this should be fixed. The current framework doesn't support searches using wildcards in numeric fields. It is not a bug, but an enhancement needed. We agreed to change from bug to enhancement, and recognize that it won't fit into 2.0 workload.
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Moving all New Feature and Improvement Jiras out of 2.1 since the scope for those is now locked. These items move to the 2.x-backlog.

          Show
          Jessica Coltrin (Inactive) added a comment - Moving all New Feature and Improvement Jiras out of 2.1 since the scope for those is now locked. These items move to the 2.x-backlog.

            People

            • Assignee:
              Unassigned
              Reporter:
              Candace Soderston (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel