Anyone have a working example of the paging grid in a test application for versi

After testing the model, when you review its implementation you will realize that I used two different approaches:

1. The first form invokes the query rule directly in the paging grid
----> This gives you an advantage: The most recent data is always displayed in the paging grid as the query rule is invoked EVERY time the task is viewed
---->Caviat: Performance wise, this is not good especially if your data is relatively static (meaning doesn't change every few minutes)

2. The second task used a node input or acp to store the result of the query rule
----> Performance wise this is better as you hit the query rule/database only once (unless you enable the "Refresh default values every time this form is viewed" option)
---->Caviat: If the data you want to display changes really frequently and you consider it can chance before the user completes the task, he/she won't get any new values that were added after this task was instantiated

After testing the model, when you review its implementation you will realize that I used two different approaches:

1. The first form invokes the query rule directly in the paging grid
----> This gives you an advantage: The most recent data is always displayed in the paging grid as the query rule is invoked EVERY time the task is viewed
---->Caviat: Performance wise, this is not good especially if your data is relatively static (meaning doesn't change every few minutes)

2. The second task used a node input or acp to store the result of the query rule
----> Performance wise this is better as you hit the query rule/database only once (unless you enable the "Refresh default values every time this form is viewed" option)
---->Caviat: If the data you want to display changes really frequently and you consider it can chance before the user completes the task, he/she won't get any new values that were added after this task was instantiated