The utiladoPushPageToken operation causes the process to push a page token for rows@next without pushing a row in the result set. This is useful in some complex scenarios, such as paging the outer call while only having the nested inner call push rows.

The following list highlights examples of defining the desired page token, which can be retrieved from _input.rows@next in the next iteration:

• Push a next page URL to rows@next:
  

  <api:set item="page" attr="pagetoken" value="[out1._next]" />
  <api:call op="utiladoPushPageToken" input="page" />

• Push a paging token or cursor to rows@next:
  

  <api:set item="page" attr="pagetoken" value="[out1.cursor]" />
  <api:call op="utiladoPushPageToken" input="page" />

• Push an incremented page number to rows@next:
  

  <api:set item="page" attr="pagetoken" value="[temp.currentpage | add(1)]" />
  <api:call op="utiladoPushPageToken" input="page" />

• Push an incremented offset to rows@next:
  

  <api:set item="page" attr="pagetoken" value="[temp.offset | add([temp.pagesize])]" />
  <api:call op="utiladoPushPageToken" input="page" />