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

Need the ability to configure results limits differently for different lookups

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-b1, 2.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-5804Ability to configure results limits differently for different lookups needs to be added to KRAD - it was contributed for KNS in KULRICE-5686
      KULRICE-7006Provide configuration on Collection Group to limit displayed records
      KULRICE-3283Allow for System Parameters to be set differently for different client applications
      KULRICE-8664Update KENConfigurer to have the ability to specify a different datasource
      KULRICE-13865Support different modes of operation in the Rice testing framework
      KULRICE-7066Issue when two quickfinders on same view have different lookup configuration
      KULRICE-8521Description Column in Lookup Results set has different font
      KULRICE-114User Login Differences need worked out.
      KULRICE-3802Document Configuration View limits permission and responsibility lookups
      KULRICE-322need ability to specify a (configurable) global limit on max file size for uploads
    • Application Requirement:
      KFS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      IU has developed RICE code we'd like to contribute to RICE 2.0 to resolve this.

      On some KFS lookups, such as those for global documents and some Capital Asset Builder searches, we need to be able to separately configure results limits. According to comments on KFSMI-5654 a RICE change is required to implement this in KFS.

      Here's snipppet from the IU JIRA (EN-2099) about the change: The lookupDefinition now has two optional properties, resultSetLimit and multipleValuesResultSetLimit. A negative number for the value in these properties will be treated as unlimited and all rows will be returned for that type of lookup.

        Issue Links

          Activity

          Hide
          James Smith added a comment -

          Added Heather as a watcher.

          Show
          James Smith added a comment - Added Heather as a watcher.
          Hide
          Shannon Hess added a comment -

          The lookupDefinition now has two optional properties, resultSetLimit and multipleValuesResultSetLimit. A negative number for the value in these properties will be treated as unlimited and all rows will be returned for that type of lookup.

          Here is an example bean that has the resultSetLimit set to 7 and the multipleValuesResultSetLimit set to -1.

          <bean id="RuleTemplate-lookupDefinition-parentBean" abstract="true" parent="LookupDefinition">

          <property name="defaultSort">
          <bean parent="SortDefinition">
          </bean>
          </property>
          <property name="lookupFields">
          <list>
          <bean parent="FieldDefinition" p:attributeName="name" p:forceLookup="true"/>
          <bean parent="FieldDefinition" p:attributeName="ruleTemplateId" p:forceLookup="true"/>
          <bean parent="FieldDefinition" p:attributeName="description"/>
          </list>
          </property>
          <property name="resultFields">
          <list>
          <bean parent="FieldDefinition" p:attributeName="ruleTemplateId"/>
          <bean parent="FieldDefinition" p:attributeName="name"/>
          </list>
          </property>
          <property name="resultSetLimit" value="7"/>
          <property name="multipleValuesResultSetLimit" value="-1"/>
          <property name="title" value="Rule Template Lookup"/>
          </bean>

          Show
          Shannon Hess added a comment - The lookupDefinition now has two optional properties, resultSetLimit and multipleValuesResultSetLimit. A negative number for the value in these properties will be treated as unlimited and all rows will be returned for that type of lookup. Here is an example bean that has the resultSetLimit set to 7 and the multipleValuesResultSetLimit set to -1. <bean id="RuleTemplate-lookupDefinition-parentBean" abstract="true" parent="LookupDefinition"> <property name="defaultSort"> <bean parent="SortDefinition"> </bean> </property> <property name="lookupFields"> <list> <bean parent="FieldDefinition" p:attributeName="name" p:forceLookup="true"/> <bean parent="FieldDefinition" p:attributeName="ruleTemplateId" p:forceLookup="true"/> <bean parent="FieldDefinition" p:attributeName="description"/> </list> </property> <property name="resultFields"> <list> <bean parent="FieldDefinition" p:attributeName="ruleTemplateId"/> <bean parent="FieldDefinition" p:attributeName="name"/> </list> </property> <property name="resultSetLimit" value="7"/> <property name="multipleValuesResultSetLimit" value="-1"/> <property name="title" value="Rule Template Lookup"/> </bean>
          Hide
          Rice-CI User (Inactive) added a comment -

          Integrated in rice-trunk-nightly #229 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/229/)
          KULRICE-5686 : Added the ability to configure results limits differently for multiple value lookups

          Show
          Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #229 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/229/ ) KULRICE-5686 : Added the ability to configure results limits differently for multiple value lookups
          Hide
          James Smith added a comment -

          Thank you greatly, Shannon!

          Show
          James Smith added a comment - Thank you greatly, Shannon!

            People

            • Assignee:
              Shannon Hess
              Reporter:
              Damon Dorsey
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel