Add general 1c to the form. How to place commands in the command bar of a form? Where is the processing form located?

Standard form commands are automatically placed in the form's command bar. It always includes all commands provided by the form extension, plus the command Reference provided by the form.

Command panel auto-filled forms

1C8: The form command panel is filled in automatically

Change form...
Allow reshaping. By default the property has the value True, and the command is included in the command bar.

Form setup command

1C8: Form setup command

Including commands in the command bar Save settings... And Restore settings... determined by the value of the form property Saving data in settings. By default this property has the value Do not use, and the commands are not included in the command bar.

Commands for saving and restoring settings

1C8: Commands for saving and restoring parameters

NOTE
Some commands are displayed directly in the command panel and in the All Actions menu, and some are displayed only in the All Actions menu.

If form elements contain tables, then the command panel is also used to place commands for processing tabular data. In the tree of form elements it is located immediately below the corresponding table element

Commands for processing tabular data

1C8: Commands for processing tabular data

NOTE
When automatically generating a set of commands for a list form, the form has a combined command panel that contains both form commands and table commands.

Global parameterizable commands

When automatically generating a set of commands, only those global parameterizable commands are included in the form, which can take as a parameter a link to the main form attribute or to the details of the main form attribute. The default placement of global parameterizable commands is determined by their category and group.

The categories of standard commands are predefined and cannot be changed. But the developer can change the group (within the category) in which the team will be placed. The category and group of arbitrary (both general and subordinate) commands are determined by the developer by selecting a value in the property Group this team.
The developer can configure the visibility of global parameterizable commands automatically included in the form. But the system will not allow you to delete them.
Global parameterizable action commands are placed in the form's command panel. In the form editor, these commands appear on the tab Command Interface command editor.

Global parameterizable action command in the form

1C8: Global parameterizable action command in the form

To include an arbitrary global parameterizable command in the command panel of the form, in the Group property of this command, a group of commands with the category must be selected Form command panel.
For example, in the form we created, the command panel of the form includes the Receipt of money command, which creates a corresponding document based on the expense document being processed (see figure above)
For the command, a link to the document being processed is passed as a parameter (from the Link property of the main form attribute). Global parameterizable navigation commands are placed in the form's navigation bar. In the form editor, these commands are displayed on the Command Interface tab of the command editor.

Global parameterizable navigation command in the form

1C8: Global parameterizable navigation command in the form

To include an arbitrary global parameterizable command in the form navigation bar in the property Group for this command, a group of commands with a category must be selected Form navigation bar.

NOTE
By default, these commands are invisible and the navigation bar
not displayed. We have configured the display of the form navigation panel
in user mode.

For example, in the form we created, in the form navigation panel I will include The Sales Register command is used, which opens a list of register entriessales generated by the processed document.

For the command, a link to the document being processed is passed as a parameter (from the Link property of the main form attribute).

ATTENTION!
If a form (for example, a document list form) is opened in the main application window, the form's navigation bar is not displayed (regardless of the navigation command visibility setting) and the commands placed in it are not available.

Availability of form commands to the user
When creating a form for an application solution user, the system takes into account his rights determined by the role and the values ​​of functional options. It follows that the set of form commands available to a specific user may differ from the commands included in the form at the development stage.
As with visibility, the system uses different rules for commands from different sources to automatically determine their availability:

• the availability of standard commands provided by the form is independent of role-based rights settings and functional option values
• The availability of standard commands provided by the extension of the main form attribute depends on the role-based setting of user rights, and the values ​​of functional options do not affect the availability of commands
• The availability of global commands depends on the role setting of user rights and the values ​​of functional options.

To demonstrate the impact of role-based rights settings on the set of commands available to the user, we include the document Product consumption to the subsystem Pricing.

For the Pricing Manager role, set the Read and View rights to the document. For the arbitrary command Subordinate to the document, Print invoice, the View right will be removed.

NOTE
To eliminate runtime errors, we will set the pricing manager to Read rights to the Warehouses, Organizations, and Currencies directories.

The Administrator user has all rights to the Goods Consumption document. When building a document form (and a document list form), all standard form commands that were included in it at the development stage are included in the available ones.

Standard commands available to users with different roles

1C8: Standard commands available to users with different roles

For a user with the Pricing Manager role, only viewing Goods Consumption documents is allowed. When constructing a document form (and a document list form) for this user, the system excluded from the available commands extensions of the main details that perform operations with a document prohibited for the user - creating, deleting, posting a document, etc.
The availability of global commands in the form is determined by their availability in the global command interface, which is formed when the system is started on behalf of a particular user.

The 1C form usually has several fields for entering data, as well as buttons for form control and various service actions. For example, for automatic filling or verification.

In order to place a button on a form, earlier, in version 8.1, you had to:

• Drag a button to the panel
• Add a function - buttons
• In this function, write code in 1C language that will perform the required actions.

In order for the user to launch them, these actions have a visual representation on the form. What it will be depends on which group of form elements you drag the command into.

For example, if you simply drag it onto a form, there will be a button, if into a command panel group, then it will be a command panel button (flat), or you can drag it to a menu, then it will be a menu item.

The command can be used as regular form, and in the managed (command) interface 1C.

Standard 1C commands

But we also know actions that do not need to be programmed in the 1C language, since they are already available in the 1C platform. For example, for directories, standard actions are the ability to create an element. For the directory form - the ability to write, and for a document - to post. Are these also actions?

Yes, and now they are called standard 1C commands. Directories, documents, forms and others have their own standard 1C commands.

Standard 1C commands can be disabled for a specific one by checking the “Use standard 1C commands” checkbox in 1C on the “1C Commands” tab.

1C team owner

1C commands are located in the sub-branch of their owner. For example, Directories/Counterparties/1C Teams.

There are also 1C teams that do not have an owner, since they are shared. Such 1C commands are not tied to objects and are located in the General/General 1C commands branch.

1C command parameters

In the configurations in reference books and documents there was a “Go” menu with which you could magically go to related 1C objects.

For example, for the Counterparties directory, the legal and physical addresses are stored in the associated Contact Data register. To go to it, you had to select the menu in the form of the counterparty(s) - Go/Contact details.

That is, for some actions, not only the fact of launching the action is required, but also a parameter that determines for which object these actions need to be performed - for example, for which counterparty to display contact information.

In the properties of the 1C command it is possible to specify:

• 1C command parameter type – type of 1C object that will be used as a parameter, for example, the Contractors directory
• Mode of use parameters – you need one value or a list (array).

To place a command on a form, you can specify in the 1C command properties the command interface group where it should be located.

Or simply drag the command to the list of form elements.

Any group of buttons (command bar, submenu, group of buttons, context menu) is filled in according to the same rules:

1. first come the buttons provided by the command source with which this group is associated;
2. then comes a fragment of the command interface, if the command source implies its inclusion;
3. then there are custom commands added to this group;
4. then there is a submenu All actions(for command panel only);
5. and at the end there is a button Reference if it was provided by the command source.

Let's consider the simplest option, when two commands are created in the form of a directory element and placed in the command panel of the form.

As a result, in 1C:Enterprise mode, the location of buttons corresponding to the created commands Team1, Team2 corresponds to the algorithm described above: in the command panel of the form and in the submenu All actions first are the commands provided by the command source - the form of the directory element (for example, Write and close, Write etc.), then commands created by the developer ( Team1, Team2), and then the command Reference.

However, there are several ways for a developer to significantly intervene in this process and improve the readability of the command bar, context menu, etc. What options are there to change the composition and order of the buttons?

1. You can separate developer-created commands from other commands with a separator.

To do this, you need to create a group like this in the command panel Button group and transfer these commands to it.

2. You can place some developer commands at the beginning of a group of commands.

To do this, you need to cancel the command source for the group (for the context menu and automatic command bar, you need to turn off the checkbox Autofill), then add your button to the group, after it add a group of the form Button group and install this group command source- For example, Form.

All actions will have the following form.

3. You can move the auto-fill buttons.

To do this, you need to place in the command bar or context menu tree a button associated with the same command that is filled in from the data source (for example, Delete, Copy and etc.). Automatically, such a button will not be placed among the standard commands and, thus, you can move the standard command to another location.

As a result, in 1C:Enterprise mode, the command panel forms and submenus All actions will have the following form.

To command icon Delete was displayed in the command panel of the form, you need to set the property of this button OnlyInAllActions in meaning No.

4. You can change the order and visibility of the buttons of the command interface fragment provided by the command source Form.

For example, a configuration object has a directory Counterparties there is a team Team3. This command has command placement group - Form command panel. Important and command parameter type - DirectoryLink.Counterparties.

After setting these properties, Team3 becomes available to the bookmark Command Interface the form of an object whose type is a command and is located in the command panel of the form after the standard commands supplied by the form of a directory element.

As a result, in 1C:Enterprise mode, the command panel forms and submenus All actions will have the following form.

Team3 is part of the command group of the command interface fragment. If you are not satisfied with the place where a fragment of the command interface is inserted, you can place a group like this in the command panel Button group and install this group command source - Global Form Command Bar Commands.

In this case, the automatic placement of the fragment will be canceled (similar to a standard button added manually), and the command interface fragment will be displayed in a new group.

As for the contents of the command interface fragment, its editing is available on the tab Command Interface form editor.

5. You can turn on/off the visibility of standard commands provided by the command source, for example - Form.

To do this you need to open a window Team composition in the form properties palette.

Finally, note that there is no option to change the order of the buttons provided by the command source. If such a need arises, you need to cancel the source from the group of commands and completely fill the group manually.

The 1C:Enterprise 8 technology platform is used to automate a wide range of management and accounting tasks at a wide variety of enterprises. With such a wide range of applications, situations may naturally arise where the functionality of standard commands is not enough.
To implement additional functionality, the built-in 1C:Enterprise language is used. This functionality is mainly implemented in event handlers. However, there is also a need to provide users with the ability to interactively access part of the implemented functions from the interface.

General arbitrary commands allow you to implement non-standard functionality that is generally related to the application solution. In this case, an arbitrary command is created as an independent configuration object belonging to the class General commands.

Arbitrary general commands

For example, let's look at how to make and configure all the properties of the command “Set up a barcode scanner”. Trade enterprises often need to automate the process of registering goods sold. Barcode scanners are used for this. However, the technology platform does not “know” anything about these devices and does not have the means to work with them. Therefore, to work with a barcode scanner, you need to connect a special program - a driver. To connect such a driver, a general custom command is implemented: Install barcode scanner. By setting certain values ​​for the properties of this command, the developer ensured its availability to users.

Custom general command “Configure scanner”

The functions for working with the scanner are common to the entire application solution, that is, they do not relate to any specific configuration object, so an arbitrary command is implemented as a general one.
The command performs an action - connects a driver to the application solution to work with a barcode scanner. Therefore, it is located in the action bar of the main application window.

Another common task is obtaining hard copies of electronic documents. The composition of documents and their structure are determined by the application task being automated. Naturally, it is impossible to provide for all the variety of documents and options for their printed forms in the platform. In order to “teach” a document to “transfer” itself to paper, you can use an arbitrary command.
In the demo database to obtain a printed form of the document Product consumption subordinate team created Printing Invoice

Arbitrary subordinate command “Print invoice”

Command property values Group And Command parameter type determined the location of the command in the command interface - the Print menu of the command panel of the document form, and the procedure in the built-in language ensured the formation of a printed form of a specific document, a link to which is passed in the command parameter.
Another, rather specific use case for arbitrary commands is to extend or override the standard functionality of a standard command. Such tasks arise, for example, due to the requirement to reduce the number of manual operations or change the standard behavior of objects.
For example, our database implements a processing object Administrative service. The command for opening the main form had to be placed in the navigation panel, and the form itself had to be opened in the work area of ​​the main application window. But the standard functionality of this object differs from the required one - the command to open the form is located in the action bar, and the form opens in a new auxiliary window.
To ensure the required functionality, the Use standard commands property has been removed from the processing - standard commands do not suit us.

Disabling the use of standard commands

Access to processing is provided by an arbitrary subordinate command Administrative service, which is set to be located in the Normal group of the navigation bar of the main application window. As a result of selecting this command, a processing form is displayed in the work area of ​​the main window.
There are many similar problems in specific application solutions, and arbitrary commands are the most suitable for solving them.

Arbitrary subordinate command “Administrative service”

Features of accommodation
A feature of arbitrary commands, compared to standard ones, is the need to describe their default location in the command interface. The location of an arbitrary command is specified by the developer when configuring the application solution.

The default location in the command interface for arbitrary commands is determined by:

• category and group assigned to the team
• the command’s belonging to the configuration subsystem (for independent commands) and the type of command parameter (for parameterizable commands).

ATTENTION!
Command property Group must be filled out. Otherwise, an error will occur when updating the database configuration and the update will fail.

When choosing a group for a command, you should pay attention to the need to pass parameters to the command and the actions that the command performs. As a general criterion, it can be suggested to adhere to the same rules that are used for standard commands.

• If a command does not require parameters for its execution, then select a group for it with the category Navigation panel or with the categoryAction bars.
• If a command requires passing a parameter for its execution, then for it you must select a group with the Form Navigation Panel category or the Form Command Panel category.
• For commands, the execution of which leads to changes in the information displayed in the work area of ​​the same window, you should select a category Navigation bar for independent teams or Form navigation bar for parameterizable commands.
• For commands the execution of which leads to changes in data in the infobase, you should select a category Action bar for independent teams or Form command panel for parameterizable commands. It is also recommended to select this category for commands that will lead to the opening of a new window to display selection forms, report forms, and processing forms.

To include a common independent command in a particular section of the command interface, you must indicate its affiliation with the corresponding subsystems. Including a command in subsystems is done by checking it in the Composition of required subsystems property.

It is impossible to directly include a subordinate command in the subsystem. Therefore, subordinate independent commands are automatically included in the command interface of those subsystems in which the command's owning object is included.
But parameterizable arbitrary commands, both general and subordinate, are included in the command interface differently. This is due to the fact that the command can only obtain the actual value of its parameter from the form data. This is why parameterizable commands can only be placed in the form's navigation bar or in the form's command bar. Moreover, this value must have a data type that is valid for the parameter. The list of allowed parameter types is set in the property Command parameter type

The list of allowed parameter types for a parameterized command is determined by its “Command Parameter Type” property

By comparing the composition of the types specified in the command property with the types of form details, the system decides whether to include the command in one form or another.

A parameterizable arbitrary command is included in the form only when the form has at least one attribute with a type included in the allowed ones. When checking, details that are subordinate to the main form details are also taken into account. The composition of the checked subordinate details is limited to the first level of subordination.
Let's return to solving our problem of separating the functionality for working with prices into a separate subsystem. In addition to setting prices, we will also need the ability to print price tags for goods. In this case, it is necessary to implement two modes:

/
Developers /
Designing interfaces for 8.3

Document Command Panel

Scope: managed application.

1. In the command bar, the default button should be located on the far left. In the vast majority of cases, the default button is "Swipe and close" or "Save and close"

2. The order of commands in all documents must be the same.

3. It is not recommended to change the composition of the system command bar buttons displayed by the platform by default and their order relative to each other.

4. The command panel should allow the user, with standard screen settings (screen width 1024 pixels, toolbar displayed vertically on the left), to perform the most important and frequent actions with the document, without opening the “More” submenu.

5. For documents that have printed forms and on the basis of which other documents can be entered, it is recommended to create the command panel from several groups:

1. System commands “Post and close”, “Write”, “Post”

2. Important application commands.
For example, the "Print" submenu

3. Other system and application commands
For example, the “Create from” submenu, the global commands “Subordination Structure” and “Additional Information”.

With standard screen settings, the user should immediately be able to see all the commands of groups 1 and 2, and some (or even all) of the commands of group 3 can be moved to the “More” submenu.

With this approach, the commands will be arranged in the following order:

Post and close / Record and close

Write down

Conduct

Document movements

Create based on

Reporting structure

additional information

For example, the command panel of the document "Invoice for payment":

In the Configurator, the command panel elements are structured as follows:

Command panel: Autocomplete - no

Group 1: CommandBarButtons Group: button group, command source – Form

Group 2: Group Important Commands: group of buttons, empty command source. The "Print" submenu is placed in this group programmatically using the BSP.

Group 3: GlobalCommands Group – a group of buttons, command source - Global commands of the form command panel.

Form Help: Only in all actions – “no”. Standard form command.

The "Subordination Structure" and "Additional Information" buttons have been added to the GroupGlobalCommands group explicitly so that they are shown to the user last, after other global commands. In a standard screen setup, these commands will only appear in the More submenu.