Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-9534

Contact Search record selection storage irrespective of previous / next page visits and improvement in current behavior

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed/Completed
    • Affects Version/s: 4.1.0
    • Fix Version/s: 4.2.0
    • Component/s: None
    • Labels:
      None

      Description

      1) If we do a contact search which results yielding 300 records, they'll span multiple pages. If we wanted to go through each page & select specific records to add to a group, for example, I'm only able to add them one page at a time because as soon as I proceed to the next page, the record selections from the previous page(s) are lost.

      2) This new feature will able user to traverse accross different search pages and select muliple contacts and then perform action tasks like : add to a group.

      we can remember the checkbox selection using AJAX, store the selection in table prev/next_cache table by adding "is_selected" column to pre/next_cache table and using that to identify selected contacts , and whenever user traverse accross serach pages the selection whould be maintained, by checking for the record selected through checkbox inside the table prev/next_cache .

      3) We can have a "reset selection" link on serach form , so that all selections can be reset .

      4) Also a page can be built which screens the selected records and a link to this page can appear on Tasks pages (eg Add Contact to Groups) , same can be done for CiviMail where we give the total number of contacts selected for a mailing.

        Attachments

          Activity

            People

            • Assignee:
              lcdweb Brian Shaughnessy
              Reporter:
              pratik.joshi Pratik Joshi
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 2 days, 7 hours
                1w 2d 7h