Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-12544

Allow for table columns to be dynamically created (based on a subcollection)

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.6
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-7867Improve details to allow subcollections in their content
      KULRICE-7887Subcollections in Details that have their own Details have 2 details links
      KULRICE-3490make assembly of permission details (e.g. in DocumentTypePermissionServiceImpl.buildDocumentTypePermissionDetails(...)) dynamic based on db config
      KULRICE-6484SubCollection label needs to allow disclosure mechanism
      KULRICE-2345Remove function-based indexes from Rice tables
      KULRICE-8858Tables - create accessible table structure
      KULRICE-2358Remove DTYPE column from Rice tables
      KULRICE-238Enhance document search to allow for dynamic drop downs and lookups dependent on external system data, for search criteria fields based on custom doc search attributes
      KULRICE-768Enhance document search to allow for dynamic drop downs and lookups dependent on external system data, for search criteria fields based on custom doc search attributes
      KULRICE-8925includeLineSelectionField breaks grid.ftl in TableCollectionSection with a subcollection
    • Epic Link:
    • Rice Team:
      Framework
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      UIF Component
    • Application Requirement:
      KC
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Need the ability to dynamically create the collection items (or table columns) from a sub-collection.

      For example, suppose we have a collection group on a List<Person>. A Person link has a List<CreditSplit>. Using a table layout, each row column should be the CreditSplit.percentage.

      Res Resp ..........
      PI 90 50
      KP 25 25

      One possibility is to create a class CollectionFieldHolder (similar to RemotesFieldHolder). This would be configured with the sub-collection property. Logic would then need to be added to CollectionLineBuilder to look for this class. If found, it will pick up the sub-collection, iterate over the entries, and create a component (based on the fieldPrototype), then insert back into the items.

      Example usage:

      <table id="PersonCreditSplits" collectionObjectClass="org.kuali.kc.Person">
      <items>
      <collectionFieldHolder propertyName="creditSplits">
      <input propertyName="percentage" label="@

      {#item.splitName}

      "/>
      </collectionFieldHolder>
      </items>
      </table>

      #item would refer to the CreditSplit the input gets generated for.

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 2 days
              2d
              Remaining:
              Remaining Estimate - 2 days
              2d
              Logged:
              Time Spent - Not Specified
              Not Specified

                Structure Helper Panel