We have QSEoCS running well (the SaaS offering for the enterprise edition).
Right now, we are developing the apps locally (via Desktop) and publishing the completed app to the SaaS environment.
Each time we do this, it creates a new app instead of replacing a target app.
This is problematic because
- user content is lost
- You have to recreate the reload schedules, tags, etc.
Back story: We are doing this because the connectivity and performance while developing in the SaaS environment is suspect. Consuming is fine but there are times when the auto-save just doesn't work. So for efficiency sake, we are developing locally and pushing to the cloud for consumption (with all data connections and reloads working automatically).
When publishing to SaaS, Is there any way to replace an existing app instead? Or could someone point me toward the workflow best practice in the SaaS environment?
I really would prefer to avoid setting up an QSEoW instance simply to automate the publishing of an app to the Cloud offering.
