1C: Enterprise. Element

2025: "1C: Enterprise. Element" 7.0

On March 3, 2025, 1C announced the release of the public final version 7.0 of 1C: Enterprise technology. Element and the start of sales of this technology for the development of its own applications in the 1C cloud and for local use.

Technology "1C: Enterprise. Element" extends the scope of the "1C: Enterprise" system. For example, it allows you to create applications focused not only on business, but also on the end user (consumer) - cabinets, storefronts, etc.

The familiar development model combined with the built-in programming language and interface layout capabilities allows you to develop applications on this technology for different target audiences and with different use cases:

• applications for companies where all users are known in advance. For example, offices and portals for employees (such as 1C: Employee's Office);
• applications for working with customers with or without open registration - for example, sites that allow customers to register themselves, or public storefronts and portals of companies;
• applications without a user interface: almost only or only with http or web services.

The listed variants are often combined. Also, the cloud provides tools for creating SaaS their own services by partners and end users of 1C.

Features of version 7.0 of 1C: Enterprise technology.Element:

• Cloud
  • The cloud has added the ability to use its own domain names.

• User Registration and Authentication
  • Improved mobile self-service operations. The following features have been added:
  • * getting a list of trusted mobile devices;
  • * adding the current device to the list of mobile devices from which * * * can log in using a PIN or biometrics (if supported by the device);
  • * Removing a mobile device from the list of trusted devices (for example, if the user has lost or changed the device)
  • * disabling the use of biometrics.
  • Now you cannot add a device to the list of trusted devices using biometrics only: you must first add a PIN. The PIN is installed on each device.
  • Single Sign On (SSO) and Single Logout (SLO) mechanics added between applications on the same server/cloud.
  • Added the ability to use TLS with client authentication in the http client.

• Development environment
  • The ability to track the developer's inactivity time has been added to the development environment settings. After the set time, the development session will be stopped, and 1C: Enterprise Element will display a window with a corresponding warning.
  • Improved appearance and usability of the development environment settings window.
  • A new Launch and Publish drop-down menu has been added to publish the project, open the application, start debugging the application, and open the control panel.
  • A new Bookmarks view has been added that displays all text files bookmarks created in the editor.
  • Improved the process of creating new items in the Project Navigator.
  • An input field has been added to the Project Explorer Project view to search for items by name.
  • Changed the display of open tabs in the editors window: to see all tabs, you can click on the special icon "Show other tabs."
  • Changed the display of icons for different file formats opened in the editor.
  • The text file editor uses bookmarks to mark lines in the program code to quickly move between them.
  • A convenient dialog for adding a command and component to the Component Tree is implemented.

Improved and simplified application interface localization process.

• Compatibility modes
  • The CompatibilityMode property settings in the Project.yaml file have changed.
  • * It is allowed to specify the compatibility mode corresponding to the old version of the technology (at least version 6.0). In this mode, the technology behaves like the specified version
    : old names of methods, properties and types work;
    Legacy API forms work
    The system behavior corresponds to the specified version of the technology.
  • * Compatibility mode settings must be the same as applications and all libraries (including transitive libraries).
  • * Do not lower compatibility mode. After publishing to an application server with compatibility mode N, you cannot publish with the N-1 configuration.
  • Improved the process of converting the project when changing the compatibility mode.
  • * Property Bar control has changed to increase compatibility mode.
  • * A new dialog has been implemented that allows you to choose how to increase compatibility mode.
  • * Added a notification that the project is in compatibility mode when the development environment is started.
  • * Converted out-of-date terms in project code.

• Interface components
  • Added the enumeration Std:: Interface:: ColorScheme, which defines the current color scheme of the application.
  • A color scheme toggle icon has been added to the action bar.
  • Added the ability to set commands to work with the input field.
  • Updated the logic of the InputField component when specifying a set of supported types in the Type parameter or in the ValidTypes property: values ​ ​ of valid types are presented as a combined drop-down list.
  • The mechanism for applying filters has been changed: confirmation at selection has been removed.
  • The order in which some handlers are called has changed: if the event handler is currently executing, then repeated calls to this event are ignored until the current handler completes. When finished, the handler is called again with the last argument.

• Project elements
  • New project item added - Accumulation Register. Accumulation registers are designed to store information about the availability and movement of funds: finance, goods, materials, etc. Use them to automate areas such as warehouse accounting, financial accounting, sales and production accounting, as well as data analysis and planning.
  • The report designer has added the ability to create parameters.

• Applied functionality
  • New Std namespace added:: Security containing objects for secure handling of sensitive and sensitive data.
  • Discussion subscription management methods have been added to the InteractionsSystem object.
  • Added interface component FormDiscussionsSystemsInteractions to work with discussions.
  • Support for the interaction system is implemented in the ArbitraryClientApplication component.
  • Support for WhatsApp message templates is implemented. They are used to create regular messages, and are also sent when initiating communication with the user or if more than 24 hours have passed since the user's last response.
  • The mechanism of inheritance of entity, type and service contracts is implemented. Contracts that have user-defined base contracts have their own properties and methods, as well as the properties and methods of the base contracts.
  • Validation of default values for contract methods and their implementations is implemented.
  • Added namespace Std:: Pdf for working with PDF files.
  • Project item ScheduledJob added.
  • When you create an application, all existing update handlers (@ ProjectUpdate) are marked as completed and are not called the next time the application is updated.
  • The search for files by regular expression is implemented.

• Query language
  • For the query language, we have implemented saving comments and their relative position in the text when formatting.