Pagination - Memory threshold issue.

saicharanb over 7 years ago

We have a query as below
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)))

In the above query how is "ri!pageInfo" working? I could not find any parameters like batch size set for pageInfo. Please help how does it work for the above query.

How does pageInfo decrease the load on Appian? I have referred the below link, but did not understand much, Please help me on this.
forum.appian.com/.../System_Functions.html

Discussion posts and replies are publicly visible

Parents

0 sikhivahans over 7 years ago

@saicharanb Two questions for you:
1. When you set the number of records as 50, did you also use data!pagingInfo while invoking the query rule?
2. Are you experiencing any error visually?
3. I did suggest an alternative already of getting the data in the process and then giving it to interface. Have you had a chance to go through and implement it? This obviously resolves the issue but I would like you to implement the total number of records and data!pagingInfo in the query rule properly and then move to the approach as suggested by me.

I can give a example of what I did: I do have a query rule which gets all the records from a data store entity and this fails because there was lots of data in the table. What I did was, I used the same query rule in the paging grid of the Forms Designer. I have configured the total number of rows as 10 and passed the data!pagingInfo to the query rule. Neither I saw any threshold errors nor a problem with the update in paging info.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 sikhivahans over 7 years ago

@saicharanb Two questions for you:
1. When you set the number of records as 50, did you also use data!pagingInfo while invoking the query rule?
2. Are you experiencing any error visually?
3. I did suggest an alternative already of getting the data in the process and then giving it to interface. Have you had a chance to go through and implement it? This obviously resolves the issue but I would like you to implement the total number of records and data!pagingInfo in the query rule properly and then move to the approach as suggested by me.

I can give a example of what I did: I do have a query rule which gets all the records from a data store entity and this fails because there was lots of data in the table. What I did was, I used the same query rule in the paging grid of the Forms Designer. I have configured the total number of rows as 10 and passed the data!pagingInfo to the query rule. Neither I saw any threshold errors nor a problem with the update in paging info.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data