
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2019 10:38 AM
Hello,
Im trying to configure a Connection & Credential Alias for use within a Flow IntegrationHub REST Step. What I would like to do is to configure the Connection Alias with both a Development/ Test Endpoint & Credentials, as well as, the Production Endpoint & Credentials so that at runtime the Flow can determine which instance the flow is running in and then determine the proper endpoint & credentials to use. I have only previously configured an Alias with a single active connection but know that the latter is possible. I've read through the docs and am still stuck on how to properly configure the Alias. Any assistance would be most appreciated.
Thank you for your time.
--David
Solved! Go to Solution.
- Labels:
-
Integrations

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-05-2019 10:17 AM
I figured out a solution that works for us so will post it here just in case anyone else is looking to do the same thing.
If you have an integration with a system that uses different endpoints and/or credentials for different environments i.e .Dev, Test, Prod then you can configure a connection alias during your development work of the integration (In our case this was in an IntegrationHub REST Step). During the development of the Integration we simply linked up the Connection Alias and then in each respective instance we configured and associated an appropriate connection record with the endpoint & credentials needed for each instance. The connections and credentials are preserved during clone downs so they are not overwritten in the sub-prod instances . When the Integration step is called during runtime in each instance it simply references the configured connection alias and will utilize the connection/credentials that are defined in the instance at that time.
Hopefully this will help someone else who finds themselves with a similar need.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-05-2019 10:17 AM
I figured out a solution that works for us so will post it here just in case anyone else is looking to do the same thing.
If you have an integration with a system that uses different endpoints and/or credentials for different environments i.e .Dev, Test, Prod then you can configure a connection alias during your development work of the integration (In our case this was in an IntegrationHub REST Step). During the development of the Integration we simply linked up the Connection Alias and then in each respective instance we configured and associated an appropriate connection record with the endpoint & credentials needed for each instance. The connections and credentials are preserved during clone downs so they are not overwritten in the sub-prod instances . When the Integration step is called during runtime in each instance it simply references the configured connection alias and will utilize the connection/credentials that are defined in the instance at that time.
Hopefully this will help someone else who finds themselves with a similar need.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2020 08:57 AM
Hi David,
We have 2 connections for 1 alias. We created connections for on prem and cloud each. Now is there a way I can know which connection is being used ?
Thanks Surya

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2020 07:23 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2020 03:28 AM
Hi David,
Cant it be done with 1 connection alias and 2 connections?