Question
TD Bank Group
CA
Last activity: 16 Oct 2018 12:03 EDT
Connect-REST pyResourcePath - Global Resource Settings
We are looking at moving from SOAP to REST for some of the services that we use and would like to continue to leverage the Global Resource Settings syntax for the endpoints.
In the documentation (https://community.pega.com/sites/default/files/help_v73/procomhelpmain.htm) it states that only 2 properties support GRS for a Connect-REST rule (pyResponseTimeout,pyAuthenticationProfile). What about pyResourcePath?
Can we also leverage it similarly to what we have with SOAP (pyEndpointURL)?
We use PRPC 7.2.2.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
US
Pegasystems Inc.
IN
Hi Patrick,
As mentioned in the document it will only support pyResponseTimeout and pyAuthenticationProfile.
Regards,
Vikash
TD Bank Group
CA
Hi Vikash,
I am really surprised by your answer.
How are we supposed to manage the change in endpoint by environment for Connector-REST rules?
Is there a plan on the roadmap to add pyResourcePath to the GRS support?
Thanks,
Pegasystems Inc.
US
You do not need to use Global Resource Settings in the resource path. The parts of the resource path can be set to be sourced from properties. You should see a grid underneath your resource path control. That is where you map the sources of the "wildcards" in your resource path.
Alternatively, most of the records that use REST Connectors have an "endpoint" field that you can use to specify the URL for the run-time connections. This will override the pyResourcePath property.
TD Bank Group
CA
In the resource parameters, can you map from a DataPage using the "Clipboard" Map from?
Doing it in the rule (activity) that leverages the connector would mean potentially maintaining it in multiple places instead of doing it on the connector rule itself.
TD Bank Group
CA
Anybody?
Accepted Solution
Pegasystems Inc.
US
I believe that in Pega 7.2.2 you are able to use Global Resource Settings for pyResourcePath, despite this property not being officially documented. it is just less "dynamic" than using parameters for the parts of the URL that are truly dynamic.
As far as I know, the resource parameters mappings do support Global Resource Settings when you set the "Map from" to Clipboard.
Of course, you should do some local testing, no matter which option you choose to go with.
Pegasystems Inc.
US
Note by the way that although Jeff is correct that support for GRS with pyResourcePath is *not* documented on the main help page that lists all fields in Pega supported by GRS ( /prhelp/procomhelpmain.htm#concepts/concepts2/globalresourcesettingfields.htm#Fields_that_support_the_Global_Resource_Settings_syntax ), the fact that GRS is supported for pyResourcePath *is* nonetheless explicitly documented on the context-sensitive help page for Connect-REST, at least for versions 7.3.1, 7.3, 7.2.2, 7.2.1, and 7.2 (I haven't checked earlier versions of the help -- the path is /prhelp/procomhelpmain.htm#rule-/rule-connect-/rule-connect-rest/service.htm ):
I believe that in Pega 7.2.2 you are able to use Global Resource Settings for pyResourcePath, despite this property not being officially documented. it is just less "dynamic" than using parameters for the parts of the URL that are truly dynamic.
As far as I know, the resource parameters mappings do support Global Resource Settings when you set the "Map from" to Clipboard.
Of course, you should do some local testing, no matter which option you choose to go with.