Scope: managed applications, mobile applications, and ordinary applications.
Library configurations (libraries) help to support configurations that use its functionality. Unlike ordinary applications, library configurations are not utilized by end users. They contain functionality, which is common for all applications.
By taking advantage of libraries when developing common application functionality, you can:
- Centrally develop common functionality rather than separately in every application.
- Release common functionality versions as products (library distribution packages).
- Reuse the code and library objects in configurations by using 1C:Enterprise platform support functionality.
- Standardize configurations by a set of common metadata objects and functional subsystems.
As a rule, libraries are not developed separately. They are used only to create applications. Applications are end configurations in the library hierarchy.
a) Application programming interface to be used by any external consumers is called from any area in the configuration code. Most frequent consumers of such application programming interface are configuration extensions, external configuration upgrades, and other applications.
b) Application programming interface for specific consumers must be located in a particular place in the configuration code specified in its documentation. It can be called only by a particular consumer. Display this application programming interface in a separate subsection For calls from other subsystems. For more information, see Library backward compatibility.
2. Service application programming interface contains export procedures and functions that can be called only from other functional subsystems of the same library (configuration).
3. Service procedures and functions contain internal implementation of a functional subsystem. Export procedures and functions available in this section, can be called only from other objects of the same subsystem.