Can we add more resource path(in Connect Rest)parameter in a DSS via Global resource Setting in pega?

General
1

In continuation of my previous query:If we have to add under resource path more properties for a connect rest how can we do that in prod? I am attaching a screenshot:

This can be added manually at the time of Connect Rest creation via wizard but can the same thing be done via GRS and DSS?for Prod

image
image562Ă—427 79.6 KB

2

Hey @TanyaS58

And that makes it three questions answered today—clearly we’re on a Pega Q&A sprint :grinning_face_with_smiling_eyes:

The short answer would be No, I don’t think we can add or dynamically change additional resource path parameters of a Connect‑REST rule using a DSS via Global Resource Settings. Global Resource Settings + DSS are used to externalize environment‑specific values such as:

  • Base URL / endpoint override

  • Authentication details

  • Request headers

  • Timeouts, keystore references

The resource path itself is part of the Connect‑REST rule definition and is not dynamically extendable via DSS. To explain in simple words: DSS can override where the service is called, but not how the resource path is structured.

What is supported instead?

  • Path parameters inside the resource path: You can define variables in the resource path and map them using rule parameters, for example: /appointments/{appointmentId}
  • Query parameters: These can be dynamically populated from clipboard properties or parameters.
  • Multiple Connect‑REST rules: If resource paths differ structurally (e.g., /v1/... vs /v2/...), define separate rules and select them conditionally.
  • Full endpoint override via Global Resource Settings: You may override the entire endpoint URL, but it must still match the resource path defined in the rule.
  • Manual Construction of the end point URL: Constructing the complete endpoint URL and parsing it from the request Data Transform of the Connect-REST rule

Summary

  • DSS cannot add or alter Connect‑REST resource path segments

  • DSS can externalize endpoint/base URL and related settings

  • Dynamic parts of the path must be handled via rule parameters, not DSS

This is expected behavior by design in Pega.

Thanks,

Roshan Raj A K

3

Thanks for such a detailed explaination @RoshanRajAK1 ,so if we just add the resource path as a parameter in the url itself then we can use DSS and provide the entire url right?cause in production how come we will add more resource paths,if the requirement comes up suddenly to do so.

4

The best practice is to leverage Application Settings for Connector rule. Application Settings for Connect REST rules enable managing environment-specific configurations—like endpoint URLs, authentication profiles, or timeouts—without updating rules during migration. They act as a robust alternative to Dynamic System Settings (DSS), allowing different values for sandbox, staging, and production within a single application.

5

Hey @TanyaS58 - If the concern is around multiple resource path parameters that keep changing across environments, Use of Application Setting will be the best choice.

Instead of hardcoding your URL within the Connect-REST Rule configuration, define an Application setting rule and pass the different Resource URLs configured for each environment within the rule.

Else, If you have multiple resource URLs for a single Connect-REST that might change in the future only in production, Just define it as a Query Parameter at runtime instead, This allows you to just include the additional resource path while keep the Base URL consistent across all environment.

This keeps the Connect‑REST configuration generic while allowing flexibility to add or change resource paths dynamically as new requirements arise.

So in short:

  • Frequent or unpredictable URL changes → Use Application Settings

  • Stable base URL with variable resource paths → Pass dynamically at runtime as Query String Parameters

Let me know if this helps

Thanks,

Roshan Raj A K