- New functionality and changes
- New functionality and changes in the 1C:Enterprise mode
- Changes that affect system behavior
- Changes that require modification of configuration and administrative settings
- Renamed objects
- Mobile version of "1C:Enterprise"
- Demo configuration changes
- Changes made after the publication of the version
- Transition from the previous version to the version 8.3.16
|Functionality||After||Before||Result of changes|
|Configuration properties.||For configuration property Compatibility mode, new value Version 8.3.15 is now implemented.||Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.14 was available.||Configurations developed using 1C:Enterprise platform version 8.3.15 or earlier can now run on version 8.3.16 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.16 in two stages: first, update the platform version (without any changes to the configuration), and then make the required changes and disable compatibility mode. This also gives you the option to open the infobase using version 8.3.15 after the migration to version 8.3.16, even if you disable the compatibility mode (simply enable it again).|
|System requirements.||Implemented Programming Training Version running on Linux and macOS.||Programming Training Version ran on Windows only.||Programming Training Version runs on all supported operating systems.|
|System requirements. macOS.||OS X family (version 10.11 or under) is no longer supported. Client application runs on macOS only (version 10.12 or above).||Client application could run on OS X (version 10.8 or above).||Outdated operating systems are no longer supported.|
|Server clusters. Administration tools.||In client/server mode, you can now limit the number of logon attempts with an incorrect password.
The following parameters are implemented for the infobase: maximum number of failed authentication attempts before a user is blocked; a time interval during which a user who made a threshold number of authentication attempts cannot attempt authentication again; username suffixes that should be used if it is necessary to authenticate as a blocked user.
New global context property: AuthenticationLock.
New form to view authentication locks in Designer (Administration – Authentication locks). This command is available only to a user with administrative rights.
Implemented the following event log events:
||This feature was not provided. The platform did not prevent someone from guessing the password by going through the options.||Reduced the likelihood of guessing the infobase user password by going through the options.|
|Queries.||New feature: the query language now supports grouping sets. Upgrade: the query language now supports keywords GROUPING SETS for sentence GROUP BY. New query language function that allows you to determine whether a function parameter can be grouped: GroupedBy().||This feature was not provided.||Upgrade: grouping by several field sets is faster because grouping is performed per table scan.|
|Charts. Data composition system.||When using charts, you can now save a map between an object (displayed by different charts) and its color. For charts displayed on the form, 1C:Enterprise code is required for this. For the data composition system, this feature is available using settings. A map between an object and its color is saved to the settings system storage. Implemented the Chart.FillSeriesColors() method. For objects DataCompositionOutputParametersValues, DataCompositionGroupOutputParametersValues, DataCompositionChartOutputParametersValues, and DataCompositionAreaChartAppearance, implemented properties ChartType.ColorsSaving and ChartType.ColorsSavingKey. New property: ProcessorOfDataCompositionResultOutputToSpreadsheetDocument.AppearanceForValues. New property: DataCompositionAreaChartGroupTemplate.Presentation.||This feature was not provided. The same object could be displayed by charts with a different color, resulting in bad report readability.||The same object can be displayed by charts with the same color that helps make charts look better and more informative.|
|Collaboration system.||When using the collaboration system, you can now share your PC screen on a video call. In the web client, screen sharing is available only in Google Chrome and Mozilla Firefox. In the web client, Google Chrome supports sharing of the current web browser tab.||This feature was not provided.||Expanded the collaboration system capabilities.|
|Collaboration system.||On setting the CollaborationSystemMessage.Text property of the FormattedString type from 1C:Enterprise code, appearance is saved (except pictures to be deleted). This message is displayed by the system considering its formatting. A message with appearance cannot be created interactively. Smileys set by emoticons (Unicode characters) are now supported.||This feature was not provided.||New operations with collaboration system messages.|
|Administration tools. Server clusters.||You can now get a server cluster version using program administration interfaces. Getting a server cluster version is only available if a server cluster is running 1C:Enterprise version 8.3.11 or above. Implemented ServerAdministration.GetVersion() method. Implemented the agent version command of the rac utility.||This feature was not provided.||On program administration of the server cluster, you can now determine which features can or cannot be used depending on 1C:Enterprise version the server cluster is running on.|
|Spreadsheet documents. Formatted documents.||On saving a PDF document, the OpenType font is now available if it is used in appearance of the document to be saved.||This feature was not provided. On saving to the PDF format, only TrueType fonts were embedded.||Improved compatibility of PDF documents generated by 1C:Enterprise with different PDF document display devices.|
|Charts.||You can now interactively change values displayed by charts of the following kinds: a line, a step, and an area (including summarized and normalized series). This feature is not provided in 8.3.15 compatibility mode. Implemented the ValuesEditMode property for Chart and ChartSeries objects. New property: ChartValue.EditMode. New event for the chart form field extension: OnEditValue. The form field extension event for the OnChangeAreaContent spreadsheet document will be called upon interactive editing of a chart and a Gantt chart inserted into the spreadsheet document. The AdditionalParameters parameter is implemented in the handler. This change is not implemented in 8.3.15 compatibility mode.||This feature was not provided. The form field extension event for the OnChangeAreaContent spreadsheet document was not called upon interactive editing of a Gantt chart inserted into the spreadsheet document.||Improved chart interactivity.|
|Web client.||You can now embed the web client in third-party sites and ensure the web client interacts with these sites. New global context property: ExternalSiteWindow. Implemented the ClientApplicationMainWindowMode.EmbeddedWorkplace system enumeration value. Implemented the MainWindowMode command-line command for the client application and web client. Implemented the following access rights, which allow you to start the client application in a main window mode: StandardMainWindowMode, MainWindowModeWorkplace, MainWindowModeEmbeddedWorkplace, MainWindowModeFullScreenWorkplace, and MainWindowModeKiosk. Implemented Embedded WebClient API, which allows a site to interact with the web client.||This feature was not provided. It was impossible to embed the web client in a third-party site.||Advanced web client features.|
|Spreadsheet documents.||New feature: you can save a spreadsheet document to PDF/A-2 and PDF/A-3 (versions of the PDF/A format used for long-term storage). New values for the SpreadsheetDocumentFileType system enumeration: PDF_A_2 and PDF_A_3. Implemented two syntax options for the SpreadsheetDocument.Write() method. Implemented the Attachments parameter for the SpreadsheetDocument.BeginWriting() method. New objects: ReadPDF and WritePDF.||It was possible to save a spreadsheet document to PDF/A-1 only.||Expanded spreadsheet document export features.|
|Charts of characteristic types.||Implemented the FullDescription() method for ChartOfCharacteristicTypesRef and ChartOfCharacteristicTypesObject objects.||This feature was not provided.||Unified behavior of the chart of characteristic types and the catalog for getting an item presentation based on hierarchy.|
|Spreadsheet documents.||New feature: you can write a spreadsheet document (using the SpreadsheetDocument.Write() method in an option for writing to a stream) to a stream as XLSX.||It was not possible to write a spreadsheet document (using the SpreadsheetDocument.Write() method in an option for writing to a stream) to a stream as XLSX.||Expanded features of spreadsheet document export to streams.|
|Configuration extensions.||You can now create the following objects in a сonfiguration extension:
||These features were not provided.||Extended configuration extension options.|
|Managed forms.||New feature: you can generate a planner context menu from 1C:Enterprise code and specify an action called upon clicking (depending on the click area). New events for the form field extension for the planner field: GenerateCommandsProcessing, DimensionItemClick, TimeScaleItemClick, and WrappedTimeScaleHeaderClick. New properties for the form field extension for the planner field: TimeScaleItemHyperlink, DimensionItemHyperlink, and WrappedTimeScaleHeaderHyperlink.||These features were not provided.||New planner features.|
|Managed forms.||New feature: you can use a search string for a form table that displays a value table, a value tree, or a value list. Search history is stored in the system settings storage with the following key: Common/TableSearchHistory/<Form name>.<Table name>. This change is not implemented in 8.3.15 compatibility mode. New feature: you can use the Find by current value command in all form tables ignoring сonfiguration compatibility mode.||The search string was available only for form tables that displayed a dynamic list. In other tables, search was done using the standard dialog box, which performed positioning. Search by current value was not available.||Improved search in tables of managed forms, including a pictorial view of searching in the table.|
|Data composition system. Pictures.||New feature: you can use pictures for conditional appearance of reports in the data composition system. New property: DataCompositionAppearance.Picture. New pictures in the picture library: AppearanceGreenUpTriangle, AppearanceYellowHyphen, AppearanceRedDownTriangle, AppearanceGreenUpArrow, AppearanceGreenUpInclineArrow, AppearanceYellowUpInclineArrow, AppearanceYellowRightArrow, AppearanceYellowDownInclineArrow, AppearanceRedDownArrow, AppearanceRedDownInclineArrow, AppearanceGrayUpArrow, AppearanceGrayUpInclineArrow, AppearanceGrayRightArrow, AppearanceGrayDownInclineArrow, AppearanceGrayDownArrow, AppearanceGreenCircle, AppearanceYellowCircle, AppearanceRedCircle, AppearanceBlackCircle, AppearanceCharCheckBox, AppearanceCharExclamationMark, AppearanceCharCross, AppearanceCheckBox, AppearanceExclamationMark, AppearanceCross, AppearanceGreenFlag, AppearanceYellowFlag, AppearanceRedFlag, AppearanceFullStar, AppearanceHalfFullStar, AppearanceEmptyStar, AppearanceFilledCircle, AppearanceThreeQuartersFilledCircle, AppearanceTwoQuartersFilledCircle, AppearanceOneQuarterFilledCircle, AppearanceEmptyCircle, AppearanceFourFilledBoxes, AppearanceThreeFilledBoxes, AppearanceTwoFilledBoxes, AppearanceOneFilledBox, and AppearanceEmptyBoxes. In conditional appearance, you can use only the above pictures from the picture library. If the сonfiguration already has pictures with the same names, a picture from the сonfiguration is added to the collection and a warning is generated upon сonfiguration update.||This feature was not provided. Conditional appearance of the data composition system did not allow you to use pictures for conditional appearance of reports.||Specifying pictures in conditional appearance of reports built using the data composition system is now easier.|
|Pictures.||For common pictures, you can now specify that a common picture is used:
||This feature was not provided.||New feature: you can specify which common pictures can be used when working with a spreadsheet document in 1C:Enterprise mode and conditional appearance. As a result, there are less pictures a user can select from in these situations.|
|XML and XDTO support.||New feature: the platform supports XSD schemas containing types, in which attributes are defined via references to global attributes, but overriding such properties as default or fixed ones.||Upon trying to use in the platform XSD schemas containing types, in which attributes were defined via references to global attributes, but overriding such properties as default or fixed ones, errors occurred when checking the XDTO model, and such schemas were not available.||Eliminated unexpected system behavior.|
|Charts. Data composition system.||You can now build combo charts and display a secondary value scale for the following chart types:
||It was impossible to build combo charts and display a secondary value scale. The Chart.ChartType property value is Column3D by default. The Chart.Outline property value is True by default.||New chart features.|
|Server clusters.||You can now start backup working processes. A backup working process is started in advance and server cluster overhead is synchronized for it. This feature allows you to reduce the time spent on switching the client application to a new working process in case of unexpected termination of the working process serving this client application.
A flag indicating whether backup is required is set for the infobase. The number of backup working processes is calculated from the Number of infobases per process working server property.
New properties: AdministrationInfobase.WorkingProcessesBackup and AdministrationWorkingProcess.Backup.
The following Java-based methods are implemented in the administration server interface: IWorkingProcessInfo.isReserve(), IInfobaseInfo.getReserveWorkingProcesses(), and IInfobaseInfo.setReserveWorkingProcesses().
The following items are implemented for the cluster service command-line utility (rac):
||This feature was not provided. A new working process was started only after the current working process was terminated, which could lead to significant time delays upon client application reconnection. From the user's point of view, it looked like the client application interface froze at the time of connection to a new working process.||Reduced time delays resulting from switching the client application to a new working process. Improved application reactivity.|
|Functionality||After||Before||Result of changes|
|Managed forms.||In the client application form table that displays the value tree (including the All functions dialog box), search using the search string is done considering a parent and by words. In the history form, record date and time are no longer involved in search.||In the client application form table that displays the value tree, search was done ignoring a parent and by substring. In the history form, record date and time were involved in search.||Improved search in client application form tables that display trees (including in the All functions dialog box).|
|Web client. File operations.||Upgrade: security check of access to the file system and clipboard when accessing the web client in Google Chrome and Mozilla Firefox (including web browser extensions and file system extensions) is updated. Once the web browser extension and the file system extension are updated, if it is required to get access to the file system, a user will have to confirm that they trust the site (where the web client is published) to use the file system on their local computer. After that, there are no question until this permission is revoked (using settings of the web browser extension). If the user refuses to trust it, the old mechanism for getting permissions is used (a separate request per action). Clipboard operations are allowed accordingly. Permissions are stored broken down by site addresses where web clients are published.||In the web client, a separate question was displayed to a user upon each file operation, which was not user-friendly.||Simplified file operations in the web client regarding the user permission on operations with the file system and clipboard.|
|Collaboration system.||New feature: the user history now displays whether this user participates in a context conversation regarding an object associated with a form in the history. Optimized user history opening.||The user history did not display whether this user participated in a context conversation regarding an object associated with a form.||In the history, it is now easier for a user to find object forms, in the context conversation of which this user was a message recipient.|
|Functionality||After||Before||Result of changes|
|Client application. Server clusters.||Improved performance of 1C:Enterprise platform running on Windows 8 or above when the client application and the server cluster are on the same computer.||Performance of 1C:Enterprise platform running on Windows 8 or above when the client application and the server cluster were on the same computer was less optimal. Interprocess interactions took more time.||Improved performance of 1C:Enterprise running on Windows 8 or above.|
|Spreadsheet documents.||Reduced amount of RAM used by a spreadsheet document that contains many text cells.||A spreadsheet document with many text cells needed more space in RAM.||A spreadsheet document now uses smaller amount of RAM.|
|Server clusters.||Improved performance of the server cluster when working with a large amount of session data. Managed form opening, a context server call, and temporary storage operations take less time now. New technological log event: <SDGC>.||The server cluster spent more time on handling a large amount of session data. Managed form opening, a context server call, and temporary storage operations took more time.||Improved server cluster performance.|
|Accumulation registers.||Improved performance of a virtual table of accumulation register balance.||When using a virtual table of accumulation register balance, more time was spent on getting the query result.||Improved performance of a virtual table of accumulation register balance.|
|Queries.||Optimized execution of query in client/server infobase mode, that includes the query language operator IN with a list of values, if the left section of IN operator contains a reference type field that includes several main tables, and the list of values contains references to different tables (from the list of composite type values) but not the Undefined value. This change is not implemented in 8.3.15 compatibility mode.||The query in client/server infobase mode, that includes the query language operator IN with a list of values, if the left section of IN operator contains a reference type field that includes several main tables, and the list of values contains references to different tables (from the list of composite type values) but not the Undefined value, took more time to execute.||Optimized execution of queries containing IN operator with composite type fields.|
|Internet-enabled functionality.||Optimized retrieving of email message headers using the InternetMailMessage.GetHeaderField() method.||Retrieving email message headers using the InternetMailMessage.GetHeaderField() method took a considerable amount of time.||Optimized email message headers retrieving.|
|Functionality||After||Before||Result of changes|
|Data display.||Upgrade: client applications (except the web client) running on macOS, Linux, and Windows are switched to graphics based on the Cairo library.||Client applications (except the web client) running on macOS, Linux, and Windows used their own graphics based on different technologies and libraries in each operating system.||Unified and optimized user interface display in supported operating systems.|
|Web client, web service, and HTTP service publishing tools.||In the dialog box for publishing the сonfiguration on a web server, labels now comply with the current client applications of the platform.||In the dialog box for publishing the сonfiguration on a web server, labels did not consider the mobile client.||The dialog box for publishing the сonfiguration on a web server considers the mobile client.|
|Full-text search.||New feature: full-text search by hashtag became available (strings of the #Word format, from the # character to the first space). To apply fuzzy search (both in interactive mode and search from 1C:Enterprise code using the FullTextSearchManager object), use the ~ character. This change is not implemented in 8.3.15 compatibility mode.||Search by hashtag was not supported but it was possible to find a hashtag value (the word after the # character) in the usual way or by double quoting a hashtag to search for. The # character was used for fuzzy search.||You can now hashtag objects involved in full-text search. As a result, it became possible to simply find several different types of objects grouped by hasgtag only.|
|Access rights.||If the access rights do not allow saving a spreadsheet document, a text document, a graphic chart, a geographical diagram, a package of displayed documents or an HTML document to the file, but after creating these objects, privileged mode was enabled, then the file can be saved.||If access rights did not allow saving a spreadsheet document, a text document, a graphic chart, a geographic diagram, a package of displayed documents or an HTML document to a file, then enabling privileged mode was ignored and the the files could not be saved.||Eliminated unexpected system behavior.|
|Input by string.||When using input by string for a managed application, all searched words are highlighted in search results if full-text search is not used for input by string or full-text search failed with an error. If full-text search in data is used for input by string, the The method of searching for the specified string during the input by string setting is ignored upon successful application of full-text search, the searched text is always split into words, and search is based on the beginning of the words. This change is not implemented in 8.3.15 compatibility mode.||When using input by string for a managed application, if full-text search was not used for input by string or full-text search failed with an error, two consecutive occurrences of the same string were not highlighted and only the first occurrence of the searched word was highlighted in the first half of results (when searching for one word).||Improved search result highlighting for input by string.|
|Data display.||With the Windows operating system, stability and responsiveness of the client application are improved when working with unavailable printers.||With the Windows operating system, there were some issues when working with unavailable printers, such as unexpected shutdown of the client application and a significant slowdown upon client application start.||With the Windows operating system, stability and responsiveness of the client application are improved when working with unavailable printers.|
|Server clusters.||This change is rolled back. New feature: parallel recalculation of register totals is available upon infobase restructuring, testing, and repair. System background jobs are used for recalculation. ID of such a background job is SystemBackgroundJob.RecalcTotals. Implemented the Number of totals recalculation job parameter for the Infobase parameters dialog box. There are 4 recalculation background jobs by default. New global context methods: GetTotalsRecalculationJobsCount() and SetTotalsRecalculationJobsCount().||Register totals were recalculated sequentially upon infobase restructuring, testing, and repair for all required infobase registers.||New feature: totals are recalculated faster upon infobase restructuring, testing, and repair.|
|Automated testing.||You can now use form item additions in automated testing. Implemented the FormItemAdditionToTest object. For the FormTableToTest object, the result returned by GetSubobjects(), GetObject(), FindObjects(), and FindObject() methods can include objects of the FormItemAdditionToTest type. For the FormTableToTest.NavigateLevelDown() method, implemented the RowDetails parameter that allows you to specify presentation of a child group to go to. For the FormTableToTest.NavigateLevelUp() method, implemented the RowDetails parameter that allows you to specify presentation of a parent group to go to. For the FormTableToTest.Expanded() method, implemented the RowDetails parameter that allows you to specify presentation of a row of a table, for which it is necessary to check whether this row is collapsed or expanded. For the FormTableToTest.CanExpand() method, implemented the RowDetails parameter that allows you to specify presentation of a table row, for which the expanding feature is being checked. Implemented the FormFieldToTest.GetStateDisplay() function that returns the current state of a spreadsheet document field. Implemented the ApplicationToTest.WaitForState() function intended for waiting within the specified time. Implemented the FormGroupToTest.CurrentOpened() function that returns a group status: collapsed or expanded. Implemented the FormButtonToTest.CurrentCheckBox() function that indicates whether the button is pressed or displays the check box. A reference to the function that will return the notification processing result to the platform can be passed to the ExecuteNotificationProcessing() method now.||These features were not provided.||Extended automated testing capabilities. New features of the Taxi interface are considered in the functionality.|
|Managed forms. Configuration extensions.||The adopted form editor now displays changed and unchanged adopted form items with different colors. The form editor command that allows you to display only changed adopted and own form items in the form item tree is now available. The extension object property panel now displays properties of a сonfiguration object changed in the extension in relation to the extendable сonfiguration with another color. The extension object property panel now has a command that shows only properties that were changed in relation to the extendable сonfiguration.||In the adopted form editor, it was impossible to hide unchanged adopted items in the form item tree. Form items were not distinguished by color. In the property panel, it was not possible to quickly distinguish between changed and unchanged properties of an adopted configuration object.||New feature: easier editing of adopted сonfiguration objects.|
|Dynamic lists.||The dynamic list does not support fields with different expressions for selection and filtering as key fields. This change is not implemented in 8.3.15 compatibility mode.||It was possible to use fields with different expressions for selection and filtering as the key fields of the dynamic list. In this case, the dynamic list operation could cause various hard-to-diagnose errors.||Eliminated unexpected system behavior.|
|Spreadsheet documents.||When opening a spreadsheet document in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format in 1C:Enterprise, conditional formatting is only imported for the area of the source document that contains data. Conditional formatting import now has reduced RAM consumption. When viewing a spreadsheet document obtained after import, there may be situations when the formatting of the resulting document differs from the source document (design of the document area that does not contain data).||When opening a spreadsheet document in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format in 1C:Enterprise, conditional formatting was not imported for the whole document. In this case, a session could abnormally terminate due to lack of RAM.||Improved 1C:Enterprise stability when importing spreadsheet documents in Microsoft Office OpenXML (*.xlsx) or Microsoft Excel (*.xls) format, when conditional formatting is set for the whole sheet, and not just for a meaningful area.|
|Data composition system.||The type of data composition system field that results from using the query language aggregate functions SUM() and AVERAGE() will be an unlimited length number. This change is not implemented in 8.3.15 compatibility mode.||The type of data composition system field that resulted from using the query language aggregate functions SUM() and AVERAGE() was the type of field, which was used as parameter for these aggregate functions.||Eliminated unexpected system behavior.|
|DBMS operations.||The data (Purpose field) returned by the GetDBStorageStructureInfo() global context method contains information that describes the tables that are created using the database copy functionality.||The data returned by the GetDBStorageStructureInfo() global context method did not contain information that described the tables that are created using the database copy functionality. The Main value was specified as the table purpose for all the tables after using the database copy functionality.||Eliminated unexpected system behavior.|
|Spreadsheet documents.||When displaying a spreadsheet document containing pictures in cells or pictures of the Picture type:
||When displaying a spreadsheet document containing pictures in cells or pictures of the Picture type, the system behaved as follows:
||Corrected spreadsheet document pictures display.|
|Client application form.||The addon menu of the Search management form item contains only the appropriate commands, that is: search by current value, advanced search, search history, cancel search). This change is not implemented in 8.3.15 compatibility mode.||The addon menu of the Search management form item contained all the commands of the linked form table (similar to autofilling the table command bar). Visibility was turned off for "excess" commands.||Eliminated unexpected system behavior.|
|Full-text search. Server clusters.||When the UpdateIndex() method of the full-text search manager is called in the client/server infobase mode, preparatory actions are performed using the system background job (its parameters are similar to the system indexing background job). This background job runs on the same working server as the full-text search service. When you click the Refresh Index button of the Full-text search management standard function, the system behavior will be the same. If a single task is configured in the full-text search settings, it will be performed in a separate background job.||When the UpdateIndex() method of the full-text search manager was called in the client/server infobase mode, preparatory actions were performed at the same computer the method was called from. If a single indexing task was configured in the full-text search settings, it was performed in a common server execution thread.||Improved reliability and speed of full-text search indexing. All the indexing actions are performed on the working server, assigned for running the full-text search service.|
|Functionality||After||Before||Result of changes|
|Queries.||Upon query execution in the infobase file mode, if a number cannot be represented with the required accuracy, an exception is thrown.||Upon query execution in the infobase file mode, if a number cannot be represented with the required accuracy, a number where all digits are 9s is put in the query result.||Eliminated unexpected system behavior.|
|Administration tools.||Implemented Java 9 or later support for the administration server interaction interface from Java.||The administration server interaction interface from Java did not support Java version 9 or later. Only Java version 1.8 was supported.||Implemented support for modern Java versions.|
|Software licensing.||When running commands, the licensing utility sends unattended statistical information to 1C:Remote service by default. You can now deactivate this action when running one command using the --send-statistics parameter.||The licensing utility did not interact with 1C:Remote service.||New feature: you can accumulate statistical information about the licensing utility activity.|
|Functional options.||If a functional option is stored in a catalog, the functional option value is recalculated once a catalog item is deleted.||If a functional option was stored in a catalog, the functional option value was not recalculated once a catalog item was deleted and the code could get the old value of the functional option.||Eliminated unexpected system behavior.|
|Web client. System requirements.||When running on macOS, Google Chrome and Mozilla Firefox can now be used to work in the web client.||When running on macOS, only Safari could be used to work in the web client.||The list of supported web browsers for macOS is expanded.|
|Web client. System requirements.||Ended support of Google Chrome versions 48 and earlier. The web client is supported in Google Chrome versions 49 and later.||Google Chrome versions 48 and earlier were supported.||Ended support for legacy Google Chrome versions.|
|Web client.||On macOS, Google Chrome and Mozilla Firefox now support the file system extension and the add-in extension. Implemented the add-in adapter library for Google Chrome and Mozilla Firefox running on macOS. Changes were made to development technology for add-ins (read more).||On macOS, Google Chrome and Mozilla Firefox did not support the file system extension and the add-in extension.||Advanced file operations on macOS using the web client.|
|File operations.||The following methods are deprecated and supported for compatibility purposes (in all clent applications):
||The following methods could be used to create applied applications:
||Deprecated methods are no longer supported.|
|File operations.||Once the BeginPutFilesToServer() method or the BeginPutFileToServer() method is called, there is no need to wait for the method completion to call these methods again.||Once the BeginPutFilesToServer() method or the BeginPutFileToServer() method was called, it was necessary to wait for completion of a previously executed call to call the methods again. A recall attempt led to an error in the thin client or waiting for completion of the previous call in the web client.||You can now import several files (or file groups) at the same time.|
|Database copies.||You can now choose сonfiguration object properties to be passed to a database copy upon enabled standard replication. You can specify the following objects:
||All data of the selected сonfiguration objects was transferred to a database copy upon standard replication usage. It was not possuble to manage properties of data to transfer. The following properties of the DatabaseCopyManager object were read-only: DBMSType, DatabaseServer, and Database. Parameters of the DatabaseCopyManager.Add() method were mandatory. The DatabaseCopyContentItem.Metadata property was read-only. The Item parameter of Insert() and Add() methods of the DatabaseCopyContent object was optional.||When generating data for a database copy, you can now set up content and volume of data stored in the database copy more precisely.|
|External reports and data processors.||The user will only be checked for having the View right for the data processor/report used when calling GetForm() method of the DataProcessorManager and ReportManager objects. The Use right is no longer checked in this case. There are no checks for access rights when calling the GetForm() method of the DataProcessorManager and ReportManager objects. This change is not implemented in 8.3.15 compatibility mode.||When calling the GetForm() method of the DataProcessorManager and ReportManager objects an exception was thrown if the user did not have the Use right for the appropriate data processor or report.||Eliminated unexpected system behavior.|
|Data composition system.||Upgrade: you can apply conditional appearance to header areas of resource and totals fields. Conditional appearance can be managed both from 1C:Enterprise code and the selection form of the conditional appearance application area. Implemented the following properties for the DataCompositionConditionalAppearanceItem object: UseInResourcesFieldsHeader, UseInOverallHeader, and UseInOverallResourcesFieldsHeader. These properties are not available in 8.3.15 compatibility mode. This change is not implemented in 8.3.15 compatibility mode.||It was impossible to apply conditional appearance to headers of resource and totals fields.||Advanced conditional appearance features for reports built using the data composition system.|
|Dynamic lists.||On getting data, the dynamic list checks whether all filter fields are present in available filter fields. When the first field unavailable for filter is found, an error is generated. This change is not implemented in 8.3.15 compatibility mode.||On getting data, the dynamic list did not check whether all filter fields were present in available filter fields.||Eliminated unexpected system behavior.|
|Database operations.||In infobase file mode, unique indexes are created the same way they are created in client/server mode of the infobase. To force generation of indexes, change the compatibility mode and test and repair the infobase with the Restructure infobase tables check box selected.. When the compatibility mode is disabled, while writing data, index keys will be checked for uniqueness for indexes that were rebuilt upon testing and repair. Upon testing and repair (in any compatibility mode), index key uniqueness is not checked. This change is not implemented in 8.3.15 compatibility mode.||In infobase file mode, non-unique indexes of infobase tables were created even when unique indexes were created in other supported DBMSs in the same case. While writing data, 1C:Enterprise did not check index keys for uniqueness, which could cause problems with infobase migration from file mode to client/server mode.||Unified behavior of 1C:Enterprise in both file and client/server modes for operations with unique indexes. Reduced the number of issues that occur when migrating an infobase from file mode to client/server mode.|
|Dynamic lists.||When you press Enter (or double-click a row) in a row of a table linked to a dynamic list or when you call the ChangeRow() form table method, a form table extension will open a form linked to this row whether or not there is the Change command in the table commands. This change is not implemented in 8.3.15 compatibility mode.||When you pressed Enter (or double-click a row) in a row of a table linked to a dynamic list or when you called the ChangeRow() form table method, a form table extension will open a form linked to this row:
||Eliminated unexpected system behavior.|
|Information registers.||If a record set of an independent information register is written to the infobase without replacement, records will be checked for uniqueness in data import mode (the DataExchange.Import property is True). Refined the text of the error that occurs when data is not unique. This change is not implemented in 8.3.15 compatibility mode.||If a record set of an independent information register was written to the infobase without replacement, records were not checked for uniqueness in data import mode (the DataExchange.Import property was True). This behavior could result in data inconsistency.||Eliminated unexpected system behavior.|
|DBMS operations.||The behavior of the IN query language operator with the subquery became the same when using any DBMS. The results of such queries using IBM DB2, PostgreSQL, or Oracle Database might change. It is recommended that you analyze usage locations of the IN operator with the subquery and rewrite these queries if necessary. This change is not implemented in 8.3.15 compatibility mode.||The behavior of the IN query language operator with the subquery depended on the DBMS the query was executed on.||The result of the IN query language operator with the subquery does not depend on the used DBMS anymore. When using PostgreSQL, reduced the time spent on executing queries that contain the IN operator with the subquery.|
|Queries.||Upon addition or subtraction in the query language, if the left operand of the operation could not be NULL but the right operand could be NULL, it is assumed that the operation result can be NULL.||Upon addition or subtraction in the query language, if the left operand of the operation could not be NULL but the right operand could be NULL, it was assumed that the operation result could not be NULL.||Eliminated unexpected system behavior.|
|Server clusters.||In client/server mode, you can now specify roles to apply in a session for a security profile when switching to privileged mode. When privileged mode is enabled, roles specified in the security profile will be used in a session. When privileged mode is disabled, they will return to roles specified by a user. If full access to privileged mode is set in the security profile, a set of roles does not change when privileged mode is enabled. Implemented the Privileged mode roles property for the security profile. New properties for the AdministrationSecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode. New properties for the ISecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode. The following Java-based properties are implemented in the administration server interface for the ISecurityProfile object: PrivilegedModeRoles and FullPrivilegedMode. The following parameters of the profile command are implemented for the cluster service command-line utility (rac): privileged-mode-roles and full–privileged-mode. Properties AdministrationSecurityProfile.PrivilegedModeAllowed and ISecurityProfile.PrivilegedModeInSafeModeAllowed (server cluster administration COM interface and Java-based administration server interface) are deprecated and supported for compatibility purposes only.||This feature was not provided. It was impossible to explicitly specify a list of roles that would be applied in a session when switching to privileged mode.||Expanded features of security profiles in client/server mode.|
|Functionality||After||Before||Result of changes|
|Mobile client.||The mobile client now supports authentication using OpenID Connect protocol. Authentication uses a system web browser of a mobile device. Authentication using OpenID Connect is supported for iOS 9.0 or higher devices and Android devices that have Google Chrome installed.||This feature was not provided.||The mobile client now supports authentication that was available in thin client and web client.|
|Mobile client.||A сonfiguration synonym is not checked for matches when you start the mobile client. The mobile client will be started if a сonfiguration name has not changed since mobile application build and a сonfiguration signature matches its digest.||Once a сonfiguration synonym changed, it was impossible to use this configuration with the mobile client application that was built with another synonym (for example, which did not have a synonym in any language).||You do not now need to rebuild a mobile application of the mobile client when only a сonfiguration synonym changes.|
|Mobile client. Mobile application builder.||Implemented a mobile client with the operating offline feature. This client application allows you to use it both online (as a mobile client) and offline (as a standalone mobile application). Implemented option to switch from online to offline mode and back.
Implemented an offline configuration feature that will be available on the mobile device in offline mode. Offline configuration is a subset of the main configuration. The offline configuration may include all metadata that exists in the platform for a PC. Configuration objects may not be a part of an offline configuration. Configuration extensions cannot be included in an offline configuration.
Implemented the MainServer global context property. Implemented the MainServerAvailable() global context method. Implemented the OnMainServerAvailabilityChange() client application module event. The following is implemented for the ClientApplicationForm object:
||This feature was not provided. It was possible to create either a standalone mobile application or a mobile client that worked online.||Expanded the options to build mobile applications using 1C:Enterprise.|
|Mobile platform. Mobile client. Mobile application builder. Mobile device-specific features.||Implemented the feature to automatically manage mobile application data backup using the mobile operating system. Implemented the Backup using OS tools mobile application permission. The backup is performed as follows:
||This feature was not provided.||Automatic mobile application data backup (without user interaction) is now possible.|
|Mobile platform. Mobile client. Mobile application builder. Mobile device-specific features.||Implemented the mobile application permission, which allows you to manage the third-party applications installation. This feature is supported by the mobile application builder when building applications for Android. Implemented ApplicationInstallation permission.||This feature was not provided. The third-party applications installation has always been permitted.||If the third-party applications installation is not required for the application, you can reduce the total number of permissions that the mobile application requires when running on Android.|
- Example of formatted string usage in collaboration system message is implemented in the uncompleted order wizard.Information that the message text is displayed as a formatted string has been added to the Guide.
- A search bar is enabled for all client application form tables.
- The Guide (Charts section) demonstrates how to embed a web client in the iframe web page.
- Simultaneous loading of several files with a shared progress bar is implemented in the stored files list form (the Catalog.StoredFiles.Form.ListForm form).
- New chart features can be seen in the following sections:
- In the Sales dynamics report: the Amount and quantity report option shows two resources on a single chart.
- Editing prices data processor demonstrates interactive changing of chart values.
- The Sales dynamics report demonstrates how to configure the reference lines and chart intervals in the Desired sales levels report option.
- The new scheduler features are demonstrated in the Catalog.Meetings.Form.Calendar form.
- A standalone part of a demo configuration is implemented. Functionality of a standalone part is almost similar to that of a demo configuration for a mobile platform.
- Notification through FCM service is enabled.
- As soon as you link photos to goods and counterparties, you can stamp your photos. For stamp settings, go to MobileDeviceSettings common form.
- The mobile demo configuration now supports an extra authentication feature to grant access to data (ClientExchange common module and Settings common form).
- A mobile demo configuration supports a file management feature (saved product files).
- A mobile demo configuration supports popup groups (Counterparties.ItemForm catalog form; AddressesAndContacts group).
|Functionality||After||Before||Result of changes|
|Development tools.||You can now export a configuration which size exceeds 2 GB to a 1Cv8.cf file from Designer. Designer version 8.3.16 and later can only be used to import such configuration.||When attempting to export a configuration which size exceeds 2 GB to a 1Cv8.cf file, the upload was interrupted with a confusing error message.||Exporting very large configurations to a 1Cv8.cf file is now available.|
|Data display.||GetStringDeclensions() and GetStringDeclensionsByNumber() methods return a maximum of 10 declension variants of the passed phrase. This change is not implemented in 8.3.15 compatibility mode.||There was no limit for GetStringDeclensions() and GetStringDeclensionsByNumber() methods of the number of the passed phrase declension variants.||GetStringDeclensions() and GetStringDeclensionsByNumber() methods performance has been improved due to decreasing the number of declension variants.|
|Data composition system. Dynamic lists.||The data composition layout composer adds ordering from the data composition system settings to the top of the ordering list of data composition layout request. This change is not implemented in 8.3.15 compatibility mode.||The data composition layout composer added ordering from the data composition system settings to the bottom of the ordering list of data composition layout request.||Eliminated unexpected system behavior.|
|Client application form. Data display.||When automatically calculating the interface element text color, a more contrasting color relative to the element background color is selected.||When automatically calculating the interface element text color, a less contrasting color relative to the element background color was selected.||Eliminated unexpected system behavior.|
|Data accelerator.||The RAM consumption for storing variable-length fields (variable-length strings and value storage) in the Data Accelerator has been reduced. Execution of some types of queries has been optimized.||Data Accelerator required more RAM to store variable-length fields (variable-length strings and a value storage). Execution of some types of queries was not optimal.||Data Accelerator has been optimized.|
|Data display.||New feature: digital signature in PDF documents. Embedding of a digital signature visual representation into a document is also available. Implemented PDFSignatureDescription object. LinkType and ContentType properties are implemented for PDFAttachment object. ContentType and LinkType parameters are implemented for PDFAttachmentCollection.Add() method. ReadPDF object is now available in the thin client and in the web client. File system extension is required to use web client. The following methods are implemented for the ReadPDF object: CheckSignatures(), CheckSignature(), GetSignatureDescription(), StartOpening(), StartRetrievingAttachments(), StartSignaturesCheck(), StartSignatureCheck(), StartRetrievingSignatureDesctiption(), StartClosing(). WritePDF object is now available in the thin client and in the web client. File system extension is required to use web client. WriteSignature(), StartOpening(), StartWritingAttachments(), StartWritingDeletingAttachments(), StartWritingSignature(), StartClosing() methods are implemented for the WritePDF object.||This feature was not provided. Creating a separate digital signature file was available.||Expanded PDF documents management capabilities. The document consistency can now be secured after signing.|
|Client application form.||The OnClose event handler called after the ShutdownSystem (False) method has the Shutdown parameter set to True. This change is not implemented in 8.3.15 compatibility mode.||The OnClose event handler called after the ShutdownSystem (False) method had the Shutdown parameter set to True in the web client and False otherwise.||Eliminated unexpected system behavior.|
|Global search.||If an error occurred while performing the global search, the search result is placed to the GlobalSearchResultElement object, which has the ErrorDetails object placed to the Value property. When displaying the results, the error will be shown using the SpecialTextColor style color. Serialization and XDTO serialization has been implemented for the ErrorDetails object.||Errors that occurred while performing a global search were not displayed to the user.||Eliminated unexpected system behavior.|
|Database copies.||The cases of excessive RAM usage when transferring data to a copy (including the Data Accelerator) have been fixed.||Cases of excessive RAM usage were possible when transferring data to a copy.||Eliminated unexpected system behavior.|
|Common attributes / Data separation.||When using two (or more) separators that are used at the same time (i.e., store their value and conditional separation flag in the same configuration objects), the DeleteInfobaseData() method will deem the configuration object to be included in the current area if it is separated by at least one of the separators from the list of separators using the same configuration objects to store their parameters. It is recommended to analyze using the DeleteInfobaseData() method in the separated configurations and refactor this code, if required. This change is not implemented in 8.3.15 compatibility mode.||When using two (or more) separators that are used at the same time (i.e., store their value and conditional separation flag in the same configuration objects), the DeleteInfobaseData() method deemed the configuration object to have been included in the current area if it was separated by at least one of the separators from the list of separators using the same configuration objects to store their parameters.||The approach to determining the data area using the DeleteInfobaseData() method has been changed.|
|Mobile platform. Mobile client.||Improved execution of certain operations (starting, creating an infobase, etc.) in mobile applications built for Android. The size of mobile applications built for Android has slightly increased.||Execution of certain operations (starting, creating an infobase, etc.) in mobile applications built for Android took more time.||Optimized 1C:Enterprise mobile version, running on Android.|
|Mobile client.||In an offline mobile client, a form that reopens after changing the availability of the main server is reopened with the same set of form parameters as the original form. The documentation contains the recommendation for generation of the offline mobile client home page. The -MobileStandalone parameter has been implemented for the CheckConfig Designer batch run command, which allows to check the configuration for using an offline mode. The -RebuildStandaloneCfg parameter is implemented for the IBCheckAndRepair Designer batch mode run command, which allows to regenerate the offline configuration.||In an offline mobile client, a form that reopens after changing the availability of the main server was reopened with the set of parameters that included the original form key parameters only.||Improved offline mobile client running.|
|macOS. Linux. Common objects.||The UniqueID object creates version 4 universal unique identifiers (a completely random universal unique identifier) when used on PCs running Linux and macOS.||The UniqueID object created version 1 universal unique identifiers (universal unique identifier dependent on time and network adapter MAC) when used on PCs running Linux and macOS.||Enabled using the platform’s built-in features if it was required to pass a version 4 universal unique identifier to an external service during integration and the existing universal unique identifier was not suitable for such transfer.|
|Dynamic lists. Full-text search.||The " " (space) character is used as a separator only when breaking into words, which is performed at input by string and at search in a dynamic list. The ".", ",","-", "/" and "\" characters are no longer considered as separators and are searched for as regular characters. Not only the lines between every two separators, but also the lines from each separator to the end of the line are added to the full-text search index during indexing.||The ".", ",","-", "/" and "\" characters were used as a separators when breaking into words, which is performed at input by string and at search in a dynamic list.||Search as you type and in the dynamic list has become better suited to the user's habits.|
|Mobile client.||It now supports forced use of main server. Use this feature when you start to fill in the infobase of a mobile client with a standalone mode enabled. SetPreferableMainServerUse()/GetPreferableMainServerUse() global context methods are implemented.||This feature was not provided.||Now, you can avoid access to a local infobase of a mobile client , when you begin to populate this database.|
|Mobile client.||Remember Me check box is available in the mobile client authentication dialog box. If this check box is selected and standard authentication is used (without biometrics), authentication data is saved in the mobile device secure storage.
The following commands of the QR-code designed to add an infobase to a mobile client are now supported:
||These features were not provided.||Mobile client start settings are now more detailed.|
|Full-text search.||During infobase data indexing, if the string does not contain any alphanumeric characters, the full-text search index comprises of substrings from each non-alphanumeric character to the end of the line only if the length of the original string is less than 64 characters.||During infobase data indexing, if the string did not contain alphanumeric characters, the full-text search index comprised of substrings from each non-alphanumeric character to the end of the line. As a result, data indexing consumed a big amount of RAM.||Eliminated unexpected system behavior.|
- 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.16.
- Some features that are added in version 8.3.16 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.