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 Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3
    • Fix Version/s: Backlog
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-2319Separate API calls that can update KIM data into separate interfaces
      KULRICE-12714Create separate example for KULRICE-10432
      KULRICE-2763Extract web java classes and resources into a separate maven module
      KULRICE-4971DataDictionaryIndex currently indexes based on "simple" class name which can result in silent conflicts in DD classes
      KULRICE-12134Add line highlighting incorrect when using separate add line functionality
      KULRICE-8099collections items need to be separated from the subcollection group
      KULRICE-6709Configuring separate add line fields for a collection causes and exception when attempting to add a line
      KULRICE-1623no longer possible to generate separate source and javadoc in the module target dirs for rice
      KULRICE-7938Data for Creating a separate permission for accessing the new super user tab
      KULRICE-1883Create a custom maintainable impl to break out entity attributes into separate sections for each namespace
    • 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.

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:

              Structure Helper Panel