Implementing Pagination

Implementing Pagination

 

Description

Pagination is the process of dividing web content and displaying it on separate pages. Verivo supports the use of pagination in its mobile app. In order to enable pagination in Verivo, the Verivo app will require additional settings for proper configuration.

You first must develop your web service so it can return the following information:

  • The page number of the current recordset
  • The page number of the previous recordset (should return null if there are no previous pages)
  • The page number of the next recordset (should return null if there are no additional pages)

Each of these page numbers should be returned in their own individual columns. For example:

Column 1 – PreviousPage (null if no previous pages)

Column 2 – CurrentPage

Column 3 – NextPage (null if no additional pages)

 

**Note: When returning the first page of results, the web service will need to be able to receive two plaintext fields, and have the logic to return the first page of the recordset. This is the behavior of the client, and should be expected by the web service.

 

Once the web service configured correctly, you can begin mapping the web service method to an entity.

 

The next/previous page number parameters should be mapped for both upload and download since they will be accepting the next or previous page number as requested from the device.

 

Narrow Selection clauses will be added to the List screens with macros which will populate with the requested actions – Next Page or Previous Page:

 

[SERVER] | [PreviousPage] = #PrevID#**

[SERVER] | [NextPage]       = #NextID#**

 

**Since there will be multiple narrow selections on the screen, the client will send the value for the Page Requested (either NextPage or PreviousPage). The client will also send the plain text of the macro that was not used by the requested page. The web service should contain logic to ignore the plain text for the page that was not requested.

 

 

Example:

  1. Starting at Page 1 of the Recordset.
  2. User Selects NextPage.
  3. Client Sends up 2 in place of the #NextID#.
  4. Client will also send the plaintext  ‘PrevID’ for #PrevID# (the server must ignore this)

 

 

The Menu for the List screen should include two separate options and mapped to the following macros:

Option 1:          -           Next Page                     -           Next

Option 2:          -           Previous Page              -           Previous

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk