Why is configuration management important?
Configuration management is a critical part of any Clio Operate implementation. The modelling and administrative capabilities in Clio Operate can be extremely powerful, and even though we are not writing code as part of the Clio Operate project, it is important that any configuration changes we make are handled in a structured and methodical way. Without a clear configuration strategy, you may end up with missing elements in releases of configuration or inconsistency between what has been tested and what is deployed to production.
Minimum recommended environments for a Clio Operate implementation
| Environment | Usage |
| Gold Configuation (vNext) | This environment should be used by all configurators to make any changes to the product. Changes should not be made directly into production or test environments they should always be made in the gold environment and then migrated using the solution import / export capability |
| UAT / Pre-Prod | There should always be an interim environment between gold and production that allows you to test the movement of configuration and also acts as a place where end user testing can take place on a stable configuration base. This ensures that when your configuration is moved into production it behaves as expected |
| Production | Configuration should never be carried out directly into a production environment. Configuration should always be carried out in the gold environment and moved through to production using a configuration package. |
How is configuration moved between environments?
Configuration is moved between environments using the Clio Operate import/export tool. As you change different elements of configuration in Clio Operate, these items should be added to a configuration package, which will ultimately ensure that the changes are propagated to each higher environment in turn. You can learn more about the import/export tool here: Exporting Clio Operate Configuration.