Version 8.2.15

See more

Version 8.2.15

Version 8.2.15 includes known bug fixes and some functionality modifications.

New functions and changes

  • PostgreSQL 9.0.3 DBMS is now supported.
  • The Count() method is implemented for the StandardAttributeDescriptions object.
  • The <system> event is implemented in the technological log. The event manages registration of "1C:Enterprise" system events, intended to analyze by experts of  "1C Company".
  • The default technological log is implemented. This log registers events occurring in critical situations (from "1C:Enterprise" functioning point of view). List of events written in the log is not documented. Another possibility is implemented to set location of the log and number of hours; upon the time out the information will be removed from the log by default.
  • The possibility to create subscriptions for events of manager modules is implemented.
  • The manager object is implemented for the FilterCriterion object. The FormGetProcessing event implemented in the manager module of the filter criterion.
  • The About 1C:Enterprise dialog now includes the information on how the license was obtained: by client application or server.
  • Cluster administration console displays information on license for the following objects:
    • Session (in the list and in the session properties)
    • Working process (in the list and in the working process properties).
  • The License property is implemented for the ISessionInfo object. The property contains information on client license used by the session.
  • The License property is implemented for the IWorkingProcessInfo object. The property contains information on client license used by the working process.
  • The ILicenseInfo object is implemented. The object contains parameters of the client license obtained.
  • The possibility to save spreadsheet documents to file of PDF format is implemented.
  • The PrintAccuracy property is implemented for spreadsheet documents. It manages the spreadsheet print mode in Google Chrome.
  • The IPv6 protocol is now supported.
  • The Select() method is implemented for the StandardSettingsStorageManager object.
  • Implemented the pass-through user authentication, which uses an OpenID-bases protocol version 2.0 (by Direct Identity model). The possibility to use an infobase as the OpenID-provider is implemented. This OpenID provider performs authentication in checkid_immediate mode. The dialog of application being launched is used for entering the user name and password. The openid element is implemented for the default.vrd file. The OIDA command line parameter is implemented for the thick- and web clients.
  • When merging configurations (including vendor configuration update) it is possible to set order rules for objects existing only in the loaded configurations and marked for merging (transition) to the main configuration.
  • Implemented generation of quieries to DBMS using ODBC escape sequences for external data sources with "Other" type and for the following functions and expressions of query language: SUBSTRING, YEAR, QUARTER, MONTH, DAYOFYEAR, DAY, WEEK, WEEKDAY, HOUR, MINUTE, SECOND, DATEDIFF, ISNULL, CAST, ESCAPE, JOIN, LEFT JOIN, RIGHT JOIN, FULL JOIN.
  • Implemented support of file mode infobase for OS Linux 64-bit.
  • ReturnCode parameter is implemented for RunApp() and RunSystem() global context methods. This parameter is used for obtaining return code of launched application, if it is possible.
  • Implemented the possibility in the configuration check mechanism to search for invalid links to predefined values for charts of accounts (if extra dimensions are specified for the chart of accounts) and for charts of calculation types. This check is performed if the Find unresolved references checkbox is set in the Configuration check dialog.
  • Implemented the possibility to write the excp events to the technological log if the error requesting of the HTTP-resource is returned.
  • When writing excp events of the technological log the value of descr property may contain identifiers and descriptions of all exceptions nested in each other.

Table of contents

New functions and changes in 1C:Enterprise mode

  • When the standard function Totals Management form is opened, it only displays registers for which all required separators (taking the conditional separation into account) are used in the current session (when the form is opened). Previously the form did not open at all if at least one separator was used for at least one register.
  • The list of available fields of the form (in the Change form dialog) is not cached for the session anymore, and is generated every time when the dialog is opened.

Table of contents

Optimization

  • For a managed form fields displaying a complex type attribute, performance of opening the quick choice list is improved for cases when reference types with different quick choice settings are included in content of complex type.
  • The impact of the debugging mode on the operation speed in "1C:Enterprise" mode is reduced for thick client, thin client, server and external connection.
  • Database operation is optimized for the cases when two or more separators are used or separator of String type is used.
  • Optimized writing of accumulation and accounting register records in the IBM DB2. The optimization is effective when operating with IBM DB2 9.7 FP5 (build 27892). It is recommended to update DBMS to the specified version. When using IBM DB2 of earlier versions negative impact on system performance is possible.
  • Client application launch is optimized.
  • Optimized operations using the IN (…) expression with many parameters in the list when operating with PostgreSQL.
  • Optimized opening of a form in the web client when using large number of elements in the form conditional appearance.
  • Optimized opening of report form containing large number of elements of conditional appearance in the web client.
  • Optimized opening of a managed form displaying one or several dynamic lists, containing large number of conditional appearance elements.
  • Operation with the Oracle Database is optimized for certain operations.

Table of contents

Changes affecting the system behavior

  • The message file specified by the Out command line option is opened in mode allowing shared reading. When Designer is launched in the batch mode writing to this file is performed immediately, and is not buffered.
  • When operating with SMTP-server using InternetMail object, it does not disconnect from SMTP-server when the error 501 occurs.
  • If RunModeOrdinaryApplication command line option is specified in the command line of launcher or in the additional startup options (in the infobase options), the thick client is started with indication of this command line option if the connection to the infobase is performed not through a web server. If RunModeManagedApplication command line option is specified in the command line of launcher, then the client application starts, which is selected based on the infobase settings, specified in the list of infobases. If any of these command line options (RunModeOrdinaryApplication or RunModeManagedApplication) is specified, then the mechanism of automatic selection of client application is disabled except for the case when user has explicitly specified the AppAutoCheckMode option in the command line.
  • Implemented the directory to store copies of basic versions licenses (%APPDATA%\1C\licenses). If any basic licenses located in 1C:Enterprise license directories version 8.0 or version 8.1 are found upon launching of a basic version of an application, they are copied to this directory. The search for basic version licenses is performed in the following order: the directory of licenses of version 8.2, directory of copies of previous versions of licenses, directory of licenses of version 8.1, licenses of version 8.0.
  • When an infobase is being restructured, the check of the uniqueness of the code/number (for documents, charts of characteristic types, charts of accounts, business processes and tasks) is performed only if the code/number length is greater than 0 and uniqueness check is enabled.
  • The Input by string right check in managed forms is implemented for text boxes, located in the form, in the table, and cell of a spreadsheet document (if it has Contains value property set).
  • The boundary values for the display period are directly set in the virtual table parameters if the managed form displays a dynamic list which main table is a virtual table with BeginOfPeriod and StartOfPeriod parameters.
  • In Designer: available fields in the dynamic list settings dialog are displayed as fields' names, not as their presentations.
  • If in the given infobase the first register record is written for the accumulation register or accounting register for the present set of separators, and the given register settings table is empty, then the register is locked entirely (for the current set of separators). In addition, for the turnover accumulation register the table of settings of aggregates will be locked entirely if the table of aggregate settings is empty for the given register and current set of separators.
  • If a license is not found upon client application start, then in the displayed dialog the Details button is available to view the log of the license search.
  • In the About 1C:Enterprise dialog the history of licenses which were used with the given infobase is displayed only for users with the Administration right.
  • If a client application is connected through a web server, licenses obtained for this client application are not listed in the cluster administration console and are not saved in the list of licensed used for the infobase.
  • During the license binding check only two first digits of Windows OS version number are used.
  • During the license binding check only absence of previously installed devices is taken into account, not installation of new ones. The face of increasing RAM does not lead to re-obtaining the license. Re-obtaining the license is needed if the volume of RAM has become less than when license was obtaines. Due to the changed rules of check of the list of devices:
    • If a license was obtained by version 8.2.14 or earlier, then the binding is checked for full match with the of list of devices.
    • If license is obtained by version 8.2.15 or older, then the binding is checked only by list of devices, installed at the moment the binding is done.
    • In order to check license binding obtained by version 8.2.14 or earlier only by list of devices installed at the moment the binding created, you need to update the license using the version 8.2.15.
  • In tabs operation mode, opening a form from a modal window is always performed in a separate window. In this case the Window parameter of OpenForm() and GetForm() methods is ignored.
  • Implemented support for time zones unknown to "1C:Enterprise". It is not recommended to store such time zones in the database or pass them to the third-party systems. If the TimeZone() method at server returns a time zone which is not supported by 1C:Enterprise, then it is recommended to use the time zone which is supported by.
  • When a configuration is loaded from a file, an update file etc., the exchange plan (with enabled Distributed infobase property) registers only changes in the current configuration (modified, removed and added objects), not in the full configuration.
  • When establishing an encrypted connection between a client application and a cluster, as well as between the debugger and the item being debugged, the algorithm of check whether server IP-address belongs to the current host (local computer) is modified. The IP-address belongs to the current host if the list of IP-addresses of the current host overlaps the list of addresses provided by DNS.
  • The XDTO-serialization of the Picture object is modified. Picture can be successfully restored if there is a picture with the same name in the target configuration.
  • NotifyChanged() method call leads to clearing of caches relating to the changed objects at client application side.
  • In the header and footer cells of managed form tables only those lines are displayed which completely fit the cell height.
  • Implemented the possibility to call SetString() method of HTMLReader object without specifying the Encoding method parameter.
  • The 'index by dimensions' is of cluster type for new independent and non-periodic information registers. When creating first scheduled job the 'index by job' identified is cluster also. To create necessary indices in the existing infobase one of the following actions can be performed:
    • Execute database restructuring.
    • Load infobase from a .dt file.
  • Moved from the OpenSSL version 0.9.8a to OpenSSL version 1.0.1.
  • If InputFileName parameter is specified for GetEventLogFilterValues() and UnloadEventLog() methods, they open log file in the mode which allows shared writing. This offers the opportunity to read event log of other 1C:Enterprise operating entity.
  • For locking-type DBMS (Microsoft SQL Server, IBM DB2) changing infobase users in transaction no longer conflicts with authentication process, except for the case:
    • User data were modified.
    • The transaction that the midification was done is not complete.
    • The user tries to perform authentication.
  • The latest versions of web-browsers – Mozilla Firefox, Apple Safari and Google Chrome – are supported without specifying a specific version supported. The Microsoft Internet Explorer is supported as before – with explicit indication of supported version of thebrowser.
  • Recommendations for implementation of external components, compatible with "1C:Enterprise" earlier than version 8.2 are removed from the external component creation technology description.
  • The call of RepresentDataChange() or NotifyChanged() methods, or writing an object in a form it updates presentations of references in managed form tables associated with a form attributes of FormDataCollection, FormDataTree, FormDataStructureAndCollection types and in the form fields of Label type. In addition, calling the NotifyChanged() method updates presentations of references in a form fields of Text box type. Also, at writing an object in a form it updates presentations of references in the form tables, associated with dynamic lists.
  • The dialog of type selection in the client application contains only types for which the current user has the View right.
  • Table box cell (in ordinary forms) and table cell (in managed forms) displays up to 20000 characters. This restriction affects working with text from the Script and generation of the tooltip text.
  • Implemented the possibility to print spreadsheet documents in a web client using documents in PDF format. Implemented Print method setting in the web client options dialog.
  • If data composition system parameter expression contains other parameters all of these parameters have no values specified, the following is used as a value of this calculated parameter:
    • If the parameter is selected on the Parameters tab of the Settings tab of the Data Composition Schema wizard, the value specified in the data composition settings is used.
    • If the parameter is not selected on the Parameters tab of the Settings tab of the Data Composition Schema wizard, the default value of this parameter specified in the data composition schema is used.
  • If the number of managed locks in a single space exceeds 20000 in a single transaction, the lock escalation occurs and the space is locked entirely.

    When using independent separators, lock escalation is performed for a single set of separators values:

    • The entire space is locked only within separator values.
    • The escalation does not affect sessions with other separator values.

Table of contents

Changes requiring changes to the configuration and administrative settings

  • If one of the command line parameters defining application operation mode (RunModeOrdinaryApplication or RunModeManagedApplication) is used in the client application launch, this parameter is passed through to the client application being started from a parent client application using RunSystem() and Exit() global context methods (with indication that restart is required).
  • RefreshInterface() method call does not trigger the OnOpen event handler of the managed form for opened forms.
  • The format of navigation links is modified. Quotes (") are removed from link texts, and parameter values (after = symbol) are encoded in correspondence with the chapter 2.2. URL Character Encoding Issues of RFC 1738 (using % symbol and two hexadecimal symbols) for dimension values of information registers and table keys of external data sources. If the information register dimension is of complex type and type name is specified in dimension value, then type name is also encoded. Navigation links created by version 8.2.15 do not work in previous versions.
  • In the external components technology implemented support of Mozilla Firefox browser version 6.0. External components adapters for Mozilla Firefox version 6.0 will work with newer versions of the browser without recompilation. For the manifest file of external components working in Mozilla Firefox it is recommended to specify only minimal required number of version of the browser.
  • New version of linguistic sorting is implemented for Oracle Database DBMS (lx327c6.nlt file). The new version is based on UNICODE 6.0 standard, also Russian Е and Ё letters are discerned. Instalation of the new version is not required. "1C:Enterprise" can operate either old or new version of linguistic sorting. If an infobase is loaded from .dt file then indices will be automatically created in the new sorting version (if it is installed in the system).
  • If the AutoMarkIncomplete is set to True for a text box then for a web client the MarkIncomplete property of this field is updated in correspondence with the value displayed by this field, on each modification of this value.
  • If authentication separation is used in an applied solution and the corresponding separators are not used in the current session then using FindByName() method of InfoBaseUsersManager object throws exception.
  • The type.xml configuration file used in Linux OS for calculation of the font metrics is located in conf/grcmncfg subdirectory of 1C:Enterprise binary files directory. The $HOME environment variable is no longer used when searching for this configuration file.
  • When operating with the configuration repository the "1C:Enterprise" used by the repository server should be the same as the one used in Designer mode.
  • If the document property Add register records on posting is set to Record selected value, then after document is written from the regular form the modification flag of register record sets, included into Register records collection of the written document, is cleared.

Table of contents

Transition from the previous version to the version 8.2.15

  • Conversion of configuration repository, external data processors and external reports is not required during the transition from version 8.2.14 to version 8.2.15. Specific case is described below.
  • If data separation is used in an infobase then Designer mode should be run once. At that, there should be no client connection established (including those with opening the authentication dialog), before starting to work with this infobase. When the conversion is complete, the infobase can be accessed using the version 8.2.14.
  • After installation of version 8.2.15 on Linux OS, config_server utility should be launched to create type.xml file in the conf/grcmncfg subdirectory of the binary files' directory.

Table of contents