Paging Tab Configuration

The Paging tab becomes available when you configure certain HTTP Operations, such as Partitioning. For more information, refer to HTTP Operations.


This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/saas/web_services/help/saas_connectivity/web_services/paging_tab_configuration.html

This section states on the first section to see the “HTTP Operations” for which operations support paging, as shown in this screenshot:

However, if you follow the link, no such information is provided.


Additionally, this section I highlighted in the screenshot
would benefit from a link directly to the mentioned section.


It would also be beneficial for the user if there were more details provided on how the page is to be used. Currently the screen in the UI looks like this:

Which seems to show that it only allows the Limit-Offset for paging. An Explanation on this page of the purpose of the first 2 fields, how the Paging Steps are used, and how the first 2 fields relate to the Paging steps would be helpful. For instance, if the Paging is Response Header Links, does it matter what is put into the first 2 fields?

Hi Geoff! Thanks for your input. I’ve created a Jira issue to track the these fixes and I’ll update the comment thread when it’s been addressed: CONDOCS-4650

Hi Geoff, the work for CONDOCS-4650 has been completed, and the Web Services SaaS document has been updated. These same changes were also made to the VA-based Web Services document, as these issues were in there as well. Thanks for bringing this to our attention.