Seamless deployment across environments. What is the best practices for an appli

In the past I've used an environment specific constant that has a unique value in each Appian environment (DEV, TEST, PROD, etc). When the webservice node is runs, it picks from a list of possible endpoints based on the environment.

The key piece here is that you need to separate your environment specific constants into a separate application so that regular deployments don't require that you update the value of the constant.

We do that the same way as Andrew described.

Hi Juregen - Typically we separate Environmental type rules and constants in a separate folder and not include those artifacts when we push from system to system. In terms of determining your environment, you can leverage a rule to call APN_getSiteUrl() (which is part of the common objects app) and based on that rule determine what environment you are running in. From there leverage logic to create dynamic links etc.

On a previous project, I also followed the procedure that Andrew describes. I'm sure that the APN_getSiteURL() rule can be useful as well, but we ran into some issues with using it in terms of performance and accuracy.

For future reference...

forum.appian.com/.../Environment_Specific_Properties.html