Can I change the admin to use pagination instead of infinite scrolling

There are times that pagination is preferred in the Broadleaf Admin over infinite scrolling.  This can be accomplished with come configuration changes.

First, enable the paging feature with the following property

admin.fetch.enable.large.result.paging=true

You can then configure what entities you want to use the pagination feature. For example, using the configuration below , all entity list grids other than static assets and structured content would use the pagination feature. Note that these changes would be in applicationContext-admin.xml or added via a JavaConfig class.

<bean id="myFetchLargeResultQualifiedEntityPatterns" class="org.springframework.beans.factory.config.ListFactoryBean">
   <property name="sourceList">
      <list>
         <bean class="com.broadleafcommerce.enterprise.workflow.admin.persistence.module.FetchLargeResultSetQualifiedEntityPattern">
            <property name="regex" value="org\.broadleafcommerce\.cms\.structure\.domain\.StructuredContentImpl"/>
         </bean>
         <bean class="com.broadleafcommerce.enterprise.workflow.admin.persistence.module.FetchLargeResultSetQualifiedEntityPattern">
            <property name="regex" value="org\.broadleafcommerce\.cms\.file\.domain\.StaticAsset"/>
         </bean>
         <bean class="com.broadleafcommerce.enterprise.workflow.admin.persistence.module.FetchLargeResultSetQualifiedEntityPattern">
            <property name="regex" value=".*"/>
            <property name="include" value="true"/>
         </bean>
      </list>
   </property>
</bean>

<bean class="org.broadleafcommerce.common.extensibility.context.merge.LateStageMergeBeanPostProcessor">
   <property name="collectionRef" value="myFetchLargeResultQualifiedEntityPatterns" />
   <property name="targetRef" value="blFetchLargeResultQualifiedEntityPatterns" />
</bean>