When creating corticon rules that depend on rest calls to fetch data, is it possible to setup the URL as config.
We cannot "hardcode" the live environment string into the package at compile/deployment stage.
Currently the rule validates the URL and we dont have access to live env from our dev and test sites.
Also with up to 3 development and 9 different client test sites and then live, you would have to switch and rebuild
the rule deployment a lot if this is hardcoded.
The REST URL is part of your vocabulary datasource definitions and can be separately deployed through the datasource.xml file at deployment time. Simply compile your EDS and export (and modify) the URL and its credentials in the exported datasource.xml for your target run time environment, which you then deploy together. Alternatively, you can predefine multiple REST datasource definitions in your vocab, and have a branching container in your ruleflow conditionally running the specific REST service callout for a target datasource based upon a decision service request parameter.
Hope this helps and above will work for what you have in mind. Best regards, Harold