We have configured a REST connection and Pega created a DataPage. Assume, we will be passing the user as parameter in the endpoint url and service returns the user details like employee id, dob and other basic details. End User has to retrieve so many user details(assume 100) while processing a single case. If we use the datapage(thread level - created by Pega when we configured connect-REST), so many datapages will be created in that thread level. If no. of end users are 10, then total number of pages created is 1000. Is it good to proceed like this or Using a user page and emptying that page before invoking a new connect-REST call. Therefore, for each user can have one user page at runtime. Correct me, If I go wrong anywhere.
If user details are same and won't change certain period of time, you can use parameteraised data page and scope is node. This will minimize the number of pages created in clipboard and save the memory.
Posted: 5 years ago
Posted: 23 Nov 2017 1:10 EST
Raviteja Chatakondu (Raviteja_CH)
Principal Technical Support Engineer
If the data is specific to the user; change the scope to 'requestor'.
The user parameter can be sourced from pxRequestor.pxUserIdentifier; consider also guarding against this page firing against batch requestors by sourcing the data page from the data transform 'empty' conditionally on the when rule inBatchRequestor.