Version 8.2.9

See more

Version 8.2.9

Version 8.2.9 is the final version of the 1C:Enterprise 8.2 platform.

What's New in Version 8.2 Compared to Version 8.1

    Managed Application

    • Managed application feature implemented: new model of functionality distribution between client and server, new forms mechanism, new command interface mechanism, functional options mechanism, new user settings saving mechanism, thin client, web client.

    What's New?

      Server and Database

      • Oracle Database management system support.
      • Default parameters for IBM DB2 database creation modified. The new values used for the parameters will reduce the number of readings from disk and will improve database operations performance.
      • User session concept introduced. Session is used for unified identification of the active infobase user, regardless of the client application type. The notion of connection no longer describes the active infobase user.
      • Resilience for software and hardware failures of 1C:Enterprise servers cluster.
      • Implemented the possibility to identify reserved working processes along with enabled and disabled working processes.
      • Ability to restart server working process upon reaching a designated virtual address space size.
      • Dynamic load balancing for cluster working processes.
      • Ability to define additional cluster manager(s) within a cluster and to distribute server services operation between such managers.
      • Session data service can run on multiple cluster managers.
      • When exclusive access to file-based infobase is attempted, connection pool is cleared for the web server connected to this infobase.
      • PID (running operating system process identifier) acquisition in cluster console and in access object model.
      • <mem> element added to configuration file of the technological log file. If <mem> element is available, 1C:Enterprise server processes calculate allocated and taken memory units and total volume of allocated and taken memory units.
      • Memory leaks tracking <leaks> element of the technological log file) for the following objects: AccountingRegisterManager, ChartOfAccountsManager, ExchangePlanManager, SettingsStorageManager, AccumulationRegisterManager, ChartOfCharacteristicTypesManager, DocumentManager, EnumManager, InformationRegisterManager, DataProcessorManager, CatalogsManager, ReportManager, BusinessProcessManager, TaskManager, ChartOfCalculationTypesManager, CalculationRegisterManager, ManagedForm, FixedStructure, FixedMap, FormDataStructure, FormDataCollection, FormDataStructureAndCollection, FormDataCollectionItem, FormDataTree, FormDataTreeItemCollection, FormDataTreeItem.
      • Implemented new method to display context in technological log if managed application is operating.
      • Linux operating system based 1C:Enterprise server requires additional libraries to be installed in the following cases:
        • for managed application running;
        • when Chart, GraphicalSchema, SpreadsheetDocument objects are used on the server;
        • when GetPicture() method is used in the Chart, GanttChart, Dendrogram, PivotChart objects;
        • when exporting a spreadsheet document to XLS on the server side.
      • 1C:Enterprise server startup/stop script for Linux operating system enhanced. Startup parameters setup added, server stop procedure improved, current server status output commands added.
      • VALUETYPE feature added to query language.
      • Type literals can be defined in query language.

      Table of contents

      Miscellaneous Objects

      • Application object manager modules.
      • Access rights definition for metadata objects attributes.
      • Application functionality can now operate with the time corresponding to the specified time zone that does not depend on server location. New global context methods SetInfoBaseTimeZone(), GetInfoBaseTimeZone(), SetSessionTimeZone(), SessionTimeZone(), CurrentUniversalDate(), ToLocalTime(), ToUniversalTime(), TimeZone(), GetAvailableTimeZones(), TimeZonePresentation(), DaylightTimeOffset(), StandardTimeOffset().
      • Aggregate mechanism intended to increase speed of operations with large data volumes of turnover accumulation registers in order to get analytical reports in various cross sections.
      • For language objects (managers, objects) with GetForm() method assigned, call parameters analysis has been introduced, and GetForm() function of the global context can be requested if required.
      • Empty record key for an information register notion introduced. Record key for an information register designer has been developed. IsEmpty() method for record key of an information register. EmptyKey() method for information register manager.
      • New register records writing method for documents posting. When documents are posted, sets of records to be recorded are clearly stated. For the RegisterRecordsDeletion property of a document’s metadata a new AutoDeleteOnUnpost variant is introduced. This is the default variant. The Write property has been added for records of the registers. RegisterRecordsWritingOnPost property for document metadata introduced. When this property is assigned the WriteSelected value (default value), it allows recording of only the sets that have the Write property assigned. This method is intended to use optimized recording of changed records sets without deleting movements when posting is initiated. The Write() method is implemented for the RegisterRecords document collection. LockForUpdate property implemented for the records set of the accumulation register and the accounting register.
      • The Size() method implemented for BinaryData object.
      • Acceptable code (number) length property for metadata objects that possess numbers or codes. The property is only available when the code (number) is of string type. This property will have the Fixed value assigned during conversion from previous versions. When a new object is created, it will have the Variable value.
      • Attributes fill check that provides for a regular description in the configuration of how to check correctness of the user-entered data. The fill check is not performed in 8.1 version compatibility mode.
      • Standard objects filling mechanics enhanced. New properties implemented for objects attributes in metadata that influence the standard filling procedure: Filling Value – this value will be assigned to an attribute by the standard filling processing procedure, Fill from filling value determines if filling from the transferred filling data is possible. It is now possible to request filling in the forms when new objects are created and to transfer filter values to filter values fill handler if filling is called from a list. StandardProcessing parameter implemented for the objects in the filling event handling procedure. Filling event handler implemented for records set of an information register. Fill() method for records set of an information register and record manager of an information register.
      • PrivilegedPostingMode and PrivilegedUnpostingMode properties implemented for Document metadata object. TaskCreatingPrivilegedMode property implemented for BusinessProcess metadata object.
      • During various system checks when objects are created (for catalogs during parent check, code owner and uniqueness, for documents, business processes, and tasks during number uniqueness check, for exchange plans disabled during code uniqueness check, for exchange plans and charts of characteristic types during parent and code uniqueness check), data is accessed in privileged mode which makes it possible not to disable access rights restrictions at the records level for respective fields if configuration will only operate this data in managed mode or in the server-executed code.
      • StoredPasswordValue property implemented for the InfoBaseUser object that is intended to get and set hash value of the password.
      • DataVersion property implemented for catalogs, documents, charts of characteristic types, charts of accounts, business processes, and tasks. This property is not available in the 8.1 version compatibility mode. In the 8.1 version compatibility mode the access rights to DataVersion field are checked based on the access rights for the Reference field.
      • A designer to create a reference based on a unique identifier is implemented for the objects of the following types: CatalogRef, DocumentRef, ChartOfCharacteristicTypesRef, ChartOfAccountsRef, ChartOfCalculationTypesRef, ExchangePlanRef, BusinessProcessRef, TaskRef.
      • Data analysis mechanism can now operate both on the server and in an external connection.
      • HTMLDocumentShell object can now be used on the server.
      • GeographicalSchema object can now be used on the server, in an external connection and in the web-client.
      • GraphicalSchema object can now be used on the server and in an external connection.
      • Implemented the possibility to obtain graphical schema using the GetCommonTemplate() method of global context and GetTemplate() method of the metadata object at server and in the external connection.
      • Spreadsheet document pagination management on the server side, including on the Linux-based server.
      • XDTO serialization for FixedArray object.
      • XDTO serialization for TextDocument object.
      • XDTO serialization for SpreadsheetDocument object.
      • Search for graphical schema item name in the Find() method of the GraphicalSchemaItems object.
      • Delayed updating of session parameter value, for example, when data or user settings are changed. This is provided for by the Clear() method of the SessionParameters object.
      • CurrentStartPosition parameter for the NextPart() and PreviousPart() methods of the FullTextSearchList object.
      • Download of the log file to a values table and a parameter intended to limit the number of downloaded log records in the UnloadEventLog() method.
      • A new GetEventLogFilterValues() method that provides available filter values that can be used in log file downloading.
      • GetModificationUniversalTime() and SetModificationUniversalTime() methods for the File object.
      • Search Subfolders parameter has been implemented for the FindFiles() global context methods and FTPConnection object.
      • FixedArray object can be used to transfer the virtual accounting registers parameters Balances, Turnovers, BalancedAndTurnovers, DrCrTurnovers, and the accounting register manager methods Balances, Turnovers, BalancesAndTurnovers, DrCrTurnovers that can be assigned extra dimension types as parameters.

      Table of contents

      1C:Enterprise Script

      • AvailableValues property for the ValueList object that makes it possible to only use a certain set of values as the available values for the list items.
      • List items can now be identified with numerical identifiers.
      • Implemented parameter for standard attribute name designation and standard attribute name designation of standard tabular section for AccessRight() method.
      • CurrentLocaleCode() global context method intended to retrieve localization code for the current session. /VL command line parameter can be used to enable this parameter. GetAvailableLocaleCodes() method has been added to the global context. LocaleCodePresentation() method has been added to the global context.
      • Software enabling and disabling of privileged mode. SetPrivilegedMode() and PrivilegedMode() methods have been added to the global context.
      • Safe mode for code execution that can be software enabled and disabled. EnableSafeMode() and SafeMode() methods have been added to the global context.
      • PredefinedValue() global context method added in order to retrieve a reference to a predefined value.
      • SetBinaryData() method for FastInfosetReader and FastInfosetWriter objects.
      • When subscribing to COM-object events as well as events of the ExternalObject object that have the same name while the number of their parameters varies, the number of handler parameters is taken into account and a handler with the respective number of parameters is selected for the event.
      • LockDataForEdit() and UnlockDataForEdit() methods have been added to the global context.
      • ServerCall property implemented for common modules. The property is available only for modules with Server flag.
      • New external components technology makes it possible to develop such components using both C++ API and COM technology. The components developed using the new technology can be uploaded both in client applications and on the 1C:Enterprise server. At the same time the previous external components are fully supported.

      Table of contents

      Reports and Data Composition System

      • MarkIncomplete parameter for the following objects: DataCompositionAreaTemplateTableCellAppearance, DataCompositionAppearanceTemplateAppearance, DataCompositionAppearance.
      • It is now possible to use the fields nested data sets in the data composition system (in the data set query text – an object in the {SELECT} and {WHERE} sentences, in the data composition schema wizard, in the data composition system query wizard, in the data composition template, in the data composition settings).
      • New comparison types In List, Not in List, In List Group, Not In List Group added to data composition system settings to be used for fields with a predefined list of available values and for the custom combo fields. Ability to fill the list of values for a parameter that has a list of available values.
      • It is now possible to set filters for the Type fields in the data composition system.
      • SetParameterValue() method that sets a value for data composition parameter and enables the Use property.
      • Ability to get data set fields appearances from query fields synonyms in the data composition system. If no synonym has been specified for the field, field data path is used instead.
      • OnComposeResult() event handler added to the ReportObject object.
      • ChoiceFoldersAndItems property for data composition system parameter editing parameters.
      • Optional RefreshMethod parameter for the Refresh() method in the DataCompositionSettingsComposer object. This optional parameter is intended to manage restoration of settings serviceability.
      • FixedSettings property and LoadFixedSettings() method have been added to the DataCompositionSettingsComposer object.
      • ValueListAllowed and ValueType properties have been added for the DataCompositionAvailableParameter object.
      • ValueType property has been added to the DataCompositionAvailableField and DataCompositionFilterAvailableField objects.
      • In the data composition system settings dialog a special icon in the settings structure will demonstrate that grouping is disabled (deleted by user). When editing the set of custom settings is finished, the developer will be notified in the event that the grouping has been created by user and is at the same time disabled.
      • If a user selects Filter by a certain field for the report details and a filter element using this field already exists without a specified appearance and located outside of the conditions group, no new filter element will be created in the new settings and the existing one will be used instead.

      Table of contents

      Designing

      • It is now possible to enable 1C:Enterprise 8.1 compatibility mode in the configuration properties. The compatibility mode is automatically enabled upon conversion of a configuration created in 1C:Enterprise versions 8.1 or 8.0. Features that depend on compatibility mode are listed in the Changes that Require Configuration Changes or Influence System Behavior.
      • When Client/server mode infobase configuration update requires database restructuring, it is now possible to attempt to force disconnection of all sessions and to update the database configuration repeatedly.
      • In all the dialogs the Windows Authentication texts are replaced with Operating System Authentication while mentions of the Windows Users are replaced with Operating System Users.
      • The context menu of the configuration tree root received new commands intended to open various configuration editors.
      • New Query Wizard with Result Processing that generates a code to build and execute a query as well as a result iteration and building a spreadsheet document or a chart.
      • New Session Locale Code parameter included in Designer mode settings dialog (1C:Enterprise Startup tab).
      • Style Elements branch is moved from the Styles branch to the Common branch root. The Value property is added to style elements.
      • Boolean type values are now displayed in the debugger as True/False depending on the values of the 1C:Enterprise Script Variant property.
      • The sequence order and type grouping changed in the type selection dialog.
      • The order of default forms in metadata editing dialogs and new forms dialogs has been changed.
      • The 1C:Enterprise startup parameters page has been divided into two panes – Main and Additional. Module Texts tab renamed to Modules.
      • Metadata object name is now displayed in the properties palette title for metadata objects.
      • The Syntax Assistant now helps better distinguish between different kinds of information based on the availability and use modes. Implemented the possibility to filter display information by availability of objects, methods, properties.
      • When a new metadata object is created that has no dedicated editing window, both the properties palette and the More window are opened (provided that the More window is applicable for this object).
      • The set of properties displayed in the Important Only mode has been changed.
      • The size of type selection list for the Type properties of the metadata objects attributes has been increased to 20 lines.
      • When a metadata object is assigned to subsystems, it is now possible to include the object into this or that subsystem regardless of mutual subordination of the subsystems. An object can now be assigned simultaneously both to a parent subsystem and to its subordinate subsystem.
      • The View right has been added for Subsystem configuration object. If a user does not have rights to view the subsystem, then the help information on configuration objects is also unavailable for viewing.
      • It is now possible to lock an individual subsystem in a repository and to customize the distribution rules for subsystems in the configuration distribution settings dialog.
      • Various changes in the metadata editing dialogs, including the changes that reflect the new set of properties of metadata objects.
      • When help is edited in Designer mode, it is now possible to use references to system help topics. When help is edited in Designer mode, when the reference to system help topic is selected:
        • For Managed application configuration edit mode only topics concerned to managed application are displayed and the Web client column is displayed only;
        • For Managed application and ordinary application configuration edit mode all topics are displayed and Managed application, Ordinary application and Web client columns are displayed.
      • The set of text templates has been changed. Templates have been modified and expanded with changes and new features of the platform.
      • When file infobase is being published on a web-server and anonymous authentication is used, the anonymous user access rights are checked for the database directory. If there are not enough rights, then warning about impossibility of working with this infobase is displayed. It is recommended to grant according rights or select the Use operating system authenticaton on web server check box.

      Table of contents

      Other

      • List of supported Linux distribution kits is modified.
      • Unified start program implemented for versions 8.0, 8.1, and 8.2.
      • Implemented setup program for thin client for operating in Client/server mode.
      • Group policies and logon-scripts can now be used to install 1C:Enterprise.
      • It is now possible to designate the used 1C:Enterprise version for every infobase from a list of infobases.
      • Web services publishing mechanism changed. The new features can also be accessed using the webinst command line utility (available for Windows and Linux operating systems). Publication name should contain latin symbols only. Also, for Apache web-server, name of publication catalog should contain latin symbols only. Publishing using .1cws files is not supported any more. The wsinst utility removed from the delivery kit.
      • It is now possible to create pictures for charts and schemas in BMP or PNG formats for Linux server.
      • Alpha-channel PNG pictures are now supported in form elements. System pictures used in 1C:Enterprise mode have been converted to PNG format.
      • Submenu Internet Information added to the Help menu.
      • No default database server type is selected when a Client/server mode infobase is created.
      • OpenHelp() method behavior has been changed. The parameter can now hold a reference to a help topic.
      • The PlatformType property for SystemInfo object.
      • Internal XML handling implementation has been changed.
      • New HTMLDocument type has been added.
      • A spreadsheet document can be saved as HTML and Excel97 both on the 1C:Enterprise server and in an external connection.
      • The Format() and Convert() methods of the Picture object can be used on the server and in external connection mode.
      • It is now possible to execute CheckPut(), CheckAttachment(), and PageCount() methods for a spreadsheet document both on the server and in an external connection.
      • New PageSize, PageWidth, PageHeight properties have been introduced for a spreadsheet document.
      • It is now possible to get the messages displayed to a user on the server, in an external connection, from Web services, and from background jobs. GetUserMessages() global context method will retrieve the messages that have not been displayed to a user yet. The GetUserMessages() method implemented for COM-connection object. GetUserMessages() method for the BackgroundJob object will make it possible to retrieve the messages generated during the background job from outside of the background job.
      • StandardPeriodEditDialog 1C:Enterprise script object that makes it possible to edit the standard period interactively.
      • New pictures added to the pictures library: ReportSettings, Form, SettingsStorage, ActiveUsers, EventLog, UserEventLog, ShowData, Properties, NewWindow, CancelSearch, GetNavigationLink, GoToNavigationLink, AddToFavorites, DataCompositionNewNestedSchema.
      • Automatic scrolling mode using the middle mouse button added to a text document, spreadsheet document, graphical schema, table field.
      • When user actions are logged (initiated by /logui command line parameter), new marks are added to show the beginning, the end, and the duration of an action.
      • New Encoding parameter added to the OpenFile() method of the XMLReader object. The input file encoding should be clearly designated if the file is 4-byte encoded (UTF-32) or uses the IBM-encoding family, i.e. for all title-enabled encodings.
      • When full-text search results are displayed as HTML, the occurred words are now highlighted in different colors.
      • Month value has been added to the StandardPeriodVariant system enumeration.
      • Ctrl + W will now select the current word in the text editor and in an entry field.
      • The selected line is now located in the center instead of on top of drop-down lists.
      • ColumnSizeChangeMode property added for a spreadsheet document cell that makes it possible to change a column size using the mouse by pointing it to the right column border. A similar property has been implemented for a data composition template area cell.
      • The infobase adding and editing dialog now has the settings that designate the infobase user authentication use mode.
      • Reuse mode introduced for retrieved values of the shared modules functions. This mode is intended to optimize multiple data acquisitions within a session or a server request.
      • In the event log implemented events of logon attempts and failed logon attempts. These events are displayed only for users with administrative rights.

      Table of contents

      1C:Enterprise Mode

      • Client licenses can now be obtained using a server or a web server add-on module. In this case a separate license is required for every session.
      • The key for the last successful connection can be stored. The next search for a license will begin from this key, which accelerates the client application launch.
      • Modified the procedure for searching the license for of the 64-bit Com connection operating. Client licenses can be used along with server licenses.
      • In 1C:Enterprise mode the About 1C:Enterprise dialog now has a Configuration text field that can display the configuration information, the URL to access configuration provider information and configuration copyright information.
      • In the dialog opened by Save as command it is now possible to choose a file type for saving. The selected file type will be used in the future for the file when the Save command is used to save it.

      Optimization

      • Optimized database operation. In the 8.1 version compatibility mode and when working with IBM DB2 database management system 9.5 or older, the previous implementation of database operations is used that is similar to version 8.1.
      • Configuration first run has been optimized.
      • File-based database operations are optimized for grouping-enabled queries execution and for execution of queries that get a large number of entries. Memory and query execution speed optimized. Execution of queries that contain Turnovers virtual tables of the accumulation and accounting registers has been optimized as well.
      • Internal platform functions related to memory and resources usage have been optimized.
      • Temporary files handling has been optimized.
      • Internal platform functions related to session data have been optimized. The volume of traffic between a client and a server during the client/server operation has been reduced.
      • In order to improve scalability and performance of 1C:Enterprise server, the configuration metadata are fully loaded by the server when connecting to the infobase.
      • For catalogs that lack a code and a name, the Owner+Reference and the Owner+Parent+[Group]+Reference indices can be created.
      • Optimized reading and writing of XML- and XDTO-files.
      • Dumping and restoring of an infobase have been optimized. Infobase dump file size reduced.
      • Processor usage reduced for entering and editing text in an entry field.
      • Data composition processor operating speed, when generating reports containing large amount of data, has been increased.
      • Optimized database configuration update when configuration includes an exchange plan with distributed infobase.

      Table of contents

      Upgrading to Version 8.2 from Versions 8.1 and 8.0

      • It is possible to upgrade to version 8.2.9 from versions 8.1.5 and older as well as version 8.0.18.
      • The 1C:Enterprise 8.2.9 platform version can be installed on a computer without uninstalling the previous platform versions already installed.
      • Attention!

        Infobase, configuration, external data processors, and external reports formats have been changed. In order to work with a new 1C:Enterprise version, it is required to convert the infobase (configuration, external data processors, and external reports). Once conversion of a particular infobase (configuration, external data processor, and external report) begins, this infobase will not be available for operation with the previous versions of the 1C:Enterprise 8 versions.

      • Please, create a backup copy of an infobase (configuration, external data processor, external report) prior to conversion!
      • If any software or hardware failures occur in the conversion process, the data contained in the infobase may be lost.
      • Infobase conversion can only be performed by a user possessing administrative rights.
      • Please, follow the procedure below to convert an infobase:

      Table of contents

      Infobase That Is Not Connected to Configuration Repository

      • Attention!

        The infobase file format has been changed. It should be converted for future use.

      • Please, create a backup copy of an infobase prior to conversion.
      • If any software or hardware failures occur in the conversion process, the data contained in the infobase may be lost. After conversion, an infobase can not be used with previous versions of the 1C:Enterprise 8 platform versions.

      File-Based Infobase

      • Create an infobase backup copy.
      • Launch Designer mode of the previous 1C:Enterprise 8 platform version.
      • If the configuration being edited does not match the database configuration, update the latter.

        Attention!

        If the database configuration is not updated, forced rollback to database configuration will be executed. In order to prevent possible conversion errors, it is recommended to perform infobase verification and repair.

      • Quit Designer mode of the previous 1C:Enterprise 8 version.
      • Launch the 1C:Enterprise 8.2 platform version Designer.
      • If an infobase is not available in the list of infobases, add an existing infobase.
      • Open the infobase in Designer mode.
      • Agree when prompted to convert the infobase. The program will continue running after displaying a successful conversion message.

      Client/Server Mode Infobase

      • Create an infobase backup copy.
      • Launch Designer mode of the previous 1C:Enterprise 8 platform version.
      • If the configuration being edited does not match the database configuration, update the latter.

        Attention!

        If the database configuration is not updated, forced rollback to database configuration will be executed. In order to prevent possible conversion errors, it is recommended to perform infobase verification and repair.

      • Quit Designer mode of the previous 1C:Enterprise 8 version.
      • Launch the 1C:Enterprise 8.2 version Designer.
      • If an infobase is not available in the list of infobases, add a new infobase. In the infobase adding dialog, perform the actions to create a new empty Client/server mode infobase. Specify all the database parameters in compliance with the parameters of the infobase being converted. Clear the Create database if none present checkbox before creating an infobase.
      • Agree when prompted to convert the infobase. The program will continue running after displaying a successful conversion message.

      Infobase Connected to Configuration Repository

      • Attention!

        Configuration repository format has been changed.

      • Please, create a backup copy of a configuration repository prior to conversion.
      • If any software or hardware failures occur in the conversion process, the data contained in the infobase may be lost. After conversion, an infobase can not be used with previous versions of the 1C:Enterprise 8 platform versions.

        • Create an infobase backup copy.
        • Perform the following actions using the previous 1C:Enterprise 8 platform version for all the infobases connected to the repository:
        • Move all the locked objects to the configuration repository and release them.
        • Obtain the last status from the configuration repository.
        • Save the configuration and update the database configuration.
        • Create a backup copy of the repository (1cv8ddb.1CD file in the repository directory). It is recommended to delete cache directory from the repository directory.
        • Lock all the objects in the repository in the infobase connected to the repository using login credentials of a user possessing administrative rights.
        • In this 1C:Enterprise 8.2 version convert all the infobases as described in the Infobase That Is Not Connected to Configuration Repository section for file-based or Client/server mode infobases. When connecting to the configuration repository, agree to convert the configuration repository. The program will continue running following the successful conversion.
        • Move all the locked configuration objects to the repository.
      • Attention!

        At that all the Subsystem metadata objects will be added to the repository.

      • Attention!

        When obtaining configurations of the previous versions from the repository (those created prior to upgrade to version 8.2.9), such configurations will be converted. When repository objects are attempted to be updated, the resulting objects are not converted.

      Configuration Dumped to a File

      • Launch the 1C:Enterprise 8.2 version Designer.
      • Open the configuration file (File – Open, select the *.cf file type and browse to the file you need).
      • Agree when prompted to convert.

      Infobase Dumped to a File

      • Infobase dump files (.dt), created using 1C:Enterprise 8.1, can be loaded by 1C:Enterprise 8.2.
      • To load the infobase from a file:
        • Launch the 1C:Enterprise 8.2 version Designer.
        • Load the dump file (click Administration - Restore infobase, select reguired dump file).
        • Answer Yes to all Designer's questions before restart.
        • After Designer is restarted answer Yes to answer the question about necessity of conversion.

      External Data Processor or External Report

      • Launch the 1C:Enterprise 8.2 version Designer.
      • Open an external data processor (external report).
      • Agree when prompted to convert.
      • You can perform batch conversion of 1C:Enterprise version 8.x files, using the /ConvertFiles command line option.

      Changes that Require Configuration Changes or Influence System Behavior

      • Application interface appearance has been changed. New display of controls, new colors and pictures used. The interface remains unchanged in the 8.1 version compatibility mode.
      • Modified display of several form elements. Table field header area increased. Left and right indents in table field cells increased. Size of panel tab size increased and space between tabs also increased. Interface is not changed in the 8.1 version compatibility mode.
      • Windows 98, Windows Me operating systems are no longer supported.
      • 1C:Enterprise installation wizard has been changed.
      • It is now possible to install and work with multiple 1C:Enterprise versions.
      • Administrative installation eliminated, the admupd.cfg file is not installed to the platform installation folder, the /AU command line option is not supported.
      • The list of infobases is contained in ibases.v8i file located at %APPDATA%\1C\1CEstart.
      • By default, configuration files are located in the C:\Program Files\1Cv82\conf folder. The folder intended to store server cluster settings has been renamed from server to srvinfo. The servers cluster settings files (when a server is installed as a service) are located in the C:\Program Files\1Cv82\srvinfo folder.
      • New location of the templates folder. It is now possible to designate multiple templates folders. The v8cscadr.lst file is no longer used.
      • Modified names of Linux distribution packages: 1C_Enterprise-*.rpm files renamed to 1C_Enterprise82-*.rpm, 1c-enterprise-*.deb files renamed to 1c-enterprise82-*.deb.
      • To operate with servers of previous versions you need to register utility of appropriate version using RegMSC.cmd file (by default the utility of the newest version is registered). The shortcut for the server cluster administration utility has been renamed to 1C Enterprise servers.
      • Maximum size for unlimited length data decreased to 1Gb in IBM DB2 database management system and data logging introduced. When an infobase is converted from the previous versions or when an infobase is loaded from file, maximum length of unlimited length data is reduced. Infobase file conversion or loading will be aborted if such an infobase contains the unlimited length data with its actual size larger than 1Gb.
      • In 1C:Enterprise server debugging mode (launched using /debug parameter) configuration objects are loaded when required, unlike regular server operation mode, when all configuration objects are loaded. Thus configuration startup is accelerated.
      • In attributes, which are not stored in the infobase, it is allowed to use all available types, excepting Characteristic.<Chart of characteristic types name>, to create composite type of attribute.
      • New approach to operations with text templates files. A separate templates file is used for every 1C:Enterprise script variant. It is not recommended to store custom templates files in the 1C:Enterprise installation folder. Standard templates can not be modified.
      • Totals split attribute is now enabled by default for new accumulation and accounting registers. When database configuration is updated, totals split attribute is enabled for such registers as well. When a new infobase is created in a configuration that has totals split enabled for the registers, this attribute will also be enabled for the respective registers in this new infobase. The behavior remains unchanged in the 8.1 version compatibility mode.
      • Subsystem metadata object storage manner changed in the configuration. After conversion from the previous versions for the infobases connected to the repository, the subsystems will be displayed as new objects. It is required to lock the metadata root object and locate the subsystems to the repository.
      • Picture editor now supports alpha-channel. When editing of pictures created in the previous versions is finished, such pictures will be converted to PNG. The behavior remains unchanged in the 8.1 version compatibility mode.
      • In picture editor Set transparent background and Remove transparency buttons are available only for BMP, JPEG and TIFF formats.
      • When spreadsheet documents are compared, the rows added in the end of a spreadsheet document and the cells added in the end of a row, are considered to be added.
      • Reference types now have a new appearance. An appearance of a reference type now only contains the metadata object appearance.
      • The accounting register fields and the Extra Dimensions type fields now have a new appearance in the tabular section of an account form.
      • It is forbidden to enter the characters that are not allowed by XML 1.0 to the entry fields and text editor. When such a character is added interactively, the entry of the character is ignored while when a text is pasted from the clipboard, the invalid characters are dismissed and will not be contained in the pasted text.
      • The behaviour of the XSLT mechanism when transforming HTML tags has been modified. The XSLT mechanism optimizes HTML according to http://www.w3.org/TR/xslt standard, described in Chapter 16.2 HTML Output Method.
      • When using tools for working with HTML it is not allowed to use the <TABLE> element as child of the <P> element. In such a way the <P><TABLE></TABLE></P> construction is transformed to the  <P></P><TABLE></TABLE> after processing. This behaviour corresponds with the HTMLstandard (http://www.w3.org/TR/html401/struct/text.html).
      • Text appearances have been changed for some commands of the data composition system.
      • Specifying the nonexistent fields of the DataCompositionDataParameters object in the data path in regular form calls the exception.
      • A changed text for the message that is displayed when an object is edited that has been changed by another user. The new message text: The data has been modified or deleted by another user.
      • A changed representations for error messages concerned with standard attributes. Messages have the following appearance: "FieldName" field value сause of error, for example, if catalog code is not unique, then the "Code" field value is not unique message is displayed.
      • Changed representation for information register record when error message is generated.
      • Error message that is displayed when an operation in event handler is cancelled, has been changed. The text that used to read Operation not performed has been replaced with Failed to post: "Sale of goods"!.
      • New format of an error message displayed in the event of database object lock error. Database object lock appearance changed in the cluster console.
      • The following item names were changed in the event log written as .XML: User (instead of UserID), Event (instead of EventName) and Metadata (instead of MetadataName).
      • New properties have been added to the technological log file events: SessionID – session number assigned to the current stream, AppID – client application identifier of the session assigned to the current stream. The value for the Usr property is now filled from the assigned session instead of from the connection.
      • Improved column width calculation in the data composition result output to a spreadsheet document.
      • When an external report or data processor is saved, the pictures selected from the pictures library are not converted to absolute pictures. This conversion is still carried out in the 8.1 version compatibility mode.
      • Modified output format of InputByString metadata object property used for configuration report. Now fields’ names are displayed in the report, not representations.
      • The values of the Number and Date types are displayed in compliance with regional settings of the current session if Use regional settings of the current session property is selected in the Infobase Regional Settings dialog.
      • Values of Boolean type is displayed in compliance with platform interface language if specific values are not set in the Infobase Regional Settings dialog.
      • Values of Boolean type are displayed by Yes/ No words instead of True/ False (corresponding with platform interface language being used). Representation is not changed in the 8.1 version compatibility mode.
      • Add-in object type and string representation are generated in accordance with what is specified in parameter of New() script operator, which is used for creating an object instance. Behaviour is not changed in the 8.1 version compatibility mode.
      • The spreadsheet document properties Output and PageOrientation can only have the values of corresponding types. When an improper value type is assigned, an exception will be generated. The behavior remains unchanged in the 8.1 version compatibility mode.
      • If a nonconventional border or border color is selected for a form element (in any client and in any form view) or if a nonconventional button background color is selected for the Button, Text box, and Track bar elements, the form element will be displayed same as it was displayed in version 8.1. In 8.1 version compatibility mode the form elements are displayed the same.
      • When Tab or Shift+Tab buttons are pressed in a form table that does not contain lines or has the Row selection mode selected, it will activate either the next form element or the previous one respectively. The behavior remains unchanged in the 8.1 version compatibility mode.
      • For commands to operate with hierarchy (in table, spreadsheet and text documents) implemented the following keyboard shortcuts: explode node ? Shift + Alt + Gray+, collapse node ? Shift + Alt + Gray-, exlode all nodes ? Ctrl + Shift + Alt + Gray+, collapse all nodes ? Ctrl + Shift + Alt + Gray-. Only these keyboard shortcuts are used in web client. In other clients previously shortcuts can be used.
      • The titles of active columns of form tables are not highlighted. The behavior remains unchanged in the 8.1 version compatibility mode.
      • GetModificationTime() and SetModificationTime() methods of the File object now feature a new behavior. The time when a file was modified is either retrieved or set taking into account the time shift rules that existed at the time of modification instead of at the time of retrieving or setting such time. The behavior remains unchanged in the 8.1 version compatibility mode.
      • A query that contains the keyword DISTINCT and a clause ORDER BY with an expression, which is absent from selection list, is treated as invalid. An error message will be displayed. The error message will not be displayed if version 8.1 compatibility mode is enabled.
      • If union data set is used in the data composition schema and some field is only available in one subsidiary data set, when filter is applied to this field, the composition result will only contain the records from this data set. The behavior remains unchanged in the 8.1 version compatibility mode.
      • If a user is not allowed to interactively view the metadata object, the composition system will treat all the object table fields as invalid. The behavior remains unchanged in the 8.1 version compatibility mode.
      • A new display of full names of modules in the technological log file, log file, etc. The previous display of full names of modules is used in the 8.1 version compatibility mode.
      • The identifier assigned to a reference of a new object created by copying, will remain the same in the object procedure OnCopy() (to be used in the future during recording). The behavior remains unchanged in the 8.1 version compatibility mode.
      • The Contains condition of the data composition system treats the _, %, and [ characters as regular characters instead of special ones. The behavior remains unchanged in the 8.1 version compatibility mode.
      • CAST query language operation will retrieve a variable-length string (without padding spaces) when it is converted to the STRING type. The behavior remains unchanged in the 8.1 version compatibility mode.
      • The Fixed Length String metadata attribute can not have a length over 100 characters. This limitation is not applicable to the 8.1 version compatibility mode.
      • In the VALUE expression of the query language when route points values are referenced, the Points term is replaced by RoutePoint. It is still possible to use the Points term for compatibility reasons.
      • The Field property of the DataCompositionAvailableField object contains the data path written using the script specified in the 1C:Enterprise Script Variant configuration property. The behavior remains unchanged in the 8.1 version compatibility mode.
      • The Parameter property of the DataCompositionAvailableParameter and the DataCompositionParameterValue objects contains the parameter written using the script specified in the 1C:Enterprise Script Variant configuration property. The behavior remains unchanged in the 8.1 version compatibility mode.
      • When data composition settings are filled by the system (in interactive editing, details processing, etc.), all the DataCompositionField properties are filled with a data path written using the script specified in the 1C:Enterprise Script Variant configuration property. The behavior remains unchanged in the 8.1 version compatibility mode.
      • In the color selection dialog web colors are sorted by shades. In the 8.1 version compatibility mode, the colors are sorted by their English-language names.
      • In form wizard and template wizard the name will not be changed when a synonym is changed same as the synonym will not be changed when the name is changed, if the synonym does not match the one created automatically. The behavior remains unchanged in the 8.1 version compatibility mode.
      • Only when the Edit right is assigned, the following rights can be assigned as well: InteractiveInsert, InteractiveDelete, InteractiveSetDeletionMark, InteractiveClearDeletionMark, InteractiveDeleteMarked, InteractivePosting, InteractivePostingRegular, InteractiveUndoPosting, InteractiveChangePosted, InteractiveStart, InteractiveActivate, InteractiveExecute. The behavior remains unchanged in the 8.1 version compatibility mode.
      • The ApplicationModule configuration property has been renamed to OrdinaryApplicationModule. The previous version preserved for the compatibility purposes. When configuration files are dumped, ordinary application module is dumped to a Configuration.OrdinaryApplicationModule.txt file while in 8.1 version compatibility mode it is dumped to a Configuration.ApplicationModule.txt file. When configuration files are loaded, both variants will be accepted.
      • The Client property has been renamed to Client (ordinary application). Those shared modules that have the Client (ordinary application) property checked, will be loaded in the thick client in the ordinary application mode.
      • The database that stores the 1C:Enterprise infobase now has a modified structure of tables. Some values have been changed in the Purpose column of the values table that is the result of the GetDBStorageStructureInfo() method.
      • In JOIN operations on request tables applied to object tables, ON section is not allowed to access tablular sections if used object tables are object of data access restrictions. In 8.1 version compatibility mode the behavior has not changed.
      • The Type property of the DataCompositionAvailableField, DataCompositionFilterAvailableField, and DataCompositionAvailableParameter objects is not recommended for use as it has only been preserved for compatibility reasons. Instead the ValueType property should be used.
      • GroupBackColor, GroupTextColor, HeaderBackColor, HeaderTextColor properties of a spreadsheet document have been removed. These properties are supported in the 8.1 version compatibility mode.
      • When an empty string is written into an XML-file using the WriteAttribute() or WriteText() methods (these methods can be requested between the WriteStartAttribute() and WriteEndAttribute()) of the WriteXML object, the output stream will contain the following expression: <AttributeName>="". The behavior remains unchanged in the 8.1 version compatibility mode: when an empty string is written as an attribute value, nothing will be written in the output stream.
      • The Client command line parameter option has been renamed to ThickClientServerOrdinaryApplication, while the ClientServer command line parameter option has been renamed to ThickClientOrdinaryApplication, and the ExternalConnectionServer – to ExternalConnection. Use of Client, ClientServer, and ExternalConnectionServer is available in 8.1 version compatibility mode.
      • If Date attribute (containing Date and Time) is edited in a field that is format string designated to display only part of the attribute (date or time), editing of one part of the attribute (date or time) will not result in modification of another part.
      • All the 1C:Enterprise 8 components are fully Unicode-applications.
      • It is now impossible to choose a character set in the font selection dialog. Unicode-fonts should be used.
      • We have switched from use of ICU 3.4 to use of ICU 4.0. ICU 4.0 is based on CLDR (Common Locale Data Repository) standard version 1.6. For more information, please visit http://www.unicode.org/cldr/. Due to updates of CLDR standard and the updated ICU version, for a number of languages and countries numbers and dates formats as well as strings sorting have been changed.
      • JIS_X0201 encoding is not supported any more.
      • Web services publishing using .1cws files is not supported. The wsinst utility removed from the delivery kit.
      • Web-service connection pool setting is performed using default.vrd file. Wsconnectionpool.xml file is not used anymore. Connection pool is enabled by default after publication.
      • New session starts and SessionParametersSettings() handler is called on each Web-service call.
      • The Type virtual field has been implemented for document journals tables. This field contains the document type.
      • If a report query uses a limitation of parameters referencing standard period dates and if some part of the date will contain an empty date, the value for this date will be treated as unassigned. If a user does not enter the end date for a custom period, it will be considered not to be designated.
      • When cells of a spreadsheet document are copied to the clipboard, the data will be stored in the clipboard in Excel97 format. This makes it possible to paste cells containing Cyrillic characters to ОpenOffice. Also a copied spreadsheet document fragment in Excel97 will preserve the columns shift for every row of a spreadsheet document.
      • When a spreadsheet document is saved in XLS format the following conversions are performed: fonts from WindowsFonts system set are substituted by Arial font, cells are merged using new algorithm (if a spreadsheet document cell is represented by several cells in Excel and along with this a spreadsheet document is limited on the left and on the right by border or color, then Excell cells are merged). In 8.1 version compatibility mode the behaviour is not changed.
      • All the system text strings generated on the 1C:Enterprise server are displayed in compliance with the interface language of the current session.
      • In 1C:Enterprise mode help can be opened from a form without selecting a topic. If no help topic has been defined for a particular form, help topic is opened for the metadata object this form belongs to while if no such topic exists, the General Information about Forms section is opened. The topic selection is preserved in 8.1 version compatibility mode.
      • For the Fill Checking property a default setting has been implemented as the Display Error value for the following standard attributes: Name of an exchange plan; Owner and Name of a catalog; Date of a document; Name of a chart of characteristics; Code, Name of a chart of accounts; ExtDimensionType of a chart of accounts for extra dimensions types; Name of a chart of calculation types; CalculationType of a chart of calculation types for leading calculation types; CalculationType of a chart of calculation types for base calculation types; CalculationType of a chart of calculation types for displacing calculation types; Period of an information register; Period of an accumulation register; Period of an accounting register; RegistrationPeriod, CalculationType, BegOfActionPeriod, EndOfActionPeriod of a calculation register; Date of a business process; Name of a job. When these objects are entered and the respective attributes have not been filled, an error will be generated. The check is not performed in the 1C:Enterprise 8.1 compatibility mode.
      • The help does not have the automatically added fields and texts at the top and in the bottom (1C Company and 1C:Enterprise, configuration and developer information).
      • In web server add-on modules operations the algorithm of designating the temporary file folder has been changed. When a query is received and a reply is sent, the default temporary files folder is the temporary files folder of the user who executes the query. When a query to a file-based infobase is processed (it is processed directly by a web server add-on module), the default temporary file folder is 1Cv8Temp subfolder of the file-based infobase folder. The <vrs:point> element of the default.vrd file has received an optional attribute temp that can be used to specify a temporary files folder for operation of web servers add-on modules.
      • The Content property has been implemented for the Subsystem object. This property contains a list of all the objects belonging to the subsystem. Upon conversion from previous versions, this property is filled based on the subsystems that the configuration objects belong to. In 8.1 version compatibility mode the Subsystem property is available via the 1C:Enterprise script for the metadata objects that could belong to subsystems. Also Content configuration property is available in the 8.1 version compatibility mode. This property is filled with the references to the objects that belonged to the root element of the subsystems tree. When 8.1 version compatibility mode is disabled, the Content configuration property will be cleared and will not be available any more in the configuration properties dialog.
      • Drop-down menu and context menu can now be scrolled using the mouse wheel if a menu can not be fully displayed. No moving up and down of the drop-down and context menus is now possible using mouse wheel.
      • The possibility to specify using several working processes in server cluster, Multiple Processes checkbox has been removed from the 1C:Enterprise server cluster console properties dialog. 1C:Enterprise server cluster supports running several working processes always. The value of the MultiProcess property in the COMConnector object of the Servers Cluster object is ignored (the property is preserved for compatibility reasons), the SetClusterMultiProcess() method of the Server Agent Connection object does not result in any actions and has also been preserved for compatibility reasons.
      • The Use property implemented for the IWorkingProcessInfo object. Property indicates the mode of using the working process (do not use/ use/ use as backup). The Enable property of this object is left for.
      • For the IServerAgentConnection object implemented the SetWorkingProcessUsage() method, using which you can set new value for the Use property of the IWorkingProcessInfo object. StartWorkingProcess() and StopWorkingProcessInfo() methods are left for compatibility.
      • For the IServerAgentConnection object implemented the SetClusterRecyclingExpirationTime() method, that sets time of forced termination of the working process. The SetClusterRecycling() method is left for compatibility.
      • Implemented global context methods SetSessionsLock() and GetSessionsLock() and also the SessionsLock object to control locking new infobase sessions. The global context methods GetConnectionsLock() and SetConnectionsLock() and the ConnectionsLock object the have been preserved for compatibility reasons. In the infobase properties, that are shown in the 1C:Enterprise server cluster console text Connection lock is set is changed to Session lock is set.
      • The SessionsDenied property implemented for the IInfoBaseInfo object. This property specifies if the creating new sessions is possible. The ConnectDenied property has been preserved for compatibility reasons.
      • The HTMLDocumentShell object now has a new set of methods.
      • Some element names have been changed in the servers cluster console. When the list of working processes is displayed, the computer name is now accompanied by a sequence number of the working process on this computer.
      • When executing the Lock() method, lock values are now checked in managed lock elements for all the fields for compliance with the lock field type. The behavior remains unchanged in the 8.1 version compatibility mode.
      • During spreadsheet document pagination on Linux-based server the size of resulting pages can differ from the size of those pages that are actually printed out. This is due to peculiarities of font information presentation by this operating system. In this case you should change the margins for the paper.
      • Date autofilling changed for year end (November-December): when dates are entered for the beginning of the year (January-February), the next year will be inserted. Date autofilling changed for the beginning of the year (January-February): when dates are entered for the end of the year (November-December), the previous year will be inserted unless the year is clearly designated.
      • The authentication dialog features a changed interface as well as displays the infobase name from the infobases list.
      • Presentation of 1CV8 application changed (in the ApplicationPresentation() method, system forms). Thick client is used instead of 1C:Enterprise.
      • Presentation of web servers applications changed (in the ApplicationPresentation method, system forms). Web prefix has replaced WEB.
      • Changes in color, font, and line selection dialogs in 1C:Enterprise mode.
      • When users list and active users list are accessed, by default the cursor is placed in the beginning of the list. Sort by user names is enabled by default for active users list as well.
      • Stricter operation implemented for DOM-XML name spaces. If name spaces are used, possible consequences of behavior changes should be analyzed.
      • Modified window mode for horizontal tile mode of Syntax assistant: command bar buttons are used instead of tabs Contents, Index and Search.
      • English-language version of the DefaultConstantsForm property name changed. DefaultConstantsForm is now used instead of DefaultConstantForm. It is still possible to use DefaultConstantForm for compatibility reasons.
      • English-language version of the DataCompositionSchema report property name changed. DataCompositionSchema is now used instead of CompositionDataSchema. It is still possible to use CompositionDataSchema for compatibility reasons.
      • For the Form object the WindowOptionsName form property has been renamed to WindowOptionsKey. The previous version has been preserved for compatibility reasons.
      • For the SpreadsheetDocument object the WindowOptionsName property has been renamed to WindowOptionsKey. The previous version has been preserved for compatibility reasons.
      • For the SpreadsheetDocument object the PrintParametersName property has been renamed to PrintParametersKey. The previous version has been preserved for compatibility reasons.
      • The print parameters saved with a name designated in the PrintParametersKey property of a spreadsheet document, will be preserved after the Page Setup dialog is opened, preview window is opened and printing is executed (both interactively and software-initiated). Print parameters are saved to an infobase. Print parameters of individual spreadsheet documents (objects) are changed independently (even if the key of print parameters is the same). The properties are filled from the print parameters saved using a key when the key was assigned. In 8.1 version compatibility mode such print parameters are not separated and are changed simultaneously.
      • The Put() and Join() methods of a spreadsheet document will result in an error if the first parameter in such methods contains a spreadsheet document area. The behavior remains unchanged in 8.1 version compatibility mode.
      • The LocaleCode() global context method has been renamed to InfobaseLocaleCode(). The previous version has been preserved for compatibility reasons.
      • For spreadsheet document, geographical schema, graphical schema, and graphical schema field objects the Print() methods will accept the values of the PrintDialogUseMode type as a parameter. Use of Boolean type parameter has been preserved for compatibility reasons.
      • The WindowsUsers() method has been renamed to OSUsers(). Use of WindowsUsers() is still possible for compatibility reasons.
      • The English-language name of the OpenFile() method for FastInfosetReader and FastInfosetWriter has been changed from Open() to OpenFile(). The previous version has been preserved for compatibility reasons.
      • The name for the Transparency property has been changed to Transparent for the following objects: GeographicalSchemaPlotArea, GeographicalSchemaLegendArea, GeographicalSchemaTitleArea. The previous version has been preserved for compatibility reasons.
      • For the InfobaseConnection object we have implemented the SessionNumber property and renamed SessionStart property to ConnectionStarted. The previous name has been preserved for compatibility reasons.
      • The following pictures are only available to be selected interactively in 8.1 version compatibility mode: DocumentObject, ChartOfCharacteristicTypesObject, ScheduledJobs, CatalogObject, BusinessProcessObject, TaskObject, ChartOfCalculationTypesObject, ExchangePlanObject, ChartOfAccountsObject, InformationRegisterRecord. The following pictures have been renamed: SelectFromList to SelectValue, AddListItem to CreateListItem, NewFolder to AddFolder, EditListItem to Edit, MarkItemToDeleteFromList to MarkForDeletion, DeleteListItemDirectly to DeleteDirectly, DeleteListItem to Delete. The pictures with new names are available to be selected interactively while the pictures with older names are only available to be selected interactively in 8.1 version compatibility mode.
      • The Data Parameters tab renamed to Parameters in the automatically generated report settings forms and data composition schema wizard.
      • The report settings command text has been changed from New nested schema to New nested report.
      • In the format string editor the texts logical and logical value have been replaced with Boolean.
      • For Client/server mode the text Infobase has been replaced with Infobase Name in the About 1C:Enterprise dialog.
      • HTML-handling features returns tags in the lowercase, independently from which case was used in source HTML-text.
      • To activate the search field in Designer mode and thick client command bar use the Ctrl+Shift+D key combination. The Ctrl+D key combination is used to call the Add to favourites command of the managed application.
      • It is not recommended to include more than one type in type of the chart of characteristics types used for storage extra dimensions of the chart of accounts, except when all types are references to database objects. This can lead to significant performance degradation.

      Table of contents

      Use of Configurations Developed in the Previous 1C:Enterprise Versions

      • Application solution (configuration) users may need to update a configuration version when they upgrade to a new 1C:Enterprise 8 platform version. We recommend that you obtain information regarding the configuration version update from the vendor (developer) of the solution.

      Using the Support Files

      • The configuration distribution files (cf) require execution of the same steps as those described in the Configuration Dumped to a File section. The update files (cfu) created in the previous 1C:Enterprise 8 versions cannot be used to update the configurations converted for the 1C:Enterprise version 8.2.