Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
4 subscribers
Views
2250 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Anyone have a working example of the paging grid in a test application for versi
dsmithgxp
Certified Associate Developer
over 11 years ago
Anyone have a working example of the paging grid in a test application for version 6.6.1?...
OriginalPostID-52588
OriginalPostID-52588
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 11 years ago
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
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 11 years ago
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
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data