Question

1
Replies
698
Views
naikt Member since 2011 2 posts
PEGA
Posted: 4 years ago
Last activity: 4 years 2 months ago
Closed

Statefull requestor (HTTP 500 error for requestor not found)

We at Verizon wireless have opened SR (SR-A17725) some time back (Feb/March-2016) to find out if there is capability in platform (Pega 6.2 SP2 ) to be able to create requestor on the fly in case if client application mismatch the cookies by mistakes for state full conversations. Based on the response on SR, the answer was NO from engineering for PRPC 6 version. Now after upgrade to 7.2 , it seems that Pega 7.2 platform has the capability built in to create requestor on the fly for state full conversations in this scenario.

We are looking for the confirmation from engineering if this enhancement is built in Pega 7.2 and also if there is way to disable this feature/functionality.

***Edited by moderator: Lochan to remove private SR communication and contact details; removed Ask the Expert tag***

***Edited by moderator: Marissa to update category topic***

Data Integration
Moderation Team has archived post
Share this page LinkedIn