Configuration properties

The configuration as a whole has its own editable properties. The properties palette is opened from the configuration name (the root of the configuration tree is selected).

In addition to the basic properties inherent in each configuration object, a configuration has the following properties.

Default run mode
The run mode for the application is specified (ordinary application or managed application). A combination of "Managed application" value with 8.1 compatibility mode values is forbidden. This check is performed when the configuration database is updated.

Use assignments
Specify the application target platform (PC or mobile). Clicking the button opens the dialog box where you can select check boxes next to the platforms you want to use.

Script variant
The default programming language (Russian or English) is selected. This property determines the language for generating programming constructs in modules and returning information about basic data types.

Default role
Default configuration role (it will be used in 1C:Enterprise mode unless users are entered). Roles are specified in the "General - Roles" branch of the configuration tree.

Managed application module
The Open link opens the managed application module edit window.

Session module
The Open link opens the session module edit window.

External connection module
The Open link opens the external connection module edit window.

Ordinary application module
The Open link opens the ordinary application configuration module editor (this property is not available if Managed application run mode is selected in configuration parameters).

Use managed forms in ordinary mode
If this property is selected, managed forms will be used in ordinary mode in the thick client (the property is not available if Managed application is selected as a run mode in configuration parameters). If the property is unchecked, the managed form module and command module are not checked in modules check with specified check modes Thick client (ordinary application) and Thick client (ordinary application) client/server mode.
When a default form is received in the thick client of ordinary application if the property is unchecked and managed form is set as a default form (main and/or additional), an ordinary form will be generated automatically anyway.

Use ordinary forms in managed mode
If this property is selected, ordinary forms will be used in managed mode in the thick client (the property is not available if Managed application is selected as a run mode in configuration parameters). If this property is unchecked, the ordinary form module is not checked during the module check if the following check modes are selected: Thick client (managed application), Thick client (managed application) client/server mode, Thin client, and Web client.
When a default form is received in the thick client of managed application if the property is unchecked and managed form is set as a default form (main and/or additional), a managed form will be generated automatically anyway.

Additional full-text search dictionaries
1C:Enterprise 8 delivery kit includes morphology and synonym dictionaries. If additional dictionaries are required, they should be specified in this property.

Settings storages - metadata objects that store data in a certain infobase object. For example, in a catalog.

Common settings storage - the storage is intended to host various application settings. The platform itself does not record any data to this settings storage. This storage should be used by a developer via the 1C:Enterprise script to save/restore custom user application settings.

Reports settings storage - this storage hosts user settings for reports.

Report option settings storage - this storage hosts options of reports.

Form data settings storage - this storage is intended for forms data.

Contents - displays the objects belonging to the root configuration object (the property is visible if Version 8.1 mode is specified in Compatibility mode property).

Command interface
This property is used to edit visibility of subsystems in general and for individual roles.

Starting page work area
The Open link opens a window to edit the main application window work area that is displayed when the program is started. The window is used to specify forms on the desktop. The desktop contains the forms with the most important information for users and those with which a user normally starts working.

Main section command interface
This interface is used to edit the assortment of main section (Quick menu) commands that are displayed when the program is started. This property should be edited if the automatic command order, command groups, and automatically selected default visibility do not meet the user requirements.

Main section picture
The Open link opens the selection window for the picture that will represent the main section (Quick menu).

Client application interface
This property is intended for specifying which panels are available when the application is started, as well as their positions. Users can add or remove panels, or change their positions.

Default interface
Select the default configuration interface (used if no users are entered). Interfaces are specified in the "Common - Interfaces" branch of the configuration tree. The property is not available if Managed Application run mode is selected in configuration parameters.

Default style
Select the configuration style to be used by default. Styles are specified in the "Common - Styles" configuration tree branch (the property is not available if Managed Application run mode is selected in parameters.

Default language
Select the configuration language to be used by default. This language will be used to display the fixed terms provided by 1C:Enterprise.

Brief information
Brief information about the configuration.

Detailed information
Configuration details.

Logo
Select a logo. A logo is selected in the standard picture selection window.

Splash
Select a splash. A splash is selected in the standard picture selection window.

Copyright
Configuration author details. This information is displayed in the “About 1C:Enterprise” dialog box and in the help window.

Vendor information address
Configuration vendor info link (Copyright property). Optionally, it may include a schema prefix ("http://"). Vendor details are displayed in the left part of the footer on help pages, including the link specified in this property.

Configuration information address
Link to configuration data. Optionally, it may include a schema prefix ("http://"). In the upper left area of the help page, you will see the configuration name defined in the Brief information property (if the property is not defined, it is selected from the Synonym property value; and if Synonym is not defined either, it is selected from the Name property value of the root configuration object). The displayed configuration name contains a link specified in this property.

Default constants form
Select the default form to enter and edit configuration constants. Forms to enter constants are built in the "Constants - Forms" configuration branch. The property is not available if Managed Application is selected as a run mode in parameters.

Default search form
Stores a common form that is used for full-text search in the client application. During the form creation, the Common form and constant wizard is started.

Vendor
Specifies the configuration vendor (optional).

Version
Current configuration release number (optional).

Update directory address
Contains the address that can be used to update the application.

Include in help contents
If checked, help content for this catalog is included in the general configuration description.

Help content
The Open link opens the configuration description editor.

Data lock control mode
Data lock control mode is specified. Each application object also has the Data lock control mode property. For the configuration, the mode can be set to Automatic, Managed, and Automatic and managed. The Automatic or Managed values determine the data lock mode that will be used for all configuration objects regardless of values selected for each individual object. When Automatic and managed is selected, for each configuration object a mode is specified in its Data lock control mode property: Automatic or Managed.

Object autonumbering mode
This property defines if the numbers automatically assigned to object codes should be reused if they have not been recorded to the database.
If Release automatically is selected, an out-of-transaction number is released automatically. When a transaction is rolled back, the numbers are automatically released regardless of the object autonumbering mode. No automatic release - numbers are not released automatically.

Modality usage mode
This property shows whether calling procedures that open modal windows is allowed.

Interface compatibility mode
Defines the application interface and the interface compatibility mode.

Version 8.2 - the client application interface is "Version 8.2". Changing the interface is not allowed;

Version 8.2. Taxi allowed - the default client application interface is "Version 8.2". Changing the interface mode from 1C:Enterprise script or using a command-line parameter is allowed.

Taxi. Version 8.2 allowed - the default client application interface is "Taxi". Changing the interface mode from 1C:Enterprise script or using a command-line parameter is allowed;

Taxi - the client application interface is "Taxi".

Compatibility Mode
Specifies how features whose behavior was changed are handled in the current 1C:Enterprise 8 version.

The property defines whether the legacy features of the specified platform version are available (in this case the feature modifications introduced in the next versions are not available).

The value None indicates that all features of the latest platform version are available, but correct functioning of configurations created on previous platform versions is not guaranteed.

Note 1: It is forbidden to use a combination of configuration properties Default run mode - Managed application and 8.1 compatibility mode. A check is performed when a database configuration is updated.
Note 2: It is forbidden to launch any client in managed application mode if the configuration is specified as compatible with version 8.1.
Note 3: When None mode is selected, it is impossible to switch to Version 8.2.13 and Version 8.1 compatibility modes if the configuration contains at least one common attribute.