Pagination - Memory threshold issue.

Hi sai charan,
lets take an simple example
rule!average() has three rule inputs a,b,c of type int. The average funticion gets these inputs from other rule or interface.
now the average() rule defination goes like

sum(ri!a,ri!b,ri!c)/3

I have an interface in that I will call the average rule by passing the inputs like below
average(a:10,b:20:30)
now ri!a holds 10 and ri!b holds 20 and ri!c holds 30,with these values, the average() call sum function with out name value pair.
The same is applicable to your rule
rule!WFT_getRequestDetailsBySearchParams(ri!process,ri!subprocess,ri!action,ri!requestor,ri!company,ri!reference,ri!sapRefNo,if(isnull(ri!fromDate),todatetime(date(2010,10,10)),ri!fromDate),if(isnull(ri!toDate),todatetime((today())),ri!toDate+intervalds(23,59,59)),ri!monetaryValue,ri!priority,ri!wftRequestID,ri!salesOffice,ri!requestStatus,ri!pageInfo)))

assume this is a sum() in the above example where you are getting the pagingInfo from some where these rule inputs are defined.

next to your question.
How does pageInfo decrease the load on Appian?
please go through the below sail receipe.
forum.appian.com/.../recipe_display_array_of_data_in_a_grid.html

in the above receipe. local!data contains hard coded data which has 6 rows, when the form loaded intially, the parameter of with, i.e. local!dataSubset we get only 3 rows since the batch size is 3 in the local!pagingInfo. When user clicks on next button in the grid, next 3 records will be loaded to local!dataSubset.
In this way the pagingInfo reduces the load on Appian by dynamically querying the data.
Please let us know you still need elaborate example.

Hi sai charan,
lets take an simple example
rule!average() has three rule inputs a,b,c of type int. The average funticion gets these inputs from other rule or interface.
now the average() rule defination goes like

sum(ri!a,ri!b,ri!c)/3

I have an interface in that I will call the average rule by passing the inputs like below
average(a:10,b:20:30)
now ri!a holds 10 and ri!b holds 20 and ri!c holds 30,with these values, the average() call sum function with out name value pair.
The same is applicable to your rule
rule!WFT_getRequestDetailsBySearchParams(ri!process,ri!subprocess,ri!action,ri!requestor,ri!company,ri!reference,ri!sapRefNo,if(isnull(ri!fromDate),todatetime(date(2010,10,10)),ri!fromDate),if(isnull(ri!toDate),todatetime((today())),ri!toDate+intervalds(23,59,59)),ri!monetaryValue,ri!priority,ri!wftRequestID,ri!salesOffice,ri!requestStatus,ri!pageInfo)))

assume this is a sum() in the above example where you are getting the pagingInfo from some where these rule inputs are defined.

next to your question.
How does pageInfo decrease the load on Appian?
please go through the below sail receipe.
forum.appian.com/.../recipe_display_array_of_data_in_a_grid.html

in the above receipe. local!data contains hard coded data which has 6 rows, when the form loaded intially, the parameter of with, i.e. local!dataSubset we get only 3 rows since the batch size is 3 in the local!pagingInfo. When user clicks on next button in the grid, next 3 records will be loaded to local!dataSubset.
In this way the pagingInfo reduces the load on Appian by dynamically querying the data.
Please let us know you still need elaborate example.