The configuration check is intended to find errors that do not critically impact application functioning but might impact the performance or cause run-time errors in some modes.
The configuration check includes the following:
- Standard logical integrity check (which is normally performed before the configuration database update)
- Unresolved reference check for all objects, forms, templates, and other configuration items
- Module syntax check in various run modes, including client/server mode emulation and external connection mode emulation
- Unused procedure and function check
- Availability of assigned handlers check
- Empty handlers check
Configuration checks are handy in the following scenarios: before delivering a configuration to a customer, before releasing a standard solution, after a mass deletion of objects, or after configuration merging.
Configuration checks are also supported in Designer batch mode.
See also:
