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

Investigate/design separating paging data retrieval into a separate class that can be configured

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3
    • Fix Version/s: Backlog
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Epic Link:
    • Rice Module:
      KRAD
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      By separating the retrieval data out from a direct call to the form, the data can be retrieved directly from a db when requested or from a cache rather than all of the data being present on the form like is required now to use these features.

      This has some issues with conflicts sorting (for table data) and the assumption that we now that all this data will be present on the form. There are also problems with where and how to hook this in correctly, that need to be designed.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              bsmith Brian Smith (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: