Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Tejas Naik (naikt)
PEGA
Principal Solutions Architect
Pegasystems Inc.
US
naikt Member since 2011 2 posts
PEGA
Posted: Jul 18, 2016
Last activity: Jul 21, 2016
Posted: 18 Jul 2016 10:41 EDT
Last activity: 21 Jul 2016 21:48 EDT
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***

To see attachments, please log in.
Data Integration

Posted: 8 years ago
Posted: 21 Jul 2016 21:06 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
Pegasystems Inc.
US

From our preliminary review, there is no such intentional enhancement for 7.2. If you would like to pursue further, please create a SR with GCS.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice