1Ci Support Help Center home page
Submit a request
Sign in
  1. 1Ci Support
  2. 1C:Enterprise Platform
  3. What’s New

Version 8.3.3

  • What’s New
    • Version 8.3.16
    • Version 8.3.15
    • Version 8.3.14
    • Version 8.3.13
    • Version 8.3.12
    • Version 8.3.11
    • Version 8.3.10
    • Version 8.3.9
    • Version 8.3.8
    • Version 8.3.7
See more
  • Version 8.3.3
    • New functionality and changes
    • New functionality and changes in 1C:Enterprise mode
    • Optimization
    • Changes that affect system behavior
    • Changes that require modification of configuration and administrative settings
    • Renamed objects
    • Mobile platform
    • Transition from the version 8.2 to the version 8.3.3
    • Transition from the previous version to version 8.3.3

Version 8.3.3

Version 8.3.3 includes known bug fixes and functionality modifications.


New functionality and changes

FunctionalityAfterBeforeResult 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 customizationExtended 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.
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

New functionality and changes in 1C:Enterprise mode

FunctionalityAfterBeforeResult of changes
Printing documents.Changed behavior of print status forms in managed applications in thin and thick clients:
  • In the Forms in tabs form opening mode, print status forms are opened in separate windows.
  • The form is opened in a modal window so that users cannot interact with the interface during printing.
  • The form cannot be closed by clicking the "X" button.

The form cannot be resized.

The print status form had different behavior.Improved usability of printing documents.
Linux. The Primary Selection clipboard is now supported (data is copied to this clipboard when a text fragment is selected, without the need to press any keys). Copying to the Primary Selection clipboard is supported for the following form elements:
  • Text box
  • Text document field
  • Formatted document field
  • Spreadsheet document field

Insertion from the Primary Selection clipboard (available by pressing the middle mouse button) is supported in text boxes.

This feature was not provided.Improved usability of client application for users with Linux experience.
Managed form. Functional options. If a text box is linked to an attribute of complex type where all types except one are disabled by access rights or functional options, when user attempts to select a value in the text box, the choice value form is opened.

This change is not implemented in 8.3.2 compatibility mode.

If a text box was linked to an attribute of complex type, when a user attempted to select a value in the text box, the type selection dialog box, was displayed even if the list of types contained a single value.

Users do not have to select from a single value in the type selection dialog box.

Automated testing. On closing an application, if the log of user actions is being recorded at the moment, a request for saving the log is sent.On closing the application, unsaved data from the log of user actions was lost.Reduced chance of losing unsaved data from the log of user actions when the application window that initiated recording to the log of user actions is closed.
Web client. During the startup of the web client, the check for a pop-up window blocker is only performed if the separate window interface is used and modal windows are enabled.  The check for a pop-up window blocker is performed after the user authentication.

The check for a pop-up window blocker was always performed during the web client startup.Users are not prompted to specify the pop-up blocker settings when it is not required.
Interface. On interface mode change, the user is prompted to restart the client application.Changing interface mode did not prompt to restart the client application.The procedure of changing the interface mode became more user-friendly: the system now informs the user what they have to do to have the changes take effect.
Standard functions. The following changes are implemented in the standard functions:
  • Event log:
    • The set of commands in the form command bar is changed, as well as the command presentations.
    • The procedures for enabling and disabling the filter are revised.
    • You can view log entry data by clicking the link in the corresponding log column.
    • You can filter records by date and time.
  • Find references to object:
    • You can search for references to a reference that is found (from the context menu).
  • Manage full-text search:
    • The form is revised.
    • Enabling or disabling full-text search is performed without opening additional forms.
  • Post documents:
    • The form is revised.
  • Active users:
    • You can open the event log filtered by user by clicking a hyperlink in the User column.
Standard function dialog boxes were less user-friendly.

Improved usability of standard functions.

Web client. The documentation includes recommendations for choosing a web browser for low-performance computers.The documentation did not include recommendations for choosing a web browser.Recommendations for choosing a web browser are available.
Web client. In Microsoft Internet Explorer web browser, notification windows do not fade out of view when they are closed automatically.In Microsoft Internet Explorer web browser, notification windows faded out of view when they were closed automatically.Improved performance of notification windows in Microsoft Internet Explorer web browser.

Table of contents

Optimization

FunctionalityAfterBeforeResult of changes
Operating with DBMS. Accumulation registers. Working with queries. Optimized performance of accumulation register virtual tables when obtaining totals with a filter that does not include all dimensions.Insufficient performance of accumulation register virtual tables when obtaining totals with a filter that did not include all dimensions.Performance of accumulation register virtual tables is increased.
Server cluster. Creation of new sessions is optimized.Creating of new sessions was performed inefficiently.Optimized performance when establishing connections to the 1C:Enterprise server in the following cases:
  • Simultaneous connections from a large number of client applications.
  • Connection of a new client application to a cluster that already runs a large number of sessions.
Information registers. Improved performance of independent, non-periodic information registers that have more than 1 dimension. This change is not implemented in 8.3.2 compatibility mode.Insufficient register performance.Increased speed of writing to a register, especially when a large number of users are working.
Applied objects. Optimized selections from catalogs and charts of characteristic types for certain scenarios. In certain scenarios performance of selections from catalogs and charts of characteristic types was inefficient.Increased performance of selections from catalogs and charts of characteristic types in certain scenarios.
Dynamic list.Improved dynamic list performance in client/server mode when a large number of users are working.In certain scenarios dynamic list performance was insufficient.Improved dynamic list performance in certain scenarios.
Server cluster. Optimized processing of session data for some scenarios.In some scenarios processing of session data was inefficient.

Improved performance and scalability of 1C:Enterprise servers.

Accumulation registers. Optimized execution of queries to turnovers registers with a large number of dimensions that include aggregates (for some scenarios). This change is not implemented in 8.3.2 compatibility mode.In some cases execution of queries to turnovers registers with a large number of dimensions that included aggregates was inefficient.You can use aggregate functions in more scenarios than before.
Operating with DBMS. In order to optimize some queries to IBM DB2 DMBS, the recommendation to run the db2set DB2_OVERRIDE_BPF=5000 command and then restart the DBMS is included into the documentation. Methods of detecting situations when the optimization is required are also described in the documentation.Some queries to IBM DB2 DBMS were performed inefficiently.Optimized performance during the execution of some types of IBM DB2 DBMS queries.
Information registers. For periodic information registers that are subordinate to recorders, the Active field is listed in the following indexes:
  • By period
  • By dimensions
  • By dimension

The Active field is the last one in these indexes. After changing the compatibility mode, full infobase restructuring must be performed for rebuilding indexes. This change is not implemented in 8.3.2 compatibility mode.

The Active field was not included in the list of indexes of periodic information registers subordinate to recorders.Improved performance when retrieving the first and the last slices.
Server cluster. 1C:Enterprise server is optimized to reduce memory usage and fragmentation.In some scenarios, 1C:Enterprise server used memory inefficiently. This led to memory fragmentation and increased memory consumption.Reduced memory consumption of 1C:Enterprise server, and lower memory fragmentation. This allows to reduce the number of planned 1C:Enterprise server restarts and improves the system stability.
Operating with DBMS.Indexes of attributes with additional ordering include deletion marks and all fields that are indexed with additional ordering. This data is added to the end of the index.Indexes of attributes with additional ordering did not include deletion marks and all fields that were indexed with additional ordering.

Improved performance of dynamic lists filtered by multiple attributes (including the deletion mark).

Managed form. Optimized performance of displaying managed forms after server calls (both explicit and implicit ones) that change the form appearance.Forms were not displayed fast enough when their appearance was changed from 1C:Enterprise script.Optimized performance of displaying forms, for example, when the displayed title of a form element is modified.
Common attributes / Data separation. Once the version 8.3.2 compatibility mode is disabled, optimization is performed on the structure that stores data on the table separators connected to objects included in the separator contents. When the version 8.3.2 compatibility mode is enabled, the reverse restructuring of the database tables is performed.The structure that stored separator data was not optimal.Improved performance due to the changes in the structure that stores separator data.
Server cluster. In server cluster, the algorithm for balancing the working process load is optimized. The following parameters are used in addition to parameters used in the previous versions to define the available server performance: size of CPU queue, current processor load, and number of CPU cores. Values used for defining the available server performance are recorded to the TXT property of the CLSTR event in the technological log. To obtain performance parameters, the user on whose behalf the 1C:Enterprise server is running must be included in the Performance Log Users group.In the server cluster, the algorithm for balancing the working process load took less number of parameters into account.Improved reactivity of the load balancing algorithm. The algorithm defines overloaded CPUs and stops sending new tasks to them.
Managed form. Optimized performance of opening managed forms with multiline text boxes that contain a large number of line breaks.Performance of opening forms with multiline text boxes containing a large number of line breaks was not high enough.Forms with multiline text boxes that contain a large number of line breaks are opened faster.

Table of contents

Changes that affect system behavior

FunctionalityAfterBeforeResult of changes
Software licensing. Licenses for basic configurations are available on Linux.Basic version licenses for Linux were unavailable.You can run basic 1C:Enterprise configuration versions on Linux.
Applied objects. Infobase object autonumbering logic is revised. The check for number or code uniqueness (including automatically generated codes and numbers) is always performed while the object is being written.

The message informing the user that a number or code is not unique now specifies the value of the non-unique number or code.

Numbers or codes that are no longer used are never re-assigned automatically, even when the desired prefix is not specified explicitly. In the event when the desired prefix is not specified explicitly, the platform forms a number or code as follows: it selects the greatest of the prefixes that match the specified pattern and then adds the next subsequent number (prefixes are compared according to their alphabetical order, for example, B is greater than A).

The uniqueness check was not performed for automatically generated numbers or codes while the object was being written.

The message informing the user that a number or code was not unique did not include the value of the non-unique number or code.

Numbers or codes that were no longer used might be re-assigned automatically in the event when the desired prefix was not specified explicitly–the platform might assign a code that was used before when its prefix matched the specified pattern and the prefix was not the greatest one among those matching the pattern (prefixes are compared according to their alphabetical order, for example, B is greater than A).

Increased stability and reliability of infobase object autonumbering. Messages informing the user that a number or code is not unique now contain more information. The autonumbering is more logical: numbers or codes are always issued in the ascending order.
Applied objects. If a text value presentation cannot be calculated during debugging, the string Error getting value presentation is returned as a text presentation.If a text value presentation could not be calculated, Designer might stop responding.Improved system stability during debugging.
Managed form. Visibility of the command for switching to the calculation register (in a recorder form) is set to True by default.

This change is not implemented in 8.3.2 compatibility mode.

Visibility of the command for switching to the calculation register (in a recorder form) was set to False by default.Default visibility of commands for switching to registers is the same for all registers.
Managed form. When attributes of Number type that have minimum or maximum values set are cleared interactively, the attribute values after clearing cannot exceed the specified limits. This change is not implemented in 8.3.2 compatibility mode.When attributes of Number type were cleared interactively, their minimum and maximum values were ignored.Users cannot enter data that does not meet the conditions specified by the developer.
Applied objects. When a spreadsheet document is saved to a .docx file, image border styles are preserved. This change is not implemented in 8.3.2 compatibility mode.When a spreadsheet document was saved to a .docx file, images always had borders.More accurate export of spreadsheet document styles to .docx format.
Applied objects. When a spreadsheet document is saved to a .docx file the following spreadsheet document print options are preserved:
  • paper size
  • page orientation
  • scale
  • pagination
  • margins
  • headers and footers
  • repeating rows
  • displaying headers and footers on the first page

This change is not implemented in 8.3.2 compatibility mode.

Print options were not preserved when a spreadsheet document was saved to a .docx file.Improved usability of spreadsheet documents saved in .docx format.
Data composition system. When a user field is added to data composition system settings and the source of available settings is not specified, the file name is generated using the language of the current script variant.

This change is not implemented in 8.2.16 compatibility mode.

When a user field was added to data composition system settings and the source of available settings was not specified, the file name was generated in English.The data composition system behavior is uniform with behavior of similar platform features.
Working with files. The look and behavior of the file selection dialog box (including the FileDialog object) in Windows Vista and later Windows versions complies with the standards of these operating systems. In Windows XP and earlier and in the web client the look of the dialog box is not changed.In Windows Vista and later, an outdated file selection dialog box was used.The look of the file selection dialog box corresponds to the operating system being used.
Working with files.If both Directory and FullFileName are specified for a FileDialog object, the dialog box is opened in the specified directory and with the specified file name.If both Directory and FullFileName were specified for a FileDialog object, the dialog box ignored the specified directory and used the directory that was obtained from the full file name.Improved usability of the file choice dialog.
Automated testing.Wildcard support implemented for the InputText() method of the TestedFormField object.The automated testing mechanism did not support wildcards in text input fields.Extended functionality of the automated testing system.
Dumping/loading configuration to files.When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName.

Configurations dumped using earlier platform versions cannot be loaded.

When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files.When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName.

Configurations dumped using earlier platform versions cannot be loaded.

When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files. When dumping a configuration to XML files, names of standard commands of managed forms follow this convention: Form.StandardCommand.CommandName.  Configurations dumped using earlier platform versions cannot be loaded.When dumping a configuration to XML files, names of standard commands followed this convention:  FormStdCommand.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files.When dumping a configuration to XML files, names of managed form commands follow this convention: Form.Command.FormCommandName. Configurations dumped earlier will not be loaded.When dumping a configuration to XML files, names of managed form commands followed this convention: FormCommand.FormCommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files.When dumping a configuration to XML files, names of standard commands of managed form elements follow this convention: Form.Item.ElementName.StandardCommand.StandardCommandName. Configurations dumped earlier will not be loaded.When dumping a configuration to XML files, the standard commands of managed form elements followed this convention: Form<ElementType>.ElementName.StandardCommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files.When a configuration is dumped to files:
  • References to missing configuration objects are dumped as text presentations of identifiers of missing configuration objects.
  • Properties of the ManagedForm element of a managed form that make sense only in 1C:Enterprise mode are not dumped.
  • For attributes and elements of managed forms, the internal identifiers required for saving their settings are dumped.

For elements of business process flowcharts, element identifiers are dumped.

When a configuration was dumped to files:

  • References to missing configuration objects were ignored.
  • Properties of the ManagedForm element of a managed form that made sense only in 1C:Enterprise mode were dumped.
  • For attributes and elements of managed forms, the internal identifiers required for saving their settings were not dumped.
  • For elements of business process flowcharts, element identifiers were not dumped.
In dumping/loading of configurations, the following improvements are implemented:
  • User settings are preserved when a configuration is dumped and then loaded.
  • The accuracy of configuration comparison (after a configuration is dumped and then loaded) is increased.
Managed forms.When Esc is pressed in a text box (except multiline text boxes), the following actions are performed:
  • If the initial text box content was modified in any way, the text box reverts to the initial content.
  • If the initial content was not modified, the text box does not process pressing the Esc key and passes the processing to the form.
Pressing Esc was always processed by the form. The text box did not perform any actions if Esc was pressed while the text was being edited.You can cancel editing a value in a text box.
Managed locks. The maximum number of managed locks is 100 000 (exceeding this limit locks the entire lock space).The maximum number of managed locks was 20 000 (exceeding this limit locked the entire lock space).Improved user experience when using transactions with a large number of locks (more than 20 000) in a single lock space.
Information registers. Data exchange. When a set of information register records is passed to the SelectChanges() method as a filter value, the system behavior depends on the compatibility mode:
  • In version 8.2.16 or earlier compatibility mode, the selection includes data that does not match the filter criteria defined by the record set;
  • In version 8.3.1 or later compatibility mode (or if the compatibility mode is not used), the selection only contains data that exactly matches the filter criteria.
When a set of information register records was passed to the SelectChanges() method as a filter value, the system behavior did not depend on the compatibility mode.
  • In version 8.2.16 or earlier, the selection included data that did not match the filter criteria defined by the record set
  • In version 8.3.1 or later, the selection only contained data that exactly matched the filter criteria.
Improved compatibility with previous platform versions.
Dynamic list. In the data composition system and query wizard, syntax units enclosed in braces {} do not lead to errors in dynamic lists.In the data composition system and query wizard, syntax units enclosed in braces led to errors in dynamic lists in some cases.Better stability of dynamic list.
Cryptography. The value of the CryptoModuleName parameter in the CryptoManager object wizard is case insensitive.The value of the CryptoModuleName parameter in the CryptoManager object wizard was case sensitive.The system behavior complies with common standards.
Managed form. Ordinary form. In managed and ordinary forms, if the second parameter (FormElement) of the ChooseFromMenu() method is a managed form table, a managed form, a table box, or an ordinary form, the menu that is opened using this method is displayed in the following location:
  • For a table box or a managed form table, the menu is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table if the current cell cannot be determined.
  • For a form, the menu is displayed in the upper left corner.

This change is not implemented in 8.3.2 compatibility mode.

If the second parameter (FormElement) of the ChooseFromMenu() method was a managed form table, a managed form, a table box, or an ordinary form, the menu was displayed in the following location:

  • For a table box or a managed form table, the menu was displayed in the lower left corner of the element passed as the parameter value.
  • For a form, the menu was displayed in the lower left corner of the current form element. If the current form element could not be determined, the menu was displayed in the lower left corner of the form. In the web client, the menu was displayed in the center of the screen.
Uniform behavior when the system opens similar menus (e.g. context menu in a managed form table) or the applied solution opens such menus (using the ChooseFromMenu() method).
Managed form. Ordinary form.In managed and ordinary forms, if the second parameter (FormElement) of the  ChooseFromList() method is a managed form table, a managed form, a table box, or an ordinary form, the list that is opened using this method is displayed in the following location:
  • For a table box or a managed form table, the list is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table, if the current cell cannot be determined.
  • For a form, the list is displayed in the upper left corner.

This change is not implemented in 8.3.2 compatibility mode.

If the second parameter (FormElement) of the ChooseFromList() method was a managed form table, a managed form, a table box, or an ordinary form, the list was opened in the following way:
  • For a table box or a managed form table, the list was displayed in the lower left corner of the element passed as the parameter value.
  • For a form, the list was displayed in the lower left corner of the current form element. If the current form element could not be determined, the list was displayed in the lower left corner of the form.
  • In the web client, the list was displayed according to form settings because a system form was used to display it.
Uniform behavior when executing similar actions (the ChooseFromMenu() and ChooseFromList() methods).
Developing tools. You can search and replace in the ChoiceParameters property of configuration objects. The search and replace algorithm is modified for the ChoiceList and ChoiceParameterLinks configuration objects. The search and replace are performed:
  • For the ChoiceParameters property: in the Name and the Value columns (including fixed array elements). The search is performed on values of String type.
  • For the ChoiceList property: in the Presentation column and in the Value column if the value has the String type.
  • For the ChoiceParameterLinks property: in the Name column.
  • Every time the search string is found, the search/replace procedure is paused and a message prompting to resume the procedure is displayed.

Search in the LinkByType property of configuration objects is no longer supported.

Search and replace in the ChoiceParameterLinks property of configuration objects was performed only in the Name column. Search and replace in the ChoiceList property of configuration objects was performed only in the Presentation column. Search and replace was not performed in the ChoiceParameters property of configuration objects. Search could be performed in the LinkByType property of configuration objects.The search and replace operations in configuration object properties are now uniform to similar operations in texts.
Developing tools. The presentation of the ChoiceParameters property of configuration objects in the object properties editing window is changed. If a value of any property element is a fixed array, presentations of array values are used. The presentation of the ChoiceList property of configuration objects in the object properties window is changed. A presentation now consists of both list item values and their presentations (if the presentations are specified).If an element of a ChoiceParameters property was a fixed array, its presentation was a FixedArray string. For the ChoiceList property of configuration objects, the presentation in the object properties window was generated from the list item values only.Improved usability of ChoiceParameters and ChoiceList properties in Designer.
Managed form. Improved look and behavior of drop-down lists in text box fields that can be edited and contain data of reference type, enumerations, or system enumerations:
  • If a field contains data of reference type or an enumeration, the field includes the choice button, and the characters typed in the field do not match any choice list values, the Click show all to select item message is displayed in the list.
  • If the drop-down list is displayed and a value is selected in it, pressing Tab, Shift+Tab, or Enter selects the current value from the list. Clicking another form element does not select the current value; the list is closed instead (same effect as pressing Esc). The selection is not moved to the form element that was clicked.
  • If the drop-down list is not displayed and the characters typed in the field uniquely identify a choice list value, pressing Tab, Shift+Tab, or Enter selects this value. Clicking another form element also selects this value.

If the drop-down list is not displayed and the characters typed in the field match multiple choice list values, pressing Tab, Shift+Tab, or Enter opens the drop-down list. Clicking another form element also opens the drop-down list.

The drop-down list had a different look and behavior. Improved usability of text box fields that contain data of reference type, enumerations, or system enumerations.
Accumulation registers. You can enable the aggregates mode for any turnovers accumulation register, regardless of the actual presence of aggregates in metadata. In the client/server mode you can create new optimal aggregates (and remove outdated ones) when aggregates are being rebuilt in 1C:Enterprise mode. This change is not implemented in 8.3.2 compatibility mode.Developers had to add aggregates in Designer to keep the list of optimal aggregates up to date.Simplified support of optimal aggregate list: you only have to rebuild aggregates on regular basis.
Managed form. In text boxes containing data of reference type, only the color of the text presentation of the value is changed on element activation.In text boxes containing data of reference type, the color of the entire field changed on element activation.Better text box usability. A tooltip can be displayed in a text box linked to data of reference type if the text box is first in the tab order of the form.
Developing tools. Configuration repository. You can perform quick comparison of selected configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. Selective comparison is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, exchange plan content objects, styles, desktop workspaces, maps, forms, online help pages, predefined items, command interface fragments, and role rights. To run the selective comparison command, right-click anywhere in any of the repository dialog boxes or in the compare configurations window, and then click Perform selective comparison with the configuration object. Selective comparison of configuration objects is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.This feature was not provided. When comparison was initiated for a specific object, full comparison of two configurations was performed. The focus in the comparison window was set to that object.Improved usability of configuration repository. Optimized comparison procedure when it is performed for a single configuration object.
Operating with DBMS. Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later is now available.

All of the required settings are specified automatically by the installation program of the patched PostgreSQL version unless a cluster created by the standard PostgreSQL version is found on the computer.

Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later was not available.1C:Enterprise supports clusters created by the following versions of PostgreSQL DBMS:
  • PostgreSQL 8.1.5-X.1C - 9.1.2-1.1C
  • PostgreSQL 9.2.1-2.1C
  • Standard version of PostgreSQL provided that the cluster locale is identical to the infobase locale.

You can upgrade or downgrade 1C:Enteprise without upgrading or downgrading the associated PostgreSQL instance; this does not require any manual configuration.

Note that once you migrate to a new PostgreSQL version, you cannot use 1C:Enterprise version 8.3.2 or earlier. This only applies to new infobases that were created using PostgreSQL 9.2.1-2.1C. Do not create infobases using PostgreSQL 9.2.1-2.1C if you are planning to access them from earlier platform versions.

Managed form.If the ChoiceDataGetProcessing event handler of the enumeration manager returns an empty list and the formal parameter StandardProcessing returned by this handler is set to False, the returned list is used for filling the choice list. This change is not implemented in 8.3.2 compatibility mode.If the ChoiceDataGetProcessing event handler of the enumeration manager returned an empty list and the formal parameter StandardProcessing returned by this handler was set to False, the client application filled the choice list by all enumeration values.The system behaves as expected when a developer decides to disable selection of enumeration values.
Standard functions. In the default event log form, filter presentation is localized.In the default event log form, filter presentation was always displayed with Russian names of event log columns.The filter presentation is uniform with other platform features.
Configuration repository. Optimized the reference integrity check algorithm for configuration repository operations (storing and retrieving) on objects that are deleted from the repository and objects that reference to deleted ones. In some cases, it is not necessary to lock objects that contain references to objects being deleted during the deletion. The reference integrity check algorithm used when deleting objects from the repository is uniform with the reference integrity check algorithm used when deleting objects from a configuration that is not bound to a repository. This change is not implemented in 8.3.2 compatibility mode.The reference integrity check algorithm for configuration repository operations was not optimized. The reference integrity check algorithm used when deleting objects from a repository was different from the reference integrity check algorithm used when deleting objects from a configuration that was not bound to a repository.Eliminated problems that occurred when deleting objects from configurations because of the reference integrity check differences. Storing deleted objects to the configuration repository is optimized.
Managed form. In the managed mode of the thick client, if the In list editing mode is selected for a configuration object, calling the OpenValue() method or clicking the Open button in the text input area opens the regular list form, provided that the following conditions are met:
  • The In list editing mode is selected.
  • A regular list form exists and it is selected as a default or additional one.
  • Using regular forms in the managed application is allowed in this applied solution.
  • The list or object managed form that is used as a default or additional one is missing.

In all other cases, this opens the object form.

This change is not implemented in 8.2.16 compatibility mode.

In the managed mode of the thick client, if the In list editing mode was selected, calling the OpenValue() method or clicking the Open button in the text input area opened the managed list form.To display configuration objects that have the In list editing mode set, or for editing their elements, the system opens the regular list form. This behavior is more consistent than before.
Development tools. The following changes are implemented in the configuration comparison feature:
  • The parent node of predefined data elements is excluded from the comparison.
  • Missing help data is considered identical to empty help data.
  • Additional properties of the ManagedForm managed form element that make sense only in 1C:Enterprise mode are excluded from the comparison.
When configurations were compared:
  • The node to which predefined data items were subordinate was included into the comparison.
  • Missing help data was considered different from empty help data.
  • Additional properties of the ManagedForm managed form element that make sense only in 1C:Enterprise mode were included into the comparison.
The configuration comparison is perfomed as expected.
Managed form. When a choice list is generated for form fields linked to data of EnumRef type, it is based on the choice parameters and choice parameter links of the form element.

This change is not implemented in 8.3.2 compatibility mode.

When a choice list was generated for form fields linked to data of EnumRef type, the choice parameters and choice parameter links were not taken into account.The choice list generation for enumerations is uniform with other similar system features.
Internet-enabled functionality. For the InternetMailProfile object, the SMTPAuthentication property (which is obsolete) is set to SMTPAuthenticationMode.Default.

This change is not implemented in version 8.2.16 compatibility mode. 

For the InternetMailProfile object, the obsolete property SMTPAuthentication was set to SMTPAuthenticationMode.None.The default settings of the authentication method is the safest among those supported by the mail server.
Internet-enabled functionality. If the SMTPSecureAuthenticationOnly property of the InternetMailProfile object is set to TRUE, authentication attempts are performed independently of other settings.

User authentication on the SMTP server is not performed in the following scenarios:

  • The SMTPUser property of the InternetMailProfile object is an empty string.
  • The SMTPAuthentication property of the InternetMailProfile object is set to SMTPAuthenticationMode.None.
  • The POP3BeforeSMTP property of the InternetMailProfile object is set to TRUE.

User authentication on the SMTP server was not performed if the name of the SMTP server user was not specified (the SMTPUser property of the InternetMailProfile object).User authentication on the SMTP server can be performed using a POP3 server if the SMTPSecureAuthenticationOnly property is not set. The value of the SMTPUser property of InternetMailProfile object does not affect this behavior. At the same time, the authentication is not performed if the mail server does not support the secure authentication methods.

When connecting to a mail server, you can exclude insecure authentication methods from the list of available ones.

Software licensing. If a license acquisition dialog box appears at the start of the client application, the first page of the dialog box specifies which kind of license (server or client) the application requires. A hyperlink to 1C:Licensing center contact information is displayed on the license registration pages and on the page that appears when license activation is not successful. A dialog box that displays 1C:Licensing center contact information is added. When a user types a PIN code or a response from a licensing center operator in the license aсquisition dialog box, once they have completed a text field, the cursor moves to the next field automatically. 

 

If a license acquisition dialog box appeared at the start of the client application, the first page of the dialog box did not specify which kind of license (server or client) was not found. The license registration pages and the page that appeared when license activation was not successful only contained information how to find 1C:Licensing center contacts in the printed documentation. When a user typed a PIN code or a response from a licensing center operator in the license aсquisition dialog box, the cursor did not move to the next field automatically.Improved usability of license acquisition dialog box.
Spreadsheet document. Web client. The web client now supports text orientation in spreadsheet document cells.The web client did not support text orientation in spreadsheet document cells.Extended formatting capabilities for spreadsheet documents in the web client.
Server cluster. When a cluster service is reassigned from one cluster manager to another, the service status is replicated to the new cluster manager and the service is shut down on the former cluster manager, which releases the resources used by the service. The status is replicated for the following services: object locks, numbering, and background restructuring. In the technological log, the <SRVC> event is implemented. It describes the following operations with cluster services: starting, stopping, and various alerts. Descriptions of operations being executed are generated in the Descr property. Each cluster manager stores its session data in a dedicated directory. You can choose how a working process is selected when a new connection is created: by available performance or by available memory. If the selection is performed by available memory, either the working process that currently maintains connections to the infobase is used, or the working process that is running on the server and has the maximum amount of available memory. In the cluster properties, the Load balancing mode property is implemented. For the IClusterInfo object, the LoadBalancingMode property is implemented. For starting a background job, the working process that maintains the session that initiated the background job is selected with the highest priority (this rule is ignored if the selection is performed by available memory). You can specify a priority for each assignment rule. If several identical assignment rules are found during assignment rule selection and all other conditions are equal, the rule with the highest priority is used. Assignment rules now have the Priority property. For the IAssignmentRule object, the Priority property is implemented. In the cluster mode of the server cluster administration utility (rac), the load-balancing-mode parameter is implemented for the create and update commands. Similar changes are implemented in the Java server administration API. When determining available working process performance, the CPU load of the working server and the number of threads in the execution queue are taken into account, in addition to other factors.In some cases, used resources were not released after the reassignment of services. The status was not replicated for the following services: object locks, numbering, and background restructuring. In the technological log, there were no events that described operations with cluster services. Data belonging to all sessions was stored in a single directory, which could lead to access collisions. When a background job was created, the working process for handling the job was always selected by available performance. If several identical assignment rules were found during assignment rule selection, the rule that was applied could not always be determined unambiguously. When available working process performance was determined, the CPU load and the number of threads in the execution queue were not taken into account.Increased fault tolerance of clusters. Improved quality and manageability of load balancing between cluster servers. A new setting ensures  efficient memory usage when a cluster maintains a large number of infobases with a small number of sessions from each infobase. 
Managed form. For unavailable groups, colors of the title and border (line) are changed.For unavailable groups, the title and border (line) had different colors.The look of unavailable groups is uniform with the look of other unavailable elements.
Applied objects. Common attributes / Data separation. Access rights. Data exchange. Mobile application. Predefined data is available for configuration objects included in separator contents in the Independent and Shared mode. Predefined items can be linked to any data elements of matching type. The linking is optional. If data elements are not linked, the predefined data is considered empty. For configuration objects that can contain predefined data, the PredefinedDataName property is implemented. Support of predefined data items that refer to deleted predefined items is implemented. Identical references to predefined items are never generated, even for objects included in separator contents in the Independent mode, and even for items that belong to different areas. The GetPredefinedItemName() method is declared deprecated is only supported for compatibility purposes. Predefined data is registered in exchange plans like any other data. You can manage creation and update of predefined data in the infobase using the new configuration object property PredefinedDataUpdate and the new methods GetUpdatingPredefinedData() and SetPredefinedDataUpdate(). The global context method InitializePredefinedData() is implemented. Using this method, you can create data objects for predefined items that are not linked to any data (in the current data area). Access rights and restrictions are specified simultaneously for the Predefined and PredefinedDataName fields. These features are also implemented for the mobile platform. The new access rights InteractiveDeletePredefinedData, InteractiveSetDeletionMarkPredefinedData, InteractiveClearDeletionMarkPredefinedData, and InteractiveDeleteMarkedPredefinedData are implemented. They specify whether editing of predefined data is allowed.

Restrictions for editing predefined data in charts of accounts and charts of calculation types are eliminated. Predefined data can be marked for deletion, and it can be completely deleted. A chart of accounts must be included into the contents of all separators that contain all extra dimensions used in the chart. The infobase restructuring process is modified. This change is not implemented in 8.3.2 compatibility mode.

Predefined data was not available for configuration objects included in separator contents in the Independent and Shared mode. Predefined data could not be linked to any existing data object. Each predefined item had identical references in all data areas. During data exchange in a distributed infobase, predefined data was replicated only together with applied solution configuration changes. Creation and update of predefined data were not available.You can use predefined data in all separation modes. Predefined data management is more flexible than before.
Interface. In the help topics, links to external resources are opened in the default web browser of the operating system.In the help topics, links to external resources were opened in the built-in web browser of 1C:Enterprise.Improved usability of viewing the resources that are opened by clicking links in the help topics.
Interface. For new users, the interface mode is set to Forms in tabs, provided that the platform version compatibility mode is not used and the interface compatibility mode is set to Version82 or Version82TaxiAllowed.For new users, the interface mode was set to Forms in separate windows.The Forms in tabs interface is the default option for new users. This interface mode provides better usability.
Interface. For a text box in a managed form table, the drop-down list is always opened at the start of editing.For a text box in a managed form table, the drop-down list was opened at the start of editing only if the editing was started using the mouse.Quick access to the drop-down list is implemented for text boxes located in managed form tables.
Common attributes / Data separation. 1C:Enteprise script. After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state matches the state that the data area had when it was accessed for the first time. In particular:
  • Tables of enumerations are not modified.
  • If the version 8.3.2 or later compatibility mode is set, predefined data values revert to the values specified in Designer or to the default values. If the compatibility mode is disabled, predefined data items will be created on the first attempt to access them.
  • In the exchange plans, the values of ThisNode element attributes revert to the default values.
  • Values of nonseparated constants revert to the default values, while values of separated constants are deleted.
After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state did not match the state that the data area had when it was first accessed:
  • Tables of enumerations were removed.
  • For nonseparated objects, the predefined data values were saved.
  • In the exchange plans, the values of ThisNode element attributes were saved.
  • Constant values were preserved.
After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the state of the data area now reflects its initial state much better than it did in the previous platform versions.
Application appearance.New splash screens are implemented for Designer, client application, Autorun program, and the installation program. The splash screen size (and the size of the applied solution splash screen template) is 600 x 255 pixels.Splash screens that were used for various parts of the system had different looks. The size of the applied solution splash screen template was 305 x 110 pixels.The new splash screens better fit the new user unterface.
Managed form. When a value is entered or selected in a text box, it is converted to the text box value type, and then the value presentation is displayed in the text box. This change is not implemented in 8.3.2 compatibility mode.When a value was entered or selected in a text box, the resulting text displayed in the box might not match the entered or selected value.The system behaves as expected. Eliminated incorrect system behavior.
Client application. The message that is displayed before updating a client application using an insecure connection is clarified. The message was not clear enough.The message describes the situation more clearly.

Table of contents

Changes that require modification of configuration and administrative settings

FunctionalityAfterBeforeResult of changes
Dumping/loading configuration to files.Only access rights that have nondefault values are included in dump files. The default values are defined by the Set rights for new objects and Set rights for attributes and tabular sections by default properties. Values of these properties are default values for access rights to metadata objects and access rights to attributes and tabular sections respectively.All access rights were included in dump files, including those having default values.Improved performance of dumping configurations to files. Reduced size of dump files.
Dumping/loading configuration to files.Applied objects. When dumping a configuration to XML files, English descriptions of document journal selection types follow this convention: DocumentJournalSelection.DocumentJournalName.When dumping a configuration to XML files, English descriptions of document journal selection types followed this convention: DocumentJournalsManager.DocumentJournalName.Type names are uniform.
Working with files. When one or multiple files are obtained from the infobase using the GetFile() or GetFiles() method, the View right is checked for the attributes that store the file data. If the GetFiles() method is used and access to at least one the requested files is denied, the entire operation is canceled. This change is not implemented in 8.3.2 compatibility mode.

When one or multiple files are obtained from the infobase using the GetFile() or GetFiles() method, the View right was not checked for the attributes that stored the file data.

The behavior of the GetFile() and GetFiles() methods is uniform with other system features.
Developing tools. Before database configuration update, the check whether the Ref attribute is present is performed for tabular sections of catalogs, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks. If this attribute exists, restructuring cannot be performed. This change is not implemented in 8.3.2 compatibility mode.Before database configuration update, the check whether the Ref attribute is present was not performed for tabular sections of catalogs, charts of characteristic types, charts of accounts, charts of calculation types, exchange plans, business processes, and tasks.Eliminated this type of errors in applied solutions.
Server cluster. In the server cluster administration utility (rac), the name and cluster-port options of the server update command are removed. In the Java-based administration server interface, the setName() and setClusterMainPort() methods are removed from the IWorkingServerInfo interface. In the server cluster administration utility (rac), the security-level option of the infobase update command is removed. In the Java-based administration server interface, the setSecurityLevel() method is removed from the IInfoBaseInfo interface.In the server cluster administration utility (rac), the name and cluster-port options were available for the server update command. The values specified in these options were never used and no error messages were displayed when the command was run with these options. 

In the Java-based administration server interface, the IWorkingServerInfo interface included the setName() and setClusterMainPort() methods. These methods did not perform any actions and there were no error messages when these methods were called.

In the server cluster administration utility (rac), the security-level option was available for the infobase update command. The value specified in this option was never used and no error messages were displayed when the command was run with this option.

In the Java-based administration server interface, the IInfoBaseInfo interface included the setSecurityLevel() method. This method did not perform any actions and there were no error messages when this method was called.

 

Options of the administration utility (rac) and the set of Java-based administration server interface methods match the set of actions that the system can actually perform. Working server parameters can be specified during the registration of the working server in the cluster. The infobase security level can be specified while adding the infobase to the cluster.
Administration tools. Server cluster. The server cluster administration utility (rac) from the previous platform versions (8.3.1 and 8.3.2) cannot be connected to the administration server (ras) of the current platform version. The server cluster administration utility (rac) from the current platform version cannot be connected to the administration server (ras) of the previous platform versions (8.3.1 and 8.3.2).The server cluster administration utility (rac) could be connected to the administration server (ras) of any platform version.The server cluster administration utility (rac) and the administration server (ras) that have incompatible versions cannot interact with each other.
Working with files.

Linux.

You can get a file mask that describes all files for the operating system where 1C:Enterprise runs. The following methods are implemented: GetAllFilesMask(), GetClientAllFilesMask(), and GetServerAllFilesMask().This feature was not provided.You can write a source code that processes files and does not depend on the operating system where 1C:Enterprise runs.
Working with files.

Linux.

You can get a file path separator for the operating system where 1C:Enterprise runs. The following methods are implemented: GetPathSeparator(), GetClientPathSeparator(), and GetServerPathSeparator().This feature was not provided.You can write a source code that processes files and does not depend on the operating system where 1C:Enterprise runs.
Working with ZIP-archives.The behavior of the ZipFileWriter object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in a source directory:
  • If a file name does not contain wildcard characters (? or *), the file is added to the archive.
  • If a file name contains the wildcard characters (? or *), an exception is generated.

The behavior of the ZipFileReader object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in the directory containing the archive file, the archive is opened in the read-only mode. This change is not implemented in 8.3.2 compatibility mode.

During the creation of an archive using the ZipFileWriter object, if the user under whose account the system was running did not have rights for viewing the list of files in the source directory, the files were not added to the archive and the resulting archive did not contain expected data. The archive could not be opened using the ZipFileReader object if the user under whose account the system was running did not have rights for viewing the contents of the directory containing the archive file.The behavior of ZipFileWriter and ZipFileReader objects became more logical. Decreased chance of creating archive files with incorrect data.
Configuration repository. The compatibility mode with 1C:Enterprise versions 8.3.2 and earlier is implemented for the configuration repository. If the compatibility mode is disabled:
  • New configuration repository database structure is used.
  • The optimized method for interaction with configuration repository server is used.

If the compatibility mode is disabled, only 1C:Enterprise version 8.3.3 or later can be used to access the repository. The command line option ConfigurationRepositoryClearCache is implemented in Designer. It is intended for clearing the local configuration cache. The option to stop the execution of repository operations by pressing Ctrl+Break is implemented (this does not depend on repository compatibility mode).

A different configuration repository database structure was used. Some repository operations were performed inefficiently. The Designer mode command line option ConfigurationRepositoryClearCache was not available. Pressing Ctrl+Break did not stop the execution of repository operations.Improved performance when accessing a configuration repository server.
Applied objects. The Filter property of the parameter structure that is passed to the formal parameter of the GetChoiceData() method or the ChoiceDataGetProcessing handler can contain elements with values of ValueList and Array types. The system applies the In list comparison type to such values (it is the same comparison type that is used with FixedArray values).The Filter property of the parameter structure that is passed to the formal parameter of the GetChoiceData() method or the ChoiceDataGetProcessing handler could not contain elements with values of ValueList and Array types.Extended filtering options when retrieving selection data. Removed unnecessary data conversions.
Background and scheduled jobs.Background and scheduled jobs can now run in the file mode without using the ProcessJobs() global context method. The ProcessJobs() method does not perform any actions. Background and scheduled jobs are executed in one of the client applications connected to the infobase. The behavior of background and scheduled jobs has some specifics (see the full list in the documentation):
  • All scheduled jobs are executed in a dedicated client application (by default, it is the first session started).
  • A background job started by a session is executed by the client application that started it.
  • Within a client application, a single background job is performed at a time (this includes scheduled jobs).

For specifying the client application that will execute scheduled jobs, the AllowExecuteScheduledJobs command-line option is implemented for the client application. The Background jobs check box, which is located in the Autoattach dialog box in Designer, affects the attachment to background jobs both at server and at client.

This change is not implemented in 8.3.2 compatibility mode.

The only way to run background and scheduled jobs in the file mode involved using the ProcessJobs() global context method.

The Background jobs check box, which is located in the Autoattach dialog box in Designer, only affected attachment to background jobs at server.

Reduced developer efforts during implementation of background and scheduled job execution in the file mode.
Applied objects. Common attributes / Data separation. In order to successfully read or write separated constants using the Constants method of the global context, values of all shared separators that split the constant must be specified. Otherwise an exception is generated. This change is not implemented in 8.3.2 compatibility mode.Reading or writing separated constants using the Constants method of the global context was performed successfully even when values of all combined separators that split the constant were not specified.The feature is uniform with other similar platform features.
Linux. The config_system configuration utility for Linux is removed from the distribution kit. The search for MS Core Fonts required by the platform is performed automatically in the following directories:
  • /usr/share/fonts/truetype/msttfcorefonts
  • /usr/share/fonts/msttfcorefonts
  • $HOME/.fonts

The system automatically searches for required dynamic libraries when functions from these libraries are used. If the required font or dynamic library is not found, an error message is displayed. The operating system setup instructions for Linux are provided in the documentation.

The config_system configuration utility for Linux was included in the distribution kit. If required fonts or dynamic libraries were missing, this was not detected directly and could lead to various errors or unexpected behavior. The operating system setup instructions for running 1C:Enterprise on Linux were not provided in the documentation.Simplified operating system for running 1C:Enterprise on Linux. Improved issue diagnostics.
Access rights. Working with queries. Accumulation registers. Accounting registers. Access rights for autogenerated period fields (YearPeriod, HalfYearPeriod, QuarterPeriod, MonthPeriod,  TenDaysPeriod, DayPeriod, HourPeriod, and SecondPeriod) in virtual tables of accumulation and accounting registers are obtained from the corresponding access rights of the standard Period attribute.

This change is not implemented in 8.3.2 compatibility mode.

Access rights for autogenerated period fields in virtual tables of accumulation and accounting registers depended on the state of the Set rights for attributes and tabular sections by default check box. If the property was set to True, the user was granted the right.Access right management is more consistent.
Developing methods.The documentation includes a section with recommendations for developing cross-platform applied solutions.The documentation did not include recommendations for developing cross-platform applied solutions.Recommendations for creating the cross-platform applied solutions at minimal costs are available.
Managed locks. Managed transaction locks can be set by object attributes. For specifying attributes whose values are taken into account when setting transaction locks, the DataLockFields property is implemented for the following configuration objects:
  • Catalogs
  • Documents
  • Charts of characteristic types
  • Charts of calculation types
  • Business processes
  • Tasks
  • Charts of accounts
  • Exchange plans

While objects are being written or deleted, they will be temporarily locked by all attributes specified in the DataLockFields property and the Ref field. For objects being written, attribute values available at the beginning of the writing process are used. For objects being deleted, current attribute values are used.

This change is not implemented in 8.3.2 compatibility mode.

Managed locks for the following objects could be set only by the standard attribute Ref: catalog, document, chart of characteristic types, charts of calculation types, business process, task, chart of accounts, and exchange plan.Extended managed lock functionality. When you need to perform a coordinated action on a set of objects filtered by a specific attribute and at the same time prohibit the creation of new objects that match the filter, you have the option to set a lock by the attribute, rather than lock the entire set of objects of the given type.
Managed locks. Using the DataLock object outside of a transaction or in the automatic data lock control mode raises an exception.

This change is not implemented in 8.3.2 compatibility mode.

Using the DataLock object outside of a transaction or in the automatic data lock control mode did not raise an exception and did not lead to any locks.Situations when the system seemed to work properly but actually did not perform any actions are eliminated.
Client application installation. Administration tools. You can specify whether the latest 1C:Enterprise updates are installed automatically. This is configured using the following new parameters:
  • The AppAutoInstallLastVersion command-line option of the non-interactive startup utility.
  • The AppAutoInstallLastVersion parameter in the 1CEStart.cfg and 1CESCmng.cfg configuration files.

When the client application version does not match the 1C:Enterprise server version, or when a specific 1C:Enterprise version is required to access an infobase, the new version is always installed unless the required version is already present at the client computer. The Install new application versions automatically check box is added to the infobase startup settings dialog box.

The non-interactive startup utility installed the latest 1C:Enterprise version, except the following scenarios:
  • In the startup utility configuration dialog box, a specific 1C:Enterprise version is selected for all infobases.
  • A specific version of the client application or interactive startup utility is started.
In the non-interactive startup utility, you have the option to disable the search and installation of the latest 1C:Enterprise version in the event when the required version is already installed at the client computer, but later versions are available and not yet installed. You still have the option to install any 1C:Enterprise version that you need.
Developing tools. During the database configuration update, the check for matches between the names of common pictures and the names of pictures from the picture library is performed. If matches are found, the message informing that the names are not unique is displayed and the database configuration is not updated. This change is not implemented in 8.3.2 compatibility mode.During the configuration update, the check for matches between the names of common pictures and the names of pictures from the picture library was not performed.The following scenario is no longer possible: when a common picture name matches a picture name from the picture library, in 1C:Enterprise mode the picture from the library is displayed instead of the common picture.
Managed form. The Close() method called on an additional form closes this form. If this form is active, the default form is made active, otherwise no additional actions are performed. The IsOpen() method called on an additional form that is open returns True. If the user switched to another additional or default form after opening the additional form, the IsOpen() method still returns True.If the Close() method was called on an additional form, an error was generated and the form was not closed. The IsOpen() method called on an additional form that was open returned False.The system behaves as expected.
Working with XML, XDTO. During the generation of the configuration data model, for all properties of the configuration data model that have more than one type in their type descriptions, the Can be empty property (the nillable attribute of the XSD schema) is set to True, otherwise the property value is not set.

If you specify the Any ref type for an attribute (such as a resource or dimension) in Designer, the type is converted into one of the following in the configuration data model:

  • The {http://v8.1c.ru/8.1/data/enterprise}AnyRef type if the configuration includes multiple metadata objects that form the Any ref type.
  • The type that corresponds to reference data type if the configuration includes a single metadata object that forms the Any ref type.

This change is not implemented in 8.3.2 compatibility mode.

During the generation of the configuration data model, for all properties of the configuration data model that have more than one type in their type descriptions, the value of the Can be empty property (the nillable attribute of the XSD schema) was never set.

If you specified the Any ref type for an attribute (such as a resource or dimension) in Designer, it was always converted to the {http://v8.1c.ru/8.1/data/enterprise}AnyRef type in the configuration data model.

The XML data model generation for the Any ref type is uniform with other types.
Full-text search.Full-text search indexes include the number of 1C:Enterprise version that was used to create them. If the full-text search index is created in version 8.3.3 or later while the compatibility mode is disabled, and then the infobase is accessed using version 8.3.2 or earlier, the search by presentations of configuration objects is not performed.Full-text search indexes did not include the number of 1C:Enterprise version that was used to create them.Reverse compatibility of full-text search indexes is implemented. The full-text search indexes are now compatible with earlier 1C:Enterprise versions that have different index format.
Web services. Web links. You can specify proxy server parameters in constructors of the WSProxy and WSDefinitions objects and in the CreateWSProxy() method.

The former constructor and method syntax is supported for compatibility purposes.

Proxy server parameters could not be specified when WSProxy or WSDefinitions objects were created or when the CreateWSProxy() method was called. The proxy server settings could be specified only by editing the inetcfg.xml configuration file.Extended web service support functionality: the proxy server settings can be specified in the configuration settings rather than by editing the configuration file.
Functional options. If the privileged get mode is set for a functional option, getting the functional option value in the safe mode does not require checking the access rights. This change is not implemented in 8.3.2 compatibility mode.If the privileged get mode was set for a functional option, getting the functional option value in the safe mode included checking the access rights. Eliminated the issues related to accessing functional options in the safe mode. The data provided by a functional option that has privileged get mode set is considered safe enough and can be retrieved in the safe mode.
Automated testing. If an object being tested cannot perform the required action, an exception is raised (except methods that search for objects, which never raise this kind of exception).It was impossible to detect situations when objects being tested could not perform the required actions. Better error detection during automated testing.
Automated testing. Methods that perform actions on objects being tested do not wait for action completion. Methods that previously returned the execution results now raise exceptions when the actions cannot be performed.Methods that performed actions on objects being tested waited for action completion. In some cases such methods returned result codes.Better error detection during automated testing.
Managed form. For managed form fields, the DropListButton property is implemented. It describes whether the button that opens the drop-down list is present. Depending on the type of the attribute linked to the text box, the list can contain the following data:
  • Choice list - from the choice list property of the text box.
  • Quick choice list - for the quick choice property of the configuration object.
  • Choice values – values matching the text entered by the user.
  • Choice history - for reference fields and enumeration fields. Note that the history is not available for fields that contain configuration objects with the quick choice option enabled.

During the text input in a text box, the platform displays unique items from all these lists (if they are available for the text box). For managed form fields, the ChoiceButtonRepresentation property is implemented. It describes whether the button that opens the choice form is present in the field. The DropListButton property of managed form fields is no longer available; it is left for compatibility purposes. The StartListChoice event of text box objects is never called. This change is not implemented in 8.3.2 compatibility mode.

The DropListButton property was available for managed form fields. When a user started selecting an item from the list, the the StartListChoice event was generated. Developers could not control whether the choice form could be opened from the choice list.The choice list is designed to allow users to select values quickly, without opening the choice form, whenever possible. For that, the choice list contains data that helps users to select a value for a text box:
  • History of choices in the fields of the given type (with the given parameters)
  • Choice values
  • Quick choice list, and so on
Web client. In the web client for iPad, only the Forms in tabs mode without modal windows and the Taxi interface are supported. The webclientmode command-line parameter is no longer supported. Standard gestures for zooming in and out are now supported. Form items with content that can be scrolled have scroll bars.In the web client for iPad, modal windows were supported with some limitations, and the Forms in tabs mode was not supported. The webclientmode command-line parameter was supported. Standard gestures for zooming in and out were not supported. Form items never had scroll bars.Configuration tuning is no longer required to run applications on iPad (provided that you switch to the mode that does not use modal windows). In earlier versions of the platform, the developer had to remove a part of functionality to make an application compatible with iPad because modal calls were supported with limitations.
Managed form. Command interface. Enhanced window blocking technology introduces innovative approach to window modality. Blocking windows are used instead of modal windows, while modal windows are supported for compatibility purposes. It is recommended that you replace all modal windows with blocking windows in your applied solutions, and use new platform methods that do not create modal windows. A call of a modal form is broken down into one or more separate calls: the first call opens a blocking form instead of a modal one and the the other one contains a callback procedure that is called by the platform when a form operation is complete (it includes getting the return value). Applied solutions designed for iPad must support the blocking windows technology. The ModalityUseMode configuration property is implemented, it defines the modal window usage mode. In the extended configuration check, the search for methods related to modal windows is implemented. You can also perform this check from the command line by using the CheckUseModality option of the ExtendedModulesCheck command-line parameter. The NotifyDescription object is implemented, it passes the callback procedure description to platform methods that open blocking windows. The global context method ExecuteNotifyProcessing() is implemented. For the FormWindowOpeningMode system enumeration, the LockWholeInterface value is implemented. For managed forms, command interface commands, and common modules, the ThisObject property is implemented. This property is not supported in version 8.3.2 compatibility mode. The global context method OpenForm() is modified. The following global context methods are implemented: ShowQueryBox(), ShowValue(), ShowMessageBox(), ShowInputDate(), ShowInputValue(), ShowInputString(), ShowInputNumber(), BeginInstallAddIn(), BeginInstallFileSystemExtension(), BeginInstallCryptoExtension(), and BeginPutFile(). For objects StandardPeriodEditDialog, FormatStringWizard, FontChooseDialog, ColorChooseDialog, and ScheduledJobDialog the Show() method is implemented. For the DataCompositionDetailsProcess object, the ShowChooseAction() method is implemented. For the ValueList object, the methods ShowCheckItems() and ShowChooseItem() are implemented. For the ManagedForm object, the Open() method is modified, and the methods ShowChooseFromMenu() and ShowChooseFromList() are implemented. For the ManagedForm object,  the OnCloseNotifyDescription property is implemented. The ThisForm property of the ManagedForm object is removed but supported for compatibility purposes. The system enumeration value PostingModeUse.Ask is supported for managed forms only in version 8.3.2 compatibility mode.In the web client on iPad, the modal window support was limited, while modal windows were widely used in applied solutions and in the system part of the interfaces.The web client meets the modern web technology standards. Removed limitations on modal window usage in the web client on iPad. Configuration modification is required for applied solutions intended to run in the web client on iPad.
Technological log. The resolution of the event time output to the technological log is increased to 1 microsecond. The count of microseconds in technological log event time has six digits. The DurationUs property is implemented. It contains the event duration measured in microseconds. For compatibility purposes, filtering by Duration properties is supported.The resolution of the event time output to the technological log was equal to 100 microseconds. The count of microseconds in the technological log had four digits. Only the Duration property was available in the technological log. It contained the event duration measured in hundreds of microseconds.Decreased chance of the time counter overflow that occurred when the count of technological log events exceeded 10 000 events per second. One second can now contain up to 1 000 000 events of the technological log. It is recommended that you use the DurationUs property instead of the Duration property.
Web client. System requirements. The following browsers are no longer supported:
  • Microsoft Internet Explorer version 7.0;
  • Safari for Windows;
  • Mozilla Firefox version 16 and earlier for Windows and Linux.
The following browsers were supported:
  • Microsoft Internet Explorer version 7.0;
  • Safari for Windows;
  • Mozilla Firefox version 16 and earlier for Windows and Linux.
Improved web client stability because rarely used browsers with errors and non-standard behavior are no longer supported.
Linux. The platform supports XBase objects on 64-bit Linux operating systemsThe platform did not support XBase objects on 64-bit Linux operating systemsOperations with .dbf files are now available on all supported architectures, except the mobile platform.
Dynamic list. The DataVersion field is removed from the list of available fields of dynamic list settings.The DataVersion field was included in the list of available fields of dynamic list settings.The field that was erroneously added to the list of available fields of dynamic list settings is now removed from the list.
Access rights. Managed forms only display data retrieved using "." (dot) if the user has access rights for all parts of the full path to the data. If they do not have the rights, the item linked to this data is not displayed on the form.If a user did not have access rights for all parts of the full path to data retrieved using "." (dot), the item linked to the data was displayed in the form, but it did not contain any data.When accessing data using "." (dot), the form item linked to the data is not displayed on the form if the user does not have access rights for all parts of the full path to the data.
Administration tools. In the Java API for server administration, the value of the RuleType property of the AssignmentRuleInfo object matches the value of the RuleType property of the IAssignmentRule object in the server cluster administration tools that use COM connection.The values of the RuleType properties differed in the Java API for server administration and in the server administration tools that used COM connection.The server cluster administration tools are unified.
Internet-enabled functionality. The OpenID pass-through authentication protocol implementation is revised. The implementation complies with the Direct Identity version 2.0 mode of the OpenID protocol. The format of the OpenID provider address in the default.vrd file is modified (the url attribute of the rely item): httрs://<address of the OpenID provider infobase>/e1cib/oid2op. The default authentication lifetime is 24 hours. The maximum authentication lifetime is 168 hours. The protocol for interaction between the relying party and the OpenID provider is modified. In the authentication dialog box, you can disable storing authentication data. For the web client, a dialog box for entering the user name and password at the OpenID provider side is implemented.The protocol implementation did not fully comply with the Direct Identity version 2.0 mode of the OpenID authentication protocol. The OpenID provider address in the default.vrd file was as follows: httрs://<address of the OpenID provider infobase>/e1cib/oida. The default authentication lifetime was 1 week. The maximum authentication lifetime was not limited. In the web client, there was no dialog box for entering the user name and password at the OpenID provider side. The OpenID pass-through authentication protocol complies with the specification.
Add-ins. Web client. The add-in technology now supports Mozilla Firefox browser version 22.0 and later. You can use add-in adapters for Mozilla Firefox 22.0 in the later versions of the web browser without recompiling the adapters.

For add-ins intended for use with all supported Mozilla Firefox versions, you have to add several add-in versions to the archive:

  • For Mozilla Firefox version 18.0 or earlier
  • For Mozilla Firefox versions 19.0 to 21.0
  • For Mozilla Firefox version 22.0 or later

It is recommended that you specify only the minimum version of the web browser in the add-in manifest file.

Documentation on creating add-ins is updated. Read more. Examples are added, new versions of adapters for web browsers.

Adapters for Mozilla Firefox versions that are no longer supported by the developer (versions 3.6, 4.0, and 5.0) are removed.

The add-in technology did not support Mozilla Firefox browser version 22.0 or later.The add-in technology now supports new versions of Mozilla Firefox browser (version 22.0 or later).
Managed form. Full-text search.When a choice list is generated for the "input by string" feature (for reference configuration objects), the following options are available:
  • Full-text search
  • Search by substring or by the beginning of the string
  • Instant or background search

You can specify each of these options in Designer, in the configuration object properties. The full-text search is performed only among the configuration object attributes that are selected in the "input by string" options of the configuration object. If a filter is applied during the input by string, the filter is converted (whenever possible) to a full-text search query in order to increase the search performance.

For external data source tables, you can only select the search modes (by substring or by beginning of the string, and instant or background). In the file mode, the background search can be performed only when any other background or scheduled job is not being executed. For the AutoComplete and TextEditEnd event handlers, the formal option Parameters is implemented. It contains settings for getting choice data and allows you to manage this process by changing the properties of the structure that is passed in this parameter.

The following options were not available in the "input by string" feature:
  • Full-text search
  • Search by substring or by the beginning of the string
  • Instant or background search

The full-text search and search by substring were available in ChoiceDataGetProcessing handlers.

New standard options for the "input by string" feature in text boxes:
  • Full-text search
  • Search by substring (as an alternative to the search by the beginning of the string)
  • Background search (the search is running while the user is typing the search string)

Table of contents

Renamed objects

ObjectThe old nameThe new name
The name of calculating register recalculation manager type is changed. This change is not implemented in version 8.3.2 compatibility mode.CalculationRegisterRecalcs.<Calculation register name> RecalculationManager.<Calculation register name>
English names of the following script objects are changed:
  • External data source table record (ExternalDataSourceTableRecord);
  • External data source record set (ExternalDataSourceTableRecordSet).

This change is not implemented in 8.3.2 compatibility mode.

  • ExternalDataSourceRecord;
  • ExternalDataSourceRecordSet.

  • ExternalDataSourceTableRecord;
  • ExternalDataSourceTableRecordSet.

For turnovers accumulation register managers and for accounting register managers, the methods for setting and getting the totals period are renamed. For compatibility purposes, the previous names are supported.
  • GetTotalsPeriod()
  • SetTotalsPeriod()
  • GetMaxTotalsPeriod()
  • SetMaxTotalsPeriod()
For objects that describe form elements being tested, the name of the property that contains the element title is changed.

  • Title
  • TitleText

The names of the UsualGroupRepresentation system enumeration items are changed. For compatibility purposes, the previous names are supported.

  • Line
  • Margin
  • GroupBox
  • WeakSeparation
  • NormalSeparation
  • StrongSeparation
The names of the methods for getting and setting the client application window caption are changed. For compatibility purposes, the previous names are supported.

  • GetApplicationCaption
  • SetApplicationCaption
  • GetClientApplicationCaption
  • SetClientApplicationCaption
The name of the configuration property that describes the desktop command interface is changed.

  • DesktopCommandInterface
  • MainSectionCommandInterface
The name of configuration property that describes the desktop workspace (the starting page) is changed.
  • DesktopWorkingArea
  • StartPageWorkingArea
The names of settings that store start page (desktop) parameters. In version 8.3.2 compatibility mode, use the old names. When the compatibility mode is changed, the saved settings keys are changed as well.
  • Common/DesktopSettings
  • Desktop/NavigationPanel/CommandInterfaceSettings
  • Desktop/ActionsPanel/CommandInterfaceSettings
  • Common/StartPageSettings
  • MainSection/NavigationPanel/CommandInterfaceSettings
  • MainSection/ActionsPanel/CommandInterfaceSettings.
The name of the type that describes the object containing start page (desktop) settings is changed. For compatibility purposes, the previous name is supported.
  • DesktopSettings
  • StartPageSettings
The Russian name of the TestedFormField object method, which ends the editing of the current area, is changed.
  • ЗавершитьРедактированиеТекущейОбласти()
  • ЗакончитьРедактированиеТекущейОбласти()

Table of contents

Mobile platform

FunctionalityAfterBeforeResult of changes
System requirements. For iOs-based devices, the iOS version 4.x is not supported. The minimum iOS version is 5.1.

For Android-based devices, the minimum RAM size is 256 MB.

iOS version 4.x was supported.

Android-based devices required 100 MB of RAM to run 1C:Enterprise.

System requirements for the mobile platform are revised.
Managed form. In the mobile application, the extended tooltop can be used, except the Balloon option.Extended tooltips were not available in mobile applications.On the mobile platform, you can create tooltips for form elements using a variety of tooltip design options.
Common objects.Geolocation functions and multimedia tools (photos, audio- and videorecording) provided by mobile devices are available in mobile applications.

The following geolocation functions are implemented: GeographicCoordinates, LocationData, LocationProviderInformation, LocationTools, AddressData. The LocationTools global context property is implemented. Global context methods GetAddressByLocation(), GetLocationByAddress(), and ShowOnMap() are  implemented. The GeographicalSchemaCoordinates type is renamed to GeographicCoordinatesp; it is used in geolocation functions. The GeographicalSchemaCoordinates type name is supported for compatibility purposes.

The MultimediaData and MultimediaTools objects are implemented to support processing multimedia features. The MultimediaTools global context property is implemented.

These features were not provided.Geolocation and multimedia functions of mobile device perating systems are now available in the mobile platform. You can add features for defining the current location, making photos of incoming items, and so on.
Development tools. The configuration check verifies whether the conifiguration language code meets the ISO standard.  It is recommended that you use ISO-compliant language codes.The language codes were not checked for compliance with ISO standard.Reduced chance of incorrect mobile platform language selection based on the mobile device language.
1C:Enteprise script. Common modules that reuse returned values are now supportedThis feature was not provided.On the mobile platform, you can optimize getting the same data multiple times during a single session or a single server call.
Predefined data.While a mobile application is being updated, metadata objects are compared by their internal identifiers. When a mobile application is updated to version 8.3.3, the corresponding restructuring is performed. While a mobile application was being updated, metadata objects were compared by their names.You can rename metadata objects while preserving the object data.
Display of information.The mobile platform picture format is replaced by the format that supports several screen resolutions of mobile devices.All mobile platform pictures had the same resolution.The sizes of system pictures displayed on mobile device screens depend on the screen resolutions.
BackupWhen an infobase is created on iOS-based devices, the directory containing the application data is marked as excluded from the backup. When the infobase data is modified (object form extension data and register data is recorded), the directory with application data is marked for backup and the backup is initiated using the system tools.On iOS-based devices, the infobase directory was marked for backup since it was created.The application behavior meets the requirements of the Apple company to user data backup.
Spreadsheet document. On the mobile platform, resolved issues with displaying spreadsheet documents that have a large number of rows and columns.In some cases displaying a spreadsheet document with a large number of rows and columns on the mobile platform led to an unexpected shutdown.Improved mobile platform stability when processing large spreadsheet documents.
Internet-enabled functionality. For the mobile platform, the HTML-document field is implemented. The HTML-document field has the following specifics:
  • The Document and Output properties are not supported.
  • The OnClick event is fired only during the attempt to switch to a new page. At this time, all properties of the EventData parameter except Href contain the UNDEFINED value. The Href property contains the address of the new page.
The HTML-document field was not supported on the mobile platform.In mobile applications, displaying HTML pages in forms is implemented. For example, you can create a manual for your configuration.
Interface. On mobile devices with Android OS, you can change the order of items in the list of applications.On mobile devices with Android OS, changing the order of items in the list of applications was not available.Improved usability of the list of applications. User can arrange applications in any order.
Data composition system. Processing data composition system details on the mobile platform is implemented (this includes opening values and remote processing of the details). For mobile platform, the DataCompositionDetailsID object is implemented.On the mobile platform, reports that contained data composition system details could not be opened.?On the mobile platform, reports can be generated using the data composition system. Report that contains details can be opened on the mobile platform.
Mobile application development.In the Mobile application creation wizard data processor, you can specify a key for Google Maps. You can also specify a logo for screen resolution 950?1136 (iPhone 5 screen) in this data processor.These features were not provided.You can use the Mobile application creation wizard data processor for creating mobile applications that utilize new mobile platform features (geocoding support). Support of iOS-based devices was improved as well.
Internet-enabled functionality. For the objects HTTPConnection, WSProxy, WSDefinitions, and InternetMailProfile, and for the CreateWSProxy() method, the option to set a timeout for interaction with a  network resource is implemented. User names and passwords that are  passed  to WSProxy, WSDefinitions, and HTTPConnection objects can contain special characters, except ":". You can encode (the EncodeString() method) and decode (the DecodeString() method) custom text strings for using them in URLs. Encoding is performed in compliance with the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt). You can process HTTP request headers and return codes, as well as get and set request bodies as strings or binary data. The HTTPRequest and HTTPResponse objects are implemented.

This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.On the mobile plaform, the following features are available:
  • Setting timeouts for interaction with network resources
  • Using characters that do not belong to the ASCII character set in user names and passwords
  • Generating URLs and getting values from them according to the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt) when custom text is added to a URL
  • Generating HTTP requests, processing responses, and interacting with REST services from 1C:Enterprise script
1C:Enteprise script. The CurrentUniversalDateInMilliseconds() function is implemented. It gets the number of milliseconds that passed since January 1, year 0001, 0:00:00 UTC.

The attempt to assign a value to a fixed structure item raises an exception. In value tables, serialization of index descriptions is implemented. The index contents are not serialized but restored during deserialization. The hash function value can be calculated based on MD5 and CRC32 algorithms using the DataHashing object. This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.On the mobile platform, you can do the following:
  • Measure time intervals more precisely. For example, this can be handy for getting the duration of a specific action.
  • Use fixed structures in a similar way to other fixed collections.
  • Restore the value table state in more detail during its deserialization.
  • Quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools.
Managed form. When specifying values of managed form fields or tables, you can specify data stored in a specific row of a form attribute that is a table (but not a dynamic list). Data belonging to dynamic lists that are currently not displayed on a managed form is not read during the operations that involve the managed form. For attributes of String type that have fixed length and are located in managed form tables, table boxes, or spreadsheet documents, the appearance of the mark that indicates that the field must be filled is modified. The following style fonts are implemented: SmallTextFont, LargeTextFont, and ExtraLargeTextFont. For the Font type, the Scale property is implemented. It defines increase or decrease of the font relative to the initial size. For groups of "usual group" or "page" type, you can set the background color of form group extensions using the BackColor property. The URLProcessing handler is implemented for the Label form field, Decoration form field of Label type, and managed form. The handler is called when a user clicks a formatted string with a hyperlink in a field. Extended appearance customization options for form fields of label type and decorations of label type. In usual groups with limited width, the size of managed form buttons can vary depending on the width, which is similar to the behavior of other form items in a group with limited width. This functionality is similar to the PC-based platform functionality.This feature was not provided on the mobile platform.On the mobile platform, you can do the following:
  • Edit data stored in specific rows of form table data in separate fields.
  • Get fast access to managed forms with dynamic lists located on different pages.
  • Ensure that the behavior of the mark that indicates that the field must be filled is the same for all attribute types.
  • Specify font size in a form relative to the form base font, without using absolute font size values.
  • Improve form usability by highlighting group colors.
  • Create a handler for each hyperlink represented as a formatted string.
  • Use more appearance customization options in managed forms.

When the size of a usual group is limited, the algorithm used for resizing group items is the same for all item types.

Applied objects. User presentations are implemented for database objects of the following types: Catalog, Document, and ExchangePlan. In document journals, the attribute containing the document number has fixed length if all documents included in the journal have the number field of String type with fixed length. Otherwise, the journal attribute has variable length. A value obtained from an unfilled table attribute, value tree, or tabular section is equal to the default value of the column attribute type, with the type qualifier taken into account. This functionality is similar to the PC-based platform functionality.This feature was not provided on the mobile platform.On the mobile platform, you can do the following:
  • Get nonstandard data presentations in various scenarios.
  • Get document numbers in a uniform way, regardless of the method used to obtain the document numbers: either from the document itself or from the document journal. 
  • Generate default values in the same way as they are generated on the PC-based platform.
Command interface. In the information register record form, if the OnlyInActions property of the Copy command has the Auto value, the system behavior is changed. This value now means that the command is located in the More (or All actions) menu only.

This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.On the mobile platform, you can specify the same default location for the Copy command in information register records set forms and in the item forms.
Charts. New types of charts are implemented:
  • Funnel
  • 3D funnel
  • Normalized funnel
  • 3D normalized funnel

The antialiasing mode is implemented for charts.

You can connect series of charts to each other.

The semitransparency mode is implemented for charts. 

The Indicator property is implemented for the tape graph chart.

This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.Extended chart features on the mobile platform.
Information registers.For periodic information registers, the totals for getting first and last slices are implemented.

This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.On the mobile platform, you can get  first and last slices, which represent data as of the last (current) moment in time, much faster.
Spreadsheet document. If a fixed area is larger than the displayed area, the spreadsheet document does not use the fixation.

The algorithm for horisontal cell placement in different rows is modified.

This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.On the mobile platform you can:
  • Improve usability of reports that contain areas with left or top fixation.
  • Improve usability of spreadsheet documents.
Working with XML, XDTO. If a message to a user contains characters incompatible with XML format (in the thick or thin client), the error XML text contains invalid characters in X position is generated.

This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.The processing of characters that are incompatible with XML format on the mobile platform is uniform with processing them on the PC-based platform.
Display of information. Formatted strings are available (the FormattedString type).

You can use a formatted string as:

  • Data for the "label field" form items
  • Title for form items of decoration type
  • MessageText parameter of the DoMessageBox() method
  • QueryText parameter of the DoQueryBox() method

This feature was not provided on the mobile platform.On the mobile platform, the text presentation capabilities are improved.
Working with XML, XDTO.During the import of XSD schema, if  the target namespace definition is missing in the schema, a diagnostic message is displayed.During the import of XSD schema, when any problems occurred while loading the XSD schema, a diagnostic message was not displayed.Improved diagnostics during XSD schema import.
Managed form. Command interface. Common objects. You can specify the Arbitrary type for a subordinate attribute of a managed form attribute (for example, a value table column or a value tree column). For managed forms, the URL and AutoURL properties are implemented. You can use the URL property to get a link to the main form of the object. For the GetForm(), OpenForm(), and OpenFormModal() methods, the URL parameter is implemented. Its value is assigned to the URL property of a form when the form is obtained or opened. Navigation links to lists are implemented. For a form whose main attribute is a dynamic list with a main table specified, the navigation link points to the list of the object specified as the main table. Following the link opens the main form of the list. You can use navigation links to global command interface commands. The format of navigation links to navigation points generated by standard commands is modified. Changes made to a table of totals storage settings for accumulation registers are applied within a transaction. Values of the ReadOnly and Protection properties are preserved when a spreadsheet document is passed between the client and the server. For the NumberInWords() global context method, the AU formatting option is implemented.

The TextReader and TextWriter objects are implemented. This functionality is similar to the PC-based platform functionality.

This feature was not provided on the mobile platform.Some mobile platform features are now uniform with PC-based platform.
Mobile application. The mobile platform supports all of the interface languages that are supported in the PC-based platform. The mobile platform delivery that supports only English and Russian interface languages is also available.

The content of the mobile platform distribution kit is modified.

The mobile platform supported English and Russian interface languages only.The system part of the mobile platform interface supports more languages than before.
Development tools. If the Use purposes configuration property is set to Mobile device only, other configuration settings are changed automatically:
  • The Modality usage mode property is set to Use.
  • The Interface compatibility mode is set to Version 8.2.
If the Use purposes configuration property was set to Mobile device only, other configuration properties were not changed automatically.For configurations being developed for mobile platform only, eliminated the chance to save configuration property values that are incompatible with mobile platform limitations.

Table of contents

Transition from the version 8.2 to the version 8.3.3

  • Conversion of configurations, infobases, external data processors, and external reports is not required during the upgrade from the version 8.2 to version 8.3.3.
  • To use certain features of version 8.3.3 you have to disable the compatibility mode. The structure of certain database objects is modified when disabling or enabling the compatibility mode. Note that to be able to work with infobases created using 1C:Enterprise version 8.2 you have to set the compatibility mode to the Version 8.2.16.

    In order to use certain optimization improvements, you have to restructure data related to the optimization areas. To restructure data, you can use the Verify and repair mode, or perform forced restructuring of the required objects.

  • Simultaneous operating of 1C:Enterprise 8.3.3 and earlier 1C:Enterprise versions with a single file infobase is not supported. In this case a diagnostic error message is displayed.
  • It is recommended that you revise the list of infobases. Infobases that are present in the list when version 8.3.3 is installed in most cases have version 8.2 or 8.1 (because it is the default version, which is set automatically when an infobase is created or added to the list). Therefore, in order to open an infobase in 8.3.3 (using the program that starts 1C:Enterprise), you have to specify the required version in the list of infobase startup settings, or specify the version directly in the infobase settings.
  • At the first start of server cluster version 8.3.3 on the computer that has previous versions of ther server cluster installed, the content of the cluster register file (1CV8Reg.lst) is converted to a new format. The register of the server cluster 8.3.3 is stored in the file 1CV8Clst.lst, in the same directory as the cluster register of the previous versions. There is no data synchronization between cluster registers of  different versions after the first start of server cluster 8.3.3. 

    To perform the conversion of the cluster register from version 8.2 to version 8.3 once more, stop the server cluster 8.3, delete the server cluster 8.3 register (the 1CV8Clst.lst file), and then start the server cluster 8.3.3.

  • To increase the performance of the configuration repository in a scenario when a repository server is used, disable the compatibility mode of the configuration repository. To access the configuration repository using earlier 1C:Enterprise versions, enable the compatibility mode of the configuration repository. The conversion process can take significant time.
  • Changed the full-text search index format. For efficient full-text search when using input by string, it is recommended that you clear and update the full-text search index during the transition to 1C:Enterprise version 8.3.3. It is also recommended that you clear and then update the full-text search index during the transition to earlier platform versions.
  • For infobases that use the OpenID authentication, you have to change the publishing settings in the default.vrd file.

Table of contents

Transition from the previous version to version 8.3.3

  • Conversion of configurations, infobases, external data processors, and external reports is not required during the transition from the previous version to the version 8.3.3.
  • Some features that are added in version 8.3.3 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.
  • Simultaneous operating of 1C:Enterprise 8.3.3 and earlier 1C:Enterprise versions with a single file infobase is not supported. In this case a diagnostic error message is displayed.
  • To increase the performance of the configuration repository in a scenario when a repository server is used, disable the compatibility mode of the configuration repository. To access the configuration repository using earlier 1C:Enterprise versions, enable the compatibility mode of the configuration repository. The conversion process can take significant time.
  • Changed the full-text search index format. For efficient full-text search when using input by string, it is recommended that you clear and update the full-text search index during the transition to 1C:Enterprise version 8.3.3. It is also recommended that you clear and then update the full-text search index during the transition to earlier platform versions.
  • For infobases that use the OpenID authentication, you have to change the publishing settings in the default.vrd file.

Table of contents

© 2020-2022 1C INTERNATIONAL LLC www.1Ci.com Support policy