Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3
    • Component/s: Analysis, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-9923Conversion Guide: Multi Value Lookup
      KULRICE-1195Multi value lookup tables
      KULRICE-10497Exception on multi-value lookup
      KULRICE-2679Pass lookup parameters to a multi-value lookup.
      KULRICE-10038Mock for Multi Value Lookups Controls
      KULRICE-13276NullPointer Exception in Demo Account Multi-Value Lookup
      KULRICE-12198Library Multi Value Lookup example adds rows but doesn't populate them
      KULRICE-10917Improve visual treatment of Multi Value Lookups Selection Control
      KULRICE-9592Design for select/deselect on multi-value lookup
      KULRICE-10894Add Multi Value Lookup conversion to MaintainableCollectionsDefinition
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Multi-Value Lookup
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Work on the "Multiple Value Lookup" section as described in KULRICE-8800

        Issue Links

          Activity

          Hide
          Claus Niesen added a comment -

          A significant JIRA that will come out of this gap analysis is the need to fix/implement the passing back the values from the muliltiple-value lookup. In KNS the results were stored in a table. Jerry mentioned something about having tried to pass back the keys via the URL and the issue of the limited URL length. For this we need to do a specific in depth analysis of what solution we are going to pursue. KULRICE-7734 and KULRICE-9107 are related to that.

          BTW, the Kitchen Sink sample for multiple-value lookup is on the Collections page.

          Show
          Claus Niesen added a comment - A significant JIRA that will come out of this gap analysis is the need to fix/implement the passing back the values from the muliltiple-value lookup. In KNS the results were stored in a table. Jerry mentioned something about having tried to pass back the keys via the URL and the issue of the limited URL length. For this we need to do a specific in depth analysis of what solution we are going to pursue. KULRICE-7734 and KULRICE-9107 are related to that. BTW, the Kitchen Sink sample for multiple-value lookup is on the Collections page.
          Hide
          Jessica Coltrin (Inactive) added a comment -

          On 8/7/13, at 11:49 AM, Steven Manning wrote:
          > @Jessica, yes, the MV lookup stuff is done

          Show
          Jessica Coltrin (Inactive) added a comment - On 8/7/13, at 11:49 AM, Steven Manning wrote: > @Jessica, yes, the MV lookup stuff is done

            People

            • Assignee:
              Steve Manning (Inactive)
              Reporter:
              Claus Niesen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel