The process for deploying, promoting and applying hot fixes to VeloCITY 365 follows a well-documented path from Development to Production. It is expected this methodology will be followed with separate environments for each phase of the development cycle. All new work or changes are made within the Development Environment. The changes are promoted to the Test Environment for testing and approval/rejection. Once these changes have been approved, they are promoted to the Production Environment. This path not only ensures the changes to the product are successful applied, it also ensures the deployment/promotion process is complete and produces the desired results.
When planning for an upgrade, promotion or hotfix there are 2 categories of information that needs to be considered, namely customizations and data.
Safe | Use Caution | Avoid |
|---|---|---|
Changes to content are considered safe. Examples include: | Changes to the Production environment that involve the creation of new application data as all actions are immediate, are visible to a large audience and having incorrect or incomplete data can have disastrous consequences. | Removing any application data as recovery is time consuming and not always possible. |
When agreeing to a Hot Fix, consideration must be given to how the change will be merged back into the Development environment. For large and/or complex changes, the recommended methodology is to use Microsoft’s Configuration Migration Tool. The conditions that need to be considered include:
