Hello Experts, We have a WS connector that requires pagination. To do that, we used the pagination option as follow: TERMINATE_IF $response.nextpagetoken$ == NULL $endpoint.fullUrl$ = $application.baseUrl$ +“/api/x/users/v2/employees?status=inactive&nextpagetoken=”+ $response.nextpagetoken$ The …

Hi Beatriz, I don’t think the templating engine supports arbitrary java code. Is there some documentation that suggests you can use the .replace() function? That may be causing the issue if the templating engine fails on that line and never assigns $endpoint.fullUrl$.

Hello Colin, actually I didn’t find anything about this function, so it make sense that the root of the error was the replace. There is another suggested way of modifying this token? Thanks

A before operation rule seems most appropriate here. You can find the guide here .

Pagination WS: Replace character

Identity Security Cloud (ISC) ISC Discussion and Questions

Topic		Replies	Views
Webservice Connector Paging Scirpt: Handle/Escape double quotes(") ISC Discussion and Questions webservice-connector , aggregation , identity-security-cloud , identityiq	4	135	March 13, 2025
Paging step based on response attribute containing @ symbol ISC Discussion and Questions webservice-connector , aggregation , identity-security-cloud	29	984	May 28, 2024
Web Services: Paging issue ISC Discussion and Questions webservice-connector , identity-security-cloud , provisioning	2	179	February 14, 2025
Paging issue with Graph API ISC Discussion and Questions webservice-connector , aggregation , identity-security-cloud	5	121	February 20, 2026
Web Services Connector \| Pagination through queryToken of 2 context URLs ISC Discussion and Questions webservice-connector , aggregation , identity-security-cloud	8	663	October 11, 2023

Pagination WS: Replace character

Related topics