Version 8.2.14

See more

Version 8.2.14

Version 8.2.14 includes known bug fixes and functionality modifications.

New functions and changes

  • The mechanism of common attributes implemented. It allows adding attributes to different metadata objects without modificating them.
  • The mechanism of separating data implemented. It allows storing data, splitting into separate data areas in one infobase. Operation with the data areas is independent.
  • Implemented the possibility to obtain data from external data sources. The ODBC interface is used. In order to access data from the external data sources you can uses object model, query language and data composition system. Manage external data sources standard function implemented. ExternalDataSource metadata object implemented.
  • Extended list of logical integrity issues, which can be detected and recovered by the configuration check.
  • RunApp() global context method operates at server.
  • The AllFunctionsMode access right implemented.
  • Implemented the possibility to merge managed forms, at that merge rules can be specifiedfor different form parts. Managed form comparison report implemented.
  • Context tooltip in the module editor opens after entering the <> operator.
  • Implemented the possibility to authenticate web client session using the POST-query to the e1cib/start address. Parameters transferred in the query body take precedence of query string parameters. Use of HTTPS protocol is recommended for sending the query.
  • Context tooltip implemented for parameters of some methods, if the parameters are specified by string literals. Automatic tooltip on typing quotation marks parameter implemented in Designer settings.
  • Multiline text editing implemented in managed form editor for the Title property of the form command, attribute, attribute column and group (of Column group type) and Footer of form table field.
  • Extended module check mode implemented. This mode provides checking for calls to object methods and properties "using dot" for some types, and validation of some parameters (String type) for some methods.
  • Mask property implemented for cells and pictures of spreadsheet documents.
  • Report form extension handlers implemented: BeforeLoadDataFromSettingsAtServer(), BeforeLoadVariantAtServer() and BeforeLoadUserSettingsAtServer().
  • SavedInSettingsDataModified property implemented for managed forms. If this property is set to True and the form has been forced to save the form data automatically, then data is saved in the settings during the form close.
  • Implemented the possibility to edit the access restrictions templates, defined for all roles, in one window.
  • Dump and load of common pictures using Designer commands Configuration – Dump configuration files and Load configuration files implemented. Picture parameters implemented for DumpConfigFiles and LoadConfigFiles options of the batch mode of Designer startup.
  • Dump and load of access rights using Designer commands Configuration – Dump configuration files and Load configuration files implemented. Right parameter implemented for DumpConfigFiles and LoadConfigFiles options of the batch mode of Designer startup.
  • Using separate table space in the Oracle Database, when ORA-01450 error is raised during infobase restructure or loading infobase (from .dt file) is now supported. Table space (V81C_INDEX_BIG) is not created automatically and must be created by a database administrator.
  • Possibility to specify named parameters in data access restriction templates implemented. Use # character in front of the parameter name when referring to the parameter in template body. Possibility to use predefined templates #CurrentTableName and #CurrentAccessRightName in texts of data access restriction is implemented. Possibility to use StrContains function and + operator for preprocessor expressions (in data access restriction texts) implemented.
  • IMAP protocol support implemented.
  • Possibility to display managed form tabs to the left and to the right from the Pages form item implemented.
  • Implemented support of GoTo operator in the web client.
  • Pictures added to the picture library: Picture, Char.
  • Possibility to specify a functional option for common form is implemented. If the common form is disabled by functional option, its standard command (of the form) is not displayed in the interface.
  • The webinst utility now can update publication, delete publication and specify OS authentication for executing the publication.
  • DBMS query plan can be written in the technological log. You must add the <plansql> element and planSQLText property for events of SQL operator execution for different DBMSs in the configuration file.
  • International domain names are supported for the HTTPConnection and FTPConnection objects according to the RFC-3490.
  • Open by value standard command implemented for the Task object.
  • VerifyAccessRight() global context function implemented. If current user does not have the verified right, then the function raises exception and writes the Access.AccessDenied event in the event log.
  • BackColor property implemented for managed form field extension. Property can be used only if a field is placed in the form table.
  • The possibility to filter configuration objects, not included in any subsystem, is implemented. <Not in any subsystem> option is implemented in the subsystems tree of the filter dialog.
  • Implemented the possibility to include functional options and functional options' parameters in the subsystems content.
  • Possibility to create common forms for report, report settings and report variant is implemented. The common forms can be specified as properties values, indicating the corresponding forms. Configuration properties DefaultReportForm, DefaultReportVariantForm and DefaultReportSettingsForm implemented. Forms, specified in these properties, are used if corresponding forms are not set for the report.
  • An array can be passed as a parameter for the OpenValue() function. The array values are displayed in form as a table.
  • Including in the configuration is not recommended distribution settings rule implemented. Objects with such rule are not offered for merging with a target configuration. In this way configuration objects for demonstration purposes can be filtered.
  • Distribution options tab is implemented in the More window.
  • OnChange event handler is called for the managed form table, linked with dynamic list, in the following cases:
    • After writing an object to a form.
    • After direct deletion.
    • After checking or clearing the deletion mark.
    • After posting and clearing posting.
    • After moving to a group.
    • After reading or writing changes of an exchange plan contents.
  • OnChange event handler is called for the managed form table, linked with register record set after executing the Switch Activity command.
  • SaveUserData access right implemented. This right allows saving user data and settings (history, favorites, form settings, command interface setting, report settings, etc.).
  • Implemented the possibility to save a spreadsheet document to an OpenDocument Format (*.ods) spreadsheet file.
  • Implemented the possibility to use Undefined as a value of a collection item for session parameters with fixed collection type (FixedArray, FixedMap or FixedStructure).
  • The Syntax Assistant now includes information on which methods cache results when called at client.
  • A user message can now be linked to a specific form. In this case implemented the TargetID property for the UserMessage object. Implemented methods SetObjectAndFormConformity() and GetObjectAndFormConformity() allowing to set and get association of object, form and attribute on this form using script.
  • FormGetProcessing event is implemented in the manager module of several objects. The event is called at server on receiving standard managed forms for some objects. You can redefine opened form using this event. If the form being opened is specified explicitly, the event is not called.
  • New possibilities of compare and merge mechanism implemented:
    • The comparison report for desktop contents.
    • The comparison report for command interface.
    • Merge of and merge report for applied objects' characteristics.
    • Merge of and merge report for functional options' content.
    • Merge of and merge report for roles, data access restrictions and data access restriction templates.
    • Merge of the of event subscription contents.
  • A query, containing IN operator with multiple operands and with sorting in a subquery, can be executed if there are no calls to the external query fields from the subquery.
  • Implemented properties Top, Bottom, Left and Right for the objects ChartPlotArea, ChartTitleArea, ChartLegendArea, GanttChartPlotArea, DendrogramPlotArea and DendrogramTitleArea. The properties are used for specifying a position of the corresponding area border relatively to the chart area.
  • Chart display is enhanced:
    • Display of horizontal labels is enhanced. The ChartLabelsOrientation property implemented for theChartPlotArea object and ChartType.LabelsOrientation parameter for the ChartAppearance object of the data composition template.
    • For the Chart objects implemented LabelFont, TransparentLabel, LabelBackColor, LabelBorder and LabelBorderColor properties.
    • For the ChartLabelLocation system enumeration implemented EdgeInside and EdgeAuto values.
  • Managed form editor enhanced:
    • When attribute or command is deleted it is offered to delete linked elements.
    • The Events submenu implemented in the context menu of form elements, allowing to create a new handler and to go to the existing one.
    • In the form element context menu, linked to a command, implemented the possibility to go to the procedure, executing the command action.
    • In the form preview window implemented selection of elements. At the same time automatic selection of element, corresponding to the element in the preview window, in the list of form elements is performed.
    • Dragging elements in form preview windows is implemented.
    • In form preview window implemented context menu for elements, similar to context menu in the list of form elements.
    • Implemented the possibility to go between linked objects in the form editor using the Go to command.
  • TDEADLOCK and TTIMEOUT events implemented in the technologic log. Events are used for analysis of interlocks and timeouts on locks.
  • The properties Regions (list of names of lock spaces), Locks (locks applied) and WaitConnections (list of numbers of connections, which a collision occurs with) are implemented in the technologic log of the TLOCK event.
  • Selecting a user from the drop-down list is available when specifying a user, on behalf of whom "1C:Enterprise" will be launched from Designer.
  • Support rules can be specified hierarchically when a configuration is compared and merged with vendor configuration.
  • The following features implemented for the GetFiles() method:
    • The FilesLocation parameter can contain the choose file dialog in the save mode, which will be called for each received file, except for those, which are specified by the full path.
    • The value of the Name property of the corresponding TransferedFileDescription object will be used as initial name of a file transferred.
    • If choosing a file to be received is canceled then the Name property of the corresponding TransferedFileDescription object will be set to empty string value.
    • The method returns True if at least one file is saved at a local file name.
    • The procedure of receiving files is actually executed after finishing with the dialogs of selecting file names for all received files.
  • Questions, asked by the cryptography extension, are generated using system interface localization language.
  • Obligatory parameters of a data composition scheme can be specified in the data composition system.
  • Implemented the DataCompositionGroupProcessing object and GroupProcessing function of the data composition system expression language. The function and the object allow creating custom aggregate functions receiving values of other aggregate functions as arguments.
  • The Array function implemented in the data composition system expression language. The function result is an array, elements of which are parameter value for each detail record. If the data composition system expression contains the Array() function, then it makes the expression aggregate. It is allowed to specify the Distinct keyword before the function parameter; in this case the returned array will not contain the same values. As a parameter the function can use an expression returning a value table. In this case the result of Array() function will be an array, containing values of the first column of the passed value table.
  • The ValueTable() function implemented in the data composition system expression language. The function result is a value table, in which the number of columns is equal to the number of the function parameters, and data in columns are obtained from detail records. If the data composition system expression contains the ValueTable() function, then it makes the expression aggregate. It is allowed to specify the Distinct keyword before function parameter; in this case the obtained value table will not contain rows with the same values.
  • The EvalExpression() function implemented in the data composition system expression language, calculating expressions in the context of some grouping. You can specify from which record to start and which record to end with the array of records for calculation (you can specify the first, last, next, previous records, also current and value of record filter by sort field), define sorting and processing for the same values, specify groupings not only by grouping names but also by names of grouping fields.
  • The DimensionAttribute property implemented for the DataCompositionDataSetFieldRole object. The property indicates that the data set is an attribute of a dimension field.
  • For the Presentation() and String() functions of the data composition system expression language the possibility is implemented to pass an array or a value table as parameter. The result is a generated string containing representation of all items of the parameter-object, separated by ; character.
  • Implemented the possibility to pass the result of Array() function as a parameter for aggregate functions of the data composition system expression language (excepting Array() and ValueTable() functions).
  • Implemented the possibility to use an array and a value table in the standard processing of report details, created in the data composition system.
  • The GroupBy function implemented in the data composition system expression language. The function intended for deletion of duplicate values from an array.
  • The GetPart function implemented in the data composition system expression language. The function is intended for obtaining a value table containing only specified columns from a source table.
  • The Order function, intended for sorting the array elements, implemented in the data composition system expression language.
  • The JoinStrings function, intended for joining strings into one, implemented in the data composition system expression language.
  • The PercentInHierarchy subordinated field implemented for each data composition system numeric resource-field. This field contains a percent of resource value in the current hierarchical group.
  • The RowOrSeriesPercent subordinated field implemented for each data composition system numeric resource-field. This field contains the ratio of the resource value in the current cell to the value of resource total by row or series (in percents).
  • The ColumnOrPointPercent subordinated field implemented for each data composition system numeric resource-field. This field contains the ration of the resource value in the current cell to the value of resource total by column or point (in percents).
  • The RowOrSeriesGroupPercent subordinated field implemented for each data composition system numeric resource-field. This field contains ratio of the resource value in the current cell to the value of resource total in current group by row or series (in percents).
  • The ColumnOrPointGroupPercent subordinated field implemented for each data composition system numeric resource-field. This field contains ratio of the resource value in the current cell to the value of resource total in current group by column or point (in percents).
  • The PercentInRowOrSeriesHierarchy subordinated field implemented for each data composition system numeric resource-field. This field contains ratio of the resource value in the current cell to the value of resource total at the current hierarchy level of current group by row or series (in percents).
  • The PercentInColumnOrPointHierarchy subordinated field implemented for each data composition system numeric resource-field. This field contains ratio of the resource value in the current cell to the value of resource total at the current hierarchy level of current group by column or point (in percents).
  • The possibility to fix rows and columns in a generated report automatically implemented. FixLeft and FixTop properties implemented for the DataCompositionAreaTemplateTableCellAppearance object.
  • The EvalExpressionWithGroupArray() function implemented in data composition system expression language. The function returns an array, each element of which contains a result of calculating expression for group by specified field.
  • The EvalExpressionWithGroupValueTable() function implemented in the data composition system expression language. The function returns a value table, each row of which contains a result of calculating expression for group by the specified field.
  • Implemented the possibility to use HIERARCHY keyword after a field name in the Groups property of the DataCompositionSchemaTotalField object. Adding this keyword indicates, that the expression will be used for hierarchical records of group by field, specified before the word, and for all nested groups, for which the value of the given resource is not specified.
  • Implemented the possibility to manage order of placement for resource fields in report: either after all group fields, or in order as they are placed in the report.
  • Implemented the possibility to display additional information in report (Group use variant data composition system parameter). All fields available in the given group can be used as additional information.
  • One can go to link in the formatted document, displayed in form in read only mode. The link is opened in new browser window.

Table of contents

New functions and changes in the 1C: Enterprise mode

  • Mobile browser Safari for Apple iPad is now supported. iOS operating systems of versions 3.2, 4.2 and older are supported. Version 4.2 or newer is recommended. The list of usage features of Apple iPad web-browser on the is published in the documentation.
  • Safari 5.0 (Mac OS X 10.5 or newer and Windows) web browser support is implemented.
  • Web browser Mozilla Firefox 4 support has been implemented.
  • The modal window that may appear when switching web clients' windows in Google Chrome is not displayed starting from browser version 8.0.
  • The composition and appearance of context menus of setting the main window panels setting is modified.
  • Appearance of check boxes, unavailable for editing (the third state), is modified in tables and forms.
  • Implemented the display of the help information on the data composition system expression language.
  • At first launch of the web client in Microsoft Internet Explorer 6.0 the warning is displayed that it is recommended to use Microsoft Internet Explorer 7 or newer, or another browser.
  • The Search in found flag implemented for the search in table dialog. You can use this flag if search was already performed in the table. Cancelling search cancels all search terms at once.
  • The View submenu implemented in the main menu. It contains commands for setting visibility of panels (sections panel, navigation panel, actions panel), setting content of panels and desktop and hiding all the panels. The Ctrl+Shift+` key press can be used to hide all the panels. The Tools – Interface setup menu item is removed.
  • A context menu is implemented in the web client for the HTML-field, displaying content, received by internal navigation link.
  • For Mozilla Firefox browser, the sequence of actions to install the file operation extension, cryptography extension and external components is modified. During the installation the user is prompted to check for the necessary permissions in the browser settings (the browser settings dialog will open).
  • Appearance of the forms displaying values of type Color and Font when using the OpenValue() method is modified in the web client.
  • The Details… button in the error message is displayed only if the debugging mode is enabled. The About 1C:Enterprise window now contains a Information for technical support hyperlink providing access to the error log. In case of critical error and platform termination, with debugging mode disabled, the Information for technical support hyperlink is displayed in the error message window.
  • User can change the composition of report express user settings either in the Settings dialog (Editing in report form column) or using the Modify set of settings command in the report settings window.
  • Operating mode setting dialog for Mozilla Firefox 4 opens at the first start of any infobase in this browser at the computer. If settings are set to the required values, then the dialog is closed automatically and the web client continues loading.
  • Implemented changes intended to support performance of the web client in Mozilla Firefox browser.

Table of contents

Optimization

  • Display of command bar icons, menu and sections panel in web client optimized.
  • Count of server calls in the web client functionality was reduced.
  • Optimized the execution the following query: ValueType(Field1) = ValueType(Field2), if Field1 and Field2 contain values of reference type.
  • When operating with Oracle DBMS performance of operations of writing register records and writing objects with tabular sections is improved.
  • The writing of register records of accumulation and accounting registers in Oracle Database DBMS is optimized.
  • The selections, executed by chunks (used in Choose() methods and at restructuring) optimized for all supported databases.
  • Transaction log parameters for an IBM DB2 database being created, are changed.
  • Optimized a number of 1C:Enterprise server mechanisms to improve performance and scalability for large number of users.
  • File operation (including temporary files) is optimized for the following mechanisms: full-text search, help, InternetMail object.
  • Web server extension module performance and scalability improved.
  • File base operation improved.
  • Work with MS SQL Server optimized for some operations.
  • Server cluster operating with session data has been optimized.
  • GetInfoBaseConnections() and GetInfoBaseSessions() functions performance improved for large number of registered users.
  • The operation of retrieving changes from the configuration repository is optimized.
  • Update of the spreadsheet document after interactive edit and also after program modification of separate cells of the spreadsheet in web client optimized.
  • Performance of the managed locks mechanism is improved.

Table of contents

Changes affecting the system behavior

  • Modified the operation of storing constants and accumulation register settings when the compatibility mode is disabled. A separate database is used for each object. If the compatibility mode is enabled (set to Version 8.2.13 or Version 8.1), then reverse conversion is performed in order to provide launch of applied solution using version 8.2.13.
  • The presentation of the Data parameter output data composition system parameter is renamed to Display parameters. The format of the parameter output in the report title is changed.
  • The behavior of the report detailing is modified. A double-click on a report cell opens a value contained in the report cell. Use right click or the corresponding key button to open the details menu. The behaviour described is only actual if the comaptibility mode is disabled. The MainAction property is implemented for the DataCompositionDetailsAreaParameter and DataCompositionDetailsProcessingAction objects. The AdditionalDetailProcessing event implemented for a spreadsheet document field extension. The UseMainAction and FormElement parameters are implemented for the ChooseAction() method of the DataCompositionDetailsProcess object.
  • The value, that is returned on a form close with the Close() method, is destroyed immediately after the form is closed, if there are not any references to this value from other objects.
  • Properties indicating the main and additional record form are cleared for the information register if the record mode property is set to Subordinate to recorder.
  • The icon for the Insert picture command is modified in the toolbar of the formatted document field.
  • If a publication at a web-server is performed for the first time, and publication with the specified name already exists, the warning is displayed.
  • The server is notified about a form close and locks releas, that are bound to the form, on call of server procedures from the client, opening forms and system inactivity for more than 20 seconds not only for low speed connections, but also on normal connection speed. The server receives information about all closed forms not only those for which the data were locked.
  • Search is cancelled, if it was performed, on activation of a user message, indicating a form table (linked with FormDataCollection, FormDataTree and FormDataStructureAndCollection form data). After the search cancelation the message is placed at the required table cell. A filter specified by the Script with the RowFilter property is not cancelled.
  • Icons of '1C:Enterprise'-related files are taken out to a separate library, registration of which is done during the first installation of the system, and it is un-registered when last version of the system is removed from the computer.
  • If the ProcessingTime parameter is not specified or is set to 0 when the ProcessJobs() global context method is called, then the Processing jobs dialog is not displayed.
  • The compare and merge mechanism is revised:
    • Only modified objects information is output into Input by string property comparison report.
    • Only modified objects information is output into exchange plans (including different autoregistration settings) comparison report.
    • Only modified objects information is output into subsystems comparison report.
  • Subsystems are displayed in the 'filter by subsystems' mode.
  • Including the subsystem help in the help contents completely depends on the state of the Include in Help Contents subsystem property and does not depend on this property of objects, included into subsystem. If 8.2.13 compatibility mode is disabled, then the system changes the state of Include in Help Contents check box automatically for subsystems so that to save the help contents tree similar to the version 8.2.13. The behavior is not altered in 8.2.13 or 8.1 compatibility mode (the subsystem help was displayed in the help contents if any of the objects included in subsystem content had the Include in Help Contents property set, and the subsystem itself had this property disabled).
  • When the web client (from Designer mode or using the webinst utility) and web-services are publicated the possibility to publish to '%SystemDrive%\Inetpub\wwwroot' directory for the Microsoft IIS web server (version 7.х) is excluded.
  • If Designer mode is launched with the ConfigurationRepositoryReport options without parameters, then the storage history report is generated with grouping by versions. If the Compatibility mode property of the configuration being edited differs from the database configuration, then the value of Compatibility mode database configuration property is used at generating the report from the command line. In the 8.1 and 8.2.13 compatibility mode the platform behavior is not changed, that is the report is generated with grouping by objects.
  • When calling managed form items (context menu or automatic form command bar) as named elements of the Items collection, you can use CommandBar, ContextMenu and Form prefixes in any script language variant, whatever language variant was used upon the form creation.
  • More than one resource can be displayed in a chart created in the data composition system. The behavior is not changed in 8.1 and 8.2.13 compatibility mode (i.e. only one resource can be displayed in a chart).
  • When creating object of the Font type basing on the font description and if a non-empty string is specified as the font name, the value of the Type property of the received object will be set to the FontType.WindowsFont value, if the configuration has the compatibility mode disabled; otherwise, the property is set to FontType.Absolute.
  • The order of properties of the properties palette is changed in some categories.
  • When dumping the configuration files, template files of graphical schema and geographical schema types are unloaded with extension (.grs and .geo accordingly). These templates can be loaded either from files with extensions specified, or without them.
  • The compiled source code is directly executed at web-client side. Translation of the source code into theJavaScript is not used any longer.
  • For the dynamic list with a custom query set, the check is performed for key values identifying a displayed row. If there are duplicate key values found – a warning is displayed and data cannot be displayed.
  • The SystemLanguage parameter is implemented for the conf.cfg configuration file. The parameter specifies the default platform interface language. Use of *.res files is kept for compatibility (in case if the SystemLanguage is absent in the configuration file).
  • For the UserMessage object the TargetID property is set on calling the SetData() object method.
  • If the compatibility mode is disabled the AccessRight() and AccessParameters() functions do not perform recording of the Access.AccessDenied event of the event log if the right being checked is absent.
  • Enhanced chart display:
    • 32 different colors can be used for chart series (the ColorPalette property of the Chart object). In the compatibility mode the data composition system uses 8 colors to generate a chart.
    • The VerticalLabels property of the ChartPlotArea object and the ChartType.VerticalLabels parameter of theChartAppearance object in the data composition templates are considered outdated and kept for compatibility.
    • Labels displayed do not overlap.
  • Default support rules now allow detailed adjustment for objects with different distribution rules when: a) enabling the possibility to modify vendor configuration; b) configuration is set to vendor support, and c) configuration is being updated and modification is enabled. You can specify the support rules in details for: a) new vendor objects by distribution rules; b) unchanged, or becoming unchanged objects, by distribution rules, and c) modified objects, by distribution rules. In the Support Options dialog, the default values disallow editing objects for which the Object is editable rule is set. In the Change Support mode the Set for subordinate objects dialog check box is unchecked by default.
  • The Check Syntax menu item (Designer menu Text) renamed to Check module. The Check Syntax in Modules menu item (Designer menu Configuration) renamed to Check modules.
  • SearchOnInput property implemented for a form tables. The property manages the call for the search dialog on text input, if the table is an active element of the form. If the compatibility mode is disabled, then if the table is linked to form data of FormDataCollection or FormDataStructureAndCollection type, the search on input is not performed.
  • When dumping the configuration files, the HTML-document templates files are unloaded for each language, for which the template is defined in the configuration. Language code is included in the filenames. On load, an attempt to load a corresponding file for each language is performed (according to the language code included in filename). If the corresponding file not found, the attempt to load file is performed without taking into account the language code in the filename.
  • The color of the lines displaying fixing of rows and columns in the spreadsheet document, is changed.
  • The managed locks mechanism implementation is revised.
  • Txt property for the TLOCK technological log event is recorded only in 8.2.13 compatibility mode.
  • The presentation of a deleted user is modified in records and in the filter dialog of the event log. The old presentation: User name <deleted>, the current presentation: User name <not found>.
  • In Russian interface the presentation of Администрирование access right is changed to Администрирование.
  • The Post Document standard function is available to all users, not only those with administrative rights.
  • The Delete Marked Objects standard function is available to users with the Exclusive mode right set, not to users with administrative rights.
  • Calling the RefreshInterface() method leads to clearing of the cache memories: reference presentation, object data, quick choice data, choice forms, and restrictions by type.
  • The query wizard uses the same icon for the Constants table fields as for the object attributes.
  • If the data composition system settings the display of totals is disabled for the row/column group, then totals for rows/columns of this grouping are not displayed in the column/row of totals by row/column.
  • In the text box, associated with attribute of Number type with 0.0 precision, implemented the possibility to display leading zeroes after the decimal point using the format string. Behavior is not changed in the compatibility mode (in described case leading zeroes are not displayed).
  • Hyperlink, inserted to the formatted document, remains unchanged. In previous versions if the hyperlink was not absolute, then full path to the infobase was added to hyperlink.
  • Increased accurasy of conversion the floating-point number (double type) to the Number type of "1C:Enterprise" system.
  • For the form control, displaying a document journal column, and for the report field the following properties are used automatically (specified for the corresponding attributes): Format, Mark negative. For the form element, displaying a document journal column, the Password mode and Tooltip are applied also.
  • When a new role is created the following rights are set by default: SavingUserData, ThickClient, WebClient and Output.
  • The cancellation of the transition to winter time is taken into account for Russia (starting from 2011). This behavior impacts the work of the following script methods: CurrentSessionDate(), ToLocalTime(), ToUniversalTime(), StandardTimeOffset(), DaylightTimeOffset(). Also this modification affects the behavior of standard platform features which operate the session date. You need to update the operating system in order to make the CurrentUniversalDate() method work properly.
  • Information about time zones for Russia is brought into accord with new rules of time calculation.
  • In accordance with the laws adopted in The Republic of Belarus and Ukraine, daylight saving time for these countries was revoked in the version 8.2.14.537. After the repeal of the above mentioned law in Ukraine, daylight saving time was restored in the version 8.2.14.540.
  • The procedure defining the time zone, set in the system for Windows OS, is modified. At first, the attempt is performed to define the time zone by presentation returned by OS. If the found zone does not meet the parameters, the search is performed for the first appropriate zone.

Table of contents

Changes that require changes to the configuration and administrative settings

  • The distribution kits for Linux are published at the http://users.v8.1c.ru using the TAR.GZ format instead of RAR.
  • The Compatibility mode configuration property can be set to Version 8.2.13 value.
  • A new interface operation mode implemented: opening forms in main window and using tabs to switch between opened windows. To manage the operating mode use command line parameters (/itdi – to work in tabs and /isdi – to work in separate windows) and parameter Form open mode in the client application settings dialog. When transiting to operating with tabs mode, it is recommended to analyze the application code of commands belonging to the Navigation panel group. If two commands must open one and the same form in two different tabs, it is required to specify the unique key or key form parameter when the form is obtained.
  • UseHwLicense command line parameter name is renamed to UseHwLicenses. The UseHwLicense parameter is left for compatibility. USEHWLICENSE installation parameter is renamed to USEHWLICENSES. The USEHWLICENSE parameter is left for compatibility.
  • StrikeOut property is renamed to Strikeout for the Font object.
  • DataCompositionSystemSettingsVariants property is renamed to DataCompositionSettingsVariants. The possibility to use DataCompositionSystemSettingsVariants is left for compatibility.
  • DataCompositionSystemSettingsVariant property is renamed to DataCompositionSettingsVariant. The possibility to use DataCompositionSystemSettingsVariant is left for compatibility.
  • OnLoadDataFromSettingsAtServer() event of form report extension is executed after loading settings. In the forms created in previous versions, the OnLoadDataFromSettingsAtServer event handler selected in form properties is switched to BeforeLoadDataFromSettingsAtServer handler.
  • Implemented the possibility to group by data composition system resource-fields. The behavior is not changed in the 8.1 and 8.2.13 version compatibility modes (data composition system resource fields can not be used for grouping).
  • System behavior is changed on calling the RefreshInterface() method and at modifying functional options' parameters. All additional forms are closed (with calling the corresponding form handlers) and then the list of elements of the main form is updated or the command that called on the opening of the additional form, is executed.
  • A query is executed to automatically define document time in the privileged mode (at writing of the document form and at calling of the SetTime() method).
  • If the compatibility mode is set to Do not use, then exception is thrown on attempt to go to invalid navigation link. The exception can be processed using the Try - Exception operator.
  • GetFullTextMode() method renamed to GetFullTextSearchMode(), SetFullTextMode() method renamed to SetFullTextSearchMode(), FullTextMode() method renamed to FullTextSearchMode(). Previous method names are left for compatibility.
  • The settings composer's form items DataParameters, Filter, Selection, Order, ConditionalAppearance, OutputParameters, UserFields, implemented for link with columns, are renamed to ItemDataParameters, ItemFilter, ItemSelection, ItemOrder, ItemConditionalAppearance, ItemOutputParameters, ItemUserFields correspondingly. Old names are available in compatibility with version 8.2.13 and version 8.1 modes.
  • If the compatibility mode is disabled then the Period parameter is obligatory for the Get() method of the periodical information register. In the 8.2.13 and 8.1 compatibility mode the behavior is not changed (the method can be used without the specifying parameter, but the result is undefined).
  • Microsoft Internet Explorer browser external component adapter registration is performed "for computer". External components installation directory is changed for the Microsoft Internet Explorer browser. %ALLUSERSPROFILE%\Application Data\1C\1СEWebExt (%ALLUSERSPROFILE%\1C\1СEWebExt for Windows Vista and older) directory is used for installation. Administrator can install external components, if user doesn’t have the rights to perform installation.
  • If the choice content model is found during XSD-schema export then all elements specified within this model are defined as not obligatory.
  • Interpreting the different variants for inheritance of object types is performed more correctly when XDTO factory is created.
  • When a row is duplicated in a managed form table linked with a value table, a value tree, a tabular section or a filter, the OnChange event handler is called after the new row is filled in.
  • When sizes of a managed form elements are defined automatically, the size of the font specified in the form elements properties is taken into account. Change of the font size performed through form and dynamic list conditional appearance, does not affect the size of the form element. A call to a server is performed if the font is changed programmatically. The behavior is not changed in the 8.2.13 compatibility mode (the font size is not taken into account when defining the element size).
  • A string consisting of 12 spaces is a text presentation of DataVersion standard attribute value for a new object. The behavior is not changed in the 8.2.13 and 8.1 compatibility modes (the presentation is equal to empty string for a new object).
  • You can manage text update in the text box when a value is passed from an attribute to a managed form element. Use the EditTextUpdate property of the text box and UpdateEditText() method of the text box extension. The behavior is not changed in the 8.2.13 compatibility (the property is ignored; update is executed always, except for the case when the value of the same type is set in the AutoCompleteText handler as a type of a value in the text box.
  • Exception occurs when SetValue() and UseFromDataSource() methods of the DataLockItem object are used simultaneously. The behavior is not changed in the 8.2.13 compatibility mode (the value set by UseFromDataSource() method is considered priority).
  • Exception occurs if the type of the Value to be locked parameter does not correspond to the type of the lock space field when calling the SetValue() method of the DataLockItem object. The behavior is not changed in the 8.2.13 compatibility mode.
  • When a lock is set on the spaces AccumulationRegister.<Name> and AccountingRegister.<Name>, in some cases the period of lock is corrected automatically. The behavior is not changed in the 8.2.13 compatibility mode.
  • When a managed lock is set on the AccumulationRegister.<Name> space if value of the extra dimension is set by a reference to a characteritic, then this characteristic must bу one of the extra dimensions for this account in the Chart of accounts. If the corresponding extra dimension is not specified for an account, then an error occurs. The behavior is not changed in the 8.2.13 compatibility mode.
  • NumberInWords() and PeriodPresentation() global context methods use session localization code by default (which can be set using the /VL command line parameter). The behavior is not changed in the compatibility mode.
  • When checking rights for attributes and tabular sections of reports/data processors, if the role has not Independent rights for subordinate object check box set, and if the View right is not set for the report/data processor, then it is considered that the Edit right is not set for the attribute (tabular section). The behavior is not changed in the compatibility mode.
  • Writing data not supporting serialization to the data value storage is not supported. The behavior is not changed in the compatibility mode.
  • FillCheck() method renamed to CheckFill(). The old name is left for compatibility.
  • In the managed form text box the text is aligned by the top edge, if multi line mode is set for the text box, otherwise – by center (vertically).
  • English presentation for the object key for the sections panel is changed from Common/PartitionPanel/CommandInterfaceSettings to Common/SectionsPanel/CommandInterfaceSettings. Settings, saved in previous versions of system and English variant of script, will be lost.
  • Modified keys of objects, intended for desktop command interface storage. For the desktop navigation panel the Desktop/NavigationPanel/CommandInterfaceSettings key is implemented instead of Subsystem.desktop/NavigationPanel/CommandInterfaceSettings. For the desktop actions panel the Desktop/ActionsPanel/CommandInterfaceSettings key is implemented instead of Subsystem.desktop/ActionsPanel/CommandInterfaceSettings. In version 8.2.13 compatibility mode old object keys are used.
  • Sequence of event handlers calls is modified for calls, associated with closing forms, when "1C:Enterprise" in managed application mode is terminated. The sequence of calling handlers is as follows:
    • BeforeExit;
    • BeforeClose of all forms, except forms, located on the desktop;
    • BeforeClose of forms, located on the desktop workspace;
    • OnClose of all forms, except forms, located on the desktop;
    • OnClose of forms, located on the desktop workspace;
    • OnExit.
  • We have switched from use of ICU 4.0 to use of ICU 4.6. Thereby date and number formatting is changed for several languages and formats.
  • Word sorting for russian language using И and Й letters is changed.
  • Name of RegistrationPeriod standard attribute is changed in metadata. RegistrationPeriod is used instead of Period. In compatibility mode the name is not changed.
  • Microsoft Internet Explorer 9 web browser support is implemented. It is recommended to verify the correctness of generating the HTML templates of the applied solution when transferring to use this browser. In particular, it is recommended to change specifying font size from px to pt.
  • In the external components technology added libraries for building extensions for the Mozilla Firefox browser with xulrunner-2.0 and xulrunner-5.0 packages.
  • Mozilla Firefox 4 and 5 browser support is implemented in the external components technology. The clientVersion attribute in manifest file is no longer ignored and is used for selecting the necessary installation kit. You should build separate installation kit for each version of browser in order to provide external components operability with this browser.
  • The RefreshValuesReuse() method is renamed to RefreshReusableValues(). The following names are left for compatibility matters: RefreshReusingValues() for executing at thick client and at server; the RefreshValuesReuse() is left for executing at thin client.
  • More complete validation for the structure of leading calculation types is implemented. At the same time the increase of number of access rights error messages is possible for the chart of calculation types, if there are data access restrictions for reading.
  • If the Grouping fields placement paramater of the data composition system is set to SeparatelyAndInTotalsOnly value, then the grouping template cells are merged only for columns of the corresponding grouping when grouping template is generated. The behavior is not changed in the version 8.1 and 8.2.13 compatibility mode (the grouping template cells are merged within all columns of parent grouping).
  • The mechanism of configuration change records for operating in the distributed infobase is changed. The configuration is fully marked as changed in the following cases: loading configuration from a file, connecting configuration to the configuration repository, updating configuration using the support mechanism with disabled possibility of changes.
  • If there are roles, that were not edited after creating (they do not have any rights for any object) during the conversion of infobase from version 8.2.13 and earlier, then the SaveUserData and AllFunctionsMode rights are not set automatically for these roles.

Table of contents

Transition from the previous version to the version 8.2.14

  • Attention!

    The infobase file format has been changed. It should be converted for use with new version of "1C:Enteprise". After conversion is started, the infobase can not be used with previous versions of the 1C:Enterprise 8 platform versions. The reverse transition (for using the infobase with previous versions of "1C:Enterprise") can be performed by executing infobase dump (in version 8.2.14) and load infobase (in previous version).

     

    File-Based Infobase

    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. Conversion is performed on first call of infobase, executed by Designer of version 8.2.14 before the authentication. In order to perform conversion you should answer in the affirmative for questions, asked by the system on Designer start.

    Configuration Storage File

    Please, create a backup copy of an infobase storage prior to conversion! If any software or hardware failures occur in the conversion process, the data contained in the storage may be lost. Infobase storage is conversed on first call to storage data by any user.

  • Conversion of configurations, infobases in Client/server mode, external data processors and external reports is not required during the transition from the version 8.2.13 to the version 8.2.14.
  • In the configuration property Compatibility mode is set to Do not use, the infobase cannot be used by versions 8.2.13 and earlier. If you need to use the infobase with these versions, you should set the property to Version 8.2.13. At the same time new functions and changes, supported in disabled compatibility mode, will not work.

Table of contents