Thank you for being a valued client of CM First Group. If you have any technical issues or concerns, please open a ticket on, email CM First technical support at or call us on our 24/7 customer hotline at +1 (512) 623-7586.


Data Fetching Process

This section describes the fetching process that WebClient implements to retrieve database records.

At run time, the blockfetch processing for WebClient apps is identical to other CA Plex Client Server (C/S) implementations where the client calls the existing C/S blockfetch programs to retrieve the data. WebClient uses Dojo JavaScript controls to render the grid information on the browser.

back to top

WebClient Comparison with Client/Server Fetching Process

This section describes how the WebClient fetching process differs from a typical Client/Server application.

WebClient only supports the default CA Plex page size of 64 records, and does not support other page sizes. This reason is to implement smooth scrolling on grids, as Dojo JavaScript smooth scrolling requires a predetermined/fixes page size. The 64 record size was chosen because it is the default size, and usually represents good performance across all back end platforms.

Additionally, in order to implement the smooth scrolling feature of the WebClient grids, after the page is loaded and displayed there is an extra blockfetch call to retrieve additional data so that the user scrolling through the page can do it smoothly without the need to stop to get additional data.

back to top

Grid Fetching Performance Recommendations

Since page sizes other that 64 are not supported, the WebClient developer may need to use different techniques to achieve optimal performance.

There are 3 possible approaches to improve BlockFetch performance:

  1. Improve the fetching process. On many occasions the implementation of non-standard page sizes is done to improve performance of inefficient fetching processes that perform row-by-row calculation and/or processing. Such inefficient processes can generally be improved by creating custom SQL queries that execute on the server and increase the overall process performance.
  2. Modify the C/S application’s fetch process to implement the 64-record blockfetch/page size.
  3. Create a layer for the fetching process based on the C/S one that implements the 64-record blockfetch/page size

back to top

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk