Version 8.3.12
Version 8.3.12 includes known bug fixes and functionality modifications.
- New functionality and changes
- New functionality and changes in the 1C:Enterprise mode
- Optimization
- Changes that affect system behavior
- Changes that require modification of configuration and administrative settings
- Renamed objects
- Mobile platform
- Library updates
- Transition from the previous version to the version 8.3.12
New functionality and changes
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.11 is now implemented. | Compatibility with versions 8.1, 8.2.13, 8.2.16, 8.3.1 - 8.3.10 was implemented. | Configurations developed using 1C:Enterprise platform version 8.3.11 or earlier can run on version 8.3.12 without any changes to configuration or to data structures. This allows for transition to version 8.3.12 in two stages: first, update the platform version (without any changes to the configuration); then, apply any required changes and disable compatibility mode. You can still access the infobase using version 8.3.11 after the transition to version 8.3.12, even if you disabled the compatibility mode (if you did, enable it again). |
| Client application. | On 64-bit Windows, you can set the bitness of a client application at application startup. In the Startup window settings dialog box, the option to specify the application bitness is implemented. This value is stored to the DefalutVersion parameter of 1CEStart.cfg file. In the infobase properties, the option to specify the bitness of the client application used with this infobase is implemented. This value is stored to the AppArch parameter of ibases.v8i file. The command-line option /AppArch is implemented for the thin and thick client applications. | This feature was not provided. On 64-bit Windows, users could not select the bitness of client applications. | On 64-bit Windows, the option to select the bitness of a client application is implemented. You can explicitly specify a 32-bit application in scenarios where a 64-bit application cannot work properly (for example, in a scenario where 64-bit add-ins are not available). |
| Configuration extensions. | The option to select the application area of configuration extensions, as well as enable or disable them, is implemented. The following application areas are available: the current data area and the entire infobase. When an extension is disabled, it is not deleted from an infobase. The extension attachment order is changed. Extensions that apply to the entire infobase are attached first. | These features were not provided. Extensions were always attached to specific data areas. Disabling extensions without deleting them was not available. | More configuration extension management options. You can add configuration extensions to all of the infibase data areas at once. You can use this feature to apply hotfixes. |
| Collaboration system. | Automatic conversion of character sequences to pictures ("smileys") is implemented. Sound alerts for the following events are implemented: new message, incoming call, waiting for reply to a video call, and end of video call. Links to conversations, getting links to conversations, and opening links to conversations (both interactively and using GotoURL() method) are implemented. The option to add such links to Favorites is implemented. The option to get presentations of such links using GetURLsPresentations() method is implemented. In conversation messages, links to conversations are displayed as hyperlinks. In the thin and thick clients for Windows, taskbar blinking upon receiving a notification is implemented. In the main collaboration system form, a context menu is implemented for the conversation list. A context menu is implemented for collaboration system messages. For noncontext conversations, service collaboration system messages are implemented for the following events: conversation topic changed, a user joined/left a conversation. The search ignores service messages. The conversation participant list view is changed. Special marking for unsent outgoing messages is implemented. The collaboration system settings dialog box is implemented. The user picture (avatar) editor is implemented. The message list view is changed. | These features were not provided. | Improved collaboration system usability. |
| Data history. | Support of data history for charts of accounts and charts of characteristic types is implemented. For ChartOfAccountsObject and ChartOfCharacteristicTypesObject objects, methods SetVersionComment() and GetVersionComment() are implemented. | This feature was not provided. | Data history is now available for more objects. |
| Configuration extensions. | For native and adopted extension objects, the option to generate records in all adopted registers is implemented, except for turnover accumulation registers with aggregates. | This feature was not provided. Extension documents could generate records only in native information registers available in the extension. | Extended configuration extension capabilities. |
| Configuration extensions. Development tools. Settings storage. | The option to store configuration extensions in configuration repositories is implemented. All of the Designer batch mode command-line options that are related to configuration repositories support configuration extensions. For Designer batch mode, the following changes are implemented:
| This feature was not provided. Configuration extensions could not be stored in configuration repositories, making development unnecessarily complicated. | Simplified group development and versioning of configuration extensions. |
| Configuration extensions. | Creation of enumerations in configuration extensions is now supported. | This feature was not provided. | Extended configuration extension capabilities. |
| Internet-enabled functionality. | Moving email messages between IMAP mailboxes is now supported. Method InternetMail.MoveToMailbox() is implemented. Getting and setting flags of IMAP email messages is implemented. For InternetMail object, methods GetMessageFlags() and SetMessageFlags() are implemented. | These features were not provided. | Extended support of IMAP email operations. |
| Charts. Data composition system. | Highlighting specific chart intervals and values is implemented. This feature is available for the following chart types: stock, open-high-low-close, all types of column charts, all types of bar charts (except for bar graph), line, step, stacked line, area (all types), scatter, bubble, radar (all types), and gauge.
For Chart object, the following properties are implemented: ColorPaletteDescription, DataIntervalsColorPaletteDescription, ValueDataLines, PointDataLines, ValueDataIntervals, and PointDataIntervals. For ChartLabelArea, the following properties are implemented: Orientation and Angle. For data composition system objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance, the following parameters are implemented: ChartType.ColorPaletteDescription, ChartType.DataIntervalsColorPaletteDescription, ChartType.ValueDataLines, ChartType.PointDataLines, ChartType.ValueDataIntervals, and ChartType.PointDataIntervals. The following properties and methods of Chart object are obsolete and not recommended for use: ColorPalette, GradientPaletteStartColor, GradientPaletteEndColor, GradientPaletteMaxColors, GetPalette(), and SetPalette(). | This feature was not provided. | Additional chart layout features are introduced. |
| Spreadsheet documents. | Implemented representable document batch export to the following formats: XLS (Microsoft Excel 97-2003), Microsoft Office OpenXML (Microsoft Excel 2007 and later), and ODT (OpenDocument). You can export each spreadsheet document of the batch to a separate sheet of the resulting document. Implemented RepresentableDocumentBatchItem.Title property. Use it to specify the sheet name. Implemented Write() and BeginWriting() methods of RepresentableDocumentBatch object. | This feature was not provided. | You can save several 1C:Enterprise spreadsheet documents to the resulting XLS, XLSX, or ODT document. |
| Full-text search. Server clusters. Technological log. | In client/server mode, the option to set the number of background jobs that update the full-text search index is implemented. You can use requirements of functionality purpose to set the number of background jobs that update the full-text search index. For FullTextSearchManager object, the following methods are implemented: SetIndexingJobsCount() and GetIndexingJobsCount(). For FTEXTUpd technological log event, the following properties are implemented: MinDataId, MemoryUsed, BackgroundJobCreated, JobCanceledByLoadLimit, TotalJobsCount, and FailedJobsCount. | This feature was not provided. The update of the full-text search index was always performed as a single background job. | Improved performance of full-text search index updates (especially in scenarios with full index rebuilding). |
| Configuration extensions. Distributed infobases. | Support of configuration extensions in distributed infobases is implemented. For exchange plans, IncludeConfigurationExtensions property is implemented. For configuration extrensions, UseInDistributedInfobase and MasterNode properties are implemented. | This feature was not provided. | Extended configuration extension usage options. You can manage the replication of configuration extensions in distributed infobases. |
| Charts. | In charts, the option to manage automatic calculation of header, legend, and plot area sizes and positions is implemented. For ChartLegendArea, GanttChartLegendArea, PivotChartLegendArea, ChartPlotArea, GanttChartPlotArea, PivotChartPlotArea, ChartTitleArea, GanttChartTitleArea, and PivotChartTitleArea objects, property Placement is implemented. Property ShowLegend of Chart, GanttChart, and PivotChart objects is deprecated. Property ShowTitle of Chart, GanttChart, and PivotChart objects is deprecated. | Charts only provided the option to manage header and legend view. | Improved chart customization options. |
| Queries. | In the query language, extended support of UUID and ValueStorage types. The option to create temporary tables based on value tables that contain columns of these types is implemented. The option to use fields and expressions of UUID type in queries where IN is applied to a selection of multiple fields is implemented. | This feature was not provided. | Extended query language capabilities. |
| Data composition system. | In data composition settings, the option to use a period addition in scenarios where the reporting period does not match a regular calendar period is implemented. You can specify month size, either a calendar month or "4-5-5". In the latter case, a year is divided into 4 quarters. Each quarter has two 4-week months and the third 5-week month.
For system enumeration DataCompositionPeriodAdditionType, the following values are implemented:
| The data composition system always used period additions based on calendar beginning of quarter or year. | Simplified reporting in scenarios where the reporting period does not match a regular calendar period. |
| Managed forms. | For managed forms, collapsible pop-up groups are implemented. When a pop-up group is collapsed, a form displays its title; clicking the title opens a pop-up window, which contains all of the group items. In a form, you can view the content of a single pop-up group at a time. The option to toggle the state of collapsible and pop-up groups from 1C:Enterprise script is implemented. The following system enumeration value is implemented: UsualGroupBehavior.PopUp. For managed form group extensions for usual groups, the following methods are implemented: IsHidden(), Show(), and Hide(). For managed form group extensions, HiddenViewTitleBackgroundColor property is implemented. | These features were not provided. | New options for grouping managed form items. |
| Database configuration update. | In the optimized restructuring mechanism (version 2), added the support of restructuring configuration objects having at least one extension (that extends data) attached in any of the data areas. This is only applicable to restructuring main database configurations. Restructuring that is performed during extension updates does not use the optimized restructuring mechanism (version 2). | This feature was not provided. For main database configurations, if any of the areas had an extension (that extended data) attached, the regular restructuring mechanism (version 1) was used. | Improved interaction between platform mechanisms. |
| Automated testing. | For TestedFormField objects that represent form items of radio button, input field, and label (with hyperlink flag set) types, method GetDisplayedText() is implemented. It gets the text displayed on the item. For TestedFormField objects that represent form items of radio button and input field types, method GetChoiceListPresentation() is implemented. It gets a fixed array that contains presentations of the form item choice list. | This feature was not provided. | Extended automated testing capabilities. |
| Mobile client. | Implemented the mobile client that is equal to the thin client running on a mobile device. Its interface is similar to mobile platform interface. The mobile client only uses HTTP protocol to connect to the infobase. TCP connection is not supported. The exact match between the mobile client version and the server (or the web server extension) version is not necessary. The mobile client can online provide almost the same application options as the thin client or the web client. The mobile client supports all mobile specific features, such as camera, location, notifications and so on. The collaboration system uses push notifications to deliver messages. Messages are delivered even if the application is not running or is inactive. The mobile client application is built to operate with configurations from the specified list only. The configuration objects assortment change in the infobase connected to the mobile client application is not supported. You can change the configuration without modifying its objects assortment. If the objects assortment changes, the mobile client application should be rebuilt. The mobile client application cannot operate with configurations that are not in the list because of application stores requirements. The configuration digital signature is used for compliance monitoring. Now configuration forms are automatically adjusted to mobile device screens. The new item properties can be used in the adjustment. Implemented the form preview in mobile client mode in the managed form editor. The mobile client home page contains the same forms list as the thin client and the web client do (but not the mobile platform). When you start an application, the first form on the list is displayed, and the others are available through commands. The mobile client supports add-ins. You cannot open external reports and data processors interactively in the mobile client. The mobile client can run configurations with 8.3.7 or higher compatibility mode. Implemented the commands of interactive mobile client launch on a mobile device. The mobile application builder can now build the mobile client application. You can choose the type of application to build – the mobile client application or the mobile platform application. Implemented the MobileClient access right. Implemented the MobileClient preprocessor command. Implemented the new syntax assistant availability of objects, properties and methods. Implemented the new managed form CollapseItemsByImportance property. Implemented the new managed form item DisplayImportance property that is used for the form adjustment. Implemented new managed form table CurrentRowUse and BehaviorOnHorizontalCompression properties. Implemented new managed form group CurrentRowUse and AssociatedTable properties. Implemented new MobileClientWriteFile and MobileClientDigiSign command line options of the Designer batch mode. Implemented the new -MobileClient parameter for CheckModules and CheckConfig command line options of the Designer batch mode. Implemented the new -MobileClientDigiSignparameter for the CheckModules command line option of the Designer batch mode. The content of the mobile platform distribution package (mobile.zip) is changed. Now it contains all mobile client files necesary for development, building and distributing mobile client applications through application stores. | This feature was not provided. The mobile platform was capable of running specialized offline applications. | Mobile devices can be used in the new way now. You can now work online with all application features that were available on the thin client and on the web client without the significant configuration refactoring. |
| Administration tools. | In Designer batch mode, for command-line options CreateDistributionFiles and CreateDistributive, implemented parameter WarningAsError. | This feature was not provided. | You can apply stricter validation rules (treat all warnings as errors) to generation of application distribution kits. |
| Server clusters. | Implemented new values for session and connection attributes. They indicate the duration of cluster service calls initiated by a session or a connection. They are available in all administrative tools: the cluster console, COM connection, Java administrative API, and the administration server. Implemented the following IInfoBaseConnectionInfo object and ISessionInfo object properties:
Added the same attributes to the session list, connection list, and the connection properties dialog box in the cluster console. Added the following parameters of connection list commands and session list commands for the cluster service command-line utility (rac): duration-current-service, current-service-name, duration-last-5min-service, and duration-all-service. | This feature was not provided. | The duration of cluster service calls initiated by a specific connection or a specific session is now available. |
| System requirements. Client application. | The client application for Linux needs the 1.4.3 version or higher of the webkitgtk-3.0 library installed. | The client application for Linux needed the 1.4.3 version or higher of the webkitgtk-1.0 library installed. | Unified the Linux and MacOs client applications operation. |
| Add-ins. | Implemented the new global context method DynamicAddInInstallationSupported(). It shows whether the add-in loading is available from the current infobase. The dynamic add-in loading is available only on Android mobile devices. Otherwise add-ins should be included in the mobile application and are available only from the Add-in type configuration templates. The dynamic add-in loading is available in the thick client, in the thin client, and in the web client (this behavior did not change). | Add-ins were available only from the mobile application and you could not load them from the infobase. You could not define the availability of dynamic add-in loading feature. | Now you can get the availability of dynamic add-in loading feature. |
New functionality and changes in the 1C:Enterprise mode
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Managed forms. | Keyboard navigation is now available for managed form decorations and fields, provided that they do not have the Hyperlink flag set and they display FormattedString values. Keyboard navigation provides the option to move between hyperlinks available in a formatted string. | This feature was not provided. | Improved managed form usability. |
| Web client. Spreadsheet documents. | In the web client, implemented all of the interactive spreadsheet document editing features that are available in other clients. Implemented the following spreadsheet document commands: AlignPictureLeft, AlignPictureCenter, AlignPictureRight, AlignPictureTop, AlignPictureMiddle, AlignPictureBottom, PicturesEqualWidth, PicturesEqualHeight, PicturesEqualSize, DistributePicturesVertically, DistributePicturesHorizontally, BringPictureForward, SendPictureBack, PringPictureToFront, and SendPictureToBack. | The options for interactive editing of spreadsheet documents were limited. The availability of interactive commands that affected spreadsheet document view was limited. Displaying row and column headers and grid lines was not supported. | Extended interactive spreadsheet document operations in the web client. |
| Spreadsheet documents. | In the thin client, in the paste special dialog box for spreadsheet documents, the option to include or exclude the following items is implemented:
In this dialog box, the All check box is replaced with buttons that select and clear all of the check boxes available in the dialog box. | In the thin client, the paste special dialog box for spreadsheet documents did not provide the option to include or exclude the following items:
In this dialog box, the All check box was available. | Extended paste special options for spreadsheet documents. |
| Interface. | In actions panel and navigation panel customization forms, the correct picture is set for Move to group command. | In actions panel and navigation panel customization forms, the picture of Move to group command was incorrect. | Eliminated unexpected system behavior. |
Optimization
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application. | The client application interface rendering is now faster. The client application load on the operating system is reduced. | The client application interface rendering was slower and used more operating system resources. | Improved client application usability. |
| Background and scheduled jobs. | Background jobs now start faster. | Background job startup took more time. | Background jobs now start faster. |
| Binary data. | Optimized performance and memory usage of the following 1C:Enterprise script function:
| The performance and memory usage of the following 1C:Enterprise script functions were insufficient:
| Improved performance and stability of several functions that process binary data. |
| Configuration extensions. | Reduced database configuration update time for configuration extensions that do not affect the database structure. | The database configuration update time was longer if the configuration extension did not affect the database structure. | Reduced database configuration update time if the update includes applying changes to the configuration extensions that do not affect the database structure. |
Changes that affect system behavior
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Charts. | The option to display Gantt chart intervals that would occupy less than 2 pixels in the current chart scale is implemented. They are displayed as 2-pixel intervals. | In some cases, Gantt chart intervals that would occupy less than 2 pixels in the current chart scale were not displayed. | Eliminated unexpected system behavior. |
| Data composition system. | The value of ResourcesAutoPosition data composition system parameter does not affect how column totals are displayed in data composition system reports. This change is not implemented in 8.3.11 compatibility mode. | In data composition system report spreadsheets, column totals were not displayed if ResourcesAutoPosition data composition system parameter was set to DontUse. | Eliminated unexpected system behavior. |
| Development tools. | In configuration comparison reports, the description of differences in XDTOPackages properties of Web service object is more detailed. The report includes the list of added and removed packages (with package names included) and their namespace data. | In configuration comparison reports, the description of differences in XDTOPackages properties of Web service object was less detailed. | Eliminated unexpected system behavior. |
| Charts. Spreadsheet documents. | In black-and-white view mode:
In black-and-white printing mode:
This change is not implemented in 8.3.11 compatibility mode. | In black-and-white view mode:
In black-and-white printing mode:
| For spreadsheet document objects, eliminated differences between black-and-white view and black-and-white printing. |
| Charts. | The background patterns used in black-and-white chart printing are based on original chart colors. If a pattern based on an original color is already in use, the next available pattern is used instead. The total number of available patterns in increased to 27. This change is not implemented in 8.3.11 compatibility mode. | The background patterns used in black-and-white chart printing were based on original chart colors (no check for duplicate patterns). The total number of available patterns was 12. | Improved chart view for black-and-white printing. |
| External data sources. | During a configuration update, the platform checks whether the Group property of external data source cube commands and external data source dimension table commands is filled. If the property is not filled, the update is canceled. This change is not implemented in 8.3.11 compatibility mode. | During a configuration update, the platform did not check whether the Group property of external data source cube commands and external data source dimension table commands was filled. | Eliminated unexpected system behavior. |
| Data history. Configuration extensions. | Support of data history is added to native and adopted extension objects. | Native and adopted extension objects did not support data history. | Data history is available for configuration extensions. |
| Spreadsheet documents. | In spreadsheet document headers and footers, the option to specify the first page number is implemented. The following property is implemented: SpreadsheetDocument.FirstPageNumber. In the spreadsheet document headers and footers dialog box, the option to specify the first page number is implemented. When a spreadsheet document is exported to OpenXML or OpenDocument format, the first page number is exported to the respective document property. | This feature was not provided. The number of the first page was always 1. | You can generate spreadsheet documents that match the requirements of regulatory authorities. |
| Internet-enabled functionality. | The platform no longer uses the imaplib library. The behavior of InternetMail object is not changed. The functionality previously provided by the library is now provided by the platform. | 1C:Enterprise used the imaplib library, which provided a part of InternetMail object functionality in compatibility modes Version 8.3.5 and earlier. | Improved platform stability and security. |
| Full-text search. Interface. | The standard full-text search form is updated. The History picture is added to the picture library. | The standard full-text search form looked differently. | Improved usability of the standard full-text search form. |
| Development tools. | The following features are added to the managed form editor:
| These features were not provided. | Improved form editor usability. |
| Data composition system. | If a query parameter belongs to a query language expression that has a name, or the parameter is an independent expression, it is available for use in data composition system data parameteres (however, it is not visible to end users). This change is not implemented in 8.3.11 compatibility mode. | If a query parameter belonged to a query language expression that had a name, or the parameter was an independent expression, it was not included in the list of available data parameters of the data composition system. | Eliminated unexpected system behavior. |
| Dynamic lists. | If a column of a table linked to a dynamic list belongs to a column group with In cell grouping, in a document generated using the Output list command, the column header is taken from the managed form table column header. This change is not implemented in 8.3.11 compatibility mode. | If a column of a table linked to a dynamic list belonged to a column group with In cell grouping, in a document generated using the Output list command, the column header was:
| Eliminated unexpected system behavior. |
| Automated testing. | The option to set and get timeouts for automated testing operations is implemented. For TestedApplication object, methods SetActionTimeout() and GetActionTimeout() are implemented. Clarified wordings of error messages related to attempts to connect to and/or operate applications being tested. | The option to set and get timeouts for automated testing operations was not available. Wordings of error messages related to attempts to connect to and/or operate applications being tested were less detailed and less accurate. | You can set timeouts for automated testing operations. Improved diagnostics for automated testing errors. |
| Spreadsheet documents. | If a spreadsheet document has docked rows or columns, the lines that outline the docked areas are only displayed after the document has been scrolled vertically (for rows) or horizontally (for columns). This change is not implemented in 8.3.11 compatibility mode. | If a spreadsheet document had docked rows or columns, the lines that outlined the docked areas were always displayed. | Improved report view. |
| Managed forms. | If the width specified for a managed form group is less than the total width of its subordinate items (at their minimum possible sizes), the specified width value is ignored. Instead, the width is calculated as follows:
This change is not implemented in 8.3.11 compatibility mode. | If the width specified for a managed form group was too small and some of the subordinate items could not fit even at their minimum possible sizes, the group still had the specified width. | Eliminated unexpected system behavior. |
| Queries. | An attempt to execute a query that contains a nested query with AUTOORDER keyword generates the following error: Nested queries cannot contain AUTOORDER operation. | An attempt to execute a query that contained a nested query with AUTOORDER keyword generated the following error: Nested queries cannot contain ORDER BY operation without TOP construction. | The error message is more accurate. |
| Configuration extensions. | Notifications related to applying configuration extensions have Important status. Therefore, they are available in the notification center and users who miss them can read them later. | Notifications related to applying configuration extensions had Information status. Therefore, they were not available in the notification center and, if errors occurred when applying configuration extensions, users who missed the notifications at the time they were generated missed them completely. | Better diagnostics of errors related to applying configuration extensions. |
| Data composition system. Dynamic lists. | When a new parameter that is a part of IN clause is added to a data set query, the data composition schema wizard automatically sets the option to use a value list as the parameter value. If a description of a query parameter that is a part of IN clause is missing from a data composition schema, the option to use a value list as the parameter value is automatically added to the available parameter of the source of available data composition settings. If a parameter of a dynamic list query is a part of IN clause, you can assign a value of value list type to this parameter in the dynamic list composition settings, and the dynamic list will pass the correct value list to the query. This change is not implemented in 8.3.11 compatibility mode. | The data composition schema wizard did not automatically set the option to use a value list as the value of a data composition schema parameter. If a parameter description was missing from a data composition schema, only a single value could be used as the parameter value. Dynamic lists processed query parameters of value list type incorrectly. | Eliminated unexpected system behavior. Improved data composition system behavior in scenarios where queries use value lists to set filters. |
| Data composition system. | In the data composition system, header templates (available for reports, tables, groupings, and charts) are not followed by blank line templates. As a result, a table or a chart header is always followed by a single blank line. This change is not implemented in 8.3.11 compatibility mode. | In the data composition system, header templates (available for reports, tables, groupings, and charts) were followed by blank line templates. As a result, a table or a chart header was always followed by two blank lines. | Eliminated unexpected system behavior. A table or a chart header is now followed by a single blank line instead of two blank lines. |
| Standard functions. | In the standard full-text search management function, the option to set the maximum size of objects to be indexed and the option to set the number of background jobs used for indexing are implemented. To set these parameters, use the dialog box that is opened using the Additional parameters button of the standard full-text search management function form. | This feature was not provided. | You can specify additional parameters for full-text search indexing. |
| Spreadsheet documents. | In the thin client, when a spreadsheet document is saved to a PDF file, if the spreadsheet page size is not specified, the page size setting of the current printer is used instead. This change is not implemented in 8.3.11 compatibility mode. | In the thin client, when a spreadsheet document was saved to a PDF file, if the spreadsheet page size was not specified, size A4 was used instead. | Eliminated unexpected system behavior. |
| Data display. | In Designer, thin client, and thick client, in the font selection dialog box, when you select a font by name (for example, "Arial"), the Scale value is applied to the resulting font. This change is not implemented in 8.3.11 compatibility mode. | In Designer, thin client, and thick client, in the font selection dialog box, when font was selected by name (for example, "Arial"), the Scale value was not applied to the resulting font. | Eliminated unexpected system behavior. |
| Data composition system. | In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag does not set that flag to its parent parameter. This change is not implemented in 8.3.11 compatibility mode. | In managed applications, during interactive editing of appearance and ouput parameters of the data composition system, setting a parameter usage flag also set that flag to its parent parameter. | Eliminated unexpected system behavior. |
| Managed forms. | In the property palette, the field linked to the font property displays the font name, style, appearance (bold, italic, or strikethrough), and scale. | In the property palette, the field linked to the font property displays the font name and style. | You can view the current font parameters in the property palette, without opening the font dialog box. |
| Technological log. | Updated the <ADMIN> event content and description in the documentation and in the technological log configuration file editor. (read more) | The <ADMIN> event content and description in the documentation and in the technological log configuration file editor were incorrect. | The technological log configuration file editor is now up-to-date. |
| Managed forms. | Implemented the new AlwaysHorizontal value of the ChildFormItemsGroup system enum. The Horizontal value of the ChildFormItemsGroup system enum is deprecated If the Horizontal value is used in the application, the PC platform wil use the AlwaysHorizontal value, and the mobile platform – the HorizontalIfPossible value instead. We recommend to replace the Horizontal by the HorizontalIfPossible value in applications in most cases. The AlwaysHorizontal value should be used only if a group must be horizontal on any screen, including mobile device screens. For example, if there is a group with an input field and a button with a picture and without text, linked to this field. | The following options of horizontal alignment of forms and form groups were available: Horizontal and HorizontalIfPossible. | The smooth conversion of previously created form to the mobile client usage is available. |
Changes that require modification of configuration and administrative settings
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Settings storage. | If a report form is opened with UserSettingsKey parameter specified and UserSettings parameter missing:
This change is not implemented in 8.3.11 compatibility mode. | If a report form was opened with UserSettingsKey parameter specified and UserSettings parameter missing:
| Eliminated unexpected system behavior. |
| Client application installation. | 1C:Enterprise launcher searches for distribution packages of new 1C:Enterprise versions in the following directories: Setup (32-bit platform) and Setup64full (64-bit platform). | 1C:Enterprise launcher searched for distribution packages of new 1C:Enterprise versions only in directories that contained specific versions (ignoring subdirectories). | Automatic client application updates support scenarios where client applications are both 32-bit and 64-bit. |
| Charts. | When OnIntervalEditEnd handler of a form item that displays a Gantt charts is executed:
This change is not implemented in 8.3.11 compatibility mode. | When OnIntervalEditEnd handler of a form item that displays a Gantt charts was executed:
| The behavior of OnIntervalEditEnd handler of form items that display Gantt charts is more logical. |
| Event log. | Interactive editing of event log format is implemented. The new event log event _$InfoBase$_.EventLogSettingsUpdate indicates the format change. In file infobases, changing event log format requires exclusive infobase access. Global context method ClearEventLog() is deprecated and only applicable to logs that have SQLite format. It is recommended that you do not use this method. If selection from event log records takes a long time, you can abort it by deleting the session that initiated the selection. The following limitations are applied to time-consuming selections from the event log:
The default event log format (the one that is selected in newly created infobases) is sequential format. | Interactive editing of event log format was not available. The default event log format (the one that was selected in newly created infobases) was SQLite format. | Interactive selection of event log format is now available. Applications no longer stop responding when performing time-consuming selections from the event log. |
| Temporary storages. | If the Address parameter of PutToTempStorage() method contains a value that was previously used in DeleteFromTempStorage() method, an exception is generated. This change is not implemented in 8.3.11 compatibility mode. | If an Address parameter value was previously used in PutToTempStorage() method and then in DeleteFromTempStorage() method, an attempt to use the value in PutToTempStorage() method again was only successful if it was a UUID of a form that was open at that time. | Eliminated unexpected system behavior. |
| Charts. | The algorithm of displaying stacked charts that have negative values is changed:
This change is not implemented in 8.3.11 compatibility mode. | In stacked charts, each point had a single column that represented the sum of all values (calculated with appropriate signs). | Eliminated unexpected system behavior. |
| Data composition system. | In data composition settings composer, when the source of user-defined settings is specified, if a data parameter value contains an array and the option to use a value list in this parameter is enabled, the parameter value is set to a value list containing all of the values from the source array. This change is not implemented in 8.3.11 compatibility mode. | In data composition settings composer, when the source of user-defined settings was specified, if a data parameter value contained an array and the option to use a value list in this parameter was enabled, the parameter value was set to a value list containing a single value (the default value for the parameter value type). | Eliminated unexpected system behavior. |
| Managed forms. | When form item properties DataPath, FooterDataPath, HeaderDataPath, TitleDataPath, and RowPictureDataPath are set from 1C:Enterprise script or a configuration with these properties is loaded from a file, if any of these properties contains a path that refers to a form item that has a row index, an error is generated. This change is not implemented in 8.3.11 compatibility mode.
| When form item properties DataPath, FooterDataPath, HeaderDataPath, TitleDataPath, and RowPictureDataPath were set from 1C:Enterprise script or a configuration with these properties was loaded from a file, if any of these properties contained a path that referred to a form item that had a row index, no errors were generated. Such property values were set but they were actually ignored. | Eliminated unexpected system behavior. |
| Dynamic lists. | In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as Ref.Products.Product.[State of origin]) are not available for filtering, sorting, or grouping. This change is not implemented in 8.3.11 compatibility mode. | In a source of available data composition system settings for a dynamic list, subordinate characteristic fields of tabular section fields retrieved using dot (such as Ref.Products.Product.[State of origin]) were available for filtering, sorting, or grouping. However, an attempt to set a filter by a value of such field returned an error. | Eliminated unexpected system behavior. |
| Data composition system. | If an expression of a calculated data composition system field is empty, NULL is substituted for the field value in detailed records. This change is not implemented in 8.3.11 compatibility mode. | If an expression of a calculated data composition system field was empty, an attempt to use the field in detailed records generated a "field not found" error. | Eliminated unexpected system behavior. The system behavior is improved in scenarios where a user selects a custom field with no expression specified. |
| Data composition system. | If calculation of EvalExpression() function result includes division by 0, the result of the expression calculated with this function is Division by zero. This change is not implemented in 8.3.11 compatibility mode. | If calculation of EvalExpression() function result included division by 0, the expression calculated with this function was fully calculated (Division by zero was used as the function result). | Eliminated unexpected system behavior. |
| Settings storage. | Each operation with the standard settings storage includes a check for SaveUserData access right. Calls of StandardSettingsStorageManager.SetDescription() method include a check for SaveUserData access right. | Operations with the standard settings storage included checks for SaveUserData access right only if they were performed from 1C:Enterprise script. Calls of StandardSettingsStorageManager.SetDescription() method did not include a check for SaveUserData access right. | Eliminated unexpected system behavior. In particular, commands related to dynamic list settings are no longer available to users that do not have SaveUserData access right. |
| Data composition system. | Items of conditional appearance of data composition system are applied using the following rules:
This change is not implemented in version 8.3.11 compatibility mode. | Items of conditional appearance of data composition system were applied using the following rules:
| Eliminated unexpected system behavior. |
| Data composition system. | In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field affects the filter presentation. This change is not implemented in version 8.3.11 compatibility mode. | In report and dynamic list forms, when a filter by a data composition field is applied, the qualifier of that field did not affect the filter presentation. | Improved filter presentations in dynamic lists and data composition system-based reports. |
| Infobase operations. | When administrative infobase parameters are set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior is different from that of the previous versions. For details, see 1C:Enterprise documentation. | When administrative infobase parameters were set from 1C:Enterprise script within a transaction, 1C:Enterprise behavior was different. This behavior was not documented. | Setting administrative infobase parameters is more intuitive and predictable. |
| Interface. | In managed applications, calls of SwitchInterface() global context method are ignored in all client modes. We recommend that you do not use ordinary forms in managed client application mode. This change is not implemented in version 8.3.11 compatibility mode. | In managed applications, calls of SwitchInterface() global context method displayed command bars. | Eliminated unexpected system behavior. |
| 1C:Enterprise script. | When CurrentLanguage() global context function is called on the server, in the thick client, or in an external connection, it returns the interface language of the current user. If the current user is not specified, or the interface language is not specified, or the specified interface language is not included in the configuration, the function returns the default configuration language. The CurrentLanguage() function behavior is now uniform across all modes. This change is not implemented in version 8.3.11 compatibility mode. | When CurrentLanguage() global context function was called on the server, in the thick client, or in an external connection, if the interface language specified for the current user was not included in the configuration, the function returned Undefined. The CurrentLanguage() function behavior on the client and on the server was not uniform. | Eliminated unexpected system behavior. |
| Data composition system. | In a nested query included in the right part of a left join, its WHERE section does not include an explicitly specified field, and the parent query includes a different field with the same data composition name, the template composer does not include the filter to the nested query. To preserve the previous query behavior, explicitly specify a field in the WHERE section. This change is not implemented in version 8.3.11 compatibility mode. | When filling available data set fields, the template composer always included the filter in the nested query. | The result of automatic filling of available data set fields is more predictable. |
| Internet-enabled functionality. | In InternetMail.Logon() method, implemented authentication request with the user name and password if APOP authentication fails. | The InternetMail.Logon() method generated an exception if APOP authentication failed. The authentication attempt with the user name and password was not performed. | The user authentication on the mail server better complies with RFC 1939 standard. |
| Managed forms. | In OpenForm() method, changed the algorithm of searching for an open form instance.
This change is not implemented in version 8.3.11 compatibility mode. | The following algorithm of searching for an open form instance was used.
| Eliminated unexpected system behavior. Unified the algorithm that searches for an open form in different client application modes. |
Renamed objects
Mobile platform
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Managed forms. | On Android, context menus are displayed next to the items where they belong. Opening a context menu does not change the form layout. | The context menu was displayed at the top of a form. Opening a context menu changed the form layout and repositioned form items. | On Android, improved usability of accessing context menus of form items. |
| Mobile device-specific features. | Optimized MultimediaData object generation algorithm used during device camera operations. | The MultimediaData object generation algorithm used during device camera operations was not optimal. | Improved performance of device camera operations in mobile applications. |
| Interface. | Changed the calendar view on mobile devices:
| The calendar view on the mobile device was different:
| Improved calendar usability on mobile devices. |
Library updates
Transition from the previous version to the version 8.3.12
- Conversion of configurations, infobases, external data processors and external reports is not required during the transition from the previous version to the version 8.3.12.
- Some features that are added in version 8.3.12 do not support compatibility mode. When you toggle the compatibility mode, the structure of some database objects is changed. To be able to work with the infobase using a previous platform version, you have to turn the compatibility mode on.