Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-5599

Multi-Value Lookups: Implement Select/Deselect All Pages

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.0-m3, 2.3
    • Component/s: Development, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • 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

      Currently only the select/deselect page buttons work on multi-value lookups. The select/unselect all pages buttons need to be implemented. These buttons need to select/unselect all records within the lookup results. Since these might not all be displayed currently in the view, a server request needs to be made. Here is one proposal:

      1) Implement the select/deselect all pages buttons to make server side calls to invoke selectAllLookupResults and deselectAllLookupResults on the LookupController. The buttons should only refresh the lookup results collection group.
      2) Currently there is a property on the LookupForm named selectedCollectionLines that holds the keys for all selected lines by default. Note also there could be a property on the lookup result data object that holds the selected status. This is configured on the collectionLookup for the respective CollectionGroup. If the latter is configured, then we simply need to iterate over the results and set this property to true/false. Else, use the generic route we need to populate selectedCollectionLines with all the return keys of the collection.

      Currently this is being set on the select control in LookupableImpl#setMultiValueLookupSelect. We could create a property on LookupForm named 'allCollectionLineKeys' and each time this method is called add the line key to this list. Then in the controller methods pull all keys from this and add to selectedCollectionLines (for selected, unselect just removes all entries).

      We possibly might want to move all this up to UifFormBase, if we want to support the buttons for non-lookup results, which currently we have the ability to make other results selectable so probably would be a good idea.

        Attachments

          Issue Links

            Activity

            Hide
            ewestfal Eric Westfall added a comment -

            Bulk update of incomplete 2.0.0-b2 issues to just a 2.0 fix version.

            Show
            ewestfal Eric Westfall added a comment - Bulk update of incomplete 2.0.0-b2 issues to just a 2.0 fix version.
            Hide
            jkneal Jerry Neal (Inactive) added a comment -

            Note this will need UX design work. Previous discussion about using a dropdown checkbox in the select header instead of the buttons. But needs to be revisted and mocked out by Tom or William.

            Show
            jkneal Jerry Neal (Inactive) added a comment - Note this will need UX design work. Previous discussion about using a dropdown checkbox in the select header instead of the buttons. But needs to be revisted and mocked out by Tom or William.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: