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

Connect REST only allows one resource parameter

SA-10701

Summary



You notice that if you have more than one resource parameter in the connection string, test connectivity operation for a Connect REST rule fails at the "Create an an HTTP Request object for the remote resource" step.

The original URL is parsed from Original_Resource_URL which in the below example has two parameters (V1 and ClaimNbr):
https://<company>/DataServices/{V1}/claims/{ClaimNbr}


to Service_URL_Tested
https://<company>/DataServices/V1}/claims/{ClaimNbr

Note that only the first and last braces are removed, not the others.


Error Messages



Create a HTTP Request object for the remote resource: Fail

Steps to Reproduce



1. Set Resource Path URL with two Resource Parameters:
https://<company>/DataServices/{V1}/claims/{ClaimNbr}
2. Run Test Connectivity. Notice failure at the creating request object step, also notice the test URL still has braces.

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. Multiple parameters are not parsed correctly.

Resolution



This issue is resolved through the following Local-change:

In Rule-Connect-REST.pyTestConnectivity activity step-4, replace the regular expression, 

\\{([^\\{]|[^\\}])+\\}

with

\\{([^}]+)\\}

This issue is also scheduled to be resolved in Pega 7.1.9.

Published June 17, 2015 - 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