Below diagram portrays the process of configuration management for IFS Cloud.
Users would have the option of creating configurations either in Build Place or Use Place.
If the new configuration require a significant level of data present at the environment during their development, then such configuration may be done in Use Place.
However, it is highly recommended to maintain all the configuration in the customer solution repository in the Build Place and perform the impact analysis via Configuration Analyzer.
In a delivery which includes changes from core and/or cust layers (eg. Feature Updates / Service updates) in addition to configurations, configuration impact analysis is recommended to be performed at build place before delivering to Use Place.
But, when there are no other layer changes except configurations, impact analysis may be performed at the Use Place itself.
Configurations which are to be deployed as a delivery via Build Place, the extracted content of ACPs should be committed to <component>/server/appconfig
Configurations which are not intended to be delivered via Build Place, the extracted content of ACPs should be committed to <component>/nobuild/appconfig