Desktop version
<script src="filter.js"></script>
<link rel="stylesheet" href="style.css">
<style>
/* === 1. ОСНОВНОЙ КОНТЕЙНЕР === */
.doc-content-wrapper {
max-width: 120ch;
margin: 0 auto;
box-sizing: border-box;
font-family: sans-serif;
}
/* === 2. ТАБЛИЦЫ === */
.doc-content-wrapper table {
width: 100% !important;
display: block;
overflow-x: auto;
border-collapse: collapse;
margin-bottom: 20px;
}
.doc-content-wrapper table th,
.doc-content-wrapper table td {
padding: 8px 12px;
border: 1px solid #ddd;
vertical-align: top;
text-align: left;
}
/* Балансировка колонок */
.doc-content-wrapper table th:first-child,
.doc-content-wrapper table td:first-child {
width: 1%;
white-space: nowrap;
}
.doc-content-wrapper table th:not(:first-child),
.doc-content-wrapper table td:not(:first-child) {
min-width: 150px;
}
/* === 3. КАРТИНКИ === */
.doc-content-wrapper img {
max-width: 100%;
height: auto;
}
/* === 4. ИСПРАВЛЕНИЕ ЗАМЕТОК (BLOCKQUOTE) - УСИЛЕННОЕ === */
/* Сброс стилей контейнера */
.doc-content-wrapper blockquote {
display: block !important;
margin: 20px 0 !important;
padding: 10px 20px !important;
border: none !important;
border-left: 4px solid #ccc !important;
background: transparent !important;
}
/* Сброс стилей параграфов */
.doc-content-wrapper blockquote p {
display: block !important;
width: 100% !important;
margin: 0 0 10px 0 !important;
padding: 0 !important;
border: none !important;
text-indent: 0 !important; /* Убираем отступы первой строки */
float: none !important;
}
.doc-content-wrapper blockquote p:last-child {
margin-bottom: 0 !important;
}
/* ЖИРНЫЙ ЗАГОЛОВОК (Notice, Note) */
/* Применяем ко всем возможным вариантам вложенности */
.doc-content-wrapper blockquote strong:first-child,
.doc-content-wrapper blockquote b:first-child,
.doc-content-wrapper blockquote p:first-child strong:first-child,
.doc-content-wrapper blockquote p:first-child b:first-child {
display: block !important;
width: 100% !important;
float: none !important;
clear: both !important;
margin-bottom: 8px !important; /* Отступ снизу от заголовка до текста */
color: #000;
}
/* ПРИНУДИТЕЛЬНЫЙ РАЗРЫВ СТРОКИ ПОСЛЕ ЗАГОЛОВКА */
.doc-content-wrapper blockquote strong:first-child::after,
.doc-content-wrapper blockquote p:first-child strong:first-child::after {
content: "\A" !important;
white-space: pre !important;
display: block !important;
height: 0px !important;
}
/* Ссылки */
.doc-content-wrapper blockquote a {
text-decoration: none;
color: #0056b3;
}
/* Оглавление */
.doc-toc {
background-color: #f9f9f9;
padding: 20px;
border: 1px solid #eee;
margin-bottom: 40px;
border-radius: 5px;
}
.doc-toc h2 {
margin-top: 0;
}
</style>
<div class="doc-content-wrapper">
<div class="doc-toc">
* [Chapter 1. Library subsystems](#chapter-1-library-subsystems)
* [Chapter 2. Library integration guide](#chapter-2-library-integration-guide)
* [Chapter 3. Setting and using subsystems during configuration development](#chapter-3-setting-and-using-subsystems-during-configuration-development)
* [Appendix 1. Data exchange message file format](#appendix-1-data-exchange-message-file-format)
* [Appendix 2. Application startup parameters](#appendix-2-application-startup-parameters)
* [Appendix 3. International SSL version without national specifics](#appendix-3-international-ssl-version-without-national-specifics)
</div>
# Chapter 1. Library subsystems
*** ** * ** ***
**1C:Standard Subsystems Library** includes a set of multipurpose functional subsystems intended for development of **1C:Enterprise 8.3** applications. The library is not a ready-for-use application. You can integrate either the entire library or individual subsystems into your configuration.
The library is compatible with configurations based on **1C:Enterprise 8.3** (see specific version number in the UpdateSSL.html file). The configuration must have the following property values:
<ul>
<li><strong>Default run mode</strong> is set to <strong>Managed application</strong>.</li>
<li><strong>Use purposes</strong> includes <strong>PC application</strong>.</li>
<li><strong>Script variant</strong> is set to <strong>English</strong>.</li>
<li><strong>Data lock control mode</strong> is set to <strong>Managed</strong>.</li>
<li><strong>Compatibility mode</strong>: see allowed values in the UpdateSSL.html file.</li>
<li><strong>Modality usage mode</strong> can be set to <strong>Do not use</strong>.</li>
<li><strong>Interface compatibility mode</strong> can be set to <strong>Version 8.2</strong>, <strong>Version 8.2. Taxi allowed</strong>, or <strong>Taxi. Version 8.2 allowed</strong>.</li>
<li><strong>Synchronous call usage mode for platform extensions and add-ins</strong> is set to <strong>Use</strong>.</li>
</ul>
All of the library subsystems can be divided into the following categories based on their integration methods:
<ol>
<li>Subsystems with independent functionalities.</li>
<li>Subsystems with functionalities intended for use in consumer configuration objects (deep integration).</li>
</ol>
You can integrate subsystems from the first category by simply copying library metadata objects to consumer configurations. Such subsystems are located in the command interface and do not require a complex setup. They might include user interfaces and might provide an API to be used in consumer configurations. When a new library version is released, it is usually enough to update the copied metadata objects. Examples: **Currencies** and **User sessions** subsystems.
To integrate subsystems from the second category, copy the subsystem functionality first and define the list of consumer configuration objects that are subject to functionality integration. Then configure some additional settings and edit the object forms and code (in other words, perform deep integration of the subsystem into the consumer configuration objects). When a new library version is released, simply update these subsystems. Usually, there is no need to change the consumer configuration objects again.
The library does not only contain subsystems but also suggests some application development methodologies, for example, the approach to configuring session parameters.
The key features of all library subsystems are described in the table below.
> **Note**
> <ul>
> <li>Certain subsystems might have limited functionalities in hosted or SaaS mode.</li>
> <li><strong>Hosted mode</strong> and <strong>SaaS mode</strong> indicate that a subsystem enables or supports hosted and SaaS modes, respectively.</li>
> <li><strong>External users</strong> indicates that a subsystem supports external users (for more information, see the <a href="#пользователи">Users</a> section).</li>
> <li><strong>Deep integration</strong> indicates that a subsystem supports integration into consumer configuration objects. <strong>Yes/No</strong> indicate whether each of the listed integration options is available.</li>
> </ul>
## Administration and maintenance tools
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Key features</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Additional reports and data processors</strong></td>
<td>
<ul>
<li>Attach additional (external) reports and data processors without changing the configuration.</li>
<li>Link additional reports and data processors to specific object types or command interface sections.</li>
<li>Execute data processors on schedule.</li>
<li>Manage the list of additional reports and data processors.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>User monitoring</strong></td>
<td>
<ul>
<li>Generate reports on user and department activity, account and access right changes, critical entries in the event log, and scheduled job runtime (hosted mode only).</li>
</ul>Set up event logging for data access auditing.<br>
SaaS mode: <strong>Yes</strong>.<br>
Hosted mode: <strong>Yes</strong>.<br>
External users: <strong>No</strong>.<br>
Deep integration: <strong>No</strong>.</td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Application settings</strong></td>
<td>
<ul>
<li>Take advantage of ready-to-use workspaces (panels) for the <strong>Administration</strong> section.</li>
<li>Adjust administration panel contents for the current application mode.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Configuration update</strong></td>
<td>
<ul>
<li>Automatically update to new application versions. Install patches on demand, at scheduled time or upon exiting the application.</li>
<li>Update the application from files in local or network directories.</li>
<li>Apply main configuration changes to the database configuration.</li>
</ul><br>
SaaS mode: <strong>No</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
5.</td>
<td><strong>Document record history</strong></td>
<td>
<ul>
<li>Generate a report with information about registers and records generated in them when posting a document.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
6.</td>
<td><strong>Performance monitor</strong></td>
<td>
<ul>
<li>Measure the overall application performance using the APDEX method.</li>
<li>Simplify and automate collection of information on the execution time of each key operation.</li>
<li>Use tools for analyzing measurement results.</li>
<li>Automatically export performance indicators.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
7.</td>
<td><strong>Duplicate cleaner</strong></td>
<td>
<ul>
<li>Search for and delete duplicate catalog items.</li>
<li>Replace one item with another, merge several identical list items into one.</li>
<li>Automatically replace references to deleted duplicates in all application documents and lists.</li>
<li>Generate a report on the selected item occurrences.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
8.</td>
<td><strong>Security profiles</strong></td>
<td>
<ul>
<li>Automatically set up infobase security profiles.</li>
<li>View the report on used external resources.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
9.</td>
<td><strong>Scheduled jobs</strong></td>
<td>
<ul>
<li>Display the list of scheduled jobs and configure their settings (schedule, start time, and end time).</li>
<li>Automatically lock operations with external resources (data synchronization, email sending, and so on) when starting up the infobase copy.</li>
</ul><br>
SaaS mode: <strong>No</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
10.</td>
<td><strong>Infobase backup</strong></td>
<td>
<ul>
<li>Create file infobase backups upon request or according to a schedule.</li>
<li>Restore file infobases from backups.</li>
<li>Get notified when configuring backup settings is required (also in client/server mode).</li>
</ul>SaaS mode: <strong>No</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
11.</td>
<td><strong>Marked object deletion</strong></td>
<td>
<ul>
<li>Delete objects marked for deletion with reference integrity monitoring (search for references to objects to be deleted).</li>
<li>Delete objects on schedule in background.</li>
<li>Manage the visibility of objects marked for deletion in lists.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
12.</td>
<td><strong>Totals and aggregates</strong></td>
<td>
<ul>
<li>Administer totals and aggregates of turnover accumulation registers.</li>
<li>Execute operations on shifting the limit of totals, recalculation, and update of aggregates (on schedule).</li>
</ul><br>
SaaS mode: <strong>No</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
</tbody>
</table>
## Users and access rights administration
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Key features</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>User sessions</strong></td>
<td>
<ul>
<li>View and terminate active user sessions.</li>
<li>Lock user activities and scheduled jobs for a certain period of time.</li>
</ul><br>
SaaS mode: <strong>No</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Users</strong></td>
<td>
<ul>
<li>Manage the list of application users.</li>
<li>Manage the list of external users who have restricted access to some application workspaces (for example, <strong>My orders</strong>, <strong>My questionnaires</strong>, <strong>Submit a ticket</strong>, and so on).</li>
<li>Configure access rights of users and external users (if integrated together with the <strong>Access management</strong> subsystem, use the subsystem tools to configure rights).</li>
<li>Group the user list and configure authorization settings (manage password complexity, disable inactive passwords, and so on).</li>
<li>Copy and clear settings of reports, forms, home page, command interface sections, <strong>Favorites</strong>, spreadsheet document printing, and other personal settings of users.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Access management</strong></td>
<td>
<ul>
<li>Set up user access rights for individual users and user groups based on access profiles and groups.</li>
<li>Configure record-level access restrictions for certain infobase data items (such as catalog items, documents, and register records).</li>
<li>Generate reports on rights of users and user groups, as well as on rights to objects and lists.</li>
<li>Select one of the two options for integration into the application: regular or simplified. The regular mode of setting access rights is designed for multi-user applications. In the simplified mode, rights are set individually for each user, which is better for applications with a small number of users.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
</tbody>
</table>
## Integration with other applications and systems
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Key features</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Add-ins</strong></td>
<td>
<ul>
<li>Import third-party add-ins into the application.</li>
<li>Install and attach add-ins via the application interface.</li>
<li>Automatically receive and update add-ins from 1C website (when used together with <strong>Online Support Library</strong>).</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Import data from spreadsheets</strong></td>
<td>
<ul>
<li>Import spreadsheet data to catalogs and tables of documents and catalogs.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>OData interface</strong></td>
<td>
<ul>
<li>Set up access to application data from external applications using standard OData interface.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Data exchange</strong></td>
<td>
<ul>
<li>Use the API and ready-to-use workspaces to organize collaboration in a distributed infobase (DIB) and to synchronize data with other applications.</li>
<li>Perform data synchronization manually or on schedule.</li>
<li>Establish connection over a variety of communication channels: a local or network directory, email, an FTP resource, or the Internet (including data synchronization with cloud applications).</li>
<li>Apply flexible rules for data synchronization between different applications, including a data mapping wizard.</li>
<li>Use data synchronization monitoring tools.</li>
<li>Develop exchange plans with or without data conversion rules. Conveniently debug conversion rule event handlers in Designer.</li>
<li>Automatically update subordinate DIB node configurations (when integrated together with the <strong>Configuration update</strong> subsystem).</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
5.</td>
<td><strong>Conversations</strong></td>
<td>
<ul>
<li>Enable the collaboration system online service so that application users can communicate with each other online, create topic conversations, and correspond on specific documents, for example, orders, sales, or counterparties.</li>
<li>Enable chats in messengers and social networks to communicate with customers.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
6.</td>
<td><strong>Text messaging</strong></td>
<td>
<ul>
<li>Use the API to send text messages in bulk and check their delivery statuses.</li>
<li>Add new providers programmatically.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
7.</td>
<td><strong>Network download</strong></td>
<td>
<ul>
<li>Use the API to get files from the Internet both in server and client code.</li>
<li>Set up proxy server parameters to access the Internet.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
8.</td>
<td><strong>Email management</strong></td>
<td>
<ul>
<li>Use the API to send and receive emails.</li>
<li>Manage email accounts.</li>
<li>Send messages using basic user interface.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
9.</td>
<td><strong>Report distribution</strong></td>
<td>
<ul>
<li>Send email reports to a user list.</li>
<li>Publish reports on FTP, in network directories, or in folders of the <strong>File management</strong> subsystem.</li>
<li>Send emails manually or set up a schedule.</li>
<li>Encrypt reports using digital signature certificates (if the "Digital signature" subsystem is available).</li>
<li>Check delivery and analyze distribution results.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
</tbody>
</table>
## Technological tools and APIs
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Key features</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Core</strong></td>
<td>
<ul>
<li>Use common procedures and functions to work with strings, other data types, the event log, scheduled jobs, the file system, to start long-running operations, and so on.</li>
<li>Perform operations with standard roles (such as <code>Administration</code>, <code>FullAccess</code>, and <code>StartThinClient</code>).</li>
<li>Store data safely, automatically track renamed metadata objects, and work with other basic developer services.</li>
<li>Use basic application administration features (event log, application window title setup, and so on).</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Barcode generation</strong></td>
<td>
<ul>
<li>Use the API to generate images of barcodes EAN8, EAN13, EAN128, Code39, Code93, Code128, Code16k, PDF417, ITF14, RSS14, EAN13AddOn2, EAN13AddOn5, QR, GS1DataBarExpandedStacked, and Datamatrix.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Object attribute lock</strong></td>
<td>
<ul>
<li>Use the API to check whether key object attributes (attributes that define the object nature) are filled.</li>
<li>Prohibit changes to key attributes of saved objects.</li>
<li>Check whether a user has rights to change key attributes.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
4.</td>
<td><strong>National language support</strong></td>
<td>
<ul>
<li>Operate multilingual data.</li>
<li>Use the API to enable operation in multiple languages.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
5.</td>
<td><strong>Infobase version update</strong></td>
<td>
<ul>
<li>Populate and update infobase data when an application version changes.</li>
<li>Display the "What's new" list of a new application version.</li>
<li>Use the API to run exclusive, real-time, and deferred update handlers.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
6.</td>
<td><strong>Attachable commands</strong></td>
<td>
<ul>
<li>Use the API to dynamically add attachable commands to application objects, lists, and journals.</li>
<li>Display generation and population commands, as well as additional reports and data processors (when used together with the <strong>Additional reports and data processors</strong> subsystem).</li>
<li>Contextually display commands in journals, lists, and documents depending on the types of selected objects and their attribute values.</li>
<li>Use the API for integration with extensions.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
7.</td>
<td><strong>Object prefixes</strong></td>
<td>
<ul>
<li>Set automatic assignment of object prefixes considering application settings.</li>
<li>Select unique object prefixes for each infobase.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
8.</td>
<td><strong>SaaS</strong></td>
<td>
<ul>
<li>Use basic functions for the configuration to work in data separation mode, which is required to run the application in SaaS mode together with <a href="https://its.1c.ru/db/smtl">1C:Cloud Technology Library</a> (in Russian).</li>
<li>Get access to auxiliary subsystems that must be included in the configuration together with the respective main subsystem. For example, when integrating the <strong>File management</strong> subsystem, integrate the <strong>File management SaaS</strong> subsystem as well.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>No</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
9.</td>
<td><strong>Monitoring center</strong></td>
<td>
<ul>
<li>Collect impersonal application usage statistics and transfer them to the Quality Management Center.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
</tbody>
</table>
## Applied subsystems and user workspaces
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Key features</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Surveys</strong></td>
<td>
<ul>
<li>Conduct surveys of respondents, which can include external application users, such as customers or partners.</li>
<li>Develop questionnaire templates and conduct surveys according to the list of respondents.</li>
<li>Use tools for analyzing survey results.</li>
</ul><br>
SaaS mode: <strong>No</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Business processes and tasks</strong></td>
<td>
<ul>
<li>Assign and execute tasks by the application users.</li>
<li>Manage the task list, inform assignees about their current tasks, and generate task reports.</li>
<li>Monitor and control task execution by interested parties, such as task authors and coordinators.</li>
<li>Develop custom business processes in the configuration.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Report options</strong></td>
<td>
<ul>
<li>Perform operations with predefined and user-created report options.</li>
<li>Use toolbars for quick access to report options; search for reports and report options.</li>
<li>Use a report form with quick settings for filters, groupings, appearance, and also with service features: sending reports by email, adding them to report distributions, getting an autosum, setting up headers and footers, and so on.</li>
<li>Work with the universal report to view data from any catalogs, documents, or registers.</li>
<li>Use the API to manage the features and appearance of report forms and panels.</li>
<li>View report snapshots saved earlier in standalone mode of the mobile client.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes/No</strong></td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Business interactions</strong></td>
<td>
<ul>
<li>Plan, register, and organize interactions with customers, colleagues, and other contact persons via emails, calls, meetings, and text messages.</li>
<li>Store all interactions and their contacts in the infobase, view interaction chains by contacts and topics (for example, by sales orders).</li>
<li>Perform operations with interaction results.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
5.</td>
<td><strong>File management</strong></td>
<td>
<ul>
<li>Jointly edit files, organize files by folders, and attach them to catalogs or documents.</li>
<li>Place files into the application from the file system of a computer or a device, from a scanner, or create files from templates.</li>
<li>View, compare, and select file versions, clean up obsolete files, use digital signature and encryption, search by content, and preview images.</li>
<li>Manage file placement in the infobase or in external volumes (network folders).</li>
<li>Synchronize files with cloud services.</li>
</ul><br>
SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes/No</strong></td>
</tr>
<tr>
<td>
6.</td>
<td><strong>To-do list</strong></td>
<td>
<ul>
<li>Display user's to-do items (for example, new emails, tasks, requests, and unapproved orders) on the application desktop.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
7.</td>
<td><strong>Source document tracking</strong></td>
<td>
<ul>
<li>Record whether signed originals of outgoing or incoming documents are available.</li>
<li>Store current states of source document originals for each print form, or one general state of a document.</li>
<li>Work with a customized list of states that might be required in accounting.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>Yes</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
<tr>
<td>
8.</td>
<td><strong>Message templates</strong></td>
<td>
<ul>
<li>Send emails and text messages generated on the basis of catalogs or documents according to prearranged message templates.</li>
<li>Develop message templates for emails and text messages.</li>
<li>Use the API to send standard notifications as emails and text messages created from templates.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>Yes</strong></td>
</tr>
</tbody>
</table>
## Master data and classifiers
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Key features</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td></td>
</tr>
<tr>
<td>
1.</td>
<td><strong>Banks</strong></td>
<td>
<ul>
<li>Store and provide access to the bank classifier to be used in other application subsystems.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Currencies</strong></td>
<td>
<ul>
<li>Store and provide access to the currency list and exchange rates.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Work schedules</strong></td>
<td>
<ul>
<li>Store calendar schedules that are used in the enterprise.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Calendar schedules</strong></td>
<td>
<ul>
<li>Store business calendars that are used in the enterprise.</li>
<li>Get a date that comes after the specified number of days in the specified calendar, and use other API functionality.</li>
</ul>SaaS mode: <strong>Yes</strong><br>
Hosted mode: <strong>Yes</strong><br>
External users: <strong>No</strong><br>
Deep integration: <strong>No</strong></td>
</tr>
</tbody>
</table>
## Service subsystems
| <strong>#</strong> | <strong>Subsystem</strong> | <strong>Key features</strong> |
|---|---|---|
| <ol class="n"><li></li></ol> | <strong>Object versioning</strong> | <ul><li>Store and view the history of changes in catalogs and documents (the user who made the changes, the change time and the nature of change up to object attributes and attributes of its tables).</li><li>Compare object versions.</li><li>View previously saved object versions and roll back to them.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Export to files</strong> | <ul><li>Export of documents and catalogs attached to the <strong>Print</strong> subsystem. (When integrated together with the Print subsystem.)</li><li>Send export files by email, save them to a local computer, or as attachments in the application (when integrated together with the <strong>Print</strong> and <strong>File management</strong> subsystem).</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>Yes</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Bulk edit</strong> | <ul><li>Enable bulk modification of object attributes and tables (for catalogs, documents, and other objects).</li><li>Modify additional attributes and information records.</li><li>Perform operations considering the predefined rules that prohibit editing object attributes.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Period-end closing dates</strong> | <ul><li>Prohibit changes to any data (such as documents, register records, and catalog items) that was entered before the specified date.</li><li>Use various options to set up period-end closing dates: one date for all documents, or different dates for specific accounting sections or objects.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>Yes</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Notes</strong> | <ul><li>Electronically replace stickers on the edges of the monitor that can be used without closing your application window.</li><li>Access the quick list of notes on your desktop, list of notes on the subject, and the common list.</li><li>Select various colors and design of note text, insert pictures into notes.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>No</strong> |
| <ol class="n"><li></li></ol> | <strong>Personal data protection</strong> | <ul><li>Supports the requirements of Federal Law No. 152-FZ ("On personal data").</li><li>Manage events of access to personal data (set event usage, get relevant status of using events, and prepare system setting form).</li><li>Classify personal data by categories.</li><li>Register consents to personal data processing.</li><li>Destroy personal subject data.</li></ul>SaaS mode: <strong>No</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>No</strong> |
| <ol class="n"><li></li></ol> | <strong>Startup notifications</strong> | <ul><li>Display various information (for example, advertisements) on application startup.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>Yes</strong><br>Deep integration: <strong>No</strong> |
| <ol class="n"><li></li></ol> | <strong>Formula editor</strong> | <ul><li>Use the API and a ready-to-use workspace to edit formulas with an arbitrary set of operands and operators.</li><li>Use the API to display hierarchical field lists on the form. For example, a list of available fields when adding filters in the report settings.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>Yes</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Contact information</strong> | <ul><li>Add contact information attributes to catalogs and documents (such as postal addresses, email addresses, or phone numbers).</li><li>Provide access to the country classifier.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Data integrity</strong> | <ul><li>Monitor infobase data integrity by arbitrary applied rules.</li><li>Display detected issues and ways to fix them for various user categories.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>User reminders</strong> | <ul><li>Add personal reminders that appear at scheduled time.</li><li>Link reminders to catalogs, documents, and conversations.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>No</strong> |
| <ol class="n"><li></li></ol> | <strong>Item order</strong> | <ul><li>Order lists using the <strong>Up</strong> and <strong>Down</strong> buttons.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Print tools</strong> | <ul><li>Use the API and a ready-to-use workspace to generate print forms for catalogs and documents.</li><li>Output print forms as spreadsheet documents or Office Open XML (.docx) documents.</li><li>Send print forms by email, save them to a local computer or as attachments in the application (when integrated together with the <strong>File management</strong> subsystem).</li><li>Attach external print forms to the application and print them together with built-in print forms (when integrated together with the <strong>Additional reports and data processors</strong> subsystem).</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>Yes</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Full-text search</strong> | <ul><li>Configure and run full-text search through all application data.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>No</strong> |
| <ol class="n"><li></li></ol> | <strong>Licensed update verification</strong> | <ul><li>Use the API and user interface to check whether a configuration update was obtained legally.</li></ul>SaaS mode: <strong>No</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>No</strong> |
| <ol class="n"><li></li></ol> | <strong>Properties</strong> | <ul><li>Add custom properties to documents and catalogs.</li><li>Display property values in reports and dynamic lists.</li><li>Store properties separately in an object (additional attributes and marks) and outside of an object owner in a separate information register (additional information records).</li><li>Add identical properties for different objects, mark added properties as required ones, and use other service features. </li><li>Mark catalogs and documents with multi-colored label icons and filter the list by labels.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>Yes/No</strong> |
| <ol class="n"><li></li></ol> | <strong>Declension tool</strong> | <ul><li>Automatically decline object presentations with available manual user correction.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>Yes</strong><br>Deep integration: <strong>Yes</strong> |
| <ol class="n"><li></li></ol> | <strong>Hierarchy</strong> | <ul><li>Display information on parent and child documents, catalogs, and charts of characteristic types for a selected object, and also display the entire structure of their dependencies.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>No</strong> |
| <ol class="n"><li></li></ol> | <strong>Digital signature</strong> | <ul><li>Use the API and user interface to work with cryptography tools: digital signature and signature verification.</li></ul>SaaS mode: <strong>Yes</strong><br>Hosted mode: <strong>Yes</strong><br>External users: <strong>No</strong><br>Deep integration: <strong>Yes</strong> |
# Chapter 2. Library integration guide
*** ** * ** ***
First-time integration of the library subsystems into a configuration significantly differs from updating an integrated library. Generally, the library integration consists of the following steps:
<ol>
<li><a href="#перенос-объектов-метаданных-из-файла-поставки-библиотеки-в-конфигурацию">Copying metadata objects from the library distribution file to the configuration</a>.</li>
<li><a href="#настройка-объектов-библиотеки">Configuring the copied library objects</a>.</li>
<li><a href="#использование-в-конфигурации">Using the library objects in configuration development</a>.</li>
</ol>
All functional subsystems included in the library are subordinate to the **Standard subsystems** subsystem in the metadata object tree of Designer. The subsystems designed for SaaS configurations are subordinate to the **SaaS** subsystem.
For the first-time integration of the library, use the `FirstSSLDeployment.epf` external data processor. You can use it to select subsystems for integration while preserving their reference integrity, and exclude unused subsystems. To validate the first SSL integration or further library version updates, use the `SSLImplementationCheck.erf` external report <a href="#прим1_1">[1]</a>. It identifies a variety of common problems related to library integration (type composition filling validation, checks for code inserts, and so on).
To quickly start the development of a new configuration based on the library, you can use the <a href="#быстрое-начало-разработки-с-нуля">quick start guide</a> containing only the essential actions required to start the configuration.
> <a name="прим1_1">[1]</a> In client/server mode, ensure that the user who started the **1C:Enterprise** server has sufficient rights to run this report.
## Copying metadata objects from the library distribution file to the configuration
### First-time integration
To copy library objects to the configuration during the first-time integration, in **Designer**, click **Configuration** – **Compare and merge with configuration from file.** In the dialog box, specify the library distribution file and confirm enrollment for support.
**Step 1**. In the configuration comparison and merging window, clear all check boxes and select all objects to be copied using the **Actions** – **Select by file subsystems** command. In the `StandardSubsystems` subsystem group, select the following:<a href="#прим2_1">[1]</a>
<ul>
<li>Required subsystems, as described in Table 2.1.</li>
<li>Additional subsystems required for SaaS configurations, as described in Table 2.2.</li>
<li>Other subsystems to be integrated into the configuration.</li>
<li>Subsystems required by the subsystems you selected, as described in Tables 2.1 to 2.3. <a href="#прим2_2">[2]</a></li>
</ul>
Click **Set**.
> **Notice:**
>
> Ensure that all required subsystems listed in Table 2.1 are selected. If the configuration is designed to run in SaaS mode, the subsystems listed in Table 2.2 are also required. Otherwise, the configuration will not work.
>
> <a name="прим2_1">[1]</a> Do not select subsystems that are not in the `StandardSubsystems` subsystem group. For example, the `Administration` subsystem.
>
> <a name="прим2_2">[2]</a> To get the file with comparison and merging settings for this operation, use the `FirstSSLDeployment.epf` data processor.
**Step 2**. Select or clear the check boxes for individual library objects and their properties as described in Table 2.5.
Next, click **Actions** – **Set rule for all** and select the **Get from file** merge rule, then click **Execute**. In the window with the list of dependent objects, click **Continue**.
> You might want to first save the configured comparison and merging settings to a file in case you have to repeat this step.
**Step 3**. Once the comparison and merging are complete, the second stage begins: <a href="#настройка-объектов-библиотеки">Configuring library objects</a>. Depending on the number of subsystems, this step can take from one to several hours.
After you configure the library objects, it is recommended that you validate the integration using the `SSLImplementationCheck.erf` external report.
### Updating library version
This section describes the general procedure of updating the library to a later version. The **updateSSL.htm** document included in the library describes the specifics of updating each library version. Migration between library major versions, minor versions, and revisions (the first, second, and third numbers in the full version number) requires some additional action, while migration between library patch releases (the fourth number) generally requires no additional action. Rarely, additional actions are required even when updating to a patch release. Instructions for these situations are available both in **updateSSL.htm** and **readme.txt** (the **Important** section).
To update library version, click **Configuration – Support – Update configuration**. In the dialog box, click **Select update file**, specify the path to the library distribution file, and confirm that you want to update the vendor configuration.
**Step 1**. Some of the library objects referenced by the objects of your configuration might have been deleted from the new library version. To have these library objects deleted automatically, clear the references to them before the update. To find such objects in the configuration comparison and merging window, clear all the check boxes for metadata objects, then set the comparison and merging filter to **Show objects available only in the old vendor configuration** in the **New vendor configuration – Old vendor configuration** group as indicated in the picture.
Next, select the check boxes for all metadata objects, select the **Get from new vendor configuration** merge rule (**Actions** – **Set rule for all**), and click **Actions** – **Find unresolved references to objects to be deleted**.
After the operation is completed, you can see the list of configuration objects that contain references to the library objects to be deleted. If there are any application objects in the list, remove the references to the library objects to be deleted from these application objects, and proceed to step 2.
**Step 2**. Run the **Configuration** – **Support** – **Update configuration** command again. Click **Select update file** and specify the path to the library distribution file.
In the configuration comparison and merging window, clear all check boxes and then select the objects to be copied using the **Actions** – **Select by new vendor configuration subsystems** command. In the `StandardSubsystems` subsystem group, select the following:<a href="#прим2_3">[3]</a>
<ul>
<li>Required subsystems, as described in Table 2.1.</li>
<li>Additional subsystems required for SaaS configurations, as described in Table 2.2.</li>
<li>All previously integrated subsystems and other subsystems that you want to integrate.</li>
<li>Subsystems required by the selected subsystems, as described in Tables 2.1 to 2.3.</li>
</ul>
Click **Set**.
> **Notice:**
>
> Ensure that all required subsystems listed in table 2.1 and the related metadata objects are selected. If the configuration is designed to run in SaaS mode, the subsystems listed in Table 2.2 are also required. Otherwise, the configuration will not work.
>
> <a name="прим2_3">[3]</a> Do not select subsystems that are not in the `StandardSubsystems` subsystem group. For example, the `Administration` subsystem.
If the **Administration** subsystem was integrated or is planned for integration, in the configuration comparison and merging window, select the check box for this subsystem ("subsystem" metadata object).
Click **Actions** – **Set rule for all** and select the **Get from new vendor configuration** merge rule.
Select or clear the check boxes for individual library objects and their properties as described in Table 2.6. Depending on the number of subsystems to update or install, this step can take from 15 minutes to one hour.
Then mark all obsolete metadata objects in the library for deletion. Set the comparison and merging filter to **Show objects available only in the old vendor configuration** in the **New vendor configuration** – **Old vendor configuration** group as indicated in the picture.
Then select the check boxes for all metadata objects and click **Execute**. In the window with the list of dependent objects, click **Continue**.
> You might want to first save the configured comparison and merging settings to a file in case you have to repeat this step.
Updating to patch releases can be automated to a greater degree, which saves time during regular (for example, weekly) updates. Library patch releases differ only in the fourth number of the full version number, for example: 2.3.4.**1**, 2.3.4.**2**, 2.3.4.**3**.
For the purpose of updating to patch releases, use the `UpdateToCorrectiveVersionSSL.epf` external data processor.
Start the data processor in the infobase with the configuration containing the previous library release, click **Update to corrective version**, and specify the .cf file with the new library version from the distribution package. The configuration will be automatically compared and merged with the new library configuration using the following rules: all built-in library objects will be copied, and objects overridden during integration will be merged prioritizing new vendor configuration (for example, type collections) or skipped (for example, overridable modules). After comparison and merging, the database configuration will not be updated automatically, which allows you to run a comparison with the database configuration and edit the changed objects: overridable modules, local fixes, and enhancements.
After the update, follow the instructions in the **Migrating from test versions** section or the **Migrating from previous versions** section of the UpdateSSL file if any.
Alternately, click **Generate a settings file** to generate a comparison and merging settings file that can be imported into Designer for manual comparison and merging.
When updating to new functional releases (releases with the third number incremented), select the checkboxes in the comparison and merging window in Designer following the instructions above.
**Step 3**. Once the comparison and merging are complete, the second stage begins: <a href="#настройка-объектов-библиотеки">Configuring library objects</a>. Pay particular attention to updating overridable modules (see the **Common modules** section).
After you configure the library objects, it is recommended that you validate the integration using the `SSLImplementationCheck.erf` external report.
### Library subsystem dependencies
#### Table 2.1. Subsystems required for integration
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Depends on</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Core</strong></td>
<td><strong>Security profiles</strong> <a href="#прим3_1">[1]</a></td>
</tr>
<tr>
<td>
2.</td>
<td colspan="2"><strong>Infobase version update</strong></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Users</strong></td>
<td><strong>Contact information</strong> <a href="#прим3_2">[2]</a></td>
</tr>
</tbody>
</table>
><a name="прим3_1">[1]</a> When integrating the **Core** subsystem without the **Security profiles** subsystem, follow the additional guidelines in the <a href="#особые-случаи-внедрения-подсистемы">Special cases of integration</a> section in Chapter 3.
><a name="прим3_2">[2]</a> When integrating the **Users** subsystem into a SaaS configuration, the **Contact information** subsystem is required. In other scenarios the subsystem is optional and can be integrated separately. For integration without this subsystem, see <a href="#особые-случаи-внедрения-подсистемы">Special cases of integration</a> in Chapter 3.
#### Table 2.2. Additional subsystems required for SaaS configurations
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Subordinate subsystem in the branch</strong></th>
<th><strong>Depends on</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>SaaS</strong></td>
<td colspan="2"><strong>Core SaaS</strong></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>SaaS</strong></td>
<td><strong>Infobase version update SaaS</strong></td>
<td><strong>User sessions</strong></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>SaaS</strong></td>
<td colspan="2"><strong>Users SaaS</strong></td>
</tr>
</tbody>
</table>
#### Table 2.3. Optional subsystems that allow selective integration
| <strong>#</strong> | <strong>Subsystem</strong> | <strong>Depends on</strong> |
|---|---|---|
| 1. | <strong>Surveys</strong> | <strong>Item order</strong><br><strong>Attachable commands</strong> |
| 2. | <strong>Banks</strong> | <strong>Online support library</strong> – <strong>Classifier management</strong> <a href="#прим4_1">[1]</a> <a href="#прим4_2">[2]</a><br><strong>Contact information</strong> <a href="#прим4_1">[1]</a> |
| 3. | <strong>Business processes and tasks</strong> | <strong>Email management</strong> <a href="#прим4_1">[1]</a><br><strong>Access management</strong> <a href="#прим4_1">[1]</a> |
| 4. | <strong>Currencies</strong> | <strong>Network download</strong><br><strong>Online Support Library</strong> – <strong>Classifiers</strong> <a href="#прим4_1">[1]</a> <a href="#прим4_2">[2]</a><br><strong>Formula editor</strong> <a href="#прим4_1">[1]</a> |
| 5. | <strong>Report options</strong> | <strong>Formula editor</strong><br><strong>Email management</strong> <a href="#прим4_1">[1]</a><br><strong>Attachable commands</strong> <a href="#прим4_1">[1]</a><br><strong>Additional reports and data processors</strong> <a href="#прим4_1">[1]</a><br><strong>Report distribution</strong> <a href="#прим4_1">[1]</a><br><strong>Conversations</strong> <a href="#прим4_1">[1]</a> |
| 6. | <strong>Object versioning</strong> ||
| 7. | <strong>Business interactions</strong> | <strong>Contact information</strong><br><strong>Item order</strong><br><strong>Text messaging</strong><br><strong>Attachable commands</strong> <br><strong>Full-text search</strong><br><strong>File management</strong><br><strong>Email management</strong><br><strong>Properties</strong> <a href="#прим4_1">[1]</a> |
| 8. | <strong>Add-ins</strong> | <strong>Online Support Library</strong> – <strong>Get add-ins</strong> <a href="#прим4_1">[1]</a> <a href="#прим4_2">[2]</a> |
| 9. | <strong>Export to files</strong> | <strong>File management</strong> <a href="#прим4_1">[1]</a><br><strong>Email management</strong> <a href="#прим4_1">[1]</a><br><strong>Print</strong> <a href="#прим4_4">[4]</a><br><strong>Attachable commands</strong> <a href="#прим4_4">[4]</a><br><strong>Formula editor</strong> <a href="#прим4_4">[4]</a> |
| 10. | <strong>Barcode generation</strong> | <strong>Add-ins</strong> <a href="#прим4_1">[1]</a> |
| 11. | <strong>Work schedules</strong> | <strong>Calendar schedules</strong> |
| 12. | <strong>Bulk edit</strong> ||
| 13. | <strong>Period-end closing dates</strong> ||
| 14. | <strong>Additional reports and data processors</strong> | <strong>Print tools</strong> <a href="#прим4_1">[1]</a><br><strong>Attachable commands</strong><br><strong>Report options</strong> <a href="#прим4_1">[1]</a><br><strong>Bulk edit</strong> <a href="#прим4_1">[1]</a> <a href="#прим4_2">[2]</a> |
| 15. | <strong>User sessions</strong> ||
| 16. | <strong>Import data from spreadsheets</strong> | <strong>Additional reports and data processors</strong> <a href="#прим4_1">[1]</a><br><strong>Bulk edit</strong> <a href="#прим4_1">[1]</a> |
| 17. | <strong>Notes</strong> ||
| 18. | <strong>Object attribute lock</strong> | <strong>Duplicate cleaner</strong> <a href="#прим4_1">[1]</a> |
| 19. | <strong>Personal data protection</strong> | <strong>Print tools</strong><br><strong>Attachable commands</strong><br><strong>Properties</strong> <a href="#прим4_1">[1]</a> |
| 20. | <strong>OData interface</strong> ||
| 21. | <strong>Startup notifications</strong> ||
| 22. | <strong>Calendar schedules</strong> ||
| 23. | <strong>Formula editor</strong> ||
| 24. | <strong>Contact information</strong> | <strong>Item order</strong><br><strong>Attachable commands</strong><br>Online Support Library – <strong>Classifiers</strong> <a href="#прим4_1">[1]</a> |
| 25. | <strong>Data integrity</strong> | <strong>Report options</strong><br><strong>Attachable commands</strong><br><strong>To-do list</strong> <a href="#прим4_1">[1]</a> |
| 26. | <strong>National language support</strong> ||
| 27. | <strong>NationalLanguageSupport.TextTranslation</strong> | <strong>Network download</strong> |
| 28. | <strong>User reminders</strong> | <strong>Attachable commands</strong> <a href="#прим4_1">[1]</a> |
| 29. | <strong>Item order</strong> ||
| 30. | <strong>Application settings</strong> | <strong>All subsystems</strong> <a href="#прим4_1">[1]</a> |
| 31. | <strong>Data exchange</strong> | <strong>Configuration update</strong> <a href="#прим4_1">[1]</a><br><strong>Network download</strong> <a href="#прим4_1">[1]</a><br><strong>Object prefixes</strong> <a href="#прим4_1">[1]</a><br><strong>Email management</strong> <a href="#прим4_1">[1]</a><br><strong>Scheduled jobs</strong> <a href="#прим4_1">[1]</a> <a href="#прим4_2">[2]</a> <a href="#прим4_3">[3]</a> |
| 32. | <strong>Configuration update</strong> | <strong>User sessions</strong><br><strong>Email management</strong> <a href="#прим4_1">[1]</a><br><strong>Licensed update verification</strong> <a href="#прим4_1">[1]</a> |
| 33. | <strong>Conversations</strong> ||
| 34. | <strong>Text messaging</strong> | <strong>Network download</strong> |
| 35. | <strong>Document record history</strong> | <strong>Report options</strong> <br><strong>Attachable commands</strong> |
| 36. | <strong>Performance monitor</strong> ||
| 37. | <strong>Print tools</strong> | <a href="#прим4_4">[4]</a><br><strong>Formula editor</strong><br><strong>Attachable commands</strong><br><strong>Email management</strong> <a href="#прим4_1">[1]</a><br><strong>File management</strong> <a href="#прим4_1">[1]</a><br><strong>Additional reports and data processors</strong> <a href="#прим4_1">[1]</a> |
| 38. | <strong>Attachable commands</strong> | <strong>Print tools</strong> <a href="#прим4_1">[1]</a><br><strong>Report options</strong> <a href="#прим4_1">[1]</a><br><strong>Additional reports and data processors</strong> <a href="#прим4_1">[1]</a> |
| 39. | <strong>Duplicate cleaner</strong> ||
| 40. | <strong>Full-text search</strong> ||
| 41. | <strong>Network download</strong> ||
| 42. | <strong>Object prefixes</strong> ||
| 43. | <strong>Licensed update verification</strong> ||
| 44. | <strong>Security profiles</strong> ||
| 45. | <strong>Email management</strong> ||
| 46. | <strong>File management</strong> | <strong>Properties</strong> <a href="#прим4_1">[1]</a><br><strong>Access management</strong> <a href="#прим4_1">[1]</a> |
| 47. | <strong>Report distribution</strong> | <strong>Report options</strong><br><strong>Business interactions</strong> <a href="#прим4_1">[1]</a><br><strong>Additional reports and data processors</strong> <a href="#прим4_1">[1]</a><br><strong>Contact information</strong><br><strong>Text messaging</strong> <a href="#прим4_1">[1]</a><br><strong>Print tools</strong> <a href="#прим4_1">[1]</a><br><strong>Attachable commands</strong> <a href="#прим4_1">[1]</a><br><strong>Network download</strong> <a href="#прим4_1">[1]</a><br><strong>Email management</strong><br><strong>File management</strong> <a href="#прим4_1">[1]</a><br><strong>Access management</strong> <a href="#прим4_1">[1]</a><br><strong>Digital signature</strong> <a href="#прим4_1">[1]</a><br><strong>Bulk edit</strong> <a href="#прим4_1">[1]</a> |
| 48. | <strong>Scheduled jobs</strong> ||
| 49. | <strong>Infobase backup</strong> | <strong>User sessions</strong> |
| 50. | <strong>Properties</strong> | <strong>Object attribute lock</strong> |
| 51. | <strong>Declension tool</strong> | <strong>Network download</strong> <a href="#прим4_1">[1]</a> |
| 52. | <strong>Hierarchy</strong> ||
| 53. | <strong>To-do list</strong> ||
| 54. | <strong>Marked object deletion</strong> ||
| 55. | <strong>Access management</strong> | <a href="#прим4_2">[2]</a> |
| 56. | <strong>Totals and aggregates</strong> ||
| 57. | <strong>Monitoring center</strong> | <strong>Performance monitor</strong> <a href="#прим4_1">[1]</a> |
| 58. | <strong>Source document tracking</strong> | <strong>Item order</strong> <a href="#прим4_1">[1]</a><br><strong>Attachable commands</strong> <a href="#прим4_1">[1]</a><br><strong>Print tools</strong> <a href="#прим4_1">[1]</a> |
| 59. | <strong>Message templates</strong> | <strong>Business interactions</strong> <a href="#прим4_1">[1]</a><br><strong>Text messaging</strong> <a href="#прим4_1">[1]</a><br><strong>Print tools</strong> <a href="#прим4_1">[1]</a><br><strong>Email management</strong> <a href="#прим4_1">[1]</a> |
| 60. | <strong>Digital signature</strong> | <strong>Contact information</strong> <a href="#прим4_1">[1]</a><br><strong>User reminders</strong> <a href="#прим4_1">[1]</a><br><strong>Print tools</strong> <a href="#прим4_1">[1]</a><br><strong>Network download</strong> <a href="#прим4_1">[1]</a> |
><a name="прим4_1">[1]</a> Optional dependency, meaning that the subsystem can be integrated separately. Chapter 3 can contain additional guidelines on independent integration of the subsystem.
>
><a name="прим4_2">[2]</a> When integrating subsystems into a SaaS configuration, also integrate the subsystem with the same name and `SaaS` postfix from the **SaaS** parent subsystem. For example, when integrating the **Currencies** subsystem, integrate the **Currencies SaaS** subsystem as well.
>
><a name="прим4_3">[3]</a> The **Data exchange** subsystem is required for the development of data exchange in a distributed infobase.
>
><a name="прим4_4">[4]</a> When integrating subsystems into a configuration designed for multiple languages, also integrate the subsystem with the same name from the **National language support** parent subsystem.
#### Table 2.4. Optional subsystems that can be integrated into SaaS configurations
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Subordinate subsystem in the branch</strong></th>
<th><strong>Depends on</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>SaaS</strong></td>
<td><strong>Add-ins SaaS</strong></td>
<td><strong>Add-ins</strong></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>SaaS</strong></td>
<td><strong>Additional reports and data processors SaaS</strong></td>
<td><strong>Additional reports and data processors</strong></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>SaaS</strong></td>
<td><strong>File management SaaS</strong></td>
<td><strong>File management</strong></td>
</tr>
<tr>
<td>
4.</td>
<td><strong>SaaS</strong></td>
<td><strong>Access management SaaS</strong></td>
<td><strong>Access management</strong></td>
</tr>
</tbody>
</table>
### Objects and object properties to be selected or cleared before merging the configuration with the library
#### Table 2.5. Objects and object properties to be selected or cleared before merging the configuration with the library (during the first-time integration of the subsystem)
| **#** | **Subsystem** | **All branch subsystems** | **Action required** | **Note** |
|-------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1. | **Core** | The **Properties** item of the root configuration object:<br><ul><li>**Default roles**</li><li>**Application module**</li><li>**Session module**</li><li>**External connection module**</li><li>**Ordinary application module**</li><li>**Modality usage mode**</li><li>**Interface compatibility mode**</li><li>**Compatibility mode**</li></ul> | Select the check box. | Application module refers to managed and ordinary application modules if they are available in the metadata tree in the configuration comparison and merging window. |
| 2. | **Core** | The **Properties** item of the root configuration object:<br/><ul><li>**Synchronous call usage mode for platform extensions and add-ins**</li></ul> | Select the check box. | When integrating the library without the **File management**, **Configuration update**, and **Infobase backup** subsystems, selecting this check box is not required |
| 3. | **Core** | Other properties of the root configuration object | Clear the check box. | |
| 4. | **Application settings** | Subsystem: **Administration**. | Select the check box. | Only for the subsystem, not for the subsystem content. |
| 5. | **Application settings** | Common commands:<br/><ul><li>`AdditionalDataProcessorsAdministration`</li><li>`AdditionalReportsAdministration`</li></ul> | Clear the check box. | Only when integrating without the **Additional reports and data processors** subsystem. |
| 6. | **Application settings** | Common command: `ReportPanelAdministration`. | Clear the check box. | <ul><li>Only when integrating without the **Report options** subsystem.</li><li>Only when integrating without the **Object prefixes** subsystem.</li></ul> |
| 7. | **Attachable commands** | Subsystem: `AttachableReportsAndDataProcessors`. | | Select the check box (only for the subsystem, not for the subsystem content). |
<br />
#### Table 2.6. Objects and object properties to be selected or cleared before merging the configuration with the library (during the subsystem update)
##### Configuration properties
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Core</strong></td>
<td>
<ul>
<li>The <strong>Properties</strong> item of the root configuration object.</li>
</ul></td>
<td>Clear the check box.</td>
</tr>
</tbody>
</table>
##### Subsystems
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Application settings</strong></td>
<td>
<ul>
<li><code>Administration</code></li>
</ul></td>
<td>For the <strong>Command interface</strong> and <strong>Content</strong> properties, set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Attachable commands</strong></td>
<td>
<ul>
<li><code>AttachableReportsAndDataProcessors</code></li>
</ul></td>
<td>For the <strong>Command interface</strong> and <strong>Content</strong> properties, set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
</tbody>
</table>
##### Common modules
Clear the check box for all overridable common modules:
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Common module</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Core</strong></td>
<td>
<ul>
<li><code>NationalLanguageSupportOverridable</code></li>
<li><code>CommonClientOverridable</code></li>
<li><code>CommonOverridable</code></li>
<li><code>ConfigurationSubsystemsOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Banks</strong></td>
<td>
<ul>
<li><code>BankManagerOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Business processes and tasks</strong></td>
<td>
<ul>
<li><code>BusinessProcessesAndTasksClientOverridable</code></li>
<li><code>BusinessProcessesAndTasksOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Report options</strong></td>
<td>
<ul>
<li><code>ReportsOptionsOverridable</code></li>
<li><code>ReportsClientOverridable</code></li>
<li><code>ReportsOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
5.</td>
<td><strong>Business interactions</strong></td>
<td>
<ul>
<li><code>InteractionsClientOverridable</code></li>
<li><code>InteractionsClientServerOverridable</code></li>
<li><code>InteractionsOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
6.</td>
<td><strong>Currencies</strong></td>
<td>
<ul>
<li><code>CurrencyRateOperationsOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
7.</td>
<td><strong>Bulk edit</strong></td>
<td>
<ul>
<li><code>BatchEditObjectsOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
8.</td>
<td><strong>Period-end closing dates</strong></td>
<td>
<ul>
<li><code>PeriodClosingDatesOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
9.</td>
<td><strong>Additional reports and data processors</strong></td>
<td>
<ul>
<li><code>AdditionalReportsAndDataProcessorsOverridable</code></li>
<li><code>AdditionalReportsAndDataProcessorsClientOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
10.</td>
<td><strong>Object attribute lock</strong></td>
<td>
<ul>
<li><code>ObjectAttributesLockOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
11.</td>
<td><strong>Personal data protection</strong></td>
<td>
<ul>
<li><code>PersonalDataProtectionOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
12.</td>
<td><strong>Startup notifications</strong></td>
<td>
<ul>
<li><code>InformationOnStartOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
13.</td>
<td><strong>Calendar schedules</strong></td>
<td>
<ul>
<li><code>CalendarSchedulesOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
14.</td>
<td><strong>Data integrity</strong></td>
<td>
<ul>
<li><code>AccountingAuditOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
15.</td>
<td><strong>National language support</strong></td>
<td>
<ul>
<li><code>NationalLanguageSupportOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
16.</td>
<td><strong>User reminders</strong></td>
<td>
<ul>
<li><code>UserRemindersOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
17.</td>
<td><strong>Application settings</strong></td>
<td>
<ul>
<li><code>ApplicationSettingsOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
18.</td>
<td><strong>Data exchange</strong></td>
<td>
<ul>
<li><code>DataExchangeOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
19.</td>
<td><strong>Infobase version update</strong></td>
<td>
<ul>
<li><code>InfobaseUpdateClientOverridable</code></li>
<li><code>InfobaseUpdateOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
20.</td>
<td><strong>Text messaging</strong></td>
<td>
<ul>
<li><code>SendSMSMessageOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
21.</td>
<td><strong>Print tools</strong></td>
<td>
<ul>
<li><code>PrintManagementClientOverridable</code></li>
<li><code>PrintManagementOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
22.</td>
<td><strong>Attachable commands</strong></td>
<td>
<ul>
<li><code>ObjectsFillingOverridable</code></li>
<li><code>AttachableCommandsOverridable</code></li>
<li><code>GenerateFromOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
23.</td>
<td><strong>Duplicate cleaner</strong></td>
<td>
<ul>
<li><code>DuplicateObjectsDetectionOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
24.</td>
<td><strong>Full-text search</strong></td>
<td>
<ul>
<li><code>FullTextSearchServerOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
25.</td>
<td><strong>Users</strong></td>
<td>
<ul>
<li><code>UsersOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
26.</td>
<td><strong>Object prefixes</strong></td>
<td>
<ul>
<li><code>ObjectsPrefixesClientServerOverridable</code></li>
<li><code>ObjectsPrefixesOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
27.</td>
<td><strong>SaaS</strong></td>
<td>
<ul>
<li><code>DataExchangeSaaSOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
28.</td>
<td><strong>Email management</strong></td>
<td>
<ul>
<li><code>EmailOperationsOverridable</code></li>
<li><code>EmailOperationsClientOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
29.</td>
<td><strong>File management</strong></td>
<td>
<ul>
<li><code>FilesOperationsClientOverridable</code></li>
<li><code>FilesOperationsOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
30.</td>
<td><strong>Report distribution</strong></td>
<td>
<ul>
<li><code>ReportMailingClientOverridable</code></li>
<li><code>ReportMailingOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
31.</td>
<td><strong>Scheduled jobs</strong></td>
<td>
<ul>
<li><code>ScheduledJobsOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
32.</td>
<td><strong>Infobase backup</strong></td>
<td>
<ul>
<li><code>IBBackupClientOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
33.</td>
<td><strong>Properties</strong></td>
<td>
<ul>
<li><code>PropertyManagerOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
34.</td>
<td><strong>Hierarchy</strong></td>
<td>
<ul>
<li><code>SubordinationStructureOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
35.</td>
<td><strong>To-do list</strong></td>
<td>
<ul>
<li><code>ToDoListOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
36.</td>
<td><strong>Access management</strong></td>
<td>
<ul>
<li><code>AccessManagementOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
37.</td>
<td><strong>Source document tracking</strong></td>
<td>
<ul>
<li><code>SourceDocumentsOriginalsRecordingClientOverridable</code></li>
<li><code>SourceDocumentsOriginalsRecordingOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
38.</td>
<td><strong>Monitoring center</strong></td>
<td>
<ul>
<li><code>MonitoringCenterOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
39.</td>
<td><strong>Message templates</strong></td>
<td>
<ul>
<li><code>MessageTemplatesOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
40.</td>
<td><strong>Digital signature</strong></td>
<td>
<ul>
<li><code>ApplicationForACertificateOverridable</code></li>
<li><code>DigitalSignatureClientOverridable</code></li>
<li><code>DigitalSignatureOverridable</code></li>
</ul></td>
</tr>
<tr>
<td>
41.</td>
<td><strong>DSS service digital signature</strong></td>
<td>
<ul>
<li><code>DSSCryptographyServiceOverridable</code></li>
</ul></td>
</tr>
</tbody>
</table>
##### Roles
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Report options</strong></td>
<td>
<ul>
<li><code>FullAccess</code></li>
<li><code>SystemAdministrator</code></li>
</ul></td>
<td>For the <code>Rights</code> property, set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
</tbody>
</table>
##### Common attributes
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>SaaS</strong></td>
<td>
<ul>
<li><code>DataAreaMainData</code></li>
<li><code>DataAreaAuxiliaryData</code></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
</tbody>
</table>
##### Exchange plans
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Infobase version update</strong></td>
<td>
<ul>
<li><code>InfobaseUpdate</code>, property: <code>Content</code>.</li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
</tbody>
</table>
##### Filter criteria
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Hierarchy</strong></td>
<td>
<ul>
<li><code>RelatedDocuments</code>, properties: <code>Type</code> and <code>Content</code></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
</tbody>
</table>
##### Functional options
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Core</strong></td>
<td>
<ul>
<li><code>StandaloneWorkplace</code></li>
<li><code>LocalMode</code></li>
<li><code>SaaSOperations</code></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
</tbody>
</table>
##### Type collections
| <strong>#</strong> | <strong>Subsystem</strong> | <strong>Object name</strong> | <strong>Action required</strong> |
|---|---|---|---|
| <ol class="n"><li></li></ol> | <strong>Core</strong> | <ul><li><code>Organization</code></li></ul> | Clear the check box. |
| <ol class="n"><li></li></ol> | <strong>Surveys</strong> | <ul><li><code>Respondent</code></li><li><code>Interviewer</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Core</strong> | <ul><li><code>FunctionalOptionsStorage</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Business processes and tasks</strong> | <ul><li><code>BusinessProcess</code></li><li><code>BusinessProcessObject</code></li><li><code>AddressingObject</code></li><li><code>TaskSubject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Business interactions</strong> | <ul><li><code>InteractionContact</code></li><li><code>InteractionSubject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Object versioning</strong> | <ul><li><code>VersionedData</code></li><li><code>VersionedDataObject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Period-end closing dates</strong> | <ul><li><code>PeriodClosingTarget</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Additional reports and data processors</strong> | <ul><li><code>ObjectWithAdditionalCommands</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Notes</strong> | <ul><li><code>NotesSubject</code></li><li><code>NotesSubjectObject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Personal data protection</strong> | <ul><li><code>PersonalDataSubject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Contact information</strong> | <ul><li><code>ContactInformationOwner</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Data integrity</strong> | <ul><li><code>AccountingChecksContext</code></li><li><code>AccountingCheckContextClarification</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Item order</strong> | <ul><li><code>ObjectWithCustomOrder</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>User reminders</strong> | <ul><li><code>ReminderSubject</code></li><li><code>ReminderSubjectObject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>SaaS</strong> | <ul><li><code>MessagesQueueEndpoint</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Print tools</strong> | <ul><li><code>ObjectWithDefaultPrintForms</code>;</li><li><code>PrintFormsRecipient</code>.</li></ul> | Clear the check box. |
| <ol class="n"><li></li></ol> | <strong>Users</strong> | <ul><li><code>Department</code></li><li><code>Individual</code></li></ul> | Clear the check box. |
| <ol class="n"><li></li></ol> | <strong>Users</strong> | <ul><li><code>User</code></li><li><code>ExternalUser</code></li><li><code>ExternalUserObject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>File management</strong> | <ul><li><code>FilesOwner</code></li><li><code>AttachedFile</code></li><li><code>AttachedFileObject</code></li><li><code>AttachedFilesOwner</code></li><li><code>AttachedFilesOwnerObject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Report distribution</strong> | <ul><li><code>BulkEmailRecipient</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Properties</strong> | <ul><li><code>DetailedInfoOwner</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Declension tool</strong> | <ul><li><code>DeclensionObject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Access management</strong> | <ul><li><code>RightsSettingsOwner</code></li><li><code>RightsSettingsOwnerObject</code></li><li><code>AccessKeysValuesOwner</code></li><li><code>AccessKeysValuesOwnerObject</code></li><li><code>AccessValue</code></li><li><code>AccessValueObject</code></li><li><code>RegisterAccessKeysRegisterField</code></li><li><code>AccessValuesSetsOwnerObject</code></li><li><code>OwnerLimitedByAccessValuesSetsObject</code></li><li><code>ExternalValuesOwnerInAccessValueSetsObject</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Access management</strong> | <ul><li><code>AccessKeysValuesOwnerDocument</code></li><li><code>AccessKeysValuesOwnerRecordSet</code></li><li><code>AccessKeysValuesOwnerCalculationRegisterRecordSet</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.<br><ul><li>If a type collection contains no types after comparison or merging, add the <code>CatalogObject.MetadataObjectIDs</code> type.</li><li>If a type collection contains types other than <code>CatalogObject.MetadataObjectIDs</code> after comparison or merging, remove the <code>CatalogObject.MetadataObjectIDs</code> type.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Source document tracking</strong> | <ul><li><code>ObjectWithSourceDocumentsOriginalsAccounting</code></li></ul> | Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>. |
| <ol class="n"><li></li></ol> | <strong>Source document tracking</strong> | <ul><li><code>Employee</code></li></ul> | Clear the check box. |
| <ol class="n"><li></li></ol> | <strong>Message templates</strong> | <ul><li><code>MessageTemplateSubject</code></li><li><code>MessageTemplateOwner</code></li></ul> | <ul><li>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Digital signature</strong> | <ul><li><code>SignedObject</code></li></ul><code>SignedObject</code></li></ul> | <ul><li>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</li></ul>
##### Common commands
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n"><li></li></ol></td>
<td><strong>Data exchange</strong></td>
<td>Property: <strong>Command parameter type</strong><br>
<ul>
<li><code>Synchronize</code></li>
<li><code>SynchronizeWithAdditionalParameters</code></li>
<li><code>ConnectionSettings</code></li>
<li><code>ImportRulesSet</code></li>
<li><code>ImportObjectConvertionRules</code></li>
<li><code>ImportObjectRegistrationRules</code></li>
<li><code>GetSynchronizationSettingsForOtherApplication</code></li>
<li><code>SynchronizationScenarios</code></li>
<li><code>SendingEvents</code></li>
<li><code>ReceivingEvents</code></li>
<li><code>DataToSendComposition</code></li>
<li><code>DeleteSynchronizationSetting</code></li>
<li><code>CreateInitialImageWithFiles</code></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
<tr>
<td>
<ol class="n"><li></li></ol></td>
<td><strong>Hierarchy</strong></td>
<td>
<ul>
<li><code>RelatedDocuments</code>, property: <strong>Command parameter type</strong></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
<tr>
<td>
<ol class="n"><li></li></ol></td>
<td><strong>Access management</strong></td>
<td>
<ul>
<li><code>SetRights</code>, property: <strong>Command parameter type</strong></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
</tbody>
</table>
##### Languages
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Core</strong></td>
<td>
<ul>
<li><code>English</code></li>
</ul></td>
<td>Select the check box.</td>
<td>If displayed in the metadata tree in the configuration comparison and merging window.</td>
</tr>
</tbody>
</table>
##### Catalogs
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Core</strong></td>
<td>
<ul>
<li><code>MetadataObjectIDs</code>, property: <strong>Predefined</strong></li>
<li><code>ExtensionObjectIDs</code>, property: <strong>Predefined</strong></li>
</ul></td>
<td>Clear the check box.<br>
Once a library is updated, update predefined items using the <strong>SSLImplementationCheck.epf</strong> report in the <strong>Access management</strong> error correction mode. Incorrect predefined items in the <code>MetadataObjectIDs</code> catalog.<br>
For your information: internal IDs of predefined items can be changed without consequences (no data loss). For example, you can delete a predefined item and create a new one with the same name. The predefined item will be linked to a data item correctly.<br>
If a predefined item name (the full metadata object name without a dot) does not match an existing metadata object, this predefined item will not be linked to a data item and will not cause any issues.</td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Business processes and tasks</strong></td>
<td>
<ul>
<li><code>PerformerRoles</code>, property: <strong>Predefined</strong></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Contact information</strong></td>
<td>
<ul>
<li><code>ContactInformationKinds</code>, property: <strong>Predefined</strong></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Users</strong></td>
<td>
<ul>
<li><code>ExternalUsers</code>, command: <code>ExternalAccess</code>, property: <strong>Command parameter type</strong></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Properties</strong></td>
<td>
<ul>
<li><code>AdditionalAttributesAndInfoSets</code>, property: <strong>Predefined</strong></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
<tr>
<td>
5.</td>
<td><strong>Access management</strong></td>
<td>
<ul>
<li><code>AccessGroupProfiles</code>, property: <strong>Predefined</strong></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
<tr>
<td>
6.</td>
<td><strong>Source document tracking</strong></td>
<td>
<ul>
<li><code>SourceDocumentsOriginalsStates</code>, property: <strong>Predefined</strong></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
</tbody>
</table>
##### Enumerations
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Text messaging</strong></td>
<td>
<ul>
<li><code>SMSProviders</code></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
</tbody>
</table>
##### Data processors
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Application settings</strong></td>
<td>
<ul>
<li><code>SSLAdministrationPanel</code></li>
</ul></td>
<td>If forms were modified, clear the check box.</td>
</tr>
</tbody>
</table>
##### Charts of characteristic types
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Surveys</strong></td>
<td>
<ul>
<li><code>QuestionsForSurvey</code>, property: <code>Type</code></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Business processes and tasks</strong></td>
<td>
<ul>
<li><code>TaskAddressingObjects</code>, properties: <code>Predefined</code> and <code>Type</code></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Period-end closing dates</strong></td>
<td>
<ul>
<li><code>PeriodClosingDatesSections</code>, property: <code>Type</code></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Period-end closing dates</strong></td>
<td>
<ul>
<li><code>PeriodClosingDatesSections</code>, property: <code>Predefined</code></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
<tr>
<td>
5.</td>
<td><strong>Properties</strong></td>
<td>
<ul>
<li><code>AdditionalAttributesAndInfo</code>, properties: <code>Predefined</code> and <code>Type</code></li>
</ul></td>
<td>Set <strong>Merge rule</strong> to <strong>Merge prioritizing new vendor configuration</strong>.</td>
</tr>
</tbody>
</table>
##### Business processes
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Business processes and tasks</strong></td>
<td>
<ul>
<li><code>Job</code>, property: <strong>Base On</strong></li>
</ul></td>
<td>Clear the check box.</td>
</tr>
</tbody>
</table>
## Configuring library objects
Right after the comparison and merging, the metadata objects are copied from the library to the configuration but not yet configured. To configure the copied library objects, follow the instructions in Table 2.7.
If different actions are required for the first-time integration of the library and for the update of an already integrated library, the instructions in Table 2.7 are divided into two sections: **First-time integration** and **Library version update**. The root configuration object modules and overridable common modules require special attention because fully automatic update is not available for these modules. General instructions for the first-time setup and update of library objects can be found after Table 2.7.
### Table 2.7. Library objects that require additional actions after comparing and merging the configuration with the library
#### Common objects
| <strong>#</strong> | <strong>Object name</strong> | <strong>Action required</strong> |
|---|---|---|
| <ol class="n"><li></li></ol> | Session module | First-time integration:<br>Copy the entire <code>SessionParametersSetting</code> handler. |
| <ol class="n"><li></li></ol> | Application module (managed and ordinary application modules) | During the initial integration into handlers<ul><li><code>BeforeStart</code></li><li><code>OnStart</code></li><li><code>BeforeExit</code></li><li><code>CollaborationSystemUsersChoiceFormGetProcessing</code></li><li><code>OnGlobalSearch</code></li><li><code>OnSelectGlobalSearchResult</code></li><li><code>OnSelectGlobalSearchResultAction</code></li><li><code>HandleURLNavigation</code></li></ul>Migrate the segments of code enclosed in the following comments:<br><code> // StandardSubsystems… // End StandardSubsystems</code><br><br>Migrate the fragments of code from the region where global variables are defined.<br><br> When updating the library version, move the code fragments related to the integrated subsystems from the library distribution file to the handlers <ul><li><code>BeforeStart</code></li><li><code>OnStart</code></li><li><code>BeforeExit</code></li><li><code>CollaborationSystemUsersChoiceFormGetProcessing</code></li><li><code>OnGlobalSearch</code></li><li><code>OnSelectGlobalSearchResult</code></li><li><code>OnSelectGlobalSearchResultAction</code></li><li><code>HandleURLNavigation</code></li></ul> and the region where global variables are defined:<br> <code> // <SubsystemPath> … // End <SubsystemPath></code> |
| <ol class="n"><li></li></ol> | Property: <strong>Version</strong> | First-time integration: set the property according to the MAJOR.MINOR.REVISION.BUILD format. Each part of the sequence contains at least 1 digit:<br>MAJOR for major version number.<br>MINOR for minor version number.<br>REVISION for revision number.<br>BUILD for build number.<br>Example: 1.0.1.1. For more information, see [Version numbering](http://its.1c.ru/db/v8std#content:-2145783164:hdoc) (in Russian).<br>Increment the version at each update. |
#### Common SSL objects for SaaS configurations
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>SaaS</strong></td>
<td>Common attribute: <code>DataAreaMainData</code></td>
<td>First-time integration:<br>
<ul>
<li>For each object of the resulting configuration that must have the same value in all areas, remove the object from the attribute content.</li>
</ul>During each update:<br>
<ul>
<li>For each library object, open the attribute content and set the <strong>Use</strong> property to the value specified in the library distribution file.</li>
</ul></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>SaaS</strong></td>
<td>Common attribute: <code>DataAreaAuxiliaryData</code></td>
<td>First-time integration:<br>
<ul>
<li>For each object of the resulting configuration that you want to be accessible from sessions with data separation disabled, remove the object from the attribute content.</li>
</ul>During each update:<br>
<ul>
<li>For each library object, open the attribute content and set the <strong>Use</strong> property to the value specified in the library distribution file.</li>
</ul></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>SaaS</strong></td>
<td>Common command: <code>AddServiceUsers</code></td>
<td>Display it in the configuration command interface.</td>
</tr>
<tr>
<td>
4.</td>
<td><strong>SaaS</strong></td>
<td>Type collection: <code>MessagesQueueEndpoint</code></td>
<td>In the <code>Type</code> property, specify the <code>MessagesExchange</code> exchange plan and exclude other data types.</td>
</tr>
<tr>
<td>
5.</td>
<td><strong>SaaS</strong></td>
<td>Scheduled job: <code>DataSynchronizationWithWebApplication</code></td>
<td>First-time integration: define a schedule for scheduled jobs. During each update: do not transfer a schedule from the distribution package.</td>
</tr>
</tbody>
</table>
#### Common modules
It is recommended that you follow the general approach to configuring the overridable common modules:
<ol>
<li><strong>During the first-time configuration</strong> of an overridable common module, read the documentation for its export procedures. If necessary, implement the logic for the export procedures.</li>
<li><strong>During each further update</strong> of an overridable common module, copy the new export procedures and functions from the library distribution file, delete the obsolete ones, and make sure that comments, the number of parameters, and the parameter names of each procedure match their library equivalents. If necessary, implement the logic for the new export procedures, and update the implementation of existing ones if their purpose or parameters were changed in the new version of the library.</li>
</ol>
Subsystem help can contain additional instructions on overridable modules.
#### Roles
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Core</strong></td>
<td>
<ul>
<li><code>BasicAccessSSL</code></li>
<li><code>BasicAccessExternalUserSSL</code></li>
</ul></td>
<td>When integrating with the <strong>Properties</strong> subsystem but without the <strong>Access management</strong> subsystem, follow the instructions in section <a href="#внедрение-подсистем-свойства-и-управление-доступом">How to integrate "Properties" and "Access management" subsystems</a>.</td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Core</strong></td>
<td>
<ul>
<li><code>FullAccess</code></li>
</ul></td>
<td>Clear the following rights for all metadata objects:<br>
<ul>
<li><strong>Interactive delete</strong></li>
<li><strong>Interactive deletion of predefined objects</strong></li>
<li><strong>Interactive deletion mark on predefined objects</strong></li>
<li><strong>Interactive removal of deletion mark from predefined objects</strong></li>
<li><strong>Interactive deletion of marked predefined objects</strong></li>
</ul>When integrating with the <strong>SaaS</strong> subsystem, add rights to all objects of the <code>DataAreaMainData</code> common separator attribute to the roles.<br>
When integrating without the <strong>SaaS</strong> subsystem, add rights to all configuration metadata objects, except for the rights listed above, to the roles.</td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Properties</strong></td>
<td>
<ul>
<li><code>EditAdditionalInfo</code></li>
<li><code>ReadAdditionalInfo</code></li>
</ul></td>
<td>When integrating without the <strong>Access management</strong> subsystem, follow the instructions in section <a href="#внедрение-подсистем-свойства-и-управление-доступом">How to integrate "Properties" and "Access management" subsystems</a>.</td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Personal data protection</strong></td>
<td>
<ul>
<li><code><Roles are not created></code></li>
</ul></td>
<td>Implement roles providing access to objects:<br>
<ul>
<li>Document <code>PersonalDataProcessingConsent</code></li>
<li>Document <code>RevocationOfPersonalDataProcessingConsent</code></li>
<li>Information register <code>PersonalDataProcessingConsents</code></li>
</ul>See examples of the <code>_DemoAddEditPersonalDataProcessingConsents</code> and <code>_DemoReadPersonalDataProcessingConsents</code> roles.<br>
For roles that provide access to personal data subjects, add access to the following objects:<br>
<ul>
<li>Information register <code>SubjectsForHidingPersonalData</code>.</li>
</ul></td>
</tr>
</tbody>
</table>
#### Filter criteria
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Hierarchy</strong></td>
<td>
<ul>
<li><code>RelatedDocuments</code></li>
</ul></td>
<td>First-time integration: set the <strong>Content</strong> property and add the types of parent documents, catalogs, and charts of characteristic types to the <code>Type</code> property. Then define the attributes of child documents, catalogs, and charts of characteristic types that will be used to search for the parent objects.</td>
</tr>
</tbody>
</table>
#### Scheduled jobs
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Totals and aggregates</strong></td>
<td>
<ul>
<li><code>UpdateAggregates</code></li>
<li><code>RebuildAggregates</code></li>
<li><code>TotalsPeriodSetup</code></li>
</ul>Property: <strong>Schedule</strong></td>
<td>First-time integration: define a schedule for scheduled jobs. During each update: do not transfer a schedule from the distribution package.</td>
</tr>
<tr>
<td colspan="4"></td>
</tr>
</tbody>
</table>
#### Type collections
| <strong>#</strong> | <strong>Subsystem</strong> | <strong>Object name</strong> | <strong>Action required</strong> |
|---|---|---|---|
| <ol class="n"><li></li></ol> | <strong>Surveys</strong> | <ul><li><code>Respondent</code></li></ul> | First-time integration:<br><ul><li>Select configuration objects to be mapped to questionnaire respondents. For example, <strong>Respondents</strong>, <strong>Employees</strong>, and <strong>Partners</strong> catalogs.</li><li>Add the allowed respondent types to the <code>Type</code> property.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Surveys</strong> | <ul><li><code>Interviewer</code></li></ul> | First-time integration:<br><ul><li>Select configuration objects to be mapped to questionnaire interviewers. For example, the <strong>Users</strong>, <strong>External users</strong>, and <strong>Employees</strong> catalogs.</li><li>Add the allowed interviewer types to the <code>Type</code> property.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Core</strong> | <ul><li><code>Organization</code></li></ul> | First-time integration: if the configuration contains the <code>Companies</code> catalog, add a reference to it to the <code>Type</code> property. |
| <ol class="n"><li></li></ol> | <strong>Business processes and tasks</strong> | <ul><li><code>BusinessProcess</code></li></ul> | First-time integration: in the <code>Type</code> property, specify references to the business processes in the configuration. |
| <ol class="n"><li></li></ol> | <strong>Business processes and tasks</strong> | <ul><li><code>BusinessProcessObject</code></li></ul> | First-time integration: in the <code>Type</code> property, specify business process objects in the configuration. |
| <ol class="n"><li></li></ol> | <strong>Business processes and tasks</strong> | <ul><li><code>TaskSubject</code></li></ul> | First-time integration:<br><ul><li>Select configuration objects to be a base for the <code>Job</code> business process or other business processes (define the list of task subjects).</li><li>Add references to the task subjects to the <code>Type</code> property.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Business processes and tasks</strong> | <ul><li><code>AddressingObject</code></li></ul> | First-time integration:<br><ul><li>Based on the received business roles, select objects to have role-based assignment (define <strong>business objects</strong>). For details, see section <a href="#бизнес-процессы-и-задачи">Business processes and tasks</a>.</li><li>Add references to the <strong>business objects</strong> to the <code>Type</code> property.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Business processes and tasks</strong> | <ul><li><code>DeferredBusinessProcess</code></li></ul> | First-time integration:<br><ul><li>Select business processes that can be deferred.</li><li>Add references to these business processes to the <code>Type</code> property.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Object versioning</strong> | <ul><li><code>VersionedData</code></li><li><code>VersionedDataObject</code></li></ul> | First-time integration: configure the types as described in section <a href="#версионирование-объектов">Object versioning</a>. |
| <ol class="n"><li></li></ol> | <strong>Business interactions</strong> | <ul><li><code>InteractionContact</code></li></ul> | First-time and further integrations:<br><ul><li>Select configuration objects to be specified as interaction contacts.</li><li>Add the allowed contact types to the <code>Type</code> property.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Business interactions</strong> | <ul><li><code>InteractionSubject</code></li></ul> | First-time and further integrations:<br><ul><li>Select configuration objects to be specified as interaction topics.</li><li>Add the allowed topic types to the <code>Type</code> property.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Period-end closing dates</strong> | <ul><li><code>PeriodClosingTarget</code></li></ul> | First-time integration:<br><ul><li>Select exchange plans that require data import restriction dates and add their types to the attribute types.</li></ul>See the detailed instructions in section <a href="#даты-запрета-изменения">Period-end closing dates</a>. |
| <ol class="n"><li></li></ol> | <strong>Additional reports and data processors</strong> | <ul><li><code>ObjectWithAdditionalCommands</code></li></ul> | First-time integration:<br><ul><li>Select configuration objects to be used with additional reports and data processors.</li><li>Add their types to the <code>Type</code> property.</li></ul>See the detailed instructions in section <a href="#дополнительные-отчеты-и-обработки">Additional reports and data processors</a>. |
| <ol class="n"><li></li></ol> | <strong>Notes</strong> | <ul><li><code>NotesSubject</code></li><li><code>NotesSubjectObject</code></li></ul> | <ul><li>Select configuration objects on which users can leave notes.</li><li>Add their types to the <code>Type</code> property.</li></ul>See the detailed instructions in section <a href="#заметки-пользователя">Notes</a>. |
| <ol class="n"><li></li></ol> | <strong>Personal data protection</strong> | <ul><li><code>PersonalDataSubject</code></li></ul> | First-time integration: specify the types in the <code>PersonalDataSubject</code> type collection. As a type, select an entity being a personal data subject in the configuration. |
| <ol class="n"><li></li></ol> | <strong>Contact information</strong> | <ul><li><code>ContactInformationOwner</code></li></ul> | First-time integration:<br><ul><li>Select configuration objects that will store contact information.</li><li>Add their types to the <code>Type</code> property.</li></ul>See the instructions in section <a href="#контактная-информация">Contact information</a>. |
| <ol class="n"><li></li></ol> | <strong>User reminders</strong> | <ul><li><code>ReminderSubject</code></li><li><code>ReminderSubjectObject</code></li></ul> | <ul><li>Select reference-type objects that require user reminders.</li><li>Add their types to the <code>Type</code> property.</li></ul>See the detailed instructions in section <a href="#напоминания-пользователя">User reminders</a>. |
| <ol class="n"><li></li></ol> | <strong>Item order</strong> | <ul><li><code>ObjectWithCustomOrder</code></li></ul> | First-time integration:<br><ul><li>Select configuration objects that require item ordering.</li><li>Add their types to the <code>Type</code> property.</li><li>See the detailed instructions in section <a href="#настройка-порядка-элементов">Item order</a>.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Print tools</strong> | <ul><li><code>ObjectWithDefaultPrintForms</code>.</li></ul> | First-time integration:<br><ul><li>Compose a list of configuration objects where the default print forms should be used. For example, the <strong>SaleOfGoodsAndServices</strong> document.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Print tools</strong> | <ul><li><code>PrintFormsRecipient</code>.</li></ul> | First-time integration:<ul><li>Select configuration objects to be mapped to default print form recipients. For example, the <strong>Counterparties</strong> catalog.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Users</strong> | <ul><li><code>Department</code></li><li><code>Individual</code></li></ul> | First-time integration:<br><ul><li>Decide whether you want to use the <code>Department</code> and <code>Individual</code> attributes of the <code>Users</code> catalog.</li><li>Add references to relevant catalogs to the type collections.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Users</strong> | <ul><li><code>ExternalUser</code></li><li><code>ExternalUserObject</code></li><li><code>User</code></li></ul> | First-time integration:<br><ul><li>First, define the infobase objects that you need to map with external users. For example, the <strong>Partners</strong> catalog.<strong></strong><strong></strong></li><li>Add the allowed types of external users to the type collections (the <code>User</code> type collection includes <code>CatalogRef.Users</code>).</li></ul> |
| <ol class="n"><li></li></ol> | <strong>File management</strong> | <ul><li><code>FilesOwner</code></li><li><code>AttachedFile</code></li><li><code>AttachedFileObject</code></li><li><code>AttachedFilesOwner</code></li><li><code>AttachedFilesOwnerObject</code></li></ul> | First-time integration:<br><ul><li>Select configuration objects that will contain attachments.</li><li>Add their types to the <code>Type</code> property.</li></ul>See the instructions in section <a href="#работа-с-файлами">File management</a>. |
| <ol class="n"><li></li></ol> | <strong>Report distribution</strong> | <ul><li><code>BulkEmailRecipient</code></li></ul> | First-time integration:<br><ul><li>Select possible distribution recipients. Email contact information must be recorded for these objects.</li><li>Add the recipient types to the <code>Type</code> property.</li></ul> |
| <ol class="n"><li></li></ol> | <strong>Properties</strong> | <ul><li><code>DetailedInfoOwner</code></li></ul> | First-time integration:<br><ul><li>Select configuration objects that will contain additional information records.</li><li>Add references to these objects to the <code>Type</code> property.</li></ul>See the instructions in section <a href="#свойства">Properties</a>. |
| <ol class="n"><li></li></ol> | <strong>Message templates</strong> | <ul><li><code>MessageTemplateSubject</code></li><li><code>MessageTemplateOwner</code></li></ul> | First-time integration:<br><ul><li>Select objects to be used in the subsystem (define subjects and owners of message templates).</li><li>Add their types to the <code>Type</code> property.</li></ul>See the instructions in section <a href="#шаблоны-сообщений">Message templates</a>. |
| <ol class="n"><li></li></ol> | <strong>Access management</strong> | <ul><li><code>RightsSettingsOwner</code></li><li><code>RightsSettingsOwnerObject</code></li><li><code>AccessKeysValuesOwner</code></li><li><code>AccessKeysValuesOwnerDocument</code></li><li><code>AccessKeysValuesOwnerRecordSet</code></li><li><code>AccessKeysValuesOwnerCalculationRegisterRecordSet</code></li><li><code>AccessKeysValuesOwnerObject</code></li><li><code>AccessValue</code></li><li><code>AccessValueObject</code></li><li><code>RegisterAccessKeysRegisterField</code></li><li><code>AccessValuesSetsOwnerObject</code></li><li><code>OwnerLimitedByAccessValuesSetsObject</code></li><li><code>ExternalValuesOwnerInAccessValueSetsObject</code></li></ul> | First-time integration: configure as described in section <a href="#управление-доступом">Access management</a>.<br>During each update: ensure that the types include all built-in types. |
| <ol class="n"><li></li></ol> | <strong>Source document tracking</strong> | <ul><li><code>ObjectWithSourceDocumentsOriginalsAccounting</code></li><li><code>Employee</code></li></ul> | First-time integration:<br><ul><li>Select objects to be used in the subsystem.</li><li>Add their types to the <code>Type</code> property.</li><li>Add references to required catalogs to the <code>Employee</code> type collection.</li></ul>See the instructions in section <a href="#учет-оригиналов-первичных-документов">Source document tracking</a>. |
#### Common forms
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Text messaging</strong></td>
<td>
<ul>
<li>Common form: <code>OutboundSMSSettings</code></li>
</ul></td>
<td>First-time integration: display it in the command interface.</td>
</tr>
</tbody>
</table>
#### Common commands
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Data exchange</strong></td>
<td>
<ul>
<li><code>Synchronize</code></li>
<li><code>SynchronizeWithAdditionalParameters</code></li>
<li><code>ConnectionSettings</code></li>
<li><code>ImportRulesSet</code></li>
<li><code>ImportObjectConvertionRules</code></li>
<li><code>ImportObjectRegistrationRules</code></li>
<li><code>GetSynchronizationSettingsForOtherApplication</code></li>
<li><code>SynchronizationScenarios</code></li>
<li><code>SendingEvents</code></li>
<li><code>ReceivingEvents</code></li>
<li><code>DataToSendComposition</code></li>
<li><code>DeleteSynchronizationSetting</code></li>
</ul></td>
<td>First-time integration: configure the subsystem as described in section <a href="#обмен-данными">Data exchange</a>.</td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Hierarchy</strong></td>
<td>
<ul>
<li><code>RelatedDocuments</code></li>
</ul></td>
<td>First-time integration: set the <strong>Command parameter type</strong> property for documents, catalogs, and charts of characteristic types to be displayed in the <strong>Hierarchy</strong> report.</td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Access management</strong></td>
<td>
<ul>
<li><code>SetRights</code>, property: <strong>Command parameter type</strong></li>
</ul></td>
<td>First-time integration: configure as described in section <a href="#управление-доступом">Access management</a>.<br>
During each update: ensure that the types include built-in types.</td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Source document tracking</strong></td>
<td>
<ul>
<li><code>SourceDocumentsOriginalsRecordingJournal</code></li>
</ul></td>
<td>First-time integration: configure the subsystem as described in section <a href="#учет-оригиналов-первичных-документов">Source document tracking</a>.</td>
</tr>
</tbody>
</table>
#### Common templates
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Infobase version update</strong></td>
<td>
<ul>
<li><code>SystemReleaseNotes</code></li>
</ul></td>
<td>First-time integration: create and maintain a template as described in section <a href="#обновление-версии-иб">Infobase version update</a>.</td>
</tr>
</tbody>
</table>
#### Catalogs
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Business processes and tasks</strong></td>
<td>
<ul>
<li><code>PerformerRoles</code></li>
</ul></td>
<td>First-time integration: create a set of predefined items for business roles available in the configuration. See the instructions in section <a href="#бизнес-процессы-и-задачи">Business processes and tasks</a>.</td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Currencies</strong></td>
<td>
<ul>
<li><code>Currencies</code></li>
</ul></td>
<td>First-time integration: display the <code>Currencies</code> catalog in the command interface. For more information, see section <a href="#валюты">Currencies</a>.</td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Contact information</strong></td>
<td>
<ul>
<li><code>ContactInformationKinds</code></li>
</ul></td>
<td>First-time integration: if necessary, create a set of predefined catalog items. See the instructions in section <a href="#контактная-информация">Contact information</a>.</td>
</tr>
<tr>
<td>
4.</td>
<td><strong>Performance monitor</strong></td>
<td>
<ul>
<li><code>KeyOperations</code></li>
</ul></td>
<td>First-time integration: if predefined items are used, create the required set of predefined items and perform the initial population of attributes from the list form. See the additional instructions in section <a href="#оценка-производительности">Performance monitor</a>.</td>
</tr>
<tr>
<td>
5.</td>
<td><strong>Users</strong></td>
<td>
<ul>
<li><code>ExternalUsers</code>, command: <code>ExternalAccess</code>, property: <strong>Command parameter type</strong></li>
</ul></td>
<td>First-time integration:<br>
<ul>
<li>First, define the infobase objects that you need to map with external users. For example, the <strong>Partners</strong> catalog.<strong></strong><strong></strong></li>
<li>Add the allowed types of external users to the type collections (the <code>User</code> type collection includes <code>CatalogRef.Users</code>).</li>
</ul></td>
</tr>
<tr>
<td>
6.</td>
<td><strong>Properties</strong></td>
<td>
<ul>
<li><code>AdditionalAttributesAndInfoSets</code></li>
</ul></td>
<td>First-time integration: for each object that will contain additional information, create a predefined item. The predefined item names must have the following format: <code>Type_Name</code>. For example, <code>Catalog_Individuals</code> for the <code>Individuals</code> catalog.<br>
See the instructions in section <a href="#свойства">Properties</a>.</td>
</tr>
</tbody>
</table>
#### Document journals
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Personal data protection</strong></td>
<td>
<ul>
<li><code>PersonalDataProcessingConsents</code></li>
</ul></td>
<td>
<ul>
<li>First-time integration: display in the command interface if the <strong>Application settings</strong> subsystem is not used in the configuration.</li>
</ul></td>
</tr>
</tbody>
</table>
#### Reports
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Personal data protection</strong></td>
<td>
<ul>
<li><code>ConsentsToPersonalDataProcessingEffective</code></li>
<li><code>ConsentsToPersonalDataProcessingExpiring</code></li>
</ul></td>
<td>
<ul>
<li>First-time integration: display in the command interface if the <strong>Application settings</strong> subsystem is not used in the configuration.</li>
</ul></td>
</tr>
</tbody>
</table>
#### Data processors
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Startup notifications</strong></td>
<td>
<ul>
<li><code>InformationOnStart</code></li>
</ul></td>
<td>For data processor templates for first-time integration:<br>
<ul>
<li>Select pages with information to be displayed at the application startup.</li>
<li>Import the pages into the data processor templates according to the subsystem instructions.</li>
</ul></td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Application settings</strong></td>
<td>
<ul>
<li><code>SSLAdministrationPanel</code></li>
</ul></td>
<td>During each update:<br>
<ul>
<li>If the administration panel form was changed, compare and merge all data processor forms to determine the list of additions and changes in the library distribution file.</li>
</ul></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Performance monitor</strong></td>
<td>
<ul>
<li><code>PerformanceMonitor</code></li>
</ul></td>
<td>First-time integration: display in the command interface if the <strong>Application settings</strong> subsystem is not used in the configuration.</td>
</tr>
</tbody>
</table>
#### Charts of characteristic types
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
1.</td>
<td><strong>Surveys</strong></td>
<td>
<ul>
<li><code>QuestionsForSurvey</code></li>
</ul></td>
<td>First-time integration:<br>
<ul>
<li>Select configuration objects to be specified as questionnaire responses (define response types).</li>
</ul>Add the allowed response types to the <strong>Value type</strong> property.</td>
</tr>
<tr>
<td>
2.</td>
<td><strong>Business processes and tasks</strong></td>
<td>
<ul>
<li><code>TaskAddressingObjects</code></li>
</ul></td>
<td>First-time integration:<br>
<ul>
<li>Specify all business object types both in the <code>Type</code> property of the chart of characteristic types and the <code>Type</code> property of the predefined <code>AllAddressingObjects</code> item of this chart of characteristic types.</li>
<li>Create a predefined item set for business objects (see the instructions in section <a href="#бизнес-процессы-и-задачи">Business processes and tasks</a>).</li>
</ul></td>
</tr>
<tr>
<td>
3.</td>
<td><strong>Properties</strong></td>
<td>
<ul>
<li><code>AdditionalAttributesAndInfo</code></li>
</ul></td>
<td>First-time integration: specify the available types of property values. You can add any metadata object available in the configuration to the list of data types.<br>
See the instructions in section <a href="#свойства">Properties</a>.</td>
</tr>
</tbody>
</table>
#### Business processes
<table>
<thead>
<tr>
<th><strong>#</strong></th>
<th><strong>Subsystem</strong></th>
<th><strong>Object name</strong></th>
<th><strong>Action required</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<ol class="n">
<li></li>
</ol></td>
<td><strong>Business processes and tasks</strong></td>
<td>
<ul>
<li><code>Job</code></li>
</ul></td>
<td>First-time integration: in the <strong>Base On</strong> property, specify references to metadata objects that require creating jobs (task subjects). See the instructions in section <a href="#бизнес-процессы-и-задачи">Business processes and tasks</a>.</td>
</tr>
</tbody>
</table>
### Deleting references to unused subsystems
Some library objects are configured to interact with other library subsystems. In such objects, keep only the code blocks related to subsystems that you integrate. A code block related to a subsystem is marked with opening and closing comments:
// <SubsystemPath>
…
// End <SubsystemPath>
For example, if you do not integrate the **Properties** subsystem into your configuration, delete all the code blocks marked with the following comments:
// StandardSubsystems.Properties
…
// End StandardSubsystems.Properties
Likewise, if you do not integrate the **Users SaaS** subsystem, delete all the code blocks marked with the following comments:
// StandardSubsystems.SaaSOperations.UsersSaaS
…
// End StandardSubsystems.SaaSOperations.UsersSaaS
For batch deletion of such code blocks, use the `FirstSSLDeployment.epf` data processor. Before running it for the first time, you might need to:
<ul>
<li>Comment out the code of the managed application module, the ordinary application module, and the session module (to be able to run the data processor).</li>
<li>Allow editing library objects in the support options.</li>
</ul>
### Subsystem integration
The library is designed for selective integration of most subsystems into the configuration. At any convenient time after the initial integration of the library, you can further integrate the required subsystems. To do so, repeat steps 1–3 of the initial integration scenario, mark the missing subsystems using the <code>FirstSSLDeployment.epf</code> data processor, and save the comparison/merge settings file for the Designer. Dependent and previously integrated subsystems will also be automatically flagged (since parts of their code required for the integrated subsystems may have been removed during the initial integration).
### Updating to specific library versions
The **updateSSL.htm** document included in the library describes the specifics of updating each library version. When updating to a version that does not directly follow the integrated one, follow all the steps in this document, starting with the earliest version.
### Incrementing configuration version number
After you integrate or update the library, increment the version number of the configuration. It is required for proper execution of all infobase update procedures in the new library version. For more information, see <a href="#обновление-вспомогательных-данных-во-время-разработки">Service data update</a>.
### Validating integration and updates
It is recommended that you perform the following validation procedures:
<ol>
<li>Check the configuration with the <strong>Perform extended check</strong> check box selected (Designer – <strong>Configuration</strong> – <strong>Check configuration</strong>).</li>
<li>Run the configuration in version update mode and in initial population mode (using an empty infobase).</li>
<li>Use the <code>SSLImplementationCheck.erf</code> external data processor.</li>
</ol>
These procedures allow you to quickly identify any incompatibility issues related to library objects that were renamed or deleted from the new library version, and to locate human errors that might have occurred during integration or update. The integration wizard also finds inconsistencies between the planned and the actual scope of library integration into the configuration.
### Integrating library subsystems into configuration objects and developing roles
Some subsystems are designed to be integrated directly into consumer configuration objects. See the instructions in the relevant sections of <a href="#глава-3-настройка-и-использование-подсистем-при-разработке-конфигурации">Chapter 3. Setting and using subsystems during configuration development</a>.
This chapter also provides recommendations for configuring user access rights. Most subsystems include a set of roles for their objects. However, sometimes a configuration developer has to develop a role system and configure roles for built-in library objects.
### Developing master data for library objects
Most library objects do not include master data because its content depends on the consumer configuration specifics. Master data for library objects must be developed directly in the configuration.
## Using subsystems in configurations
To use most library subsystems, follow the instructions for integration and configuring, display subsystem objects in the command interface, and integrate the subsystem into configuration objects.
Also, the subsystems include an API that you can use in your configuration. For the API description, see the library source code. For the description of additional subsystem features for developers, see <a href="#использование-при-разработке-конфигурации">How to use the subsystem in development</a> subsections in Chapter 3.
The library source code is distributed under the **Attribution 4.0 International (CC BY 4.0)** license. The license text is available <a href="https://creativecommons.org/licenses/by/4.0/legalcode">here</a>. This license allows you to use, distribute, rework, edit, and develop the library for any purposes including commercial ones provided that the authorship of the library is indicated in your software. See also: <a href="http://v8.1c.ru/predpriyatie/questions_licence.htm">1C:Enterprise licensing FAQ</a> (in Russian).
## Quick start of development "from scratch"
This section contains a quick start guide for SSL-based configuration development. It only describes the steps required to run an SSL-based configuration for the first time. For the complete list of steps, see <a href="#инструкция-по-внедрению-библиотеки">Chapter 2</a>.
### Preparation
<ol>
<li>Select subsystems you want to integrate. In the simplest scenario, all SSL subsystems are integrated. It is recommended that you use the <code>FirstSSLDeployment</code> data processor. It allows you to select subsystems for integration and ensures their reference integrity.</li>
<li>After selecting the subsystems, click <strong>Save settings for Designer</strong> and specify the settings file name.</li>
<li>Create an empty infobase.</li>
</ol>
### Comparison and merging
<ol>
<li>Click <strong>Configuration</strong> – <strong>Compare and merge with configuration from file</strong>.</li>
<li>Select the <strong>1Cv8.cf</strong> file from the SSL distribution package.</li>
<li>When prompted to load the full configuration, click <strong>No</strong>.</li>
<li>When prompted to enroll for support, click <strong>Yes</strong>.</li>
<li>Click <strong>Actions</strong> – <strong>Load settings from file</strong>. Select the settings file saved in step 2 of the <strong>Preparation</strong> stage.</li>
<li>Then click <strong>Execute</strong>.</li>
<li>If a window informing about unsolved references is displayed, skip the messages in this window and click <strong>Continue</strong>. This window is displayed when you do not integrate all SSL subsystems. See an example in <a href="#внедрение-подсистемы-обмен-данными-без-подсистемы-работа-с-почтовыми-сообщениями">How to integrate "Data exchange" subsystem without "Email management" subsystem</a>.</li>
<li>In the <strong>Support rule settings</strong> window, click <strong>OK</strong>.</li>
</ol>
### Actions after comparison and merging
1. Type the configuration name in the configuration properties. Example: <code>MyConfiguration</code>.
2. In the configuration properties, set the version number. For example, you can set the version number to <strong>1.0.1.1</strong> when you start developing a configuration.
3. Copy the <code>InfobaseUpdateSSL</code> common module.
4. Replace the name of the copied module with the name or abbreviation of the configuration name (for example, <code>InfobaseUpdateMC</code>).
5. Replace the module text with:
```
Procedure OnAddSubsystem(LongDesc) Export
LongDesc.Name = "MyConfiguration";
LongDesc.Version = "1.0.1.1";
// Standard Subsystems Library is required.
LongDesc.RequiredSubsystems1.Add("StandardSubsystems");
EndProcedure
Procedure OnAddUpdateHandlers(Handlers) Export
EndProcedure
Procedure BeforeUpdateInfobase() Export
EndProcedure
Procedure AfterUpdateInfobase(Val PreviousVersion, Val CurrentVersion,
Val CompletedHandlers, OutputUpdatesDetails, ExclusiveMode) Export
EndProcedure
Procedure OnPrepareUpdateDetailsTemplate(Val Template) Export
EndProcedure
Procedure OnAddApplicationMigrationHandlers(Handlers) Export
EndProcedure
Procedure OnDefineDataUpdateMode(DataUpdateMode, StandardProcessing) Export
EndProcedure
Procedure OnCompleteApplicationMigration(Val PreviousConfigurationName, Val PreviousConfigurationVersion, Parameters) Export
EndProcedure
```
In the `OnAddSubsystem` procedure, replace the configuration name and version number with the name and number specified in steps 1 and 2.
6. Allow editing the `ConfigurationSubsystemsOverridable` module and add the following line to the `OnAddSubsystems` procedure:
```
SubsystemsModules.Add("InfobaseUpdateMC");
```
In this line, specify the name of the module created in step 4.
7. Run the application for the first time. Ensure there are no errors during the initial population.
</div>