Making Integrations Server Specific
  • 11 Mar 2022
  • 2 Minutes to read
  • Dark

Making Integrations Server Specific

  • Dark


By parameterizing a REST Integration, Designers provide the ability to make Integration dynamic without having to create a new Integration each time. This parameterization allows an environment to be dynamic enough to point to the Development environment and provides the ability to change from Production to Production. The following document demonstrates how to make an Integration more Server-specific via parameterization. 

Additional Information 
The following example involves the creation and use of a REST Integration in Decisions. For more information on REST Integration see REST Service Integration Overview.


  1. From the Decisions Studio, navigate to System > Integrations > External Services. Then select ADD REST SERVICE. 
  2. From the Add REST Service window, provide a relevant Service Name
  3. Under Service URL, define the URL first by providing the protocol, and then by blocking off the URL with curly brackets, separating each element with periods (for this example "https://{Server}.{Domain}"). 
    Additional Information on Parameterization 
    As the Note on this window states, encapsulating a text value in curly brackets ({}) will turn that value into a Flow Input that can be dynamically changed via the Flow Designer. For this example, one Input will represent the desired Server, the other will represent the Domain.

    This allows Designers to use the same Integration Step to navigate to different specific without having to create separate Services for each one. 

  4. Under AUTHENTICATION > Authentication select/define the required Authentication type, then click SAVE INTEGRATION. 

  5. After the Service is added, right-click it and select Add Method to Service

  6. From the New REST Service Method window, provide a Name. Then in the URL box, provide a parameterized element (for example "{Decisions}"). 

    About Method and URL 
    Adding a Method to a REST Integration will create a Step for the Service within the Flow Designer.
    Note that the URL value of the Method represents a path relative to the Service Base URL. This value would follow a forward slash in the typical URL configuration.

    For example, in the URL, the path "decisions" at the end of the entire URL would be represented by this value.

  7. Select the desired HTTP Method, then click OK. 

  8. After the Method is successfully added, navigate to a Designer Project, select CREATE FLOW, then CREATE a new Flow

  9. From the Flow Designer, navigate to Toolbox > INTEGRATION > REST SERVICES > [NAME OF SERVICE], and attach the defined Method step to the Start step. 

  10. From the Properties tab of the Rest Method, Constant map the desired Domain, Server, and URL (Path) values. Then, connect the Done and Error paths to the End step. 

    Additional Information on Inputs 
    If the Method calls for any additional Inputs (such as via POST), provide the respective value. 

  11. Save the Flow, then close via X.

    Service Reuse 
    Upon future uses, due to the parameterization of the URL for the REST Service Method, this step may be utilized in different Flows and mapped to navigate to different Servers/Domains/URL Paths in an environment. 

    For further information on Integrations, visit the Decisions Forum.

Was this article helpful?