New functionality and changes

Functionality After Before Result of changes
Configuration properties. Version 8.3.2 is added to the list of available values of the Compatibility mode property. Compatibility modes were available for the following platform versions: 8.1, 8.2.13, 8.2.16, and 8.3.1. In version 8.3.3 you can run configurations created in version 8.3.2 or earlier without making changes to the configuration and without changing its data structure. This allows you to perform quick transition to version 8.3.3 without making any configuration changes, then work with the configuration as usual and remove the compatibility mode at later time. This also allows you to use version 8.3.2 for working with the infobase even after the transition to version 8.3.3. You can use this option both before and after the compatibility mode is removed (in the latter case you have to turn the compatibility mode back on).
Managed form. You can specify settings for vertical scaling of form elements, namely the minimum element height, at the development stage in Designer using the new VerticalScroll property.

If a form has a vertical scroll bar and the command bar is located above or below all form elements and occupies the entire form width, the area being scrolled does not include the command bar.

Managed form elements could be reduced to the default minimum height by reducing the form height. If a managed form had a vertical scroll bar, the area being scrolled included all form elements. Elements of managed forms with vertical scroll bars cannot be compressed below the minimum height guaranteeing comfortable work. The command bar with important form commands, such as Write and close, is always available because it is not included in the area being scrolled.
Managed form. Web client. In the web client, if the VerticalScroll property of the managed form is set to UseIfNecessary, reducing the vertical form size never leads to reducing the vertical size of the form elements to the point where they can no longer be used. In the web client, reducing the vertical form size could lead to reducing the vertical size of the form elements to the point where they could no longer be used. Eliminated situations when reducing the vertical form size led to reducing the vertical size of the form elements to the point where they could no longer be used.
Developing tools. In the built-in script editor, you can group an arbitrary number of lines in the same way as they are grouped in some syntax units (conditions or cycles). 

#Region and #EndRegion preprocessor instructions are implemented. These instructions are ignored during script execution. A template for creating a script fragment with line grouping is added to the set of standard templates.

This feature was not provided. Only a few script syntax units allowed line grouping. Improved usability for working with source text. You can group parts of source text in a logical way and hide text that is not used at the moment. 
External data sources. Support of the following OLAP sources is added to the external data sources mechanism:
  • Microsoft SQL Server Analysis Services
  • IBM InfoSphere Warehouse
  • Oracle Essbase

Requests to OLAP sources and errors that occur during the request execution are recorded to the EDS event of the technological log.

The following pictures are added to the picture library: ExternalDataSourceCube, ExternalDataSourceCubeDimensionTableObject.

External data sources provided access to relational tables only. Both relational data and OLAP sources can be used when creating reports based on data from external systems (external data sources).
Interface. You can get the resolution and DPI of monitors connected to a computer in the client application (thin client, thick client, web client) and at the server. For the external connection, the GetClientDisplayInformations() method returns UNDEFINED.

The information on characteristic of client computer monitors is passed through at the session start and when the RefreshInterface() method is called.

You could get the information on monitors connected to a computer only on the mobile platform. You can determine the number of monitors connected to the computer where the application is being executed, as well as their characteristics.
Data composition system. For conditional appearance elements, you can specify areas where the given conditional appearance element will be used.

This feature is not used in dynamic lists.

This change is not implemented in 8.3.2 compatibility mode.

The conditional appearance was applied both to data area and area header, without further customization Extended formatting capabilities for complex reports.
Tools for publishing the web client and web services. Infobases, web services, and mobile applications can be published from Designer that is running on Linux.  Publishing can only be performed to Apache web servers and only if Designer is running under root account. Publishing of infobases and web services on Linux was possible only using the webinst utility. Publishing mobile applications was not available on Linux. Eliminated some Designer limitations on Linux.

You can create distribution kits in the Linux version of Designer. The platform distribution files now include an installation program that installs templates and updates for applied solutions that run on Linux. The installation program supports both 32-bit and 64-bit Linux versions. The installation program shares the list of Linux operating systems with the client application. Creation of distribution kits was not available on Linux. You can install templates and update applied solutions on Linux operating systems.
Autorun. The Autorun application is capable of running on Linux. The application supports both 32-bit and 64-bit Linux versions. The application shares the list of Linux operating systems with the client applications. The following properties are added to the Element section of the autorun.lst configuration file: CommandWindows, CommandLinux, and RunAsRoot. The properties specify how a given item is executed in various operating systems. The Autorun application was not available for Linux systems. The autorun.lst configuration file did not include CommandWindows, CommandLinux, and RunAsRoot properties. You can create applied solution distribution kits that include the Autorun application and are delivered on removable media that can be used to install the solution on both Windows and Linux operating systems.
Applied objects. Managed form. Objects of reference types can be created while data is being entered in a form. A new property of configuration objects and form elements is implemented for this feature. The form element property manages the visibility of the command that creates a choice list element. The feature is implemented for catalogs, documents, charts of characteristic types, charts of accounts, charts of calculation types, business processes, tasks, and exchange plans. The command for creating a choice list element is not available in version 8.3.2 compatibility mode. This feature was not provided. Users had the option to open the choice form and create an object there, and then select the created object. Improved usability in cases when object creation is required while data is being entered.
Managed form. Development tools. In the managed form editor, the list of elements available for adding to the form now includes a usual group without a title. In the managed form editor, in order to create a usual group without a title, a developer had to add a usual group and then change the properties that define whether the title is displayed. Improved usability of editing managed forms when groups are used for defining element positions on the form.
Managed form. Developing tools. During the generation of event handlers for client form elements and commands, you can specify which procedures will be generated:
  • A client handler only
  • A client handler and a server procedure (to be executed outside of a context) that is called from the handler
  • A client handler and a context server procedure that is called from the handler

A context server procedure cannot be generated for those client handlers where calling context server procedures is not recommended.

When a client handler was generated, this only included the generation of the handler itself. The associated procedures were not generated. Simplified development of forms where actions that are called at client are executed at server. Developers no longer have to create the server method manually and then add the method call to the client handler body.
Configuration repository. The data storage format of the configuration repository is modified. Repository objects are stored in the file system. The 1cv8ddb.1CD file stores information on changed objects. The compatibility mode is implemented for the configuration repository. The new storage format is available only if the compatibility mode is disabled. Optimization of configuration repository data is introduced. The optimization procedure is available both from the repository administration window and by using the ConfigurationRepositoryOptimizeData command-line option when Designer is started in batch mode. The format of configuration repository files is not intended for reading or writing by any tools other than 1C:Enterprise. All configuration repository data was stored in the 1cv8ddb.1CD file. Optimization of the configuration repository was not available. Significantly increased number of changes (versions) that can be stored in the configuration repository.
Developing tools. Client application. The infobase selection dialog box and the two authentication dialog boxes (for access to infobases and configuration repositories) that are displayed during the start of a client application or Designer can be disabled.

To disable them, use the DisableStartupDialogs command-line option for the 1cv8.exe/1cv8 file.

If the command-line that starts a client application or Designer contains errors that led to displaying these dialog boxes in earlier platform versions, the dialog boxes are not displayed; diagnostic messages are generated instead. These messages are recorded to the file that stores service messages (the Out command-line option).

During the start of client application or Designer in the batch mode, provided that infobase parameters or authentication parameters contained any errors, modal dialog boxes that prompted users to enter the correct parameters were displayed. This paused the execution of the entire batch. When Designer is started in batch mode - especially if Designer is started from another application or service - it is now possible to avoid the hard-to-detect situations when Designer attempts to create a selection dialog box for parameters that cannot be specified interactively, and therefore stops responding.
Localization. The NumberInWords() and PeriodPresentation() global context methods support French language. The language code is as follows: fr, fr_CA. Values of the NumerationItemOptions parameter of the NumberInWords() method are specified similar to English, Finnish, and Kazakh languages. The NumberInWords() and PeriodPresentation() global context methods did not support French language. Improved presentation of information for French-speaking users.
Managed form. Full-text search. For the FullTextSearchList object, you can disable the search by presentations of configuration objects. Use the MetadataUse property of this object to enable or disable this feature. The search by presentations of configuration objects could not be disabled. You can search by data only, without seaching by presentations of configuration objects at the same time.
1C:Enteprise script. For the Array, Structure, and Map collections implemented constructors that create these objects based on the corresponding fixed collections (FixedArray, FixedStructure, and FixedMap). Recursive conversion is performed for arrays—a fixed array item that is a fixed array itself is recorded to a regular array. Fixed collections could be converted to their regular analogs only by using program loops. Simplified editing of values stored in fixed collections.
Common attributes / Data separation. Exclusive access can be set for a data area. Exclusive access is not compatible with any data locks set by other sessions in this area. Exclusive access to a data area must be explicitly set or removed using the SetExclusiveMode() method. When a background job is started from a session that set exclusive access to a data area, the background job obtains exclusive access and the parent session loses exclusive access until the parent session is completed. At this time, changing data from the parent session is not available. Exclusive access is returned to the parent session after the background job completion. When a session switches to a different area, this does not affect the list of areas where the session has exclusive access.

Exclusive access to an area prohibits the following actions:

  • Creation of new sessions with the same set of separators.
  • Access to the area-contained data from enveloping areas.
  • Setting exclusive access in enveloping areas.

Setting shared managed locks for an area is ignored if exclusive access is set for this area.

Exclusive access to a data area could not be set. Instead, you only could set an exclusive managed transaction lock to all area-contained data. You can perform consistent changes of the data area even if they cannot be included into a transaction.
Common objects. The DataHashing object can calculate the SHA1 and SHA256 hash functions. The DataHashing objects could calculate only the MD5 and CRC32 hash functions. The list of supported hash functions is extended.
Applied objects. You can create defined types. A defined type consists of one or several allowed types, and it has a unique name. Defined data types can be used as types of configuration object attributes. Defined types cannot be included in complex types and cannot be used as data types for charts of characteristic types. If you want to run the applied solution on a previous platform version, you have to remove all defined types from the configuration. This feature was not provided. You can create a type that can be used for defining types of specific attributes. For example, in a universal multipurpose configuration fragment, you can describe attributes that refer to data that will be defined when the fragment is included into a specific configuration.
Mobile application. You can choose a ZIP archive containing multiple pictures of different sizes, instead of a single picture, for the application. This option is targeted for mobile applications that can be used in devices with different screen resolutions. The following mobile device screen types are supported:
  • devices with screen resolution below 140 DPI
  • devices with screen resolution from 140 to 180 DPI and Apple devices with standard screens
  • devices with screen resolution from 180 to 270 DPI
  • devices with screen resolution over 270 DPI and Apple devices with Retina screens

Each picture corresponds to specific screen settings of the target device. It is recommended that you use the PNG format for the archived pictures and you create the archive without compression. For the Picture object, the ChoiceSet property is implemented.

This feature was not provided. On the mobile platform, the developer had to specify multiple picture versions for various screen resolutions using 1C:Enterprise script. Simplified process of creating applications intended for running on both PC and mobile devices. The developer only has to provide pictures for different display resolutions, and they do not have to write the script for resizing the pictures before displaying them in 1C:Enterprise mode.
Accumulation registers. Accounting registers. In accumulation and accounting registers, the interval for storing totals by periods can be limited. You can specify both the lower and the upper boundary of the interval. Totals within this interval can be recalculated automatically when totals outside of the interval are changed. Totals by periods are not stored outside of the interval. They are calculated by register record tables when needed. For accumulation register managers and accounting register managers, the following methods are implemented: SetMinTotalsPeriod(), GetMinTotalsPeriod(), and SetMinAndMaxTotalsPeriods().  The totals storage limits are taken into account when the chart of accounts is changed, when register records are generated, when totals are recalculated, and when balance is obtained by balance accumulation and accounting registers. When totals are enabled, periods are only recalculated if they contain actual changes. This change is not implemented in 8.3.2 compatibility mode. Totals were stored by all periods later than the period of calculated totals for the register. When register records were changed for a prior period, all totals were recalculated for periods later than the modified date. When using totals was turned on, all register totals were also recalculated. This change reduces database size and optimizes performance of administrative operations. This decreases the system load for databases that store data for long periods (several years), and where changes in prior periods are performed on regular basis but regular data retrieval (using totals) is performed within a limited time interval from the current date.
Add-ins. The add-in creation functionality includes the option to display interactive messages to users and the option to store values between sessions in a local web browser cache. The add-in creation functionality did not include the option to display interactive messages to users or the option to store values between sessions in a local web browser cache. When a web browser add-in attempts to access local resources, warnings can be displayed. They are similar to warnings available in the built-in platform features.
Web client. Spreadsheet document. Printing documents. Documents intended for printing can be combined into batches. To print the entire batch, you only have to start printing once. You can specify printing options for batches. Batches can be nested. A batch can be written to a single PDF file, which simplifies printing in the web client. The RepresentableDocumentBatch object is implemented. Batch printing was not available in the web client. To print a set of documents, the user had to click the Print button for each single document. Improved usability of printing muptiple documents (with different printing options) in the web client. To print a batch of documents, the user has to start printing once (regardless of the number or documents in the batch), and the printing options (including page orientation and the number of copies) will be set for each individual document.
Server cluster. In the client/server mode, security profiles are implemented for the purpose of managing applied solution access to the following external resources on 1C:Enterprise server: file system, COM objects, add-ins, operating system applications, Internet resources, privileged mode, external reports and data processors, and global context methods Execute() and Eval(). A security profile can be assigned to each infobase; a security profile can also be assigned to the source code that is executed in the safe mode.

For the purposes of software cluster administration:

  • ISecurityProfile object is implemented.
  • ISecurityProfileVirtualDirectory object is implemented.
  • ISecurityProfileCOMClass object is implemented.
  • ISecurityProfileAddIn object is implemented.
  • ISecurityProfileExternalModule object is implemented.
  • ISecurityProfileApplication object is implemented.
  • ISecurityProfileInternetResource object is implemented.
  • For the IServerAgentConnection object, the following methods are implemented: GetSecurityProfiles(), RegSecurityProfile(), UregSecurityProfile(), CreateSecurityProfile(), GetSecurityProfileVirtualDirectories(), RegSecurityProfileVirtualDirectory(), UnregSecurityProfileVirtualDirectory(), CreateSecurityProfileVirtualDirectory(), GetSecurityProfileCOMClasses(), RegSecurityProfileCOMClass(), UnregSecurityProfileCOMClass(), CreateSecurityProfileCOMClass(), GetSecurityProfileAddIns(), RegSecurityProfileAddIn(), UnregSecurityProfileAddIn(),CreateSecurityProfileAddIn(), GetSecurityProfileUnSafeExternalModules(), RegSecurityProfileUnSafeExternalModule(), UnregSecurityProfileUnSafeExternalModule(), CreateSecurityProfileUnSafeExternalModule(), GetSecurityProfileApplications(), RegSecurityProfileApplication(), UnregSecurityProfileApplication(), CreateSecurityProfileApplication(), GetSecurityProfileInternetResources(), RegSecurityProfileInternetResource(), UnregSecurityProfileInternetResource(), and CreateSecurityProfileInternetResource().
  • For the IInfoBase object, the following properties are implemented: SecurityProfileName and SafeModeSecurityProfileName.
  • The type of the SafeMode parameter (used in the Create() and Connect() methods of external report and data processor managers and in the SetSafeMode() global context method) was changed from BOOLEAN to STRING. The type of value returned by the SafeMode() global context method was changed from BOOLEAN to STRING. When this parameter (or returned value) has STRING type, it stores the security profile name.

Similar changes are implemented in:

  • Cluster administration utility (rac) – the profile mode is implemented, and the update command of the infobase mode is modified.
  • Java API for server administration.
This feature was not provided. You can limit access of applied solutions to the resources of the system in which they run by using administrative tools (without modification of the applied solution source code). The functionality of the source code that is executed in the safe mode (for example, code developed by user) can be extended while preserving the required security level.

For example, you can use security profiles to organize individual temporary storage directories for each data area, or describe the list of Internet resources available for use in a specific infobase.

Automated testing. The following objects are implemented:

TestedCommandInterfaceButton, TestedCommandInterfaceGroup, and TestedWindowCommandInterface. For tested objects, the GetObject() method is implemented. Its set of parameters is similar to that of the FindObject() and FindObjects() methods. If the object is not found, the GetObject() method raises an exception. Methods for testing user messages are implemented. The list of properties and methods for managing tested objects is extended. You can get the form name, the current window, the command interface, and so on. You can get the information on the last error that occurred in the tested client application. For the TestedApplication object, the methods GetActiveWindow() and GetCurrentErrorInfo() are implemented. For the TestedClientApplicationWindow object, the methods GetCommandInterface(), GetUserMessageTexts(), and ChooseUserMessage() are implemented. For the TestedForm object, the FormName property and the methods FindDefaultButton(), CurrentModified(), and GetCommandBar() are implemented, while the Close() method is moved to the TestedClientApplicationWindow object. For the TestedFormField object, the methods CurrentModeIsEdit() and GetEditText() are implemented, and the methods BeginEditCurrentArea() and EndEditCurrentArea() are modified. For the TestedFormTable object, the method CurrentModeIsEdit() is implemented, and the methods ChangeRow(), EndEditRow(), GotoPreviousRow(), GotoNextRow(), Expand(), and Collapse() are modified. For objects that describe tested form elements, the methods GetToolTipText(), CurrentVisible(), CurrentEnable(), CurrentReadOnly(), GetContextMenu(), and GetCommandBar() are implemented.


The application window command interface could not be tested automatically. Operations on user messages were not available during the automated testing. You can test the application window command interface automatically. In test scenarios, simplified the processing of errors that occur when attempts to get non-existent objects are made.
Dynamic list. Dynamic list settings can be saved automatically. For managing this feature, the Auto save user settings property is implemented for dynamic lists. For storing settings, the dynamic list settings storage is implemented. For managed form tables linked to dynamic lists, the following functionality is implemented: commands for saving and restoring settings, and events for implementing custom responces to saving, restoring, or editing dynamic list settings. The view mode of the dynamic list (list, tree, or hierarchical list) is stored together with form element settings.

You can edit user settings of a dynamic list in a separate group of the form that displays the dynamic list. For that purpose, the User settings group property is implemented. Dynamic list settings can be edited in a separate common form, which is specified using the Default dynamic list settings form configuration property.

For the DynamicList object, the SettingsComposer property is implemented, which is similar to the corresponding property of report objects.

This change is not implemented in 8.3.2 compatibility mode.

For dynamic lists, only the following settings were saved automatically: filters (that were restored with disabled usage flag) and conditional appearance. To save and restore other settings, developers had to create custom algorithms in 1C:Enterprise script. Improved usability of dynamic lists for end users. Simplified development of dynamic lists with quick access to filters for developers. Development of custom algorigthms for saving or restoring dynamic list settings is not required.
Managed form. A new permission allowing end users to expand or collapse a managed form group (only vertically) was added. If the permission is granted, a user can collapse the group (hide all of the items that are included in the group). For managed form groups, the following properties are implemented: Behavior, ControlRepresentation, ShowLeftMargin, and CollapsedRepresentationTitle.

Only usual groups with displayed titles can be collapsed.

This feature was not provided. The only available method to hide unused items was to change their visibility.

Hiding form items that are rarely used is available. This decreases the amount of data that is displayed to an end user. To view the hidden data, an end user can expand the group.


Developing tools. On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed is displayed in the message window. On an attempt to modify a configuration object that cannot be modified, a message informing that the action cannot be performed was displayed in a modal window.

Developers no longer have to close modal dialog boxes many times when they attempt to perform mass modification of objects that cannot be modified (for example, objects stored in a configuration repository that are not locked).

Interface. A new client application interface type "Taxi" is implemented.

The Taxi interface includes a large number of changes, with the following highlights:

  • A whole new view: enlarged fonts, increased spacing between elements in forms, modified color scheme and form element layout, enlarged form elements.
  • Improved application navigation: focus on a single-window functionality, single purpose panels (such as history or favorites), switching back and forward between previously opened windows, and so on.
  • Extended main application window settings: developers can define the content and location of panels for the applied solution, at the same time users can arrange these panels as they like.
  • A system form for the full-text search.
  • The form navigation panel is located in the upper part of the form.
  • The message window is located in the lower part of the form and is only visible when there are messages to display.
  • The performance meter is displayed in a separate application window panel, not in a separate window.
  • In the History panel, records are grouped by days with their opening time displayed. You can search for history items and add them to Favorites.
  • In the Favorites panel, you can search for items, rename them, and "pin" important ones at the top of the list.

Use the iTaxi command-line option of the client application for the forced start of this interface mode (provided that using Taxi is allowed in the applied solution). You can also switch between interface modes using the client application settings window. The following configuration properties are implemented:

  • InterfaceCompatibilityMode - specifies which interface modes are available in the applied solution.
  • ClientApplicationInterface - stores the list of panels used by default in the client application, as well as their positions.
  • DefaultSearchForm - specifies the search form that is used for the full-text search in application data. If the form is not specified, the system full-text search form is used.


A brand new look for the calendar. For the managed form calendar field, the following properties related to the new features are implemented: HeightInMonths, WidthInMonths, and ShowMonthsPanel. These properties are only used in the Taxi interface. For the ClientApplicationInterfaceVariant object, the ClientApplicationInterfaceVariant property is implemented (it is used for getting the interface mode), and the global context method ClientApplicationInterfaceCurrentVariant(). The ClientApplicationBaseFontCurrentVariant() global context method is implemented. It gets the size of the base font in the client application. For the UserWorkFavoritesItem object, the Important and Presentation properties are implemented. In the Taxi interface, the Desktop is renamed to Start page (the related commands are renamed accordingly). The Dashboard section of the section pane is used for accessing the command interface. In the Taxi interface:

  • The All actions menu is renamed to More.
  • The default presentations of standard commands in forms are changed, as well as command presentations in the command panel and in the More menu.
  • The presentations of form item groups are changed.

The link to the start page (desktop) of the applied solution has the following format: e1cib/navigationpoint/startpage. Start page (desktop) settings are stored with the settings key StartPage/WindowSettings (for Taxi interface, StartPage/Taxi/WindowSettings). In the managed form editor, switching between interface 8.2 and Taxi modes in the preview window is implemented.


The interface implemented in platform version 8.2 was used in managed applications. Improved applied solution navigation, improved usability, development according to modern interface design trends.
Interface. The NormalTextFont style font used as a basis for size calculation for other style fonts except the TextFont is implemented. The actual choice of font depends on the interface mode of the applied solution (Taxi or interface 8.2). This feature was not provided. Using the new font (and the fonts based on it) allows storing fort size proportions for managed form elements in both interface modes.
Interface. The MainSectionPicture configuration property is implemented. In this property, you can specify a picture that will be used for the main section (desktop) in the section panel. The desktop had a fixed picture that could not be changed. You can create a uniform graphic design for your applied solution, and you can create a desktop look that will be friendly to the primary audience of the solution.
Development tools. A context tooltip can be displayed for the

parameters of the function or procedure that is being edited in the module text editor. If the method has several syntax variants, you can select the required variant. Automatic parsing of procedure and function comments for displaying them in context tooltips is implemented. Procedure and function comments can be sorted for displaying in the context tooltip. The comment format is described in the documentation and complies with the applied solution development standards. Procedure and function templates that comply with this format are included into the distribution kit. The option that shows or hides the context tooltips is implemented in Designer. In the source code editor, you can open the context tooltip by pressing Ctrl+Shift+Spacebar.

In Designer, context tooltip for procedure and function parameters was not available. The context tooltip was only available for names of applied solution procedures and functions. Comments to procedures and functions were not used for getting information on their parameters. Improved usability of writing source codes. The Syntax Assistant is not required for a quick reference on the order and types of procedure or function parameters.
Administration tools. The documentation describes DBMS setup and maintenance features that can be used for 1C:Enterprise administration. The documentation did not describe the administration tools that could be used without violating the license agreements. You can use DBMS features that do not affect the structure of data used by 1C:Enterprise (the changes that are made do not affect the restructuring and are saved after the restructuring).
Managed form. For fields of check box and radio button types, the tumbler look is implemented (several adjacent buttons where the active value has a different color). For managed form fields of these types, the properties CheckBoxType and RadioButtonsType are implemented. This feature was not provided. New presentation features. Improved usability for touch interfaces.
Database configuration update. Server cluster. Infobase restructuring is required when a chart of characteristic types is modified or when a chart of accounts where a chart of characteristic types is used as an extra dimension,is modified.

The following changes are implemented in the background restructuring procedure:

  • You cannot create, edit, or delete exchange plan items if the exchange plan requires the restructuring. The restructuring is performed during the processing phase.
  • You cannot create, edit, or delete chart of characteristic types items if the chart is specified as an extra dimension for a chart of accounts and this chart of accounts requires restructuring. In this case the restructuring of the chart of characteristic types is performed during the processing phase.
  • The SetPredefinedDataUpdate() method cannot be called during the background restructuring.
Charts of characteristic types were restructured when they were modified.

All charts of characteristic types and exchange plans were restructured when the changes were applied (during the background restructuring).

In the background database configuration update, the specifics of changing some data structures are taken into account. This prevents mismatching of object data.
System requirements. Microsoft Windows Server 2012 (x86-64) is now supported. Microsoft Windows Server 2012 (x86-64) was not supported. New version of the Microsoft operating system is now supported.
Display of information. If the Interface compatibility mode configuration property is set to Taxi or Taxi.Version 8.2 enabled, the Help picture from the picture library corresponds to the Taxi interface. The appearance of the Help picture in the picture library did not depend on the configuration property values. The appearance of the Help button depends on the interface mode.

Table of contents

Next page: New functionality and changes in 1C:Enterprise mode

Be the first to know tips & tricks on business application development!

A confirmation e-mail has been sent to the e-mail address you provided .

Click the link in the e-mail to confirm and activate the subscription.