Brief theoretical information. The “Directory” configuration object is an application object and is designed to work with lists of data. Directory configuration object What are the characteristic features of a directory

1C:Enterprise 8.0

Practical guidedeveloper

Examples and typical techniques

As an example, let's look at development methods in 1C:Enterprise 8.0, let's take a small company - OO "Jack of All Trades", which provides repair services for various household appliances.

The task is to automate its work by the end of the practical examples using 1C:Enterprise 8.0.

1C:Enterprise

The 1C:Enterprise system is a universal system for automating the economic and organizational activities of an enterprise. Since such activities can be quite diverse, the 1C:Enterprise system has the ability to “adapt” to the characteristics of the specific area of ​​activity in which it is used. The term used to denote this ability is configurability, that is, the ability to customize the system to the characteristics of a specific enterprise and the class of problems being solved.

This is achieved by the fact that 1C:Enterprise is not just a program that exists as a set of immutable files, but a collection of various software tools that developers and users work with. Logically, the entire system can be divided into two large parts, which

closely interact with each other: the configuration and the platform that manages the operation of the configuration.

There is one platform (1C:Enterprise 8.0) and many configurations. For any application solution to function, a platform and some (one) configuration are always required.

The platform itself cannot perform any automation tasks, since it is created to ensure the operation of any configuration. The configuration itself is also useless, because in order for it to perform the tasks for which it was created, there must be a platform that manages its operation.

Examples of existing application solutions include the “Trade Management” solution, designed to automate operational and management accounting tasks, “Human Resources Management,” designed to implement the company’s personnel policy, or “Manufacturing Enterprise Management,” covering the main contours of accounting and management at a manufacturing enterprise .

The application solution is, where possible, universal in order to meet the needs of a wide variety of enterprises operating in the same field of activity. And this is good. On the other hand, such versatility will inevitably lead to the fact that not all capabilities of the application solution will be used at a particular enterprise, and some capabilities will be missing.

This is where the configurability of the system comes to the fore, since the platform, in addition to managing the configuration, contains tools that allow you to make changes to the configuration in use. Moreover, the platform allows you to create your own configuration from scratch, if for some reason.

The 1C:Enterprise system has different operating modes: 1C:Enterprise and Configurator.

Mode 1C:Enterprise is the main one and serves for the work of system users. In this mode, users enter data, process it, and receive output results.

Configurator mode used by developers and database administrators. It is this mode that provides the tools necessary to modify an existing or create a new configuration.

First we need an infobase with an empty configuration:

Let's create an information base with an empty configuration

Let's launch 1C:Enterprise in configurator mode. Let's execute the first command, which starts working with any configuration - Configuration - Open configuration.

The configuration tree is the main tool with which the developer works. It contains almost all the information about what the configuration consists of:

To make the developer’s work easier, “everything that makes up the configuration” is collected into several separate groups, and now the tree shows you these groups.

Configuration Objects

The configuration is a description. It describes the structure of the data that the user will use in 1C:Enterprise mode. In addition, the configuration describes various algorithms for processing this data, the configuration contains information about how this data should look on the screen and on the printer, etc.

In the future, the 1C:Enterprise platform, based on this description, will create a database that will have the necessary structure and provide the user with the opportunity to work with this database.

In order for the 1C:Enterprise system to be quickly and easily configured for the required application tasks, the entire description that the configuration contains consists of certain logical units called configuration objects.

How to work with the configuration tree and how to create an object

Before we start creating the first configuration objects, we should explain some techniques for working with the configurator.

To open and close a configuration, use the following menu items:

Configuration - Open configuration, and

Configuration - Close configuration.

After the configuration is opened, its composition appears in the configuration tree window. You can close this window like any other Windows window, but the configuration will remain open (i.e., available for editing). To display the configuration tree window on the screen again, use the menu command Configuration - Configuration window.

There are several ways to create a new configuration object, and you can always use the method that is clearer and more convenient for you.

First way. You need to place the cursor on the type of configuration objects that interests you, and click the button in the command panel of the configuration window Actions - Add.

Second way. You can use the context menu, which is called up when you click the right mouse button.

Place the cursor on the type of configuration objects you are interested in and press the right mouse button. In the menu that appears, select Add.

Configuration object Directory

The Directory configuration object is an application object and is intended to describe lists of data. The Directory configuration object is used so that, based on it, the platform creates an information structure in the database in which, for example, a list of employees, a list of goods, a list of clients or suppliers will be stored.

A characteristic feature of the Directory configuration object is that the user can independently add new elements to the directory while working. For example, a user can add new employees to the directory, create a new product, or add a new client.

Each directory element typically contains some additional information that describes that element in more detail. For example, each element of the “Products” directory may contain additional information about the manufacturer, expiration date, etc. The set of such information is the same for all elements of the directory, and to describe such a set we use requisites Directory configuration object, which are also, in turn, configuration objects. Because these objects are logically related to the Directory object, they are called subordinates. The developer creates most of the details of the Directory configuration object independently, however, each Directory configuration object has two “default” fields: code and name.

In addition, each directory element may contain a certain set of information, which is the same in structure, but different in quantity, for different directory elements. For example, each element of the Employees directory can contain information about the composition of the employee’s family. For one employee this will be only the spouse, while for another the family may consist of a spouse, son and daughter. To describe such information can be used tabular parts Directory configuration objects, which are subordinate configuration objects.

For ease of use, the directory elements can be grouped by the user according to some principle. For example, in the “Household Appliances” directory the following groups can be created: “Refrigerators”, “TVs”, “Washing machines”, etc. The ability to create such groups in the directory is specified by the “Hierarchical” property of the Directory configuration object. In this case, the directory element, which is a group, will be parent for all elements and groups included in this group. This type of hierarchy is called hierarchy of groups and elements.

Another type of hierarchy is also possible - hierarchy of elements. In this case, the parent is not a group of directory elements, but one of the directory elements itself. For example, this type of hierarchy can be used when creating a “Divisions” directory, when one division is the parent of several other divisions that are part of it.

Elements of one directory can be subordinated to elements or groups of another directory. For example, the “Units of Measurement” directory can be subordinated to the “Products” directory. Then, for each element of the “Products” directory, we will be able to indicate the units of measurement in which this product arrives at the warehouse. In the 1C:Enterprise system this is achieved by the fact that for each configuration object the Directory can be specified list of directory owners.

Sometimes there are situations when it is necessary for some elements to always exist in the directory, regardless of user actions. Suppose the logic of business processes at an enterprise is such that all goods first arrive at the main warehouse, and then, as needed, are moved to other warehouses. In this case, the “Main” warehouse must always exist in the “Warehouses” directory, otherwise the receipt of goods will be carried out incorrectly. The Directory configuration object allows you to describe any number of such directory elements. They're called predefined directory elements.

Depending on what actions we want to perform with the directory, we need to display the directory in “different views”. For example, in order to select some directory element, it is more convenient to present the directory in the form of a list, and in order to change some directory element, it is more convenient to present all the details of this directory element on one form. Therefore, the Directory configuration object can have an arbitrary number of forms, some of which can be designated as the main forms of the directory.

The following table explains the names of these forms as defined in the configurator:

Configuration objectDirectory

Directory

Basic object shape

Directory element form

Basic group form

Directory element group form

Basic list form

Directory list form

Main selection form

Form for selecting a directory element or group

Main form for selecting a group

Form for selecting a group of directory elements

The form serves to “visualize” the data in the database. The form presents this data in a user-friendly form and allows you to describe the algorithms that will accompany the user’s work with the data presented in the form.

Any form can be described in the configurator. To create such a description, there is a subordinate configuration object, Form. As a rule, it is subordinate to one of the application objects, but it can exist independently. Based on the description contained in the Form configuration object, at the right moment in the user’s work, the 1C:Enterprise platform will create a Form program object with which the user will work.

Creating a directory Clients

Now that we are a little familiar with the capabilities of the Directory configuration object, let's create several such objects to describe the directories that will be used in our database.

Since our LLC “Master of All Trades” provides repair services for household appliances, it is obvious that for record keeping we will need to set some list information.

First, we need a list of company employees who will provide services. Then we will need a list of clients with whom our company works. After this, we will need a list of services that our company can provide and a list of materials that can be consumed. In addition, we will need a list of warehouses that may contain materials from 000 “Jack of All Trades.”

Let's start with simple things - a list of employees and a list of clients. Let's open our training configuration in the configurator and create a new configuration object, Directory.

Our task will be to create a directory in which the names of our clients will be stored.

After you click "Add", the system will open configuration object editing window.

This is a tool that was created to help the developer. It was created specifically for complex configuration objects and allows you to quickly create such objects by performing sequential actions. In order to follow the correct sequence of actions, there are “Next” and “Back” buttons at the bottom of the window. The “Next” button allows you to set the object’s properties in the desired sequence (so as not to miss anything or skip ahead where data that should have been entered earlier is required). The “Back” button allows you to go back a few steps if you discover that you have previously entered incomplete or incorrect data.

Let's set Name directory - “Clients”. The name is the main property of any configuration object. When a new object is created, the system automatically assigns it a name. You can use the name assigned by the system, but it is better to replace it with your own user-friendly name. You can set any name, as long as it starts with a letter and does not contain some special characters (for example, a space). To make the configuration easier to read, it is customary to create intuitive names and, if they consist of several words, remove spaces between words and start each word with a capital letter.

Based on the name, the platform will automatically create synonym -"Clients". Any configuration object also has the “Synonym” property. It is intended to store an “alternative” name for the configuration object, which will be used in the interface elements of our program - that is, it will be shown to the user.

Therefore, there are practically no restrictions on the synonym, and it can be specified in a form familiar to humans.

Let's set the name and synonym of the directory

We will not configure all the properties of the Directory configuration object for now; we will be completely satisfied with the values ​​that the system offers for them by default. Therefore, click “Next” three times and find yourself on the “Data” tab.

What is of interest to us here is the length of the code and the length of the name. Code length is an important property of a reference book. As a rule, a directory code is used to identify directory elements and contains values ​​unique to each directory element. The platform itself can control the uniqueness of codes and support automatic numbering of directory elements.

The platform itself can track the uniqueness of codes, so the number of elements that can be contained in the directory will depend on the length of the code. The code length is 5 characters - this is from 0 to 99999, that is, one hundred thousand elements. For our small OOO “Jack of all trades” this is quite enough.

Let's move on to the length of the name. 25 characters are clearly not enough for us, let’s increase the length of the name to 50.

Let's agree on the length of the code and set the length of the name

We will leave all other properties of the Directory configuration object as they are offered by the system by default, and click “Close”.

Now let's see what the system will create based on the Directory configuration object that we added. Let's execute the menu item Debugging - Start debugging. To answer the question:

A system window will open in front of us, in 1C:Enterprise mode. Since we didn't create any user interfaces, we should use the menu that the system creates by default to view the results of our work.

Let's execute the menu item Operations - Directories... and select the “Clients” directory.

Let’s perform Operations I Directories... and select the “Clients” directory

The system will open one of the main forms of the directory - the main list form.

For now, our “Clients” directory is empty, so let’s add several elements to it (you can add a new element to the directory using the menu item Actions I Add, the corresponding icon or the “Insert” key).

Add new items to the directory using a menu or icon

After adding elements, the directory will look like this.

Now we can move on to creating the second directory that will be used in our configuration - the “Employees” directory.

Creating a directory Employees

The “Employees” directory will be somewhat more complex than the “Clients” directory. The fact is that in it we will store not only the last name, first name and patronymic of the employee, but also information about his past work activity. This information is homogeneous in its structure (organization, start, end of work, position held), but the number of previous jobs may vary for different employees. Therefore, to store such information we will use the tabular part of the directory.

Let's return to the configurator and create a new Directory configuration object. Let's call it "Employees".

Our task will be to create a directory that has a tabular part.

On the “Data” tab, set the length of the directory name to 50 characters and add a new tabular part to the directory with the name “Labor Activity”:

Let's add a new tabular part to the "Employees" directory and set its name...

Let’s create the details of the “Labor Activities” tabular section:

    “Organization” - type String, length 100,

    “Getting Started” - type Date, date composition - “Date”,

    “Completion of Work” - date type, date composition - “Date”,

    “Position” - type String, length 100:

Let's create the details of the tabular part of the directory...

For the details “Start of Work” and “End of Work” we chose the date composition - “Date”, since in the 1C: Enterprise 8.0 system, values ​​of the Date type contain both date and time. In this case, we do not care about the start and end times of work.

Now we should select the option to edit the directory. Obviously, editing in the list will no longer work for us, since in the list we will not be able to edit the tabular part of the directory and enter information about work activity.

Therefore, in the “Employees” directory, we will select the option to edit the directory in both ways - both in the list and in the dialogue. To do this, go to the “Forms” tab and set the corresponding switch:

Let's set the option for editing the directory.

The creation of the “Employees” directory is completed - now you can launch 1C:Enterprise in debug mode and fill out the directory.

Execute menu item Debugging - Continue debugging, to the system question:

answer “Yes”, answer the subsequent questions in the same way as before.

In the program window that appears, open the “Employees” directory and make sure that the mode for editing the directory in the dialogue is set (Actions menu - Edit in dialogue or a similar icon in the command panel).

Create employees Nikolai Dmitrievich Gusakov, Ivan Sergeevich Delovoy and Valery Mikhailovich Simonov, as shown in the pictures. Please note that the rows of the tabular part of the directory can be sorted by the contents of any of the columns, or arranged in any order using the command bar icons:

You can control the order of rows in the tabular section...

Now we can start creating the next xNomenclature directory.”

Creating a directory Nomenclature

The “Nomenclature” directory will contain information about the services provided by “Jack of All Trades” LLC and about the materials that can be used.

This directory will not be complicated; the only feature it will have is the presence of a hierarchical structure. To make the directory convenient to use, we will group services into one group, and materials into another. In addition, since Master of All Trades LLC provides a wide variety of services, they will also be logically grouped into several groups. The same can be said about materials.

Our task will be to create a hierarchical directory. Let's create a new configuration object Directory and call it “Nomenclature”. Let's go to the "Hierarchy" tab and set the "Hierarchical directory" flag.

Let's make the directory hierarchical...

On the “Data” tab, set the length of the directory name to 100 characters.

Now let’s launch 1C:Enterprise in debugging mode and fill out the “Nomenclature” directory. In the process of filling out the directory, we will show how to create directory groups and transfer elements from one group to another.

Let's create two groups in the root of the directory: “Materials” and “Services” (menu Actions - New Group):

In the “Materials” group we will create five elements:

    "Samsung horizontal transformer"

    "GoldStar horizontal transformer"

    "Philips 2N2369 transistor",

    "Rubber hose"

"Electrical cable":

In the “Services” group we will also create several elements - TV repair services:

    "Diagnostics",

    "Repair of domestic TV"

“Imported TV repair”

and installation services for washing machines:

    "Water connection"

    "Electrical connection":

In the last lesson we learned WHAT 1C Objects are.

Let's now see what 1C Objects are there and what are they for?

The main objects of the 1C configuration constitute the very essence of the configuration; it is precisely because of the differences in the main objects that 1C Accounting differs from the 1C Trade Management configuration.

Main 1C configuration objects - for accounting

These 1C configuration objects are a means of accounting.

1C Documents

The essence of accounting is entering documents into a database. Each document means that something happened in the life of the company. The document records this event.

For example, “Purchase of goods”, “Sale of goods”, etc.

Directories 1C

It is clear that different documents work with the same data. For example, the product “Shovel” is first bought and then sold. The product is the same.

In order not to re-enter it several times, it is entered into the directory once and then the directory value “Shovel” is used. The meaning remains the same.

Directories are such lists of different values.

Registers 1C

Document 1C records one operation. It is absolutely clear that in the life of a company there are hundreds and millions of documents.

The result of the [movement] of the document is a change in at least one digit in the results of operations. For example, there was 0 product, now +10.

Each document moves this digit in at least one of the registers. The result is a table of such movements, from which totals can be calculated.

The essence of registers is to measure the results of a company's operations.

There are several types of 1C registers:

  • 1C information registers are simple tables like Excel, often used to store information related to 1C directories
  • 1C accumulation registers - tables that receive totals for their movements, balances (2+10, balance 12) and turnover (2+10, turnover 10), are used for operational (warehouse) accounting
  • 1C accounting registers - tables based on the accounting chart of accounts, used for accounting
  • 1C calculation registers - tables based on plans for types of calculations, are used to maintain payroll records.

Basic 1C configuration objects - for the user

1C user objects do not allow for accounting, but are required to make it convenient for the user to work with the program.

1C document logs

Allows you to combine lists of documents for the user by type. For example, the magazine “Warehouse Documents” or “Bank Documents”. Each journal usually includes several types of documents.

1C reports

Information registers allow you to calculate the result. However, the user needs to work with it in a form convenient for him.

There are 1C reports for this.

The report is a ready-made calculated results of the company's activities in a form similar to Excel or Word.

The report can exist separately from the configuration and database - it can be saved to a file. In this case it is called an "external report".

Continuation of the single topic, answers to Radchenko’s book, lesson 2 and 3.

What is the "Subsystem" configuration object used for?
A subsystem is the main element for building the 1C:Enterprise interface. Subsystems distinguish functional parts in the configuration into which the application solution is logically divided.

How to describe a logical structure using Subsystems?
By dividing it into functional parts, which represent separate subject areas.

How to control the order of output and display of subsystems in the configuration?
Right-click on the configuration, select the command “Open configuration command interface”, you can change positions using the arrows.

What is the configuration object editing window and how does it differ from the properties panel?

Edit window - mainly used for creating new objects.
Properties palette - not tied to a specific configuration object.

Lesson 3.

What is the purpose of the Directory configuration object?
The reference book is intended for working with lists of data, describing their properties and structure.

What are the characteristic features of the Directory configuration object?
The directory consists of elements; Each element represents a separate record in a table that stores information from this directory;
An element may also contain additional information that describes this element in more detail - attributes that are the same for all elements of the directory; Props are also a configuration object;

What are the details and tabular parts of the directory used for?
Details are used to describe additional information describing a directory element;
The tabular part is used to describe the information of a directory element, the same in structure, but different in quantity.

Why are hierarchical directories needed and what is a Parent?
Hierarchical directories are needed to group directory elements according to any criteria or principles. There are several types of hierarchies: hierarchy of groups and elements- a directory element representing a group - the parent for all elements and groups included in this group;
Hierarchy of elements- the parent is not a group of directory elements, but the element itself.

Why are subordinate directories needed and what is an Owner?
Elements of one directory can be subordinated to elements of another directory, and in this case a one-to-many relationship is established. A one-to-one relationship can also be used, when each element of a subordinate directory is associated with one of the elements of the owner directory.

What are the main forms of a directory?
Element form - for editing or creating a directory element;
Group form - for editing or creating a directory group;
List form - to display a list of elements in the directory;
Group selection form - for selecting one of the directory groups;

What are predefined directory elements?
Directory elements created in the configurator cannot be deleted by the user; Serve to store information always, regardless of user actions;

In terms of configuration, what is the difference between a regular element and a predefined element?
Configuration algorithms can be tied to predefined elements; therefore, the system adds these elements to the database structure itself, without user intervention.

How can a user distinguish a regular element from a predefined one?
Via pictogram

How to create a directory configuration object and describe its structure?
Create a new directory - structure - on the tabs hierarchy, data, pictures here

How to add a new element to the directory?
Through 1C:Enterprise mode.

How to create a directory group?
Via 1C:Enterprise mode

How to move an element from one group to another?
Right click on the element, "move to group"

Why do we need basic and database configuration?
The main configuration is the developer configuration. Database configuration - for working with users.

How to change the Database configuration?
No way. You can only update to the main configuration state.

How are configuration objects and database objects related?
Configuration objects describe storages and tables. And Database objects are the records that are contained in these tables.

What are configuration subobjects?
Details, tabular parts, etc.

Why do you need to check the details of the directory?
So that the user cannot enter empty or incorrect records.

What is Quick Select and when to use it?
To select elements not from a separate form, but from a drop-down list filled with elements of this directory.

How to display a directory and define its presentation in various sections of the application interface?
To display - right click on the directory, "Edit" tab, "Subsystems" tab.
Directory view - "Main" tab, then General - subsystems - all subsystems. pictures here

How to display commands for creating a new directory item in the subsystems interface?
General - subsystems - all subsystems - checkbox "Nomenclature: create"

How to edit the command interface of a subsystem?
General - subsystems - all subsystems. At the top is the "Command Interface" field

What standard panels are used in the application interface, and how to configure the location of these panels in the configurator and in 1C:Enterprise mode?

Section panel; the command panel of the current section (if they are specified; contains commands corresponding to the selected section; at the beginning of the panel there are commands that allow you to open any lists, and then commands that allow you to create new data elements, generate a report, or perform processing); toolbar and information panel (favorites panel, history panel, open panel...).
Setting up the location of these panels in the configurator is done as follows:
Let's select the root of the object tree of our configuration, right-click to call up the context menu and select "Open client application interface". In the window that appears on the right there is a list of all standard panels of the application solution. By dragging them to the left side of the window or removing them from there, we will configure the desired display of panels.
Setting up the location of these panels in 1C:Enterprise mode is done as follows:
Main menu -> View -> Panel settings -> By selecting and dragging with the mouse, we will configure the desired display of panels.


Continuation of the single topic, answers to Radchenko’s book, lesson 2 and 3.

What is the "Subsystem" configuration object used for?
A subsystem is the main element for building the 1C:Enterprise interface. Subsystems distinguish functional parts in the configuration into which the application solution is logically divided.

How to describe a logical structure using Subsystems?
By dividing it into functional parts, which represent separate subject areas.

How to control the order of output and display of subsystems in the configuration?
Right-click on the configuration, select the command “Open configuration command interface”, you can change positions using the arrows.

What is the configuration object editing window and how does it differ from the properties panel?

Edit window - mainly used for creating new objects.
Properties palette - not tied to a specific configuration object.

Lesson 3.

What is the purpose of the Directory configuration object?
The reference book is intended for working with lists of data, describing their properties and structure.

What are the characteristic features of the Directory configuration object?
The directory consists of elements; Each element represents a separate record in a table that stores information from this directory;
An element may also contain additional information that describes this element in more detail - attributes that are the same for all elements of the directory; Props are also a configuration object;

What are the details and tabular parts of the directory used for?
Details are used to describe additional information describing a directory element;
The tabular part is used to describe the information of a directory element, the same in structure, but different in quantity.

Why are hierarchical directories needed and what is a Parent?
Hierarchical directories are needed to group directory elements according to any criteria or principles. There are several types of hierarchies: hierarchy of groups and elements- a directory element representing a group - the parent for all elements and groups included in this group;
Hierarchy of elements- the parent is not a group of directory elements, but the element itself.

Why are subordinate directories needed and what is an Owner?
Elements of one directory can be subordinated to elements of another directory, and in this case a one-to-many relationship is established. A one-to-one relationship can also be used, when each element of a subordinate directory is associated with one of the elements of the owner directory.

What are the main forms of a directory?
Element form - for editing or creating a directory element;
Group form - for editing or creating a directory group;
List form - to display a list of elements in the directory;
Group selection form - for selecting one of the directory groups;

What are predefined directory elements?
Directory elements created in the configurator cannot be deleted by the user; Serve to store information always, regardless of user actions;

In terms of configuration, what is the difference between a regular element and a predefined element?
Configuration algorithms can be tied to predefined elements; therefore, the system adds these elements to the database structure itself, without user intervention.

How can a user distinguish a regular element from a predefined one?
Via pictogram

How to create a directory configuration object and describe its structure?
Create a new directory - structure - on the tabs hierarchy, data, pictures here

How to add a new element to the directory?
Through 1C:Enterprise mode.

How to create a directory group?
Via 1C:Enterprise mode

How to move an element from one group to another?
Right click on the element, "move to group"

Why do we need basic and database configuration?
The main configuration is the developer configuration. Database configuration - for working with users.

How to change the Database configuration?
No way. You can only update to the main configuration state.

How are configuration objects and database objects related?
Configuration objects describe storages and tables. And Database objects are the records that are contained in these tables.

What are configuration subobjects?
Details, tabular parts, etc.

Why do you need to check the details of the directory?
So that the user cannot enter empty or incorrect records.

What is Quick Select and when to use it?
To select elements not from a separate form, but from a drop-down list filled with elements of this directory.

How to display a directory and define its presentation in various sections of the application interface?
To display - right click on the directory, "Edit" tab, "Subsystems" tab.
Directory view - "Main" tab, then General - subsystems - all subsystems. pictures here

How to display commands for creating a new directory item in the subsystems interface?
General - subsystems - all subsystems - checkbox "Nomenclature: create"

How to edit the command interface of a subsystem?
General - subsystems - all subsystems. At the top is the "Command Interface" field

What standard panels are used in the application interface, and how to configure the location of these panels in the configurator and in 1C:Enterprise mode?

Section panel; the command panel of the current section (if they are specified; contains commands corresponding to the selected section; at the beginning of the panel there are commands that allow you to open any lists, and then commands that allow you to create new data elements, generate a report, or perform processing); toolbar and information panel (favorites panel, history panel, open panel...).
Setting up the location of these panels in the configurator is done as follows:
Let's select the root of the object tree of our configuration, right-click to call up the context menu and select "Open client application interface". In the window that appears on the right there is a list of all standard panels of the application solution. By dragging them to the left side of the window or removing them from there, we will configure the desired display of panels.
Setting up the location of these panels in 1C:Enterprise mode is done as follows:
Main menu -> View -> Panel settings -> By selecting and dragging with the mouse, we will configure the desired display of panels.


Now we will briefly get acquainted with the main configuration objects in 1C:Enterprise 8.2.

Configuration Objects- these are the constituent elements, the “details” that make up any application solution.
They are custom objects (objects with custom properties) supported at the technology platform level. By and large, the developer’s task is to assemble from these objects, as from a constructor, the necessary structure of an application solution and then describe specific algorithms for the functioning and interaction of these objects, which differ from their typical behavior.

The composition of objects supported by the technology platform is the result of an analysis of the subject areas of 1C:Enterprise use, and the identification and classification of business entities used in these areas. As a result of this analysis, the developer can operate with such objects as directories, documents, information registers, charts of accounts, etc.

In order to standardize and simplify the process of developing and modifying application solutions, the developer is provided with a graphical interface with which he can describe the composition of the objects used in a specific application solution.

Based on this description, the technology platform will create appropriate information structures in the database and work in a certain way with the data stored in these structures. The developer does not need to worry about which tables, for example, the data should be placed in, how it will be modified or presented to the user. The platform will perform all these actions automatically, based on the typical behavior of the objects used.

Thus, the developer operates with metadata - “data about data”, or configuration objects. By adding another configuration object to the structure of the application solution, the developer, in essence, adds a description of how the corresponding data will be placed and how it will interact with other data stored in the information base.

The set of objects that a developer can use is fixed and defined at the platform level. The developer cannot create his own types of objects; he can only operate with the set of objects that is available. Such an approach to the development of application solutions allows, firstly, to standardize the development process, and secondly, to ensure simple and quick modification of application solutions by other developers or users.

The composition of the main configuration objects used in 1C:Enterprise 8.2 is as follows:

Team
Commands are actions that the user can perform. In addition to the commands generated by the platform, the developer can create his own commands that belong to the entire application solution or individual configuration objects.

Constant
Constants are designed to store permanent or conditionally permanent information. For example, a constant can store the name of the organization, last name, first name and patronymic of the manager or chief accountant, etc.

Transfer
Enumerations are designed to describe a list of values ​​that a variable can take. For example, an enumeration might store values ​​that describe a customer's status: "wholesale" and "retail."

Directory
Directories are used to describe such entities as goods, counterparties, currencies, warehouses, etc. All these entities have common properties: internal identification of an object in the system, the need to support hierarchy and grouping of elements, the need to support nested tables, etc.

Document, Document Journal
They are used to describe entities such as accounts, invoices, orders, etc. These entities record various events occurring in the life of the organization, they are time-bound, contain nested tables, must be reflected in accounting mechanisms, etc.

Processing, Report
Processing and reporting are used to process information accumulated in the system and obtain summary data in a form convenient for viewing and analysis. They describe information processing algorithms and contain various forms and algorithms for presenting this information to the user. Allows you to use tables and various types of charts to visually display data.

Accumulation register
Accumulation registers are “responsible” for accounting for movements of resources (finance, goods, materials, etc.). They allow you to automate such areas as warehouse accounting, mutual settlements, and planning. Accumulation registers store information about the receipt and consumption of certain resources, and the functionality of these objects provides the ability to obtain balances at a certain point in time, calculate totals, cache totals, etc.

Register of information
Information registers are designed to store multidimensional information about the values ​​of various quantities. Such values ​​could be, for example, exchange rates or prices for competitors' products as of a certain date. This information can be either static or changing over time - in this case, it is provided for storing a history of changes.

Subsystem
With the help of subsystems, the application solution is visually divided into large and small functional blocks. Subsystems form the basis for the formation of the program command interface.

General details
Common details are used to store data of the same type in different configuration objects and as an integral part of the data separation mechanism.

Task, Business process
Tasks and business processes allow you to create formalized descriptions of typical sequences of work performed in an organization, and on their basis, create lists of tasks that need to be performed by a particular employee of the organization at a given moment. For example, the process of selling a product can be represented as a sequence of issuing an invoice, approving it, receiving cash payment and shipping the product from the warehouse. Different employees may be responsible for completing each stage, so at any given time you can determine the state of the product sales process and which employee currently needs to perform any actions.

Chart of accounts, Accounting register
Charts of accounts and accounting registers are intended to build a model that implements a double-entry bookkeeping system. They implement multi-level charts of accounts with fixed or variable codes, multi-level and multidimensional analytical accounting, accounting for several charts of accounts, accounting for several organizations, optional maintenance of quantitative, total and currency accounting for individual analytical sections, etc.

Calculation types plan, Calculation register
Payroll type plans and payroll registers serve to implement payroll models. They allow you to describe various types of calculation (for example, salary, personal surcharge, alimony, fine, etc.), set rules according to which some types of calculation can influence the results of other types of calculation, and store intermediate data and final results of calculations. With the help of these objects, the calculation of basic accruals, the calculation of personal income tax, the distribution of payroll results for the purposes of reflection in accounting, etc. can be organized.

Plan of characteristics types
Characteristic type plans are designed to store information about the characteristics of various objects. They allow the user to create all kinds of characteristics, describe the type of these characteristics and set their values. The characteristic type plan can be used, for example, to allow the user to describe products with an arbitrary number of arbitrary characteristics (color, size, smell, etc.). It allows you to create and store the name of a characteristic and the data type that the values ​​of this characteristic should take.

Exchange plan
Exchange plans are intended to describe the structure of a distributed information system and specify a list of data that will be exchanged within this distributed system. Allows you to create geographically distributed information systems both based on 1C:Enterprise information bases and using arbitrary information systems not based on 1C:Enterprise.

Selection bias
Selection criteria are used to select information in directories, documents, etc. They allow you to define rules according to which not all information existing in the database will be selected, but only that which meets the specified conditions. For example, using the selection criteria, you can organize the selection of documents related only to a specific counterparty.

Role
Roles allow you to describe various user access rights to data stored in the information base and determine the range of possible user actions. For example, the head of an organization can have full access to any information stored in the information base, while a storekeeper must operate only with warehouse documents and not have access to other information.

Event Subscription
Event subscriptions allow you to assign handlers for non-interactive events of one or more application objects.

Scheduled task
Scheduled tasks allow you to organize automatic execution of procedures of common modules according to a schedule.

External data source
External data sources allow you to use data obtained from external databases in your application solution. Including from databases not based on 1C:Enterprise.

Language
These configuration objects are used to create application solution interfaces in various languages. Thanks to the use of languages, it becomes possible to create multilingual application solutions in which the user can choose his own language to work with the application solution.

Session parameter
Session parameters are primarily intended for use in queries and to restrict data access for the current session.

Functional option, Functional option parameter
Functional options allow the developer to describe configuration capabilities that can be quickly turned on or off at the implementation stage and/or during system operation. For example, the ability to work with additional product properties can be separated into a separate functional option. Then if you disable this feature, all related (with additional product properties) features will “disappear” in the configuration interface.