General configuration requirements

See more

Scope: managed applications, mobile applications, and ordinary applications.

1.1. The configuration must use only standard and documented 1C:Enterprise platform functionality.

Scope (details): a managed application, an ordinary application.

1.2. The configuration must be equally suitable for operations with all DBMS, operating systems, web browsers, and various modes supported by 1C:Enterprise platform. Particularly, all key configuration features must be available to users in the web client without using file extensions. Interactions with users must be asynchronous.
Supplementary materials:

1.3. Make sure the configuration does not contain errors, which can be detected upon the configuration check. To check the configuration, in Designer, click Configuration, and then click Check configuration. Exceptions:

1.4. To support backward compatibility with own or third party solutions, external data processors and reports developed on previous versions of 1C:Enterprise 8.0 and 8.1 platforms, the configuration must also run in an ordinary application mode (thick client) and support external connection for administrators or users with full rights. Recommendations: 

  • Set the "Use managed forms in ordinary application" configuration property to True. Set the "Use ordinary forms in managed mode" to False.
  • Follow guidelines of setting common module flags.
  • Use the edit mode upon development in Designer for both startup modes: a managed and ordinary application (in Designer, click Tools – Options, and then click the General tab).

You do not need to support an ordinary application mode and external connection for administrators of the configuration startup only in reasonable cases.

1.5. When designing solutions, developing user interface, reports, and other, we recommend that you apply default settings provided by 1C:Enterprise platform. You can implement alternative options of solutions only if it is strongly required.

2.1. Make sure you avoid slang and jargons in names, synonyms, metadata object comments, common modules, and any text information displayed to users and shown to developers.

2.2. Make sure your configuration does not contain unused metadata objects, such as catalogs, documents, command interface sections, and other. Also it must not contain the code of common modules, procedures, functions, and variables, which is not used in the configuration and for integration with other systems.

2.3. We recommend that you sort by name metadata objects of the upper level, such as Catalogs, Documents, Common modules, and other, in the metadata tree. Subordinate metadata objects, such as attributes, dimensions, forms are located in the metadata tree according to the project logics.

Exceptions:

  • Common attributes as for common attributes acting as separators, it is required to set a sequence in the metadata tree according to the order of setting session parameters.
  • Objects with the "Obsolete" prefix, which can be placed at the end of the respective metadata tree branch.