Hi Chris,
first of all thanks for a prompt feedback.
I am afraid I have not described the situation well. Let me be a bit more detailed.
Step 1: SW House build and deploys the app with CloudAppLauncher and runtime into a zip. The app is accompanied with an INI with general settings
Step 2: The deployment package goes to a customer
Step 3: Customer extracts the zip to a temp folder
This is the moment when customer needs to introduce some modifications into the INI file to setup e.g. their DB connection
Step 3: Customer completes the deployment making a copy of the package in a location on their server where the app shall get distributed from.
Step 4: User on a local machine opens app launcher form the published location on server
I hope an attached diagram will help to understand our situation better.
There is a similar situation with some external files which are supposed to be available for all the app installation instances, however it does not make much sense to add one picture (to be presented on a report's footer) and build+deploy the whole thing. So it would help to have a mechanism, do add that picture to the deployed app, so it would get distributed automatically to all the installation instances that do not have that picture file. This one, however, is not that hot issue, and we are aware of some possible workarounds. On the other hand, the INI modifications represent a considerable complication within our distribution chain.
Thanks a lot for your help.
Best regards,
Marian
