Version 8.3.1

Version 8.3.1

Version 8.3.1 does not include changes introduced in version 8.2.17.

Version 8.3.1 includes known bug fixes and functionality modifications.

Improved the list of new and updated features:

Keywords and interface texts are color-coded (it is the same formatting that is used in the documentation).
Sections describing behavior in the compatibility mode have color background.
The list structure is updated, providing more details and better usability (only for version 8.3.1 or later).

New functions and changes

Functionality	After	Before	Result of changes
Configuration properties.	Version 8.2.16 is added to the list of available values of the Compatibility mode property.	Compatibility modes were available for the following platform versions: 8.1 and 8.2.13.	1C:Enterprise provides compatibility of configurations developed using version 8.3.1 or later with previous platform versions.
Designer. Multiplatform architecture.	The client application for Linux operating system is available. It includes thin client, thick client, and Designer. It supports file and client/server operation modes. Thin client can connect to infobases using a web browser. Limitations of the client application for Linux are listed in the documentation. Installation of multiple 1C:Enterprise versions is not supported. Shortcuts for noninteractive startup application, thin client, and thick client are added to the application menu of Linux desktop environment. They are located in the Finance subsection of the Office section.	Only the 1C:Enterprise server and the web client were available for Linux operating system.	You can develop applied solutions and run client applications on Linux operating system.
Thin client access over the Internet.	The thin client is now HTTPS-enabled, thanks to client certificate support. The following client certificate storage options are supported: file, Windows certificate store, and NSS certificate store. The following command line options for specifying certificate parameters are implemented: HttpsCert, HttpsCA and HttpsNSS. Client applications for Linux operating system do not support Windows certificate store, and HttpsCert, and HttpsCA command line options.	The thin client was not HTTP-enabled, and client certificates were not supported.	The thin client is HTTP-enabled, and client certificates are supported.
Web links.	Web services can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).	Web services could not operate using HTTPS with client certificates.	Web services are operational in cases when the server side requires a client certificate to use HTTPS.
Internet-enabled functionality.	HTTP and FTP connections can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).	HTTP and FTP connections could not operate using HTTPS with client certificates.	HTTP and FTP connections are operational in cases when the server side requires a client certificate to use HTTPS.
1C:Enterprise script.	You can calculate the value of hash function by MD5 and CRC32 algorithms using the DataHashing object.	Calculating the hash function required the use of third-party (add-ins, etc.) tools.	You can 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.
External data sources. Common attributes / Data separation.	A common attribute can include an external data source. Connection parameters for such external data sources are stored by separator values. If a separator is not used in a session, the separator is treated as an independent value for storing connection parameters. Data located in tables of external data sources is not separated by separator values.	Common attributes could not include external data sources.	You can specify connection parameters for each data area in the infobase. This provides you with the option to access either different infobases with the same structure, or a single infobase with different connection parameters.
Managed form.	You can specify data located in a specific row of a form attribute that has table structure (except dynamic lists) as a value of a managed form field or table.	This feature was not provided.	You can implement such interface features as displaying report settings in separate form fields.
External data sources.	Operating system authentication is available when working with external data sources. The SessionOSAuthenticationChange access right is implemented. It allows or denies changing the operating system authentication setting both in user settings and in current session parameters.	This feature was not provided.	You can establish connection to external data sources if the only authentication method available is operating system authentication.
Applied objects. Display of information.	User presentations for data base objects of the following types: Catalog, Document, ChartOfAccounts, ChartOfCalculationTypes, ChartOfCharacteristicTypes, BusinessProcess, Task, ExchangePlan, Table. Implemented the PresentationFieldsGetProcessing and PresentationGetProcessing event handlers for object manager modules of these types. This change is not implemented in version 8.2.16 compatibility mode.	Modification of database objects using script tools was not allowed.	Custom presentations for database objects. The option to obtain presentations for external data source tables when the field that provides the presentation is not specified. The option to obtain presentations of objects that include localized data.
External data sources. 1C:Enterprise script.	You can search for references to objects of external data source tables using the FindByRef() global context method or Find references to object standard function. The search is performed both in infobase tables and in external data source tables.	Searching for references to objects of external data sources tables using the FindByRef() global context method or Find references to object standard function was not available.	You can search for references to objects of external data source tables.
External data sources.	The AllRefsType() method is implemented for the ExternalDataSourceTablesManager object.	This feature was not provided.	Implementation of missing features for working with external data sources.
External data sources.	The OpenValue() global context method allows opening the following value types: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey.	The OpenValue() global context method did not allow opening the following value type: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey.	Implementation of missing features for working with information registers and external data sources.
Database configuration update. Server cluster.	Background database configuration update is implemented. Supported in client/server mode only. Available when the data structure is modified. Does not require long-lasting exclusive access to the infobase. The exclusive access is required at the final stage of the background update for a short period of time. Database configuration update service is implemented in the server cluster. A system background job, which is used for the background database configuration update, is implemented. The following events are implemented in the event log: _$InfoBase$_.DBConfigBackgroundUpdateStart, _$InfoBase$_.DBConfigBackgroundUpdateFinish, _$InfoBase$_.DBConfigBackgroundUpdateCancel, _$InfoBase$_.DBConfigBackgroundUpdateSuspend, and _$InfoBase$_.DBConfigBackgroundUpdateResume.	Database configuration update related to the change of data structure was possible only in the exclusive mode.	The update of database configuration with significant changes in the data structure does not cause long application downtime for end users.
1C:Enterprise script. Working with files. Web client.	The TempFilesDir() method is implemented for the web client. The method is available when the file system extension is installed. The UserDataWorkDir() method is implemented. It provides access to the user directory created by the system. The method is available for thin, thick, and web clients. In the web client the method is available when the file system extension is installed. The DocumentsDir() method is implemented. It provides access to the default document directory of the operating system. The method is available for thin, thick and web clients. In the web client the method is available when the file system extension is installed.	Standard catalogs (user data directory and document directory) were inaccessible for standard tools. In the thick and thin clients the access could be implemented using third-party tools, which reduced 1C:Enterprise portability between operating systems and client applications types.	Access to certain standard directories on the client computer, which allows storing user file data in designed locations without using third-party tools.
Display of information.	Formatted strings are available (FormattedString type). You can use formatted strings as: data for the form elements of Label type; title for the Decoration form element; MessageText parameter of the DoMessageBox() method QueryText parameter of the DoQueryBox() method.	Displaying text that included various formatting styles was only available for HTML documents and formatted documents.	Improved text presentation capabilities and usability.
1C:Enterprise script. Managed form.	The URLProcessing handler is implemented for the form field Label, form field Decoration of Label type, and managed form. The handler is called if the following conditions are met: there is a formatted string in any of the specified form fields, it contains a hyperlink, and the Hyperlink property of the form element is set to False.	Implementing presentation of an entire form element as a hyperlink was allowed, but including multiple hyperlinks in a single field was not allowed.	The option to handle each hyperlink contained in a formatted string separately.
Command interface.	You can use navigation links to commands of the global command interface. Using a link executes the command. Support of navigation links to commands is implemented for the GotoURLGotoURL() global context method.	This feature was not provided.	Using a link can execute a command, and this feature can be used in the script.
Managed form.	The URL property is implemented for managed forms. It is used for obtaining a link to the default object form. The AutoURL property is implemented for the managed form. The GetURL() method of the ClientApplicationWindow objects returns a value of the URL property (if the AutoURL property is set to False) or the standard link to the default form.	This feature was not provided.	You can specify the value of the navigation link obtained from the client application window.
1C:Enterprise script. Common attributes / Data separation. Applied objects.	Document journals can be included in contents of common attributes, which are not used as separators. For compatibility purposes, in infobases created in 1C:Enterprise version 8.2, the value of the Use property of the the common attribute content element is set to Do not use for document journals.	Common attributes could not be displayed in document journals.	Common attributes can be displayed in document journals.
Display of information. Managed form.	Implemented the following style fonts: SmallTextFont, LargeTextFont, ExtraLargeTextFont. For the Font type the Scale property is implemented. It specifies increase or decrease of the font size relatively to the original size.	The only method of specifying font size in a managed form was setting absolute font size.	You can specify the size of the form font relatively to the base font of the form, without using absolute font size values.
Server cluster. 1С:Enterprise script.	The SafeCallMemoryLimit property is implemented for the IWorkingProcessInfo object. It specifies the amount of memory (in bytes) that the application can use during a single server call. The SafeWorkingProcessesMemoryLimit property for the IWorkingServerInfo object is implemented. It specifies maximum amount of memory (in bytes) available for all running processes on a given working server.	No tools for limiting memory usage were available. It might cause problems in some situations - for example, when users customized reports that selected large amounts of data.	Server stability improved. If a specific session consumes a large amount of memory, it does not cause emergency shutdown of the entire server cluster. Instead, the client application that causes the memory consumption is shut down.
Server cluster. 1C:Enterprise script.	While a working process is executing a script in the client/server infobase mode, the stack is monitored to prevent it from overflowing.	Infinite recursion might lead to emergency shutdown of the working process of the server cluster.	Stability of server cluster operation improved.
Server cluster. 1C:Enterprise script.	For the ISessionInfo and IInfoBaseConnectionInfo objects the following properties are implemented: MemoryCurrent - size of memory (in bytes), used from the beginning of the current call; MemoryLast5Min - size of memory (in bytes), used by calls during the last 5 minutes; MemoryAll - size of memory (in bytes), used by calls since the beginning of the session; InBytesCurrent - number of bytes read from the disk since the start of the current call; InBytesLast5Min - number of bytes read by the session from the disk during the last 5 minutes; InBytesAll - number of bytes read from the disk by the session since the beginning of the session; OutBytesCurrent - number of bytes written to the disk by the session since the beginning of the current call; OutBytesLast5Min - number of bytes written to the disk by the session for the last 5 minutes; OutBytesAll - number of bytes written to the disk by the session since the beginning of the session. Similar properties are implemented in the cluster console for the list of sessions, list of connections, and connection properties dialog.	This feature was not provided.	Monitoring tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.
Technological log. Server cluster.	Extended the list of properties for the <call> event of the technological log when the event is generated for the rphost process (the process property is set to rphost), and also when the rphost process performs a call to virtual system resources. The following properties are added: Report - metadata object name of the report being executed; Method - name of the called method; SessionID - session number; Memory - size of memory (in bytes) that was occupied and not released during the call; MemoryPeak - size of memory (in bytes) that was occupied and not released during the call. The peak value; InBytes - number of bytes read from the disk during the call; OutBytes - number of bytes written to the disk during the call; Context - event context.	The listed properties were absent from the <call> event.	Technological log tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.
Common attributes / Data separation. 1C:Enterprise script.	You can delete data from a specific data area or from the entire infobase. The following data can be deleted: Applied object data Settings storage data History List of users Time zone settings The Administration right is required for deletion. The deletion can be performed: using the /EraseData command line option of Designer batch mode using the EraseInfoBaseData() global context method The _$InfoBase$_.EraseData event is implemented in the event log.	It was impossible to delete a specific data area.	You can delete a data area that is no longer needed (for example, data belonging to a subscriber that stopped using the system).
Server cluster. Software licensing.	The licensing service is implemented for the server cluster. The license search algorithm is modified.	The licensing service was not present.	You have the option to bind a software license to a specific computer, which is intended for running the licensing service only and will not be subject to hardware changes.
Developing tools.	Dumping configurations to files and loading configurations from files is implemented. Most objects are dumped to .xml files. Modules are dumped to the text files. Pictures are dumped to files in their original format, help information is dumped to .html files. Vendor configurations are dumped to configuration files (.cf). Ordinary forms and interfaces are dumped to binary files. Dump configuration to files and Load configuration from files commands are added to the Configuration menu. Dump configuration files and Load configuration files commands are removed from the Configuration menu, but you can restore them using the main menu settings dialog. The DumpConfigToFiles and LoadConfigFromFiles command line options are implemented.	Limited set of data was dumped and loaded: modules, help information, templates, rights, and pictures. Other configuration data was not dumped. Dump configuration files and Load configuration files commands from the Configuration menu were used for dumping and loading data.	You can analyze and modify configurations using third-party tools.
Display of information. Managed form.	You can specify the background color for form group extensions of regular groups and pages using the BackColor property. If the background color of a group is different from Auto and the group is displayed as a Group box, the group box (including the title) is filled with the specified background color.	The option to specify background color for form groups was not provided.	The color highlighting of groups improves visibility of form elements and the overall usability of forms.
Common attributes / Data separation.	New global context methods for managing the safe mode of data separation are available in 1C:Enterprise script: SetDataSeparationSafeMode and DataSeparationSafeMode. They duplicate the functionality of the safe attribute in the zone tag of the default.vrd file.	Switching to the safe mode of data separation was only available by editing the file default.vrd and only if the web server connection to the infobase (the HTTP protocol) was used.	The new methods enable safe execution of code fragments called from sessions that do not use separator values (but are intended to run in specific data areas, without any way to change the area accidentally).
Event log. OpenID authentication.	In case of successful or unsuccessful OpenID authentication the Session.Authentication or Session. Authentication error events are generated in the event log.	OpenID authentication events were not written to the event log.	You can obtain information about OpenID authentication events from the event log.
Event log. OpenID-authentication.	For infobases that are OpenID providers the OpenIDProvider.PositiveAssertion event is implemented. It is generated in case of a positive response to the authentication request. If the response to the authentication request is negative, the OpenIDProvider.NegativeAssertion event is generated in the event log of the infobase.	This feature was not provided.	Improved tools for administration of OpenID providers.
Developing tools.	You can view the values of the form element properties Font, TitleFont, FooterFont and ChoiceList in a separate window when editing of these properties is disabled.	These properties could not be viewed if the object was not locked in the repository or was supported.	If an item is not locked in the configuration repository or is supported, you can view its font style and choice list without disabling support and without locking the object in the repository.
Server cluster.	When logon to or logout from an infobase that requires a client license is performed, the platform can notify an external application using web service methods. In response to logon notification, the external application can allow or deny the start of the session. This option is only available in client/server infobase mode. For specifying web service parameters, the following properties are implemented: External session manager property of the infobase in the cluster console ExternalSessionManagerConnectionString property of the IInfoBaseInfo object. If a web service for external session management is unavailable, the system behavior is determined using the following properties: Required usage of external session manager property of the infobase in the cluster; ExternalSessionManagerRequired property of the IInfoBaseInfo object. The external session manager service is implemented on the server. Parameters of invoked web services are listed in the documentation.	The only option to limit the number of simultaneous sessions was appropriate modification of the applied solution. A platform mechanism for performing this task was not available.	A platform mechanism for monitoring the number of simultaneously used licenses for various applied solutions, which does not require modification of these applied solutions.
Web client. Add-ins.	You can use add-ins in Google Chrome and Safari web browsers (for operating systems of Windows family and Mac OS X). The Mac OS value is implemented for the PlatformType system enumeration. A file system extension is available for these browsers on operating systems of Windows family and Mac OS X. A cryptographic extension is available for these browsers on operating systems of Windows family only.	Add-ins, file system extension, and cryptographic extension were not supported for Google Chrome and Safari web browsers.	A file system extension and cryptographic extension (for operating systems of Windows family only) are available for Google Chrome and Safari web browsers. Add-ins can be created for all supported web browsers.
Pictures.	Processing pictures from the script with help of the new PictureProcessor object. The following options are available: Selecting a significant picture part Rotating a picture	This feature was not provided.	A way to process pictures before placing them in a spreadsheet document. Usage examples: Select a seal from a photo Rotate a picture by a specified angle to align a signature
Charts.	The managed form editor allows interactive setup for the following attribute types: Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema. You can open the interactive setup dialog box from the property panel of the attribute.	Only the following ways to set up the Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema objects were available: through 1C:Enterprise script, or by putting a set up object to a template and then putting the object from the template to a form element at form creation.	This feature facilitates development.
Display of information.	New parameter AU for the global context method NumberInWords(). It is only used in the English locale (en, en_XX). It defines the number notation, classic or compact. In the classic notation "and" is always used between the word "hundred" (or "thousand" or "million") and the word representing the last two decimal digits. For example, 150 is "one hundred and fifty", while 100 is "one hundred" and 50 is "fifty". In the compact notation "and" is omitted.	The compact notation was always used for converting numbers to English words.	Correct number-to-word conversion according to the common practice rule in European countries.
Chart of characteristic types.	You can use the ALLOWED keyword when retrieving a list of characteristics, provided that the list was defined using one of the following: the CHARACTERISTICS keyword of the query language or the dialog box for specifying object characteristics. If you retrieve the list of characteristics using a query, you have the option to use the ALLOWED keyword there.	The ALLOWED keyword was not used when retrieving lists of characteristics.	Data access restrictions are implemented for tables that store property lists (for example, charts of characteristic types).
Data composition system.	Fields from data sets that are not connected can be displayed in details. For DataCompositionTemplateRecordsDataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects, the DataSets properties are implemented. The property value is an array containing names of data sets whose details are displayed. The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects is deprecated. It is recommended that you do not use this property, although it is supported for compatibility purposes. Calling the DataSet property throws an exception if the DataSets property contains an array with more than one item.	It was impossible to display fields from data sets that were not connected. The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords contained the name of the dataset whose details were displayed.	You can create complex analytic reports.
External data sources.	The FormGetProcessing event is implemented in the manager module of external data source table.	This feature was not provided.	The default form of the external data source can be redefined when the external data source is opened or obtained.
External data sources.	Hierarchical lists can be organized for object data of external data sources. The ParentField and UnfilledParentValue attributes are implemented for the Table metadata object. Hierarchical object tables can be used in the data composition system, queries, and dynamic lists.	This feature was not provided.	You can work with hierarchical data in external data sources.
External data sources. Working with queries. Data composition system.	You can use temporary tables when working with external data sources. Temporary tables are created directly in the database of the external data source. The following syntax is used for calling temporary tables:ExternalDataSource.<External data source name>.TempTable.<Temp table name>.	This feature was not provided.	You can create complex reports based on external data source tables.
Chart of characteristic types. Data composition system.	When creating object characteristics using the Additional characteristics of metadata object dialog, if the list of characteristics is not obtained from the chart of characteristic types, the characteristic value type is defined by the attribute type specified in the Value field attribute of this dialog. If this attribute is not specified, the characteristic value type is Boolean. When object characteristics are specified using the CHARACTERISTICS query language extension of the data composition system, if the TYPE property is not specified, the characteristic type is defined by the value type obtained in the CHARACTERISTICVALUES property. If the CHARACTERISTICVALUES property is not specified, the characteristic value type is Boolean.	When object characteristics were specified using the Additional characteristics of metadata object dialog or the CHARACTERISTICS query language extension, if the list of characteristics was not obtained from the chart of characteristic types, the characteristic value type was Boolean.	You can store characteristic types in catalogs, and you can modify characteristic types using a complex type of the attribute that stores the characteristic value (e.g., type of information register resource).
1C:Enterprise script.	Serialization of value table index descriptions is implemented. The index content is not serialized, but restored during deserialization.	Value table indexes were lost during serialization/deserialization.	More complete restoration of value table state during deserialization.
Charts	New types of charts are implemented: Funnel 3D funnel Normalized funnel 3D normalized funnel The following properties are implemented for the Chart object: FunnelNeckHeight, FunnelNeckWidth, and FunnelSpace. These properties are applicable for the new charts types only.	This feature was not provided.	New chart functionality.
Charts.	Antialiasing mode is implemented for charts. SplineMode and SplineStrain properties are implemented for the Chart object. These properties are applicable to the following chart types: line, stacked line, area, stacked area, normalized area, ceil graph, tape graph, waterfall, funnel, and 3D funnel, and also for the following chart types, which have the Indicator flag set for the series: column, 3D column, bar, 3D bar, stacked column, 3D stacked column, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.	This feature was not provided.	New chart functionality.
Charts.	You can connect series of charts with each other. For the Chart object the following properties are implemented: ValuesBySeriesConnection, ValuesBySeriesConnectionLines, and ValuesBySeriesConnectionColor. These properties are applicable to the following chart types: stacked column, 3D stacked column, stacked bar, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.	This feature was not provided.	New chart functionality.
Charts.	The semitransparency mode is implemented for charts. SemitransparencyMode and SemitransparencyPercent properties are implemented for the Chart object. These properties are applicable to the following chart types: area, bar graph, pyramid graph, ceil graph, tape graph, waterfall, funnel, 3D funnel, and 3D normalized funnel.	This feature was not provided.	New chart functionality.
Charts. Data composition system.	For the objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance the following properties are implemented: ChartType.ValuesBySeriesConnection, ChartType.ValuesBySeriesConnectionLines, ChartType.ValuesBySeriesConnectionColor, ChartType.SplineMode, ChartType.SplineStrain, and ChartType.SemitransparencyMode. These properties are used for setting data composition template parameters.	This feature was not provided.	New chart management options in the data composition system.
Data composition system.	In the data composition system expression language the following aggregate functions are implemented: Every(), Any(), Stddev_Pop(), Stddev_Samp(), Var_Samp(), Var_Pop(), Covar_Pop(), Covar_Samp(), Corr(), Regr_Slope(), Regr_Intercept(), Regr_Count(), Regr_R2(), Regr_AvgX(), Regr_AvgY(), Regr_SXX(), Regr_SYY(), and Regr_SXY().	These aggregate functions were not provided in the data composition system expression language.	The new functions facilitate creation of complex analytic reports.
Data composition system.	In the data composition system expression language the following functions are implemented: ACos(), ASin(), ATan(), Sin(), Cos(), Tan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Round(), Int(), ValueType(), and Type().	These functions were not provided in the data composition system expression language.	The new functions facilitate creation of complex analytic reports.
Data composition system.	New aggregate function Rank() in the data composition system expression language. The function returns a sequence number of the current record in the current grouping, provided that all records of the current grouping are sorted in the specified order.	This aggregate function was not provided in the data composition system expression language.	The new functions facilitate creation of complex analytic reports.
Data composition system.	New aggregate function ClassificationABC() in the data composition system expression language. The function returns the class number: 1 – class "А", 2 – class "B", 3 – class "C".	This aggregate function was not provided in the data composition system expression language.	The new function facilitates creation of complex analytic reports.
Spreadsheet document.	The Merge command is added to the shortcut menu of a spreadsheet document. It is also accessible through a keyboard shortcut Ctrl+M.	Merging cells of a spreadsheet document was only available by using the menu command Table - Merge or clicking the corresponding toolbar button.	Improved usability of spreadsheet documents containing a large number of merged cells.
Charts.	The Indicator property is supported for the tape graph chart: when antialiasing is disabled, the series with the Indicator property set are displayed semitransparently on the entire chart area, overlapping other series.	This feature was not provided.	New chart functionality.
Managed form.	You can specify the Arbitrary type for a subordinated attribute of a managed form attribute (e.g., column of a value table, column of a value tree, etc.).	It was impossible to store some data types (such as a references to external data source tables) in subordinated attributes of managed form attributes.	You can store references to external data source tables in subordinated attributes of managed form attributes.
Display of information.	You can manage duplex printing of spreadsheet documents, graphical schemas (using script and interactively), and text documents (interactively only). System enumerations DuplexPrintingType and PagePlacementAlternation are implemented.	This functionality was only available from a printer driver.	You can explicitly specify the duplex printing option in some use cases.
Developing tools. Tools for publishing the web client and web services.	In the dialog for publishing to the web server you can edit all tags present in the default.vrd file. You can edit custom default.vrd files in this dialog. The descriptor parameter of the webinst utility allows you to perform publishing by template. The generated default.vrd file is used as a template.	A limited set of tags present in the default.vrd file was available for editing in the dialog for publishing to the web server. The option to publish by template was unavailable in the webinst utility, which limited the capabilities of automatic publication. E.g., publishing of web services using the utility was impossible.	You can edit all tags of the default.vrd file interactively, and you can create templates for the future automatic publication. Using templates allows publishing web services using the command line utility.
Client application installation.	You can set up the update of thin client distribution kit and downloading the list of common infobases using an HTTP connection or a web service. If versions of client and server applications do not match, the thin client is downloaded and installed automatically. The following parameters of the 1cestart.cfg file are implemented : InternetService - address of the web service for updating of the thin client distribution kit and the list of common infobases, WebCommonInfoBases - address of the web service for downloading the list of common infobases, WebDistributiveLocation - address of the web service for updating the thin client distribution kit. You can specify a link to the thin client distribution kit in the following configuration files: In the default.vrd file using the pubdst attribute; In the conf.cfg file using the PublishDistributiveLocation parameter.	Automatic update of the thin client and downloading of list of common infobases were only available in a local network.	You can update the thin client distribution kit and download the list of common infobases without creating common directories. This allows you to obtain an up-to-date version of the distribution kit and the current list of infobases from a remote network.
Working with DBMS.	DBA rights are not required for creating infobases in Oracle Database. The following actions cannot be performed without DBA rights: creating a database (data schema) deleting a data base (data schema) using the cluster management console	DBA rights were required for creating infobases in Oracle Database.	Increased security of DBMS operations. New scenario of creating an infobase without DBA rights, provided the database (data schema) already exists.
Working with Internet. 1C:Enterprise script.	Encoding of text strings is implemented (the global context method EncodeString()). It simplifies the following operations: Converting a text string to a format that allows using it as a part of a URL Converting a URL string to a RFC 1738-compliant format Decoding of text strings is implemented (method DecodeString()).	This feature was not available.	Easier generation of URLs containing non-English characters.
Administration tools	You can create a self-extracting archive (SFX archive) of a client application and upload it to a web site. You can include the client application distribution kit and the 1CEStart.cfg configuration file, which is used for installing the client application, into the archive. The created executable file is only intended to run on Windows operating systems. The self-extracting archive is generated using the 1CEClientSetupMake.exe utility, which is distributed via ITS (http://its.1c.ru/db/metod81#content:4914:1).	This feature was not provided.	Simplified installation of client applications on the client computer for infobase access over the Internet (instead of using the web client).

Table of contents

New functions and changes in 1C:Enterprise mode

Functionality	After	Before	Result of change
Standard functions.	The search for references to external data source tables is available for the standard function Find references to object, which operates in the managed mode.	It was impossible to find references to objects of external data sources tables using the standard function Find references to object.	You can search for references to external data source objects using a standard function.
Spreadsheet document.	In a spreadsheet document that is in the read-only mode, you can expand and collapse groups not only using a mouse, but also using keyboard shortcuts and the shortcut menu of the spreadsheet document.	In a spreadsheet document that was in the read-only mode, expanding and collapsing groups could only be performed using a mouse.	Improved usability of spreadsheet documents.
Navigation links.	In the In tabs form opening mode when a form is opened by clicking a navigation panel command and the navigation link is requested, if the managed form property AutoUrl is set to True, the form returns a link to the object displayed by the form. Otherwise, it returns the value of the Url property of the managed form.	In the In tabs form opening mode forms opened by clicking navigation panel commands returned links to navigation points.	You can open a list form in a separate window using the shortcut menu of the tab title.
Managed form.	If the EditMode property of a managed form table cell is set to Directly, pressing the Enter key in this cell moves the cursor to the next editable cell in this row. If the cell is last in a row, the cursor is moved to the first editable cell of the next row. If there is no next row and the managed form table has the Autoinput new row property set to True, a new row is added.	In the row editing mode pressing the Enter key finished editing the table cell and did not move the cursor to the next cell.	Pressing the Enter key is handled in the same way in the new row input mode and in the row editing mode. This simplifies working with the platform and enhances editing table data using the keyboard.
Managed form.	While editing a cell of a managed form table with EditMode property set to Directly: Pressing the Ins key adds a new row; Pressing PgUp or PgDn moves one table page up or down; Pressing Ctrl+Home or Ctrl+End moves to the first or to the last table row.	These features were not provided.	Improved usability of managed form tables.
Managed form.	In managed forms, in automatic table row adding mode, you can delete rows by pressing Alt+Shift+Del. A row is deleted in the following cases: The row does not contain any data, and you click in any area outside the new row. The row does not contain any data, and you move to another row using the keyboard. You can use this keyboard shortcut even while you are editing a table row.	This feature was not provided.	Improved usability of managed form tables.
The managed form.	If you press the Down Arrow key while the cursor is in the last row of a managed form table, a new row is added. If you press the Up Arrow key while the cursor is in a new row and the new row is still empty, this row is deleted. If you move the cursor from top to bottom by holding down the Down Arrow key, the cursor will stop at the last row of the managed form table. To add a new row, release the Down Arrow key and press it again.	Pressing the Down Arrow key did not create a new row. Pressing the Up Arrow key did not undo the creation of a new row.	Improved usability of managed form tables.
Managed form.	For attributes of String type that have fixed length, the automatic marking of incomplete attributes is modified. The change affects attributes located in managed form tables, table boxes or spreadsheet documents. The check whether the attribute is performed using the ValueIsFilled() method, so the value of String type is considered incomplete if it does not contain any any characters except spaces.	An attribute was considered incomplete only if it contained a blank string.	Unified the behavior of marking of incomplete attributes.
Web client.	When the web client is started in a web browser that is not in the list of supported ones, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per week.	The check for supported web browsers was not performed.	The user receives a warning if they use an unsupported web browser or an unsupported version of a supported browser.
Web client.	When the web client is started in a web browser whose version is not supported, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month.	The check for supported browser versions was not performed.	The user receives a warning when they use an unsupported web browser or an unsupported version of a supported browser. It is recommended that they change their browser version when they receive the warning.
Web client.	When the web client is started in Microsoft Internet Explorer version later than those available during the platform development, a warning is displayed. The user has the choice to continue their work in the current browser or to view the list of supported web browsers. The warning is displayed no more than once per month.	The check for supported Microsoft Internet Explorer versions was not performed.	The user is notified if their Microsoft Internet Explorer version was not tested for compatibility with 1C:Enterprise.
Technological log.	You can write information about working with external data sources to the technological log. For this purpose, the <EDS> event is added to the configuration file of the technological log.	Working with external data sources was not reflected in the system technological log.	A tool for analyzing problems that might occur while working with external data sources.
Technological log.	You can have all operations that affect server cluster functioning (for example, operations performed during data replication between cluster services) written to the technological log. For this purpose, the <CLSTR> event is added to the technological log configuration file.	Events that were generated during the execution of operations that affected server cluster functioning were not reflected in the technological log.	A tool for analyzing server cluster issues.
Server cluster. Administration tools.	Cross-platform administration server (RAS) is implemented for administering the server cluster. The application can run both as a standalone application and a service (daemon). The administration server is installed with 1C:Enterprise server. The cross-platform command line utility (RAC) is implemented for the administrator server. The utility is installed with 1C:Enterprise server. Administration utility version and administration server version may differ. The utility provides the same administration functionality as program cluster administration tools (the V82.ComConnector COM object), except operating system authentication of the administrator in infobases, clusters, or working servers. The utility does not support this feature. An interface for working with the administration server using Java is also implemented. The interface is distributed via ITS (together with its description and usage example) (http://its.1c.ru/db/metod81#content:4985:1).	Tools for 1C:Enterprise server cluster administration were only available for Windows operating system as a cluster administration console and as V82.ComConnector COM object. Linux tools for server cluster administration were not provided.	You can administer 1C:Enterprise server cluster using the command line in various operating systems (Windows and Linux), and also from Java programs.

Table of contents

Optimization

Functionality	After	Before	Result of changes
Working with DBMS.	Optimized performance of Oracle DBMS queries that include complex conditions for data access restrictions.	Insufficient performance of queries that include complex conditions for data access restrictions.	Improved performance of operations with data access restrictions in Oracle Database.
Applied objects.	Working with memory is optimized for some mechanisms.	Insufficient performance in certain scenarios.	Improved overall system performance in some scenarios.
Working with queries.	When executing a query, for all IN HIERARCHY conditions with the same parameter value a single temporary table per batch query is generated.	When executing a query, for IN HIERARCHY conditions with the same parameter value several temporary tables were generated.	Improved the performance of queries containing the same parameter values in several IN HIERARCHY operations.
Working with queries.	When executing a query, for all IN conditions with the same list of values a single temporary table per batch query (for storing the list) is used.	When executing a query, for IN conditions with the same list of values several temporary tables were generated, one for each condition.	Improved the performance of queries containing the same list of values in several IN operations.
Working with queries.	Improved performance of queries that include the IN HIERARCHY expression. Improved performance of queries that include performing data composition system operations on external data sources by using the IN GROUP and IN GROUP FROM THE LIST expressions.	Insufficient performance of query and report selections in some cases when hierarchy conditions were used.	Improved performance of query and report selections in some cases when hierarchy conditions are used.
Server cluster. Client application.	The amount of memory consumed by server working processes is significantly reduced. Reduced client application startup time. The effect is especially noticeable on configurations having large volumes of metadata.	Inefficient use of memory on configurations having large volumes of metadata.	Memory requirements for servers with configurations having large volumes of metadata are reduced.
Operating with DBMS.	For PostgreSQL and Oracle Database, optimized recording register records with update of account register totals. The optimization is achieved by introducing a new index. The performance increase takes effect after restructuring accounting registers and disabling the compatibility mode.	The data structure did not allow using the existing indexes at their full potential, which led to insufficient system efficiency.	Improved performance of operations with accounting registers in PostgreSQL and Oracle Database DBMS.
Operating with DBMS.	Improved performance of requests to main tables when Oracle Database is used.	Response time for some DBMS requests was sub-optimal.	Improved performance of database requests. This includes a significant increase in the speed of configuration updates that require infobase structure updates.
Operating with DBMS.	Optimized some accounting register-related DBMS requests. In particular, optimized requests that include filters by account.	Inefficient usage of DBMS capabilities.	Improved performance for "heavy" accounting register requests (such as, when creating accounting reports or performing month-end closing).
Operating with DBMS.	Optimized operations with temporary tables in Microsoft SQL Server, as well as operations with objects that use temporary tables: accumulation registers, accounting registers, sequences, and so on.	Insufficient performance in case of heavy usage of temporary tables.	Improved performance in case of heavy usage of temporary tables in Microsoft SQL Server.
Web client.	Faster start of the web client on slow connections.	A large amount of service information was obtained during the start of the web client.	Faster start of the web client on slow connections.
Operating with DBMS.	Improved performance of operations with Microsoft SQL Server DBMS in the following cases: reading and writing data; loading infobase from the *.dt file (if the recovery mode is set to Simple or Bulk-logged); infobase restructuring (if the recovery mode is set to Simple or Bulk-logged).	Inefficient usage of DBMS capabilities.	Improved performance of operations with infobases that use Microsoft SQL Server DBMS.
Accounting registers.	Improved performance of accounting register operations in the following cases: writing record sets with up to ten records and with several hundred records; obtaining totals for a given time; generating reports that use the accounting register. The performance increase takes effect after infobase restructuring.	Insufficient performance of accounting register operations in certain use cases.	Improved performance of operations with accounting registers containing a large amount of data.
Operating with DBMS.	The performance of operations with PostgreSQL is improved by changing the index structure. The optimization applies both to new infobases and to existing ones (after restructuring their databases).	Cluster indexes were not used in PostgreSQL operations; regular indexes were created instead.	Faster execution of PostgreSQL operations.
Operating with DBMS.	You can use separate table spaces for indexes (the v81c_index space) and for data (the v81c_data space) in PostgreSQL. Table spaces are not created automatically; a database administrator creates them. If no additional table spaces are created, the default table space (pg_default) is used.	Using a single table space might decrease the performance (due to storage medium overload or performance limitations).	Balancing system performance by recording table spaces to multiple storage media in PostgreSQL.
Web client.	Faster opening of the following forms in the web client: Forms located on the main window tabs Forms that block windows of their owner forms	Delays when opening forms in the web client.	Faster form opening, which improves user experience.
Working with queries.	Improved performance retrieving a selection by group (with a large number of records) from a result of a query containing a TOTALS clause.	Insufficient performance when retrieving a selection by group from a result of a query that contains totals.	Improved performance when processing results of queries that contain totals.
Server cluster.	Improved server performance and scalability when processing reference data types.	Insufficient server performance when processing reference data types.	Improved server performance when processing reference data types.
Operating with DBMS.	Temporary tables containing data of unrestricted length are temporary in IBM DB2 version 8.7 and later.	For data of unrestricted length, permanent tables were created and then deleted after use.	System tables cannot get locked. Improved user experience in case when a large number of users are working simultaneously.
Operating with DBMS.	Certain operations with IBM DB2 are optimized.	Insufficient usage of IBM DB2 capabilities.	Faster execution of IBM DB2 operations.
Operating with DBMS. Accounting registers.	Faster processing of accounting register data during database configuration update in the client/server infobase mode.	Insufficient performance when reconfiguring accounting registers.	Faster processing of accounting register data during their reconfiguration.
Information registers.	Totals are implemented for periodic information registers. They are intended for retrieving first and last slices, provided that the following conditions are met: using totals is allowed (in metadata); using totals is enabled (in 1C:Enterprise mode); slice retrieval conditions do not include date; slice retrieval conditions only include dimensions and separators; data access restrictions for the register only include dimensions and separators. Properties EnableTotalsSliceFirst and EnableTotalsSliceLast are implemented for information registers. Methods RecalcTotals(), SetTotalsUsing(), and GetTotalsUsing() are implemented for information register managers. Access right TotalsControl is implemented for information registers. The Verify and Repair action in Designer includes recalculation of first and last slices if the Recalculating totals option is enabled in the Verifications and modes list and using totals is enabled for the register.	Each slice retrieval resulted in execution of a query to the main register table, with calculation of resource values.	Faster retrieval of first and last slices for the first and the last (current) moments of time.
Developing tools.	Optimized memory usage in the following cases: operations with configurations that are on support loading and dumping the 1cv8.dt file This change is not implemented in 8.2.16 compatibility mode.	In some cases working with configurations that are supported by vendor configurations of large size was impossible.	Reduced RAM usage when working with vendor configurations of large size.

Table of contents

Changes altering the system behavior

Functionality	After	Before	Result of change
Operating with DBMS.	If a database query contains more than 400 levels of expression nesting, an exception occurs but the system is not shut down. This change is not implemented in 8.2.16 compatibility mode.	If a database query contained more than 400 levels of expression nesting, the system performed emergency shutdown.	The system stability increased, preventing shutdowns when executing complex queries.
Attribute fill check. Functional options	Attributes disabled by a functional option are not included in the list of checked attributes of the FillCheckProcessingAtServer() handler. This change is not implemented in 8.2.16 compatibility mode.	When generating the list of checked attributes, functional options were not considered.	Application developers do not need to programmatically exclude attributes disabled by functional options from the check.
Working with queries.	If there is a list of totals with a grand total in the query result, unloading the query result using the Unload method (QueryResultIteration.ByGroups) of the QueryResult object results in a tree with a single node with the grand total, while nodes for groupings located in the query after the grand total become the tree elements. This change is not implemented in 8.2.16 compatibility mode.	If there was a list of totals with a grand total in the query result, unloading of the query result using the Unload method (QueryResultIteration.ByGroups) of the QueryResult object created a tree with several nodes of the same level: the grand total and groupings located in the query after the grand total.	The query behavior provides more comfortable work with totals when unloading the result to a tree.
Data composition system.	When a data composition result is exported to a collection of values, columns containing calculated fields will have value types specified in the calculated fields. If the calculated field value type is not specified, the value type for the corresponding column is determined automatically based on the calculated field expression. This change is not implemented in 8.2.16 compatibility mode.	When a data composition result was exported to a collection of values, the value types for columns that contained calculated fields were always determined automatically based on the calculated field expressions.	You can specify the calculated field type explicitly in cases when automatic type definition is difficult or impossible.
Client/server interaction.	When the server version is changed, sessions running at the time when the server manager is started are not deleted automatically. When a client application that uses a web server is shut down due to the client/server version difference exception, an attempt to delete the session at the server is made.	When the server version was changed, the message Session is missing or deleted was generated. Furthermore, users did not receive messages that clearly described the problem	When the platform version is changed at the server, users receive messages stating that the client application version and the server version differ (instead of the messages stating that the session is missing or deleted).
Configuration repository.	Working with configuration repository is only possible if the repository version matches the Designer mode version.	The check whether the repository version matches Designer version was not performed.	Prevention of compatibility problems when the configuration repository server and Designer have different versions.
Configuration repository.	When Designer operates in batch mode, if the location of the infobase that is bound to the repository is changed, the infobase is rebound to the repository and no warnings are displayed. When the location check is performed for the infobase bound to the repository, the name of computer from which the connection to the infobase in established is ignored for client/server infobases and for file infobases located on network drives.	In batch mode, a warning about the infobase location change was displayed and user response was expected. When the location check was performed for the infobase bound to the repository, the name of computer from which the connection to the infobase was established was taken into account for client/server infobases and file infobases located on network drives.	In batch mode, an attempt to access a copy of an infobase bound to the repository from the repository user account that is used for accessing the original infobase will lead to disconnecting the original infobase from the repository. A warning about the infobase location change is not displayed for client/server infobases and for file infobases located on network drives if the connections differ only by the name of computer from which the connection is established.
Operating with DBMS.	The following clustered indexes are created when using IBM DB2 DBMS: for object tables - primary key (reference); for tables of totals between accounts - by period; for information registers - Dimensions, Dimensions+Period, Recorder+Number, Dimensions+Period+Recorder+Number, and Dimensions+Period (depending on register type).	When using IBM DB2 DBMS the following indexes were created: for object tables - index by the primary key was not clustered; for tables of totals between accounts - no clustered index; for information registers - clustered indexes were used only in the following cases: Recorder, Dimensions, Dimensions+Period (depending on register type).	Unified approach to the implementation of object indexes in various DBMS.
Export to Microsoft Excel.	When a spreadsheet document is exported to Microsoft Excel 97 or Microsoft Excel 2007 format, cells of the spreadsheet document that are left-aligned are exported together with their general formatting. This change is not implemented in 8.2.16 compatibility mode.	When a spreadsheet document was exported to Microsoft Excel 97 or Microsoft Excel 2007, cell values were converted to numbers in the following cases: a number is recognized in the string content, and there is no text data after the number; a number is recognized in the string content, and text data is following it, but the cell is right- or center-aligned.	If a cell of a spreadsheet document contains a numeric value, which is intended to be used as text, and the value is left-aligned (e.g., the cell contains a product code or article), when the spreadsheet document is exported to Microsoft Excel format, the cell value is not converted to a number. This simplifies the use of the converted document (including editing and comparison).
1C:Enterprise script. Managed form.	For methods GetForm(), OpenForm(), and OpenFormModal() the URL parameter is implemented. Its value is assigned to the URL property of received or opened forms, unless the parameter value is Undefined. Furthermore, the AutoURL property of received or opened forms is set to False. For the CommandExecuteParameters object the URL property is implemented. The property usage example is added to the command module example.	This feature was not provided.	You can specify a navigation link for a form that is being opened. The navigation link can be used later in the interactive mode (e.g., stored in the history).
List of infobase users.	When you press Shift+Del in the list of infobase users, a warning is displayed.	Pressing Shift+Del in the list of infobase users deleted a user without a warning.	Prevention of accidental deletion of infobase users.
Software licensing.	If an application license is not found during the start of the application, the differences between the current hardware settings and hardware settings at the moment when the license was obtained are written to the license search log. This information is only written for software licenses.	Information on differences in hardware settings was not listed in the license search log.	Simplified diagnostics of software license problems when the license is not issued due to hardware settings differences.
Operating with DBMS. Managed locks.	When working with Microsoft SQL Server version 2005 or later, if the configuration uses the managed locks mode, row versioning is used. The READ_COMMITED_SNAPSHOT transaction isolation level is used. Consistent read is used for reading data outside of transactions.	Microsoft SQL Server 2005 and later was running in the lock mode. The READ_COMMITED transaction isolation level was used. "Dirty" read was used for reading outside of transactions.	The implemented modifications lead to: reducing the number of locks and deadlocks while executing transaction queries; elimination of errors when executing out-of-transaction queries involving frequently modified applied objects; obtaining consistent out-of-transaction report results at report execution time.
Managed form. Data composition system.	You can implement quick choice user settings as a set of form fields in a separate group. You can manage location and other parameters of this group. The User settings group property is implemented for managed form extension for reports. You can create user settings items using the CreateUserSettingsFormElements() method of managed form extension for reports. Before settings elements are created, all existing elements are deleted from the group. Forms that are created automatically (report and user settings forms) include dedicated groups with elements used for editing settings. The OnUpdateUserSettingSetAtServer event is implemented for managed report form extension. The event is called in the following cases: when the report form is created; after the report variant is loaded; after the report variant is changed; after user modification of settings. Presentation of automatically generated report forms is changed: report variant presentation moved to report title; the variant selection button moved to report command bar, etc. This change is not implemented in 8.2.16 compatibility mode.	Quick choice user settings were edited in a special table located in the form. The form for editing user settings contained a table for editing all user settings. There was a field with current report presentation and a button for selecting report variant in the report form.	Improved report settings usability - they are displayed similarly to other form elements because standard form elements (text box, check box, etc.) are used instead of tables for editing settings.
Event log.	When event log is being read, events are not filtered by current separator value if the separator is conditionally disabled in the current session.	When event log was being read, records were filtered by value of a conditionally disabled separator.	Eliminated the differences between event log functioning in infobases without separators and infobases with conditionally disabled separators.
Operating with DBMS.	Internal implementation of several query executions for PostgreSQL, IBM DB2, and Oracle Database is modified. This change is not implemented in 8.2.16 compatibility mode.	The implementation took advantage of DBMS specifics to a lesser extent.	Improved the internal implementation of query executions for specific DBMS.
Command interface.	Navigation links to lists are implemented. A navigation link request to a form whose main attribute is a dynamic list with the main table specified returns a navigation link to the list of the object specified as the main table. This link opens the default list form. Support of navigation links to lists is implemented for the GotoURLGotoURL() global context method. This change is not implemented in 8.2.16 compatibility mode.	Navigation links to lists were not provided.	Users can store links to lists in history and favorites.
Configuration comparison report.	The configuration comparison report no longer includes added and removed objects whose access rights exactly match their default access rights.	Added and removed objects whose access rights exactly matched their default access rights were included in the report.	The report no longer displays redundant information that does not help in merging data.
Used components.	Migrated from OpenSSL 1.0.1 to OpenSSL 1.0.0g.	OpenSSL version 1.0.1 was used.	An HTTP server query error is no longer displayed when the thin client is started.
Applied objects.	Value length for Description length and Order length properties of Chart of accounts objects is limited by 628 characters. The current value length is only checked when an attempt to change it is made.	Value length for Description length and Order length properties of Chart of accounts objects was not limited.	Increased platform stability. Prevention of infobase corruption (in the file mode). Prevention of performance losses.
Working with queries.	If a script generated by the query wizard includes result processing, the name of the variable where the result is stored is QueryResult. This change is not implemented in 8.2.16 compatibility mode.	In certain cases (for example, when a query was created with the option to display the processed result in a report), a naming conflict occurred between variable names created by the wizard and attribute names of the report form whose module contained this code. As a result, the generated code did not work properly.	Eliminated naming conflicts between variable names created by the query wizard and report form attribute names (for queries that include result processing).
Data composition system.	A query field used in a union operation becomes unavailable to filters if it has the NULL value in all parts of the union. This change is not implemented in 8.2.16 compatibility mode.	If a query field used in a union operation had the NULL value in all parts of the union, filters were applied at the data set level of data composition template, not inside the query.	When the UNION or UNION ALL expression is used in a query that retrieves a data set of the data composition system (with automatic filling of available settings), if a filter is applied to a field attribute, the filter is only applied to the parts of the union where the given attribute exists. When a filter is applied to a field, it is only applied to the parts where the field expression is not equal to NULL.
Event log.	The .elf extension is removed from the Files of type list in the open file dialog box in the thick client and Designer. Opening event logs in the .elf format is still supported. To open an .elf file, select the Event log (*.lgf) file type and then enter the file name, including the elf extension.	The list of file extensions in the open file dialog box in the thick client and Designer included both .lgf and .elf extensions.	Removed obsolete user interface options.
Event log. Display of information.	Events related to canceled transactions are displayed in gray in the ordinary form of the event log (in the same way as they are displayed in the managed form of the event log). This change is not implemented in 8.1 compatibility mode.	Events related to canceled transactions were displayed in black in the ordinary form of the event log.	Unification of display of ordinary and managed forms of the event log.
Standard functions. Display of information.	Object presentation in standard functions Find references to object and Delete marked objects is modified. Names of metadata objects types are removed from object presentations.	In standard functions Find references to object and Delete marked objects object presentation contained the name of metadata object type.	System-standard object presentation is introduced.
Accumulation registers. Accounting registers. Common attributes / Data separation. Server cluster.	Changes in the table of storage settings for accumulation and accounting register totals are performed within a transaction. While tables are being modified, managed data locks are applied to the corresponding lock namespace. A cache for storing totals storage settings for working processes is implemented.	Changes in the tables of storage settings for accumulation and accounting register totals were performed outside a transaction. Each retrieval of totals storage settings was performed using a database query.	Elimination of conflicts that might occur during the modification of totals storage settings tables from multiple simultaneous sessions that have identical data separator values. Reducing the number of database queries and improving parallel processing for sessions that use separators.
Common attributes / Data separation. Accounting registers. Accumulation registers.	If separators are deleted or separator types are modified, during the next update of database configuration records in the tables of totals storage settings for accounting and accumulation registers are merged according to the new sets of separators.	If separators were deleted or separator types were modified, the following situations might occur: Inserting records with identical values in a table of totals storage settings. Database update errors due to attempts to insert records with identical values.	Improved reliability of operations during database configuration updates caused by deleting separators or modifying separator types.
Working with text.	Implemented recording a byte order mark (BOM) to the beginning of files generated by the TextWriter object if the following conditions are met: the file to be recorded does not yet exist, the FinishWriter constructor parameter is set to True, and the text encoding is set to UTF-8. This change is not implemented in the compatibility with 8.2.16 mode.	A byte order mark (BOM) was not added to the beginning of files generated by the TextWriter object if the following conditions were met: the file to be recorded does not yet exist, the FinishWriter constructor parameter is set to True, and the text encoding is set to UTF-8.	A byte order mark (BOM) ensures unique identification of text encoding used in a file.
Working with XML, XDTO.	During the import of XSD schema, if definition is missing from the target namespace schema, a diagnostic message is displayed.	During the import of XSD schema, if any loading problems occurred, a diagnostic message was not displayed.	Improved diagnostics during XSD schema import.
Operating with DMBS.	The documentation describes the specifics of working with the following DBMS: Oracle Database and PostgreSQL.	The documentation did not contain enough details about the specifics of working with the following DBMS: Oracle Database and PostgreSQL.	Documentation is expanded to clarify DBMS usage specifics during configuration development.
Spreadsheet document.	While you are changing the selection area in a spreadsheet document, if the selection area contains rows with different formatting, the platform switches to the row selection mode. Then, if the platform previously was in cell selection mode and after another selection change all selected rows have the same formatting, the platform switches back to the cell selection mode.	The only ways to select rows with different formatting were using headers of spreadsheet document rows or the Alt+Shift+Arrows key combination.	Simplified copying of data from spreadsheet documents with different row formatting.
Web client. Spreadsheet document.	Users can edit spreadsheet documents in the web client. The Table main menu is modified in the web client. Clipboard is implemented for spreadsheet documents in Google Chrome web browser. The clipboard is available within a single browser instance working with a single infobase.	This feature was not provided (except editing cells with values, changing the display mode of groupings, freezing rows and columns, and changing column width).	Users can edit spreadsheet documents after they are generated in the web client.
Client application. Web client. Designer. Spreadsheet document.	In the Table menu of thin client, web client, thick client, and Designer, the Cells submenu is implemented. It includes some of the commands that were previously located in the Table menu, and some new commands.	The Cells submenu was not available in the Table menu of thin client, web client, thick client, and Designer.	Improved usability of spreadsheet documents. Menu items intended for working with spreadsheet document cells are grouped into a single submenu.
Dynamic update.	Improved reliability of dynamic update in various situations.	In certain situations dynamic update worked improperly.	Improved reliability of dynamic update operations.
Managed form.	If a width limit is set for a regular group in a managed form, the size of buttons within the group is adjusted (similar to adjusting the size of other elements included in the group).	A width limit set for a regular group might not affect the size of buttons within the group.	Unified the algorithm of adjusting element sizes when a width limit is set for a regular group.
Display of information. Managed form.	Tooltips of managed form items can have one of the following types: displayed directly in the text box, displayed near the form item, and opened clicking a button (in a pop-up window). If a tooltip is not specified for a form item, the command bar button linked to this item also does not have a tooltip. You can use the InputHint property, which contains tooltip text, to display a tooltip directly in the text box. This type of tooltip is unavailable for text boxes that display data of Number and Date types. To manage the display of tooltips and their appearance, the ExtendedTooltip and TooltipDisplay properties are implemented for the following form controls: field, table, group, button, and decoration of Text type.	Tooltips were only available in pop-up windows of form items. If a tooltip was not specified for a form item, its title was used as a tooltip for the command bar button linked to this item.	You can manage tooltip formatting and tooltip positions.

Table of contents

Changes that require changes to the configuration and administrative settings

Functionality	After	Before	Result of change
1C:Enterprise software system.	1C:Enterprise version is changed to 8.3. Installation directories are changed: For Windows: C:\Program Files\1cv8; For Linux: /opt/1С/v8.3. Names of installation files are changed: For Windows: 1CEnterprise 8.msi; For Linux: 1С_Enterprise83. Names of COM objects are changed: V83.Application, V83.ComConnector. The server service name is : For Windows: 1C:Enterprise 8.3 Server Agent; For Linux: srv1cv83. The default name of the user on whose behalf the server service starts is usr1cv8. Default template directory is changed: %APPDATA%\1C\1Cv8\tmplts. Add-in installation directory is changed: %APPDATA%\1C\1Cv8\ExCompT.	1C:Enterprise version was 8.2. Installation directories had the following names: For Windows: C:\Program Files\1cv82; For Linux: /opt/1С/v8.2. Installation files had the following names: For Windows: 1CEnterprise 8.2.msi; For Linux: 1С_Enterprise82. COM objects had the following names: : V82.Application, V82.ComConnector. The server service had the following name: For Windows: 1C:Enterprise 8.2 Server Agent; For Linux: srv1cv82. The default name of the user on whose behalf the server service started was usr1cv82. Default template directory was %APPDATA%\1C\1Cv82\tmplts. Add-ins installation directory was %APPDATA%\1C\1Cv82\ExCompT.	Due to the version number change, names and identifiers that include the version number are changed.
Applied objects.	In a document journal the attribute containing the document number is generated with fixed length if all documents included in the journal have a number field of String type of fixed length. Otherwise, the journal field will have variable length. This change is not implemented in 8.2.16 compatibility mode.	In a document journal the attribute containing the number of documents was always generated with fixed length.	The document number is retrieved in a uniform way, which does not depend on the retrieval method (from the document itself or from the document journal).
Spreadsheet document.	When any of the spreadsheet document methods Show(), Print(), Hide(), and Write() is called at server or in an external connection with the SpreadsheetDocumentFileType parameter set to XLS95, an exception occurs. This change is not implemented in 8.2.16 compatibility mode.	When the method was called at server or in an external connection, this did not lead to an error, but the method did not perform any actions either.	Simplified detection of configuration errors related to specifying incorrect file type when working with a spreadsheet document at server or in an external connection.
Working with queries.	Specifying type qualifiers in the Type() function of the query language is not allowed. This change is not implemented in 8.2.16 compatibility mode.	Specifying type qualifiers for the Type() function was allowed, but it did not affect the returned values.	Implemented a check that eliminates the chance to misuse the query language syntax.
Spreadsheet document.	Print scaling of a spreadsheet document does not affect its margin size. This change is not implemented in 8.2.16 compatibility mode.	Print scaling of a spreadsheet document affected its margin size.	Independent management of margin size and print scaling.
Data composition system.	When data composition result is put into a collection of values, fields belonging to different groups and referencing to the same data composition field are put in the same collection column. This change is not implemented in 8.2.16 compatibility mode.	When data composition result was put into a collection of values, fields belonging to different groups and referencing to the same data composition field were put in different collection columns.	Output of the result to a collection is performed in the same way as output of the result to a spreadsheet document.
Command interface. 1C:Enterprise script.	Format of navigation links to navigation points generated by standard command is modified to the following: e1cib/navigationpoint/Purchases/Catalog.Products.OpenList (example link). The former navigation link format is also supported. This change is not implemented in 8.2.16 compatibility mode.	Navigation links to navigation points generated by standard commands had the following format: e1cib/navigationpoint/Purchases/Catalog.Products.Command.OpenList (example link).	Unified usage of metadata names.
Operating with DBMS. External data sources.	If the Name in the data source property of an external data source field contains a value enclosed in single straight quotation marks, when a DBMS query is generated, this value is not enclosed in double straight quotation marks. Otherwise, if the field value contains special characters, it is enclosed in double straight quotation marks. This change is not implemented in 8.2.16 compatibility mode.	If the Name in the data source property of an external data source field contained special characters (including single straight quotation marks), the value was enclosed in double straight quotation marks.	Compatibility with DMBS that use different field description syntaxes in their query and database fields (for example, MySQL).
Software licensing.	The search for available licenses covers all folders where they might be located.	The search for available licenses only covered *.lic files stored in the first folder of the list and skipped any other folders where the license files might be located, regardless of whether the license was found in the first folder.	Increased flexibility of the licensing mechanism. Elimination of problems that occured when the license files were located in multiple folders (for example, the first folder that was searched contained a server license, while another folder contained a multiuser license).
Managed form.	In managed forms, the platform does not read data from hidden dynamic lists. When a form is opened, the value of the CurrentRow attribute of the managed form table connected to the dynamic list is Undefined. The CurrentRow attribute value is changed at the moment when the table is displayed to the user. This change is not implemented in 8.2.16 compatibility mode.	In managed forms, the platform read data from all dynamic lists, whether they were displayed on the form or not.	Reduced time for opening forms that contain multiple pages with dynamic lists.
Functional options. Managed form.	Behavior of the following form elements related to functional options is modified: Form attributes of reference type are disabled if configuration objects that determine their type are disabled by functional options. Form attributes of complex type are disabled if functional options disable all types that form the complex type. Form attributes of <Type>Object type (e.g., the main attribute of the form) are disabled if configuration objects that determine their type are disabled by functional options. Form tables are disabled if they display data belonging to attributes disabled by functional options. Types are not included in type selection dialogs (e.g., in text boxes connected with attributes of complex types) if configuration objects that determine these types are disabled by a functional option. Information on types disabled by functional options is cached at the client and is cleared in 20 minutes or when the RefreshInterface() method is called. This change is not implemented in 8.2.16 compatibility mode.	Attributes and form elements had the following behavior: Form attributes of reference type were not disabled when configuration objects that determined their type were disabled by functional options. Form attributes of <Type>Object type were not disabled if configuration objects that determined their type were disabled by functional options. Form tables were not disabled if they displayed data belonging to attributes disabled by functional options. Type selection dialogs contained all types, including those disabled by functional options.	Increased effect of default functional option values on the data composition system. Unification of functional option effect on various application elements.
Functional options. Data composition system.	Functional option effect on the data composition system is modified: A data composition system field becomes unavailable if it is connected to attributes whose types are disabled by functional options. A query table and attributes of this table become unavailable if a functional option disables the configuration object forming this table. This change is not implemented in 8.2.16 compatibility mode.	The data composition system did not disable fields or query tables connected to data whose type was disabled by functional options.	Increased automatic effect of functional options on the data composition system. Unification of functional option effect on various application elements.
Functional options. Command interface.	Commands of the command interface become unavailable in the following cases: An attribute, which is a command parameter, is disabled by a functional option. A command parameter type is disabled by a functional option. If the command parameter has complex type, the command becomes unavailable if all of the parameter types are disabled. This change is not implemented in 8.2.16 compatibility mode.	The command availability was not changed if the availability of the attribute, which was used as a parameter for the command, was changed, or when the command parameter type was disabled by a functional option.	Increased effect of functional options on the data composition system. Unification of functional option effect on various application elements.
Data composition system. Spreadsheet document.	You can fix rows and columns of a spreadsheet document using the FixedLeft and FixedTop output parameters. If the fixed area exceeds the displayed area, the fixing is automatically turned off.	The data composition system always used fixing of rows and columns in reports. In spreadsheet documents the fixed area might be larger than the displayed area.	Improved usability of row and column fixing in reports. Users can disable fixing in reports when they find it inconvenient. Fixing is disabled automatically when it does not allow scrolling of the spreadsheet document.
Managed form.	It is recommended that you use methods SetObjectAndFormConformity() and GetObjectAndFormConformity(). Methods SetObjectAndFormAttributeConformity() and GetObjectAndFormAttributeConformity() are declared deprecated, they are only supported for compatibility purposes.	Methods SetObjectAndFormAttributeConformity() and GetObjectAndFormAttributeConformity() were not declared deprecated.	New methods with enhanced functionality are implemented, while the old ones that provide similar functionality are declared deprecated.
Lock manager.	When using the Range object constructor, an exception is thrown if the left range boundary is greater than the right one. This change is not implemented in 8.2.16 compatibility mode.	Using the Range object constructor was allowed when the left boundary of the range was greater than the right one.	Elimination of unpredictable behavior of the managed locks manager. Elimination of developer errors.
Managed locks.	When a managed lock is set in the file mode of the infobase, types are validated for the values located in the DataSource attribute of the DataLockItem object. This change is not implemented in 8.2.16 compatibility mode.	Validation of the value types was not performed in the file mode.	Unified behavior in the file and client/server modes. Easier detections of errors in the applied solution.
1C:Enterprise script.	An attempt to assign a value to an item of a fixed structure causes an exception. This change is not implemented in 8.2.16 compatibility mode.	An attempt to assign a value to an item of a fixed structure did not cause an exception, and the value was not assigned.	Behavior of fixed structures is similar to behavior of other fixed collections.
Web client. System requirements.	Mozilla Firefox versions 3.0 and 3.5 are no longer supported.	Mozilla Firefox versions 3.0 and 3.5 were supported.	Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported.
Web client. System requirements.	Microsoft Internet Explorer version 6.0 is no longer supported. The warning that was displayed when the web client was started in Microsoft Internet Explorer 6.0 is changed to the warning about unsupported web browser.	Microsoft Internet Explorer version 6.0 was supported.	Increased web client stability, as web browsers with issues, non-standard behavior, and low popularity are no longer supported.
Spreadsheet document.	Whenever a spreadsheet document is transferred between the client and the server, the values of its ReadOnly and Protection properties are preserved. This change is not implemented in 8.2.16 compatibility mode.	Whenever a spreadsheet document was transferred between the client and the server, the values of its ReadOnly and Protection properties were set to False.	Whenever a spreadsheet document is transferred between the client and the server, its properties are preserved in a uniform way.
Formatted document.	Formatted document object model is extended. The document text consists of paragraphs of various types, which are included in the paragraph collection. A paragraph consists of items included in the formatted document item collection. Functionalities for paragraph and item management are implemented. Methods GetItems() and GenerateItems() return the array of formatted document items located between the specified bookmarks. Method FindText() returns the formatted document area (FormattedDocumentRange object) that contains the specified text. The ItemType parameter type in methods Add() and Insert() of the FormattedDocument object was changed. Methods Add() and Insert() of the FormattedDocument object return the added/inserted item. You can add a picture by specifying its URL (in text format). It is recommended that you do not add or insert pictures using binary data, this options is present for compatibility purposes only. It is recommended that you use the Picture object for inserting pictures.	Formatted document text was not represented as an object model.	You can implement various text processing algorithms that are based on standard formatting elements (paragraphs, lists, and so on). Automated text generation is now simpler.
Data access restriction.	If the Update right of an object includes data access restrictions with conditions that apply to tabular section attributes, writing the object after it was modified is only allowed if tabular section data before and after the modification match the data access restrictions. Requests from data access restrictions to tabular sections increase the processing time. This change is not implemented in 8.2.16 compatibility mode.	If the Update right of an object included data access restrictions with conditions that applied to tabular section attributes, then whenever tabular section attributes were modified, their compliance with the data access restrictions was not be verified.	Data access restrictions apply to object data and object tabular section data in a uniform way.
Operating with DBMS.	For complex Oracle Database queries of certain type, DBMS request generation rules are modified. Cases that led to DBMS errors are eliminated. A slowdown in DBMS request execution can occur if there are many join operations. It is recommended that you do not use queries with a large number of join operations. This change is not implemented in 8.2.16 compatibility mode.	When executing complex Oracle Database queries of certain type, DBMS errors might occur in some cases.	Improved stability when using Oracle Database.
Internet-enabled functionality.	You can use secure versions of SMTP and POP3. The following properties are implemented for the InternetMailProfile object: SMTPUseSSL, POP3UseSSL, IMAPSecureAuthenticationOnly, SMTPSecureAuthenticationOnly, and POP3SecureAuthenticationOnly. POP3 supports the GetMessageCount() method of the InternetMail object. It is recommended that you do not use SMTPAuthentication and POP3Authentication properties of theInternetMailProfile object, as well as SMTPAuthenticationMode and POP3AuthenticationMode enumerations. SMTPAuthentication and POP3Authentication properties, as well as SMTPAuthenticationMode and POP3AuthenticationMode enumerations are supported for compatibility. It is recommended that you use SMTPSecureAuthenticationOnly and POP3SecureAuthenticationOnly properties of the InternetMailProfile object.	The InternetMail object did not supportsecure versions of SMTP and POP3.	You can use secure versions of SMTP and POP3.
Working with Internet.	Default values are changed for InternetMailProfile object properties that store port numbers: The default SMTPPort value is 0, which means port 25 for nonsecure connections and port 465 for secure connections. The default POP3Port value is 0, which means port 110 for nonsecure connections and port 995 for secure connections. The default IMAPPort value is 0, which means port 143 for nonsecure connections and port 993 for secure connections. This change is not implemented in 8.2.16 compatibility mode.	The InternetMailProfile object properties that store port numbers had the following default values: SMTPPort - 25. POP3Port - 110. IMAPPort - 143.	Simplified port setup for the InternetMailProfile object. In most cases the default port values suffice.
Managed form.	Changed the behavior of the drop-down list in form fields that contain reference data types, enumerations, or system enumerations. Changed the look and behavior of the drop-down list. The system storage settings now store the history of previously selected values (the ChoiceHistory setting). If user-generated lists, using a value of the FormattedString type as a value presentation is allowed. This change is not implemented in 8.2.16 compatibility mode.	The drop-down list had a different look and behavior. The choice list did not appear in the drop-down list.	Better usability of fields, which display data of reference types, enumerations, or system enumerations.
Working with Linux OS.	The configuration utility for Linux is named config_system.	The configuration utility for Linux was named config_server.	The new utility name provides a better description of its purpose because it performs the environment check not only at the server side, but also at the client application side.
Administration.	The location.cfg configuration file stores the list of directories where 1C:Enterprise searches for system data. During the installation of version 8.3, the search for data (user profiles, configuration files, software license files, etc.) belonging to version 8.2 is performed in directories available to the current user. If directories with data belonging to version 8.2 are found, then location.cfg files are generated in the directories intended for storing data in version 8.3. These files contain links to directories with data from version 8.2. Therefore, installing the new version does not require transferring all data and settings from version 8.2 directories to version 8.3 directories.	This feature was not provided.	After installing version 8.3, you can use a single list of settings for version 8.2.16 and version 8.3.
Software licensing.	If the software license is activated "for all users" or using 1C:Enterprise server, the following directory is used for storing software licenses: on Windows: %ALLUSERSPROFILE%\Application Data\1C\licenses (%ALLUSERSPROFILE%\1C\licenses - for Windows Vista and later); on Linux: /var/1C/licenses. The directory is created during 1C:Enterprise installation. Rights for accessing the created directory are granted depending on the operating system being used: On Windows, read and write rights are granted to the user under whose account the server service runs. If the service is not installed, the rights for accessing the directory are not changed. On Linux, the user group grp1cv8 is created. All users under whose names the server daemon runs must be included into this group. The following rights are set for the created directory: owner - root, rights - read and write; owner group - grp1cv8, rights - read and write; other users are granted the read only right. Only users with administrative rights can obtain a client license "for all users".	The following directory was used for storing the software license files: on Windows: %ALLUSERSPROFILE%\Application Data\1C\1Cv82\Conf (%ALLUSERSPROFILE%\1C\1Cv82\Conf for Windows Vista and later); on Linux: ~/.1cv82/conf. On Windows, the directory was used when the software license was activated "for all users", and on Linux - when the software license was activated using 1C:Enterprise server.	Administration of software license files is made easier. 1C:Enteprise versions 8.2.16 and 8.3 can use the same set of licenses when their software licenses are activated "for all users" or using 1C:Enterprise server.
Server cluster. Administration tools.	The server cluster administration scheme is modified. The management of cluster processes and function distribution between these processes are performed automatically, and therefore the option to manage them manually is removed. You can affect the automatic distribution process by creating service cluster assignment rules or working server connection rules. The server cluster is functional until at least one working server marked as central server is running. The server cluster availability is defined by the Fault tolerance level parameter (the maximum number of working servers that can become unavailable without service interruption). In the cluster console, the server cluster is displayed by its name (the Cluster name property), not by its port. The software tools for administering server cluster version 8.3 are not compatible with the software tools for administering server cluster version 8.2. The SessionFaultToleranceLevel property is implemented for the IClusterInfo object. For the IWorkingServerInfo object the following properties are implemented: MainServer, ClusterMainPort, DedicatedManagers, InfoBasesPerWorkingProcessLimit, ConnectionsPerWorkingProcessLimit, and WorkingProcessMemoryLimit. The IAssignmentRule object is implemented, it allows to manage the functionality of working servers. The list of required functionality assignments is available via the IServerAgentConnection object and the cluster console. For the IServerAgentConnection object the following methods are implemented: RegAssignmentRule(), UnregAssignmentRule(), GetAssignmentRules(), CreateAssignmentRule(), and ApplyAssignmentRules(). The properties of IWorkingProcessInfo, IClusterManagerInfo, and IClusterServiceInfo objects are read-only. For the IServerAgentConnection object the following methods are removed: CreateWorkingProcessInfo(), RegWorkingProcess(), UnregWorkingProcess(), StartWorkingProcess(), StopWorkingProcess(), SetWorkingProcessUsage(), SetClusterMultiProcess(), SetWorkingProcessCapacity(), SetClusterDescription(), CreateClusterManagerInfo(), RegClusterManager(), UnregClusterManager(), RegClusterService(), UnregClusterService(), CreateStandbyClusterItem(), RegStandbyCluster(), UnregStandbyCluster(), and GetStandbyClusterList(). The IStandbyClusterItem object is deleted. The SyncPort property is deleted for the following objects: IWorkingProcessInfo, IClusterManagerInfo, IWorkingServerInfo, and IClusterInfo.	Management of cluster processes and function distribution between these processes could only be performed manually. The server cluster was displayed in the cluster console as a port number. The fault tolerance level could not be set.	Working processes are managed automatically, so that the load distribution in the server cluster is improved. At the same time, an administrator can specify working servers where certain cluster services or connections will be executed (using rules). For example, they can move the license management service to a separate working server with minimal configuration changes, or execute certain background jobs at the working server that is running Windows operating system.
Server cluster.	On Linux operating system, a server is not automatically started after it is installed.	On Linux operating system, servers were automatically started after they were installed.	A server is not started in the environment that is not fully configured. To configure the environment, you have to run the config_system utility first, and then you can start the server.

Table of contents

Renamed objects

Object	The old name	The new name
Column groups in the user settings table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1.	<Table name>ColumnGroupSettings; <Table name>ColumnGroupValues.
Column groups in the data parameters table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1; <Table name>ColumnGroup2; <Table name>ColumnGroup3.	<Table name>ColumnGroupParameterAndPeriodValue; <Table name>ColumnGroupParameter; <Table name>ColumnGroupPeriodValue; <Table name>ColumnGroupParameterValue.
A column group in the available fields table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupAvailableField.
Column groups in the group fields table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1; <Table name>ColumnGroup2; <Table name>ColumnGroup3; <Table name>ColumnGroup4; <Table name>ColumnGroup5.	<Table name>ColumnGroupGroupField; <Table name>ColumnGroupFieldAndType; <Table name>ColumnGroupPeriod; <Table name>ColumnGroupField; <Table name>ColumnGroupBeginOfPeriod; <Table name>ColumnGroupEndOfPeriod.
Column groups in the selected fields table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1; <Table name>ColumnGroup3; <Table name>ColumnGroup2.	<Table name>ColumnGroupSelectedField; <Table name>ColumnGroupHeaderAndPlacement; <Table name>ColumnGroupHeader; <Table name>ColumnGroupField.
Column groups in the filter table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup2; <Table name>ColumnGroup3; <Table name>ColumnGroup4; <Table name>ColumnGroup1.	<Table name>ColumnGroupFilter; <Table name>ColumnGroupMainFilterItems; <Table name>ColumnGroupLeftValue; <Table name>ColumnGroupRightValue; <Table name>ColumnGroupApplication.
A column group in the order table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupField.
Column groups in the output parameters table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1; <Table name>ColumnGroup2; <Table name>ColumnGroup3.	<Table name>ColumnGroupParameterAndPeriodValue; <Table name>ColumnGroupParameter; <Table name>ColumnGroupParameterValue; <Table name>ColumnGroupParameter.
A column group in the user field case variants table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupValue.
A column group in the appearance fields table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupField.
A column group in the gauge chart quality bands table of the data composition system is renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup.	<Table name>ColumnGroupBackColor.
Column groups in the filter conditions table of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	<Table name>ColumnGroup; <Table name>ColumnGroup1.	<Table name>ColumnGroupValueAndPeriod; <Table name>ColumnGroupPeriod.
Column groups in the report variant form elements of the data composition system are renamed. This change is not implemented in version 8.2.16 compatibility mode.	GoToReportSelectedFields1; GoToReportFilter1; GoToReportOrder1; GoToReportConditionalAppearance1; GoToReportOutputParameters1.	GoToReportSelectedFieldsFromInaccessibleSelectedFields; GoToReportFilterFromInaccessibleFilter; GoToReportOrderFromInaccessibleOrder; GoToReportConditionalAppearanceFromInaccessibleConditionalAppearance; GoToReportOutputParametersFromInaccessibleOutputParameters.
Russian presentation for the ReportSettings command of the report form is changed.	Настройка ....	Настройки ....
English and Russian presentations for the LoadReportSettings command of the report form are changed.	Select setting .... Выбрать настройку ...	Select settings .... Выбрать настройки ...
English and Russian presentations for the SaveReportSettings command of the report form are changed.	Save setting ... Сохранить настройку ...	Save settings ... Сохранить настройки ...
Presentation of the StandardSettings command in the report variant form is modified.	Standard setting.	Standard settings.
Field containing name of saved settings in the Save settings dialog is changed.	Name of saved setting.	Name of saved settings.

Table of contents

Upgrade from the previous version to version 8.3.1

Conversion of configurations, infobases, external data processors, and external reports is not required during the upgrade from the previous version to version 8.3.1.
To use certain features of version 8.3.1 you have to disable the compatibility mode. The structure of certain objects is modified when disabling or enabling the compatibility mode. Note that to be able to work with infobases created using previous 1C:Enterprise versions you have to enable the compatibility mode. 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 object restructuring.
It is recommended that you revise the list of infobases. Infobases that are present in the list when version 8.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, 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.1 on the computer hat 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.1 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.1.
To perforrm 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.

Table of contents