Details

    • Type: Sub Task Sub Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 2.2.0-m1, 2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7324Add ability to specify table layout collections action column sequence
      KULRICE-4725Provide more default layout options and ability to specify custom layout
      KULRICE-6977Do POC on creating a simple table layout that renders a basic read only table
      KULRICE-12029Issue with delete functionality on Table Layout library demo
      KULRICE-8420Horizontal layout does not work within a collection item
      KULRICE-12544Allow for table columns to be dynamically created (based on a subcollection)
      KULRICE-11147Provide grid layout beans with Bootstrap table styles
      KULRICE-7417Collections - table layout sequence column is editable
      KULRICE-12815 Expressions in field labels not carried through for table headers
      KULRICE-1551Build KOM business objects
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Currently collections are a source of slow performance and memory issues. One reason for this is the field components that get built for each collection row property. This is necessary in a full featured table since each cell can be different. However, there are many cases (like lookup results) where the collection table is read only and each cell is the same (except for the value). In these cases we can provide a simpler table layout that does not build the field components for each. This will save memory and result in better performance.

      In addition, with the simpler table we can perform the table rendering in the client, reducing the size of the response.

        Issue Links

          Activity

          Hide
          Jerry Neal (Inactive) added a comment -

          Discussion with Kamal has lead to implementing datatables with an Ajax source. This will give us the best performance possible. Therefore we will create an AjaxDataTable in KRAD to support this.

          Show
          Jerry Neal (Inactive) added a comment - Discussion with Kamal has lead to implementing datatables with an Ajax source. This will give us the best performance possible. Therefore we will create an AjaxDataTable in KRAD to support this.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

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

                  Structure Helper Panel