Version 8.3.21
Version 8.3.21 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 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.21
New functionality and changes
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Configuration properties. | For configuration property Compatibility mode, new value Version 8.3.20 is now implemented. | Compatibility mode with versions 8.1, 8.2.13, 8.2.16, and 8.3.1–8.3.19 was available. | Configurations developed using 1C:Enterprise platform version 8.3.20 or earlier can now run on version 8.3.21 (without the need to update the configuration or the application data structures). This provides the option to migrate to version 8.3.21 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.20 after the migration to version 8.3.21, even if you disable the compatibility mode (simply enable it again). |
| Dynamic lists. | You can now get a URL to an object or a record of the current dynamic list row without having to open the object/record form. New form table extension property for the dynamic list: AllowGetCurrentRowURL. New event handlers for the form table extension for a dynamic list: URLListGetProcessing and URLGetProcessing. The dialog box for getting a form URL is upgraded considering this feature. The dialog box for getting a URL on the home page displays all the URL options received from all forms on the home page. | Getting a URL to an object or a record of the current dynamic list row without having to open the object/record form was unavailable. On the home page, getting a URL of any home page form from one dialog box was unavailable. | Improved and simplified interface for getting a URL in a dynamic list or on the home page. |
| Dumping configurations to files/Restoring configurations from files. Standalone server. Development tools. | You can now export the application to the zip. archive of XML files. New feature: multi-threaded application export on the server cluster side.
The Dump configuration to files command in Designer allows you to set the export method (on the server/on the client), the number of simultaneous export threads, and the need to archive the export file.
To enable this feature, a special parameter is implemented for the following import tools:
|
This feature was not provided. | Improved performance of the application export to XML files. Now you can export files to another computer in a ZIP archive. |
| Data display. | New pictures in the picture library:
|
The listed pictures were not available in the picture library. | The picture library is upgraded. |
| Processing PDF documents. | You can now view and print PDF documents using 1C:Enterprise platform tools. You can view and verify digital signatures in documents. Encrypted documents are now supported. Current restrictions are listed in the documentation. New object: PDFDocument. New field form kind for the client application: PDFDocumentField. New global context methods: PasswordProtectedDocument() and PasswordProtectedDocumentAsync(). New methods for the PDFAttachmentCollection object: Clear() and Delete(). New properties for the PDFDocumentFileType system enumeration: PDF, PDF_A_1, PDF_A_2, and PDF_A_3. New properties for the ErrorCategory system enumeration: IncorrectPassword and SignatureCheckError. | This feature was not provided. Only PDF document generation was available. | Advanced PDF document features. |
| Internet-enabled functionality. | New feature for the HTTPConnection object: use client certificates supporting GOST algorithms. CryptoPRO CSP is now supported on Linux and macOS. New parameter for the conf.cfg configuration file: CryptoAPILibraryLocation. New objects: LinuxClientCertificate, OSCertificateSelectMode, and OSClientCertificate. The OpenSSLSecureConnection object constructor can take the OSClientCertificate object as the value of its ClientCertificate parameter. | Client certificates supporting GOST algorithms were not supported. | Extended list of certificate kinds used for the HTTPConnection object operations. |
| Client application form. | New feature: display the Gantt chart with a table that contains additional data for the chart values. New feature: expand the form table for the Gantt chart. New property for the GanttChart object: DataColumns. New method for the GanttChart object: FindValueByID(). New property to expand the form field for the Gantt chart: TablePosition. New properties for the GanttChartValue object: ID and Data. New properties for the GanttChartPlotArea object: ShowPointsText and ShowData. New property for the FormField object Table. | This feature was not provided. The Gantt chart could only display the point names created for the chart series. | Advanced Gantt chart features. |
| Database copies. | New feature to update a database copy when using standard replication. This feature applies specialized DBMS tools of the main database. The new feature is used only for Microsoft SQL Server DBMS that records changes. New methods for the DatabaseCopiesManager object: GetStandardReplicationVersion() and InstallStandardReplicationVersion(). | This feature was not provided. | Improved performance of database copy update when using the new database copy update tool. |
| Internet-enabled functionality. | New feature: use the JWT token (URL44 standard) for authorization in online services of 1C:Enterprise platform. You can also create and verify a JSON Web Signature (JWS). New object: AccessToken. New method for the HTTPRequest object: AddAccessToken(). New property for the InfoBaseUser object: AccessTokenAuthentication. New item for the defaul.vrd file: <accessTokenAuthentication>. New startup command line commands for thin and web clients: /AccessToken. | This feature was not provided. | Advanced access token features and improved security when using online services. |
| Error handling. | In the dialog box that appears in case of infobase connection errors, you can now view information that will help you understand why a certain error occurred and who you need to contact in case of such error. New object: StartupErrorProcessingSettings. New methods for the ErrorProcessingManager object: SetStartupErrorProcessingSettings() and GetStartupErrorProcessingSettings(). New parameters for the infobase connection parameters described in the *.v8i file: StartupErrorHelpURL and StartupErrorHelpText. | This feature was not provided. A link to supporting information could be placed only in the dialog box for entering the username and password. | Connection errors of the client application to the infobase are now more comprehensible to users. |
| Command interface. | When selecting a subsystem, you can now execute only one command of this subsystem. New property for the Subsystem metadata object: UseOneCommand. | This feature was not provided. | Simplified application usage with only one subsystem command available to a user. |
| Web client. Internet-enabled functionality. | You can now take advantage of HTTP requests in web client. Provided features are limited by web browser capabilities. The following objects are available in the web client: HTTPConnection, HTTPRequest, HTTPResponse, and OpenSSLSecureConnection. Synchronous object methods are not supported in web client. | This feature was not provided. | Advanced web client features for Internet resources. |
| Internet-enabled functionality. | New feature in client applications (thin, mobile, thick, and web clients): asynchronous HTTP requests. New methods for the HTTPConnection object: CallHTTPMethodAsync(), WriteAsync(), ChangeAsync(), PostAsync(), GetAsync(), GetHeadersAsync(), and DeleteAsync(). The CallHTTPMethod(), Write(), Change(), Post(), Get(), GetHeaders(), and Delete() methods of the HTTPConnection object are considered obsolete for client applications and supported for compatibility reasons. Specified methods are available only on the server application side. | 1C:Enterprise did not support asynchronous HTTP request execution. Only request execution timeout could be specified. | Asynchronous data exchange with various Internet resources. |
| Configuration extensions. Common attributes / Data separation. | New feature: include your own extension objects in adopted common attributes being separators. New feature: install extensions that extend data simultaneously for the whole infobase as well as for a specific data area. | Including your own extension objects in adopted common attributes being separators was not supported. An extension that extends data could be installed in a specific data area or for the whole infobase. Simultaneous installation of such extensions was not supported. | The configuration extension now provides more features. |
| Applied objects. Dynamic lists. Data composition system. | When setting up application object characteristics, you can now specify that a characteristic can contain more than one value. This feature is implemented in the data composition system and dynamic list. New properties for the CharacteristicsDescription object: MultipleValuesUseField and MultipleValuesKeyField. MultipleValuesOrderField. If multiple characteristics are specified in the infobase, data can be duplicated as a result of data composition when migrating to previous platform versions. It is not recommended that you use previous versions of 1C:Enterprise after specifying multiple characteristic values. | More than one value could not be specified in object characteristics. | Support of multiple values in required characteristics. For example, WiFi frequency bands, materials used for goods, and so on. |
New functionality and changes in the 1C:Enterprise mode
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Collaboration system. | You can now create a new conversation during a video call in the collaboration system. The current video call participants are added to the conversation participants. In the video call window, there is a submenu for the Go to conversation button containing the following commands: Go to conversation and New video call conversation. | Participants could go to a conversation during a video call only if a video call was started from a conversation. If a video call was started from the collaboration system menu, to exchange text messages on the discussed topic, a user had to manually create a new conversation and add all video call participants to it. | Fast creation of a text chat (and access to it) during a video call. |
| Error handling. | New feature: view About window in the dialog box that generates an error report. | This feature was not provided. | Access to error environment details (application and platform version, connection mode, user, infobase name, and so on) when generating an error report. |
| Error handling. Web client. | If a web client connects to an infobase using the HTTPS protocol, this infobase was accessed from this computer before, and the web browser supports the service-worker technology, a special page will be displayed in case of a connection error (similar to the exit page). This page will display connection error information and various supporting information. The page will be functionally identical to the connection error form in thin client, but its implementation will depend on web application specifics. | This feature was not provided. | The same view of the infobase connection error via HTTPS and errors in web applications. |
| Collaboration system. | When working via a video server, the image quality in a video call in the speaker view mode has been improved. When working via a video server, the load on the client computer is reduced when all subscribers in a group video call are displayed in the gallery view mode. | When working via a video server, the image quality in a video call in the speaker view mode was insufficient. When working via a video server, the load on the client computer was significant when all subscribers in a group video call were displayed in the gallery view mode. | Improved video call quality via a video server. |
Optimization
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application form. | Optimized transfer of tables from the server to the client in the client application form. If some table rows are changed on the server, only the rows with changed columns are transferred to the client. Only the lines previously transferred to the client side are modified. The transfer is carried out in portions of 35 rows (or less). If more than 105 rows are changed on the server (3 portions of 35 rows), then after transferring three portions of 35 rows each, all table rows are transferred to the client. If a form is opened, no more than 35 rows are trensferred to the client. | When a form was opened, only the displayed table part was transferred to the client. In case of any change of the table on the server, the entire table was transferred to the client. With a large table, this could take a long time and even cause run-time errors. | Improved performance of the client application form when a small number of rows are changed in a large table on the server (in one call). |
| Server clusters. | Improved working process cache: frequently used objects are stored for longer periods and rarely used objects are deleted sooner. Reduced memory consumption by the working process, improved operation stability, and reduced probability of restarting cluster working processes when the memory threshold is exceeded. | The working process cache of server clusters had a different operation procedure. This could lead to increased RAM consumption by the working process. | Reduced memory consumption by the working process, improved operation stability, and reduced probability of restarting cluster working processes when the memory threshold is exceeded. |
| Common objects. | Improved setting of values in the ValueTable object if the column where a value is specified participates in the index created for the value table. The following operations take less time now (not limited to this list):
|
Setting a value to the ValueTable type object column that participated in the index was very time-consuming. | Improved performance when changing values in the ValueTable type object columns that participate in the indexes created for the value table. |
| Full-text search. | Improved full-text search by the beginning of a word. The improvement is manifested when performing a full-text search from 1C:Enterprise language with a search string of the "sear*" kind or when using the global search field. | Full-text search by the beginning of a word took more time. | Improved performance of full-text data search. |
| Metadata objects. | Improved performance of the application that contains numerous metadata objects, including improved:
|
Performance of the application that contains numerous metadata objects was insufficient. | Improved performance of applications with numerous metadata objects. |
| Spreadsheet documents. | In thin client, the display of a spreadsheet document that contains a large number of merged cells and columns is improved. | In thin client, the display of a spreadsheet document that contains a large number of merged cells and columns took longer. | Improved display of spreadsheet documents with a complex structure. |
| Development tools. | When trying to view a large collection in the Expression dialog box, the collection is received by Designer (for display) in portions. As a result, you do not have to spend a lot of time to view the collection. | When trying to view a large collection in the Expression dialog box, the entire collection was received by Designer (for display). This caused significant delays and could lead to disconnection from the debug item. | Viewing large collections in the Expression dialog box is more convenient for developers. |
| Full-text search. | Preparing full-text search results for users takes less time now. In full-text search results, the first exact match of the search word (if there is one) is always highlighted. If there is no exact match, the first found form of the search word is highlighted. | Preparing full-text search results for users took longer. In full-text search results, the first found form of the search word was always highlighted. | Displaying search results to users takes less time. Search text in search results is highlighted more correctly. |
Changes that affect system behavior
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Web client. Client application form. | In web client, the indent between a picture and a page title text as well as the indent from page edges depend on the font size of all Page items of the current form. | In web client, the indent between a picture and a page title text as well as the indent from page edges depended on the font size of a Page item. | The web client behavior is now identical to the thin client behavior. |
| Queries. | When working in the thick client, the QueryWizard object constructor can be called with an empty query text. In this case, the default constructor is called. | When working in the thick client, the QueryWizard object constructor threw an exception if the constructor parameter value was an empty string. | Unified behavior of the QueryWizard object constructor in different client applications. |
| Error handling. | Extended features when working with errors for application developers. New features: define exception codes for your own exceptions; throw an exception based on another exception. The presentation of errors generated from the application code has been changed. New parameters for the Raise operator: Category, Code, AdditionalInformation, and Cause. When specifying more than one parameter, the operator can be written only in the functional form (with parameters enclosed in parentheses). New system enumeration property: ErrorCategory.ConfigurationError. New properties for the ErrorInfo object: Code and AdditionalInformation. New parameters for the getInfo query of the error registration service: errorCategories, clientID, and reportID. New error report properties: id (contains the reportID value from the getInfo query) and dump.reasonForNoDump (contains the reason why a report does not contain a crash dump). New properties for the ErrorProcessingSettings object: SendReportAtServer, SendCrashReportAtServer, SendCrashReportToPlatformErrorRegistrationService, IncludeUserNameInReportAtServer, IncludeInfobaseInformationInReportAtServer, IncludeDetailErrorDescriptionInReportAtServer. | These features were not provided. | Extended features for error operations. You can now create codes for application errors. Extended API features of the error registration service. |
| 1C:Enterprise language. | The Undefined value can now be used as a key for the objects of the Map and FixedMap types. This feature was already available in the web client. This change is not implemented in 8.3.20 version compatibility mode. | The Undefined value could be used as a key for the objects of the Map and FixedMap types only in the web client. | Possible use of the Undefined value as a key for the objects of the Map and FixedMap types. |
| XML and XDTO support. | For the WriteXML() and XDTOSerializer.WriteXML() global context methods, you can now pass a metadata object of the following types as the Value parameter: a catalog, a document, a chart of characteristic types, a chart of accounts, a chart of calculation types, an information, accumulation, or accounting register, a constant, a business process and task. All metadata object data available to the user that writes data will be written. | This feature was not provided. Export of all configuration object data to XML was unavailable. Data had to be sorted and each data item had to be exported separately. | Improved performance of data export from the application. |
| URLs. | New feature: get a URL with its presentation. New radio button in the dialog box for getting a URL: Copy name. The dialog box to follow a link, the global search, and the collaboration system consider that the clipboard may contain a URL with a presentation. | This feature was not provided. | Simplified simultaneous receiving of a URL and a presentation of the object to which this URL refers. |
| Common objects. | New feature: generate UUIDs of versions 1, 3, 4, and 5. New parameters for the UUID object constructor for creating IDs of the required version. New system enumeration: UUIDVersion. | This feature was not provided. Only version 4 IDs could be generated by 1C:Enterprise platform. | Now application developers can generate a UUID version required to complete a specific task. |
| Internet-enabled functionality. | If the HTMLDocumentField form item in thin and thick clients displays a URL that requires an SSL certificate, and this certificate contains any errors (for example, it is invalid), a page with error details will be displayed, and you will be offered to continue working with the URL or close it. | If the HTMLDocumentField form item in thin and thick clients displays a URL that requires an SSL certificate, and this certificate contains any errors (for example, it is invalid), an error message will be displayed in the field and further operations with the required URL will be unavailable. | Improved troubleshooting of problems with URLs displayed in the client application. Access to resource operations in cases where such operations are not recommended, but the user is confident in their actions. |
| Database copies. Data Composition System. | If during the execution of a data query to a copy, an error occurs related to the copy used in the query, the copy is no longer used in all existing or new sessions until the copy is updated or the server cluster is restarted. If an error is caused by a copy during the execution of the report created in the Data Composition System that contains several data sets or a hierarchical data set, the data access error will be displayed to the user. In other cases, as well as if a report/query does not require using only a database copy, an error is not displayed to the user, and the query is automatically re-executed in the main database or in one of the available database copies (except for the copy with an error). | This feature was not provided. The copy in which an error occurred had to be manually disabled. After restarting the cluster or updating the copy, it had to be included in the used copies again. | When working with database copies, the damaged copy is disabled automatically without user intervention. If a query can be generated without the damaged copy of the database, the user will not notice the copy failure. The user will receive an error message only if a data query cannot be completed without the data of the database copy, all copies are marked as damaged, and queries to them are not executed. |
| Full-text search. | Full-text search correctly processes situations with numerous iterations of full-text search index update (hundreds of thousands iterations) and numerous indexed items. To enable this feature, the user must create an index in compatibility mode with version 8.3.14 or later (including the "Do not use" value). | Full-text search index could be incorrect in case of numerous iterations of full-text search index update (hundreds of thousands iterations) and numerous indexed items in the infobase. | Eliminated unexpected system behavior. |
| Spreadsheet documents. | When converting a spreadsheet document to compact mode used on mobile devices, the AutoIndent property is used to align text in cells. | When converting a spreadsheet document to compact mode used on mobile devices, only the Indent property was used to align text in cells. | Improved spreadsheet documents view on mobile devices. |
| Collaboration System. | If screen sharing is enabled during a video call in thin or web clients, the video call window switches to the compact display mode. New feature: minimize the compact video call window to the heading size. | If screen sharing was enabled during a video call in thin or web clients, the video call window disappeared from the screen. The users that shared the screen could not tell whether they had listeners or not. | Improved screen sharing during a video call. |
| Spreadsheet documents. | When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the Sheet1 name is set in the resulting document for the Microsoft Excel sheet. In version 8.3.20 compatibility mode, this behavior is not changed. When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the document sheet panel is not hidden. | When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the TDSheet name was set in the resulting document for the Microsoft Excel sheet. When saving a spreadsheet document in XLS format (Microsoft Excel 97) or Microsoft Office OpenXML (Microsoft Excel 2007 and later), the document sheet panel was hidden. | Eliminated performance issues when trying to open a document with a hidden sheet panel in Microsoft Excel. The naming of sheets in the resulting Microsoft Excel document is more understandable and predictable now. |
| Collaboration system. | You can now enable support for specific types of audio devices (multichannel microphones and audio systems) in the Collaboration System. This feature is enabled separately in the settings dialog box for video and sound in the Collaboration System settings. The user can use this feature in case of problems with capturing or playing audio on their computer. | Some users had sound problems when making video calls. | Extended list of supported audio devices in thin client. |
| Data composition system. | When displaying list templates of the data composition system in the lower-right cell of the template, the cell is no longer vertically merged with an empty cell in the row below. This change is not implemented in 8.3.20 compatibility mode. | When displaying list templates of the data composition system in the lower-right cell of the template, the cell was vertically merged with an empty cell in the row below. | Eliminated unexpected system behavior. |
| Dynamic list. | If a dynamic list contains a visible field whose type consists of a string of unlimited length and any other type (except for NULL and Undefined):
|
If a dynamic list contained a visible field whose type consisted of a string of unlimited length and any other type (except for NULL and Undefined):
|
Eliminated unexpected system behavior. |
| Add-ins. | New method for the program and add-in interface: SetUserInterfaceLanguageCode(). It is used to transfer an interface localization language of the client application to the add-in. The SetLocale() method is considered deprecated. The technology for creating add-ins has been changed (read more). It is recommended that you use the new method of getting the interface localization code for the current add-in. | The SetLocale() method was used to transfer an interface localization language of the client application to the add-in. This method worked differently in different client applications and with different interface localization languages. | Unified method of transferring information about a client application localization language to the add-in. |
| Data display. Spreadsheet document. | If the print scale of a spreadsheet document is set to "Fit page width" in the print parameters, and the page width is not enough to fit the whole document, then when exporting a spreadsheet document to Microsoft Word format, the document is scaled similarly to the scaling applied by 1C:Enterprise when printing a spreadsheet document: the column width, the row height, and the font size are changed. In version 8.3.20 compatibility mode, the behavior has not changed. | If the print scale of a spreadsheet document was set to "Fit page width" in the print parameters, and the page width was not enough to fit the document, then when the spreadsheet document was exported to Microsoft Word format, the document was not changed in the way 1C:Enterprise system would change this spreadsheet document when printing. | If the print scale is set to "Fit page width" for a spreadsheet document, the printed document and the document exported to Microsoft Word format will be almost identical. |
| Dumping configurations to files/Restoring configurations from files. | The format version of configuration dump to XML files is 2.14. | The format version of configuration dump to XML files was 2.13. | Configuration dump to XML files supports new platform features. |
Changes that require modification of configuration and administrative settings
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Client application form. | When trying to change the form attributes or dynamic list settings from 1C:Enterprise language, adding an attribute/column with a duplicate name will result in an exception. This change is not implemented in 8.3.20 version compatibility mode. | When trying to change the form attributes or dynamic list settings from 1C:Enterprise language, adding an attribute/column with a duplicate name did not cause adding errors. Access to such attribute from 1C:Enterprise language was impossible. | Eliminated unexpected system behavior. |
| Linux. Administration tools. Server clusters. | When using a 1C:Enterprise server cluster running on Linux, the SystemV subsystem for initialization and management of services will no longer be used. The systemd subsystem (similar to the previously mentioned one in terms of purpose) is used instead. The distribution package includes a systemd-scenario for starting a server cluster and an administration server (ras) and their configuration files. The SystemV-scenario for starting a server cluster (and its configuration file) was deleted from 1C:Enterprise distribution package. After migration to a new version, you need to reconfigure the functionality to automatically start a server cluster. | When using a 1C:Enterprise server cluster running on Linux, the SystemV subsystem for initialization and management of services was used. | Improved startup and configuring of 1C:Enterprise service instances for system administrators working on Linux including (if required) multiple startups of different instances. |
| Add-ins. | New feature: import add-ins in a separate process separated from 1C:Enterprise platform processes. In this case, abnormal add-in termination will not result in the abnormal platform termination, but the add-in reattachment will be required. The add-in creation technology has been changed. An add-in can now provide the platform with information about available add-in operation modes and current URL1 mode. New parameter for the AttachAddIn() method (and all asynchronous analogs): AddInAttachmentType. New method: CheckAddInAtachment(). New event: AddInDetachmentProcessing. It is called upon abnormal termination of the add-in operating process. It is recommended that you develop add-ins that support the isolated operation mode. When using add-ins on the client side, it is recommended that you provide a reload code in case of abnormal add-in termination. When developing configurations in the compatibility mode with version 8.3.20 or earlier, isolated add-in import is recommended if the add-in can run in a separate process. | This feature was not provided. Add-ins were imported only to the address space of 1C:Enterprise platform process that used this add-in. Abnormal add-in termination resulted in the abnormal termination of 1C:Enterprise process. | Improved stability of add-ins. |
| Administration tools. | If OS updates were automatically installed before the platform was installed, or the updated files were used by other applications, after installing the platform you will see a warning stating that a computer restart might be required. | If OS updates were automatically installed before the platform was installed, or the updated files were used by other applications, after installing the platform the computer was restarted without a warning. That could lead to data loss of the user who installed 1C:Enterprise. | Improved installer behavior for cases when a computer restart is required to complete the installation. |
| Client application. | When connecting to the infobase via HTTP using thin or web clients, the /UC command can be specified in the startup command line if the session start is locked with an unlock code. | When connecting to the infobase via HTTP using thin or web clients, the /UC command in the startup command line was ignored. | Possible connection to the infobase via HTTP for the user knowing the unlock code even if the session start is locked. |
| Error handling. | If the technician mode is enabled in the user session, the interpretation of the Auto value of the ErrorProcessingSettings.MessageDisplayVariant property is changed:
|
The Auto value of the ErrorProcessingSettings.MessageDisplayVariant property was always interpreted as ErrorMessageForUser. | Simplified troubleshooting and problem solving due to errors being displayed in a more technical form for developers and technicians. |
| Configuration extensions. | New feature: create your own predefined items for adopted objects of the following types: catalogs, charts of characteristic types, charts of accounts, and charts of calculation types. Predefined items can be adopted or native. This change is not implemented in 8.3.20 compatibility mode. | This feature was not provided. | The configuration extension now provides more features. |
| DBMS operations. | For PostgreSQL, Oracle Database, and IBM DB2 DBMS, a query language expression containing a multiple B operator with a subquery is translated to the DBMS language using the EXISTS() operator. After the change, the multiple B operator with a subquery always returns a Boolean type value. This change is not implemented in 8.3.20 compatibility mode. It is recommended that you check the use of queries that contain the multiple B operator with a subquery in applications. | For PostgreSQL, Oracle Database, and IBM DB2 DBMS, a query language expression containing a multiple B operator with a subquery was translated to the DBMS language using the multivalue IN operator. The EXISTS() operator was used in Microsoft SQL Server DBMS and the file mode of the infobase. Because of that, the query language expression could return different values in different DBMS. | Unified behavior of the multiple B operator with a subquery for all supported DBMS. |
| Data composition system. | The Data Composition System does not display records from other periods in the report if the following grouping is specified: field-period - field not being a period - field-period. In version 8.3.20 compatibility mode, this behavior is not changed. | The Data Composition System displayed records from other periods in the report if the following grouping is specified: field-period - field not being a period - field-period. | Eliminated unexpected system behavior. |
| Data composition system. | When generating a data composition template, if some optional connection of a data set query is considered used (in the data composition settings, a field from the tables of this connection is used), connections with tables whose fields are used in this connection are also considered used. In version 8.3.20 compatibility mode, this behavior is not changed. | When generating a data composition template, if some optional data set query connection is considered used (in the data composition settings, a field from the tables of this connection is used), connections with tables whose fields were used in this connection were not considered used. | The behavior of the data composition template generator is now more predictable. |
| Full-text search. | If a full-text search query contains the * character surrounded by quotation marks, for example, "table*", the expression is interpreted as a search for the * character, not as a metacharacter. | If a full-text search query contained the * character, such expression was always interpreted as a metacharacter, no matter how the search string was formatted. | Eliminated unexpected system behavior. |
| Dynamic list. | The dynamic list key fields are added to the end of the list of order fields in the data composition system settings obtained by calling the form table extension method for the GetPerformingDataCompositionSettings() dynamic list if these fields are specified in the Key fields property of the dynamic list. As a result, data sorting performed according to such settings will always be stable. It is recommended that you analyze all places where the GetPerformingDataCompositionSettings() method is used for dynamic lists with any key and make sure that the resulting settings are not imported to the dynamic list settings. The resulting settings can be used only with the data composition schema obtained by calling the GetPerformingDataCompositionScheme() method of the form table extension for the same dynamic list. | Dynamic list key fields were not added to the end of the list of order fields in the data composition system settings obtained by calling the form table extension method for the GetPerformingDataCompositionSettings() dynamic list. As a result, data sorting performed according to such settings could be unstable. | Consistently stable sorting of data obtained using the executable data composition schema and the executable data composition settings of the dynamic list. |
| XML and XDTO support. | When importing XDTO package from XSD schema, a value specified in the schema is set as the minimum value for properties whose items are included in the Choice contents model. This change is not implemented in 8.3.20 compatibility mode. | When importing XDTO package from XSD schema, the minimum value was set to 0 for properties whose items were included in the Choice contents model. | Eliminated unexpected system behavior. |
Renamed objects
Table of contentsMobile version of "1C:Enterprise"
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile platform. Mobile client. ZIP archive operations. | The mobile version of 1C: Enterprise now supports ZIP archive operations. | This feature was not provided. | Supported ZIP archive operations in the mobile version of 1C:Enterprise. |
| Mobile platform. Mobile client. Dynamic list. Data composition system. | In the mobile version of 1C:Enterprise, custom report settings are saved when generating a report. The UserSettingsModified report form extension property is set to False when generating the report result. This change is not implemented in 8.3.20 compatibility mode. In the mobile version of 1C:Enterprise, a report option is saved after closing the report option editing form by clicking Finish editing. This change is not implemented in 8.3.20 compatibility mode. Custom dynamic list settings are saved after dynamic list records are successfully imported. | In the mobile version of 1C:Enterprise, custom report settings were saved when closing a report form. The UserSettingsModified report form extension property was set to False when closing the form. In the mobile version of 1C:Enterprise, a report option was saved only when the Save option command was manually called. | More logical and understandable operations with report and dynamic list settings. |
Demo configuration changes
- You can find an example of using the Gantt chart with a data table in the demo configuration for operating with charts (Read more.).
- View operations with multiple characteristics in the Price list report.
- New feature: highlight order status in the list of orders.You can find an example of filling in the GoodsConsumption document based on the Order document.
Changes made after the publication of the version
| Functionality | After | Before | Result of changes |
|---|---|---|---|
| Mobile client. | Startup of the mobile client with the connected collaboration system takes less time. | Startup of the mobile client with the connected collaboration system took more time. | Startup of the mobile client with the connected collaboration system takes less time. |
| Development tools. | New feature: prohibit exporting references to deleted configuration objects to XML files. New radio button in the dialog box for dumping configuration to files: Do not export references to non-existent objects. New parameter for the /DumpConfigToFiles command: -ignoreUnresolvedReferences. New parameter for the config dump-config-to-files Designer agent command: --ignore-unresolved-refs. New parameter for the (ibcmd) config export management utility of the standalone server: --ignore-unresolved-refs. | This feature was not provided. | You can deny export of references to previously deleted objects that remained in forms, command interface, and so on to XML configuration files. |
| Collaboration system. Web client. | If a collaboration system user makes a video call in web client using Mozilla Firefox, video stream quality always remains high. Video stream quality does not depend on how this user is displayed for their counterparty. | If a collaboration system user made a video call in web client using Mozilla Firefox, the web client tried to manage video stream quality, but the attempts failed. | Eliminated unexpected system behavior. |
| Dynamic lists. | You cannot receive a URL of the current row for an information register subordinate to the recorder. An item with the WriteCurrentListRow key is not passed to the list of URLs. This list is passed to the ProcessURLsReceiving event handler for this information register. | You could receive a URL of the current row for an information register subordinate to the recorder. | Eliminated unexpected system behavior as the record form is missing for an information register subordinate to the recorder. |
| Data composition system. Mobile client. | User report settings are saved:
|
User report settings were saved only upon calling the standard report generation command. | Eliminated unexpected system behavior. Reduced risk of losing configured settings due to automatic saving. |
| Distributed infobases. | Licensing client data must be entered in each node of a distributed infobase. | Licensing client data had to be entered only in the main node of a distributed infobase. | Eliminated unexpected system behavior. |
| Mobile platform. Mobile client. Administration tools. | The cacertnx.pem file that contains root CA certificates is included in the mobile version of 1C:Enterprise. When establishing a secure connection, certificate revocation is checked in the following order: certificates from the cacertnx.pem file, configuration certificates, application certificates, and mobile OS certificates. | This feature was not provided. | Advanced features for certificate revocation check. |
| DBMS operations. Accounting registers. | Accounting register indexes have been changed when running in PostgreSQL, Oracle Database, and Data accelerator. Indexes change in case of accounting register restructuring including verification and restoration operations. | Accounting register indexes when running in PostgreSQL, Oracle Database, and Data accelerator were different. | Data acquisition from accounting registers is faster now. |
| Mobile client. System requirements. Mobile application builder. | Android 12 is supported now. Android 4.1 is no longer supported. The minimum supported Android version is 4.4. (read more) add-in development technology has been changed. The mobile application that will be published in Google Play Store and uses the "Installing applications" functionality must meet the app store requirements effective on July 11, 2022. To meet the requirements, use mobile version 8.3.21.41 or later. | Android version 4.1 was supported. | The latest Android version is supported. The mobile version of 1C:Enterprise no longer supports devices for which Google stopped releasing security updates. |
| Infobase operations. Administration tools. | If you call the EraseInfoBaseData() method and exclusive mode is disabled, the system attempts to enable it. If the attempt is not successful, the method throws an exception. The EraseInfoBaseData() method deletes data in extension object tables, but does not delete extensions installed in the infobase. | In file infobases, the EraseInfoBaseData() method could be successfully executed with disabled exclusive mode. | Eliminated unexpected system behavior. |
| PDF document operations. | New parameters for the Write() and WriteAsync() methods: FileType. New feature: when saving a PDF document interactively, select a PDF subset for it. | This feature was not provided. | Saving PDF files in required format (including PDF/A archival formats). |
| Mobile platform. Mobile client. | If the scale is increased on a mobile device on iOS, the interface of the mobile 1C:Enterprise version is also increased in scale. | This feature was not provided. | Improved user interface view on mobile devices on iOS. |
| XML and XDTO support. | If XSL transformation using the XSLTransform object results in an HTML file, the attribute value is URL-encoded for the href, action, and src attributes of various elements, and for the name attribute of the a element. You cannot use the following characters in URL encoding: @/:=?;#%&,+\. | If XSL transformation using the XSLTransform object resulted in an HTML file, no values were URL-encoded. | Eliminated unexpected system behavior. |
| XML and XDTO support. | New feature for the ReadXML() global context method: partial reading. You can read only data specified in an XML file without changing the data in the infobase object. Such reading is enabled if an XML element that describes a 1C:Enterprise object contains the optional dataPart attribute set to True. 1C:Enterprise does not allow creating an XML file to perform partial reading. Partial reading is implemented for the following configuration objects: catalogs, documents, tasks, business processes, exchange plans, charts of accounts, charts of calculation types, charts of characteristic types, and accumulation, information, calculation, and accounting registers. | Previously the ReadXML() method did not allow partial reading of a configuration object from an XML file. | Advanced exchange with third-party systems using XML files. |
| Internet-enabled functionality. | Secure connection is used when calling the InternetMail.Logon() method. If the application uses mail servers that do not require server certificate verification, specify these servers in the conf.cfg configuration file. Now you can do it using the new IgnoreInternetMailServerCertificateVerificationList parameter of the configuration file. | Unsecure connection was used when calling the InternetMail.Logon() method. | Enhanced security for using objects related to remote access to various external services. |
Transition from the previous version to the version 8.3.21
- 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.21.
- Some features that are added in version 8.3.21 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.
- When using a server cluster on Linux, re-configure the requirement to automatically start the cluster at the start of the operating system or the requirement to run different cluster versions at the same time. You need to do this because the systemd subsystem for initialization and management of services is now used to manage the server cluster auto start (instead of the System V subsystem with a similar purpose).
- For full-text search to correctly process situations with numerous iterations of full-text search index update (hundreds of thousands iterations) and numerous indexed items, the user must create an index in compatibility mode with version 8.3.14 or later (including the "Do not use" value).