If we have common files for a corporate site (e.g., images) but separate branches deployed separately for independent business units, we can get the corporate files combined with the Buisiness Unit files on the production web server via OpenDeploy. However, if the common files from corporate are not in the Business Unit's Staging Area, they will not be in the Edition created for the Business Unit and thus not be available for Business Unit site rollback.
How do you address this?
So you perform a Copy_to_Area command in workflow to copy the common images files from corporate into the Business Unit's Staging Area, when the Business "Submits" their Business Unit specific WorkArea, from within their branch to their Business Unit's Staging Area?
If that's the approach are there file permission issues the workflow script will encounter upon copy to area?
Will a Direct Submit and direct invoke of Open Deploy (i.e., not going throuhg workflow) work in this scenario? In other words, it would probably work as long as the common images from coporate were submitted once to the Staging Area of the Business unit and haven't changed since then. Can you direct submit the common corporate images to a specific staging Area such as the Business Unit's?
dave@simpleinternet.com+USA (215) 962-5153
