If we have to add under resource path more properties for a connect rest how can we do that in prod?
If we have to add under resource path more properties for a connect rest how can we do that in prod?
If I understand the requirement correctly, if you need to add more dynamic values in the REST connector resource path, the better approach would be to parameterize those parts of the path and pass the values from the case/data context before invoking the connector.
For example, instead of hardcoding the full resource path, keep the variable parts as parameters/placeholders and map them from properties in the request data transform or connector invocation.
In Production, ideally we should not directly modify the Connect REST rule. The updated connector rule/request mapping should be moved through the normal deployment process. For environment-specific values like the endpoint/base URL, configuration through application settings can be used so that the same rule works across Dev/Test/UAT/Prod.
Please correct me if I understood the scenario differently.
Hi @Shirisha_Boinapalli yes your understanding is absolutely correct but in prod if we use app settings say now we have a requirement to add 100’s of other param values so will that be feasible? This was asked in a scenario based interview.
Hi @Tanya_Singh,
Good question this actually made me think a bit deeper, and I picked up some interesting learnings from it.
Yes in the above scenario, using App Settings for 100+ dynamic parameters would not scale well, they are better suited for environment-level configs like base URLs.
A better approach would be to keep the connector generic and populate values dynamically using Data Transforms. If the values are configuration-driven, we can store them in a data object and fetch them via a Data Page.
For larger or frequently changing configurations, we could also externalize them into a config service(like AWS) and fetch them at runtime, depending on the use case.