Pagination - Memory threshold issue.

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

OriginalPostID-254399

  Discussion posts and replies are publicly visible

Parents
  • If pageInfo is used the query returns a datasubset, then query returms same number of records that is mentioned in the "batchSize" of pagingInfo, but the totalCount if the datasubset is the total number of records that matches the search criteria.
    For exampple there are 15 records that match the search criteria, if the pagingInfo(startIndex:1, batchSize:10), then the query returns only 10
    records out of 15, but the totalCount of the datasubset will be 15. If the user clicks on the next button in the paging grid, the the startindex gets updated to 11 and gets the query gets the next 5 records. So at a time appian gets 10 records even if the total number of records matching the search criteria are more that the batchsize. Hence the load on appian gets reduced.

    Please let me know if you need more information.
Reply
  • If pageInfo is used the query returns a datasubset, then query returms same number of records that is mentioned in the "batchSize" of pagingInfo, but the totalCount if the datasubset is the total number of records that matches the search criteria.
    For exampple there are 15 records that match the search criteria, if the pagingInfo(startIndex:1, batchSize:10), then the query returns only 10
    records out of 15, but the totalCount of the datasubset will be 15. If the user clicks on the next button in the paging grid, the the startindex gets updated to 11 and gets the query gets the next 5 records. So at a time appian gets 10 records even if the total number of records matching the search criteria are more that the batchsize. Hence the load on appian gets reduced.

    Please let me know if you need more information.
Children
No Data