Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Mappin in pyInvokeRESTConnector takes too long



User created a Activity which calls Connect-Rest in which they are calling an External Service which returns few thousand Results.The content passed between these two system is JSON with 2000 fields.

Application throws a request to External Service and receives a response without any issue, however when PRPC starts mapping the received data to the clipboard in the activity called pyInvokeRESTConnector, it takes about 60 seconds to map all the fields.

As this is taking huge time to Map, User is expecting less time than above mentioned.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create an activity which calls connect-REST
  2. Call an external service which will return few thousand results

Root Cause

Users' Connect-REST responses are extremely slow and system hangs when the JSON response is large. 
Modified if condition which is used for lookup property qualifier property names. 



Published November 9, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us