Sorin Vatasoiu

Cedric,

Thank you again for your help.

I'm now able to set and use the custom environmental variables for my app.

I post here the code that worked, it may help other people, as many examples on the web are for v1 framework and they do not seems to work for v2

var zendeskAcsWSurl = '';

Cedric,

I tried to follow your advice and I added a new line to the manifest file "ACSServiceBaseUrl":

I added the line with an empty value as I was expecting to fill it an use it in the app settings and use it in the code.

After I validated, packaged and install the app in Zendesk, I opened the the app settings, but I do not see a place where I can update a value for "ACSServiceBaseUrl".

Did I miss anything from your explanation?

manifest.json

Thank you for those ideas. This seems to be the correct way to do the setup.

Cedric,

Thank you for the response.

I see how your solution will move the variables from the javascript code (where I have them now) to the manifest file.

Does this means that for various environments, I will need to have more manifest files, of that I will need to change the values in the manifest before each "zap package" operation?

I did built a custom app that integrate another system into the Zendesk UI for our company.

The application is working very well and I'm getting ready to deploy it into the production environment.

There are few variables that hold connection information that will need to switch between values based on the environment where it is deployed.

Those variables holds url's for web services, database connection strings, logging setup...

I would like to know if there are best practices for setting and managing those  environmental variables to be easy to deploy the app in different environment?