This article covers view pagination and usability enhancements released in various Aptify releases as mentioned below.
- Aptify Release 7.2 Enhancements (View pagination performance improvements)
- Aptify Release 7.3 Enhancements (View Usability Enhancements to load views using Advanced SQL query)
Aptify Release 7.2 Enhancements
This topic covers View Pagination Enhancements released in Aptify 7.2. The details of the enhancements are covered in below sub-topics:
View pagination performance improvements
In Aptify release 7.2, the performance of the view pagination functionality has been improved for Entity list view, Dashboard part views and Form template part views. The performance enhancement is achieved by making the large datasets of the views more manageable for efficient navigation.
To enable this feature, a new checkbox labelled "Is Load All Records" has been implemented on view properties popup. The checkbox offers an option to the users to configure a specific view to load all the records in a single service request or to make a view service request with every paging event.
Below is the detail description on how to configure each type of views:
- Configuring Entity List view and Card view
- Configuring Dashboard Part View
- Configuring Form Template Part View
Configuring Entity List view and Card view
To enable the performance improvements for Entity List views and Card views, select the Is Load All Records checkbox located on view properties popup under configuration tab. By doing so, all the view records are fetched in a single server request without any further service request for rest of the pages. Clear the checkbox to revert to the default view pagination functionality, that is, for each page, service request is raised to fetch records page by page. By default, Is Load All Records is not selected.
Configuring Dashboard Part view
The ELVs present on dashboards are configured from Dashboard parts. To fetch the dashboard ELVs, records , dashboard part has two view types namely, "sql view" and "view id" as shown in the below screenshot.
Dashboard part with view type configured as sql view:
In the Input Map tab of dashboard parts, set Input Property "IsLoadAllRecords" to "Yes" to fetch all the view records in single service request. To fetch the view records page by page, set "IsLoadAllRecords" to "No".
Dashboard part with view type configured as view id:
For this configuration, the "Is Load All Records" option is available on view properties popup under the configuration tab. Select the "Is Load All Records" checkbox to fetch all the view records in single service request. Clear the checkbox to revert to the default view pagination functionality, that is, for each page, service request is raised to fetch records page by page.
Configuring Form Template part view
The List views displayed under any form template are configured from Form template parts. The Form template has two view types similar to dashboard board part namely, "sql view" and "view id" as shown in the below screenshot
Form Template part with view type configured as sql view:
In the Input Map tab of dashboard parts, set Input Property "IsLoadAllRecords" to "Yes" to fetch all the view records in single service request. To fetch the view records page by page, set "IsLoadAllRecords" to "No".
Form Template part with view type configured as view id:
For this configuration, the "Is Load All Records" option is available on view properties popup under the configuration tab. select the "Is Load All Records" checkbox to fetch all the view records in single service request. Clear the checkbox to revert to the default view pagination functionality, that is, for each page, service request is raised to fetch records page by page.
Enabling Disk cache option for better user experience
Along with the View Pagination performance improvements, the user experience has also been enhanced by making use of disk cache. The cache storage retains the page data with request URLs and serves the request from the cache by avoiding the service calls for already loaded pages. This enables fast data binding to grid as data is fetched from the disk cache at client side.
This feature is configurable by setting the flag Aptify.framework.configuration.enableViewPaginationDiskCache to true or false in "\Aptify\script\Aptify\configuration\Aptify.Framework.Configuration.External.js" file.
Aptify Release 7.3 Enhancements
This topic covers View Usability Enhancements to load views using Advanced SQL query, this enhancement is available starting Aptify 7.3.
In Aptify 7.3 release, views have been enhanced to load Advance SQL directly. This enhancement skips all the custom logic on the views and allows the user to execute Advance SQL directly.
Advance SQL is accessible via the View Properties pop-up under Advanced>SQL for ELVs, Form Template Parts and Dashboard Part views.
For Form Template Parts and Dashboard Part with view type as SQL, Advance SQL is accessible via the Input Property SQL source type as show in below image.
Below is the detail description on how to configure each type of views:
- Configuring Entity List view and Card view to load using Advanced SQL
- Configuring Dashboard Part to load view using Advanced SQL
- Configuring Form Template Part to load view using Advanced SQL
Configuring Entity List view and Card view to load using Advanced SQL
To enable the improvements for Entity List views and Card views, select the Is Load Advanced SQL checkbox located on view properties pop-up under configuration tab. By doing so, Advanced SQL for the view executes in a single server request. Clear the checkbox to revert to the default view pagination functionality. By default, Is Load Advanced SQL is not selected. 
Let us understand how Is Load All Records and Is Load Advanced SQL work together.
| Is Load All Records (7.2) | Is Load Advanced SQL (7.3) | Result |
| selected | selected | Is Load Advanced SQL override the Is Load All Records |
| selected | not selected | Is Load All Records will work. |
| not selected | selected | Is Load Advanced SQL will work. |
Configuring Dashboard Part to load view using Advanced SQL
The ELVs present on dashboards are configured from dashboard parts. To fetch the dashboard ELV, records, dashboard part has two view types namely, "sql view" and "view id" as shown in the below screenshot.
Dashboard part with view type configured as sql view:
In the Input Map tab of dashboard parts, set Input Property "IsLoadAdvancedquery" to "Yes" to execute the Advanced SQL query in a single service request and display it in the grid. To run the default behavior, set "IsLoadAdvancedquery" to "No".
Dashboard part with view type configured as view id:
For this configuration, the "Is Load Advanced SQL" option is available on the view properties pop-up under the configuration tab. Select the "Is Load All Records" checkbox to execute view Advanced SQL query in a single service request. Clear the checkbox to revert to the default view pagination functionality.
Configuring Form Template part to load view using Advanced SQL
The List views displayed under any form template are configured from Form template parts. The Form template has two view types similar to dashboard board part namely, "sql view" and "view id" as shown in the below screenshot.
Form Template part with view type configured as sql view:
In the Input Map tab of dashboard parts, set Input Property "IsLoadAdvancedquery" to "Yes" to execute the Advanced SQL query in a single service request and display it in the grid. To run the default behavior, set "IsLoadAdvancedquery" to "No".
Form Template part with view type configured as view id:
For this configuration, the "Is Load Advanced SQL" option is available on view properties popup under the configuration tab. Select the "Is Load All Records" checkbox to execute the Advanced SQL query in a single service request. Clear the checkbox to revert to the default view pagination functionality.
Comments
Please sign in to leave a comment.