Scope: managed applications, mobile applications, and ordinary applications.
1. When you develop a configuration if one or several libraries are used, you need to avoid conflicts between names of metadata objects (catalogs, documents, common modules, and so on) supplied from libraries and names of configuration objects.
To resolve such conflicts, assign the preferential right to select a name to a down-level library. If one of its consumers has an object with the same name, you need to rename the object in the consumer using a more specific name.
For example, if the Enterprise Resource Management configuration has the Settings command group that conflicts with a command group of the same name in the Core library, select a more specific name for the end user configuration, for example, ManagementAccountingSettings, CostCalculationSettings, and so on.
To reduce probability of conflicts, always name metadata objects meaningfully. A name must briefly describe an object. It is not to be too universal.
2.3. We recommend that you name functionality that expands the similar functionality of a down-level library or conflicts with an adjacent library of the same level by adding a detail postfix that match a name of a particular library or end user configuration.
- The InfobaseUpdateMF common module contains infobase update functions specific for the "My Finance" end user configuration (MF postfix).
- The StringFunctionsRegul common module contains common functions specific for a regulatory accounting library (Regul postfix).
- The FormsOperationsPayrollHR common module contains functions used to work with forms in the library of the basic payroll and human resources functionality (PayrollHR postfix).
- Subscription to the SetAttachedFilesDeletionMarksPayrollHR event is defined in the library of the basic payroll human resources functionality.