Best practices for deploying and migrating EnterWorks.
The EnterWorks platform has inherent capabilities to support the migration of the solution and solution configurations from one environment to another. The best practice is to master configuration changes in a single environment. For example, profile changes should be made only in the Development (DEV) environment, then migrated to the Quality Assurance (QA) environment, then to the Production (PROD) environment. Allowing changes to profiles in the PROD and UAT environment requires additional steps to determine how to merge the changes.
Similarly, the best practice is to master data in only one environment and migrate the data from the single environment, typically test, and them migrate that data to the other environments.
Following these principles simplifies the migration process and allows a customer to rely on the delivered migration functionality for the migratable objects. For more information about migration functionality, see EnterWorks Migration.
However, we understand that for a variety of reasons, customers may choose to allow mastering data in multiple environments. The following sections describes techniques that can be used to determine out of sync scenarios between environments and provides guidance on how to identify and resolve those discrepancies.