To specify the general settings, on the Tools menu, click Options.
On the General tab you can select the configuration editing mode (which depends on its startup mode).
If you select Managed application and ordinary
application, the platform hides the configuration
editing controls that only make sense in the ordinary mode.
For example, the Thick client (ordinary application): start debugging item is hidden from the Start debugging with section of the Debug menu.
Also the Interfaces and Styles branches are hidden from the Common branch of the configuration tree, as well as the Interfaces tab in the More pane. The following configuration properties are hidden: Ordinary application module, Use managed forms in ordinary application, and Use ordinary forms in managed application. The print wizard is also changed.
If you select Managed application, the platform also hides some configuration parameters. On the Check tab of the Modules tab, the Ordinary application item is hidden from the Default run mode list, and the Thick client (ordinary application) check box is also hidden. Note that the visibility settings are only applied when you click Apply.
Refactoring on changing forms or metadata objects
Specify whether refactoring is performed on changing forms or metadata objects:
- Check modules before deletion. If the check box is selected, all of the module texts are checked before deletion of a metadata object.
- Update modules on renaming. If the check box is selected, all of the module texts are checked before renaming a metadata object, and after the renaming the module texts are changed accordingly.
- Check the entire configuration before changing a form. If the check box is selected, the entire configuration is checked when objects subordinate to a form are changed. The check box is cleared by default.
Actions triggered by presumed reference detection. The action performed when a metadata object name matching the following conditions is encountered during the check:
- the object type cannot be determined unambiguously by its name. Example: "Parameter1.Item";
- the object name is used in string constants, data composition system queries, dynamic list queries in forms, or access restriction queries. Example: "| Catalog.Currencies".