Changes that affect system behavior




FunctionalityAfterBeforeResult of changes
Software licensing. Licenses for basic configurations are available on Linux.Basic version licenses for Linux were unavailable.You can run basic 1C:Enterprise configuration versions on Linux.
Applied objects. Infobase object autonumbering logic is revised. The check for number or code uniqueness (including automatically generated codes and numbers) is always performed while the object is being written.

The message informing the user that a number or code is not unique now specifies the value of the non-unique number or code.

Numbers or codes that are no longer used are never re-assigned automatically, even when the desired prefix is not specified explicitly. In the event when the desired prefix is not specified explicitly, the platform forms a number or code as follows: it selects the greatest of the prefixes that match the specified pattern and then adds the next subsequent number (prefixes are compared according to their alphabetical order, for example, B is greater than A).

The uniqueness check was not performed for automatically generated numbers or codes while the object was being written.

The message informing the user that a number or code was not unique did not include the value of the non-unique number or code.

Numbers or codes that were no longer used might be re-assigned automatically in the event when the desired prefix was not specified explicitly–the platform might assign a code that was used before when its prefix matched the specified pattern and the prefix was not the greatest one among those matching the pattern (prefixes are compared according to their alphabetical order, for example, B is greater than A).

Increased stability and reliability of infobase object autonumbering. Messages informing the user that a number or code is not unique now contain more information. The autonumbering is more logical: numbers or codes are always issued in the ascending order.
Applied objects. If a text value presentation cannot be calculated during debugging, the string Error getting value presentation is returned as a text presentation.If a text value presentation could not be calculated, Designer might stop responding.Improved system stability during debugging.
Managed form. Visibility of the command for switching to the calculation register (in a recorder form) is set to True by default.

This change is not implemented in 8.3.2 compatibility mode.

Visibility of the command for switching to the calculation register (in a recorder form) was set to False by default.Default visibility of commands for switching to registers is the same for all registers.
Managed form. When attributes of Number type that have minimum or maximum values set are cleared interactively, the attribute values after clearing cannot exceed the specified limits. This change is not implemented in 8.3.2 compatibility mode.When attributes of Number type were cleared interactively, their minimum and maximum values were ignored.Users cannot enter data that does not meet the conditions specified by the developer.
Applied objects. When a spreadsheet document is saved to a .docx file, image border styles are preserved. This change is not implemented in 8.3.2 compatibility mode.When a spreadsheet document was saved to a .docx file, images always had borders.More accurate export of spreadsheet document styles to .docx format.
Applied objects. When a spreadsheet document is saved to a .docx file the following spreadsheet document print options are preserved:
  • paper size
  • page orientation
  • scale
  • pagination
  • margins
  • headers and footers
  • repeating rows
  • displaying headers and footers on the first page

This change is not implemented in 8.3.2 compatibility mode.

Print options were not preserved when a spreadsheet document was saved to a .docx file.Improved usability of spreadsheet documents saved in .docx format.
Data composition system. When a user field is added to data composition system settings and the source of available settings is not specified, the file name is generated using the language of the current script variant.

This change is not implemented in 8.2.16 compatibility mode.

When a user field was added to data composition system settings and the source of available settings was not specified, the file name was generated in English.The data composition system behavior is uniform with behavior of similar platform features.
Working with files. The look and behavior of the file selection dialog box (including the FileDialog object) in Windows Vista and later Windows versions complies with the standards of these operating systems. In Windows XP and earlier and in the web client the look of the dialog box is not changed.In Windows Vista and later, an outdated file selection dialog box was used.The look of the file selection dialog box corresponds to the operating system being used.
Working with files.If both Directory and FullFileName are specified for a FileDialog object, the dialog box is opened in the specified directory and with the specified file name.If both Directory and FullFileName were specified for a FileDialog object, the dialog box ignored the specified directory and used the directory that was obtained from the full file name.Improved usability of the file choice dialog.
Automated testing.Wildcard support implemented for the InputText() method of the TestedFormField object.The automated testing mechanism did not support wildcards in text input fields.Extended functionality of the automated testing system.
Dumping/loading configuration to files.When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName.

Configurations dumped using earlier platform versions cannot be loaded.

When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files.When dumping a configuration to XML files, names of metadata object commands follow this convention: Catalog.CatalogName.Command.CommandName.

Configurations dumped using earlier platform versions cannot be loaded.

When dumping a configuration to XML files, names of metadata object commands followed this convention: Catalog.CatalogName.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files. When dumping a configuration to XML files, names of standard commands of managed forms follow this convention: Form.StandardCommand.CommandName.  Configurations dumped using earlier platform versions cannot be loaded.When dumping a configuration to XML files, names of standard commands followed this convention:  FormStdCommand.CommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files.When dumping a configuration to XML files, names of managed form commands follow this convention: Form.Command.FormCommandName. Configurations dumped earlier will not be loaded.When dumping a configuration to XML files, names of managed form commands followed this convention: FormCommand.FormCommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files.When dumping a configuration to XML files, names of standard commands of managed form elements follow this convention: Form.Item.ElementName.StandardCommand.StandardCommandName. Configurations dumped earlier will not be loaded.When dumping a configuration to XML files, the standard commands of managed form elements followed this convention: Form<ElementType>.ElementName.StandardCommandName.Command names are uniform; you can figure out the command purpose from its name.
Dumping/loading configuration to files.When a configuration is dumped to files:
  • References to missing configuration objects are dumped as text presentations of identifiers of missing configuration objects.
  • Properties of the ManagedForm element of a managed form that make sense only in 1C:Enterprise mode are not dumped.
  • For attributes and elements of managed forms, the internal identifiers required for saving their settings are dumped.

For elements of business process flowcharts, element identifiers are dumped.

When a configuration was dumped to files:

  • References to missing configuration objects were ignored.
  • Properties of the ManagedForm element of a managed form that made sense only in 1C:Enterprise mode were dumped.
  • For attributes and elements of managed forms, the internal identifiers required for saving their settings were not dumped.
  • For elements of business process flowcharts, element identifiers were not dumped.
In dumping/loading of configurations, the following improvements are implemented:
  • User settings are preserved when a configuration is dumped and then loaded.
  • The accuracy of configuration comparison (after a configuration is dumped and then loaded) is increased.
Managed forms.When Esc is pressed in a text box (except multiline text boxes), the following actions are performed:
  • If the initial text box content was modified in any way, the text box reverts to the initial content.
  • If the initial content was not modified, the text box does not process pressing the Esc key and passes the processing to the form.
Pressing Esc was always processed by the form. The text box did not perform any actions if Esc was pressed while the text was being edited.You can cancel editing a value in a text box.
Managed locks. The maximum number of managed locks is 100 000 (exceeding this limit locks the entire lock space).The maximum number of managed locks was 20 000 (exceeding this limit locked the entire lock space).Improved user experience when using transactions with a large number of locks (more than 20 000) in a single lock space.
Information registers. Data exchange. When a set of information register records is passed to the SelectChanges() method as a filter value, the system behavior depends on the compatibility mode:
  • In version 8.2.16 or earlier compatibility mode, the selection includes data that does not match the filter criteria defined by the record set;
  • In version 8.3.1 or later compatibility mode (or if the compatibility mode is not used), the selection only contains data that exactly matches the filter criteria.
When a set of information register records was passed to the SelectChanges() method as a filter value, the system behavior did not depend on the compatibility mode.
  • In version 8.2.16 or earlier, the selection included data that did not match the filter criteria defined by the record set
  • In version 8.3.1 or later, the selection only contained data that exactly matched the filter criteria.
Improved compatibility with previous platform versions.
Dynamic list. In the data composition system and query wizard, syntax units enclosed in braces {} do not lead to errors in dynamic lists.In the data composition system and query wizard, syntax units enclosed in braces led to errors in dynamic lists in some cases.Better stability of dynamic list.
Cryptography. The value of the CryptoModuleName parameter in the CryptoManager object wizard is case insensitive.The value of the CryptoModuleName parameter in the CryptoManager object wizard was case sensitive.The system behavior complies with common standards.
Managed form. Ordinary form. In managed and ordinary forms, if the second parameter (FormElement) of the ChooseFromMenu() method is a managed form table, a managed form, a table box, or an ordinary form, the menu that is opened using this method is displayed in the following location:
  • For a table box or a managed form table, the menu is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table if the current cell cannot be determined.
  • For a form, the menu is displayed in the upper left corner.

This change is not implemented in 8.3.2 compatibility mode.

If the second parameter (FormElement) of the ChooseFromMenu() method was a managed form table, a managed form, a table box, or an ordinary form, the menu was displayed in the following location:

  • For a table box or a managed form table, the menu was displayed in the lower left corner of the element passed as the parameter value.
  • For a form, the menu was displayed in the lower left corner of the current form element. If the current form element could not be determined, the menu was displayed in the lower left corner of the form. In the web client, the menu was displayed in the center of the screen.
Uniform behavior when the system opens similar menus (e.g. context menu in a managed form table) or the applied solution opens such menus (using the ChooseFromMenu() method).
Managed form. Ordinary form.In managed and ordinary forms, if the second parameter (FormElement) of the  ChooseFromList() method is a managed form table, a managed form, a table box, or an ordinary form, the list that is opened using this method is displayed in the following location:
  • For a table box or a managed form table, the list is displayed in the upper left corner of the current cell, or in the upper left corner of the managed form table, if the current cell cannot be determined.
  • For a form, the list is displayed in the upper left corner.

This change is not implemented in 8.3.2 compatibility mode.

If the second parameter (FormElement) of the ChooseFromList() method was a managed form table, a managed form, a table box, or an ordinary form, the list was opened in the following way:
  • For a table box or a managed form table, the list was displayed in the lower left corner of the element passed as the parameter value.
  • For a form, the list was displayed in the lower left corner of the current form element. If the current form element could not be determined, the list was displayed in the lower left corner of the form.
  • In the web client, the list was displayed according to form settings because a system form was used to display it.
Uniform behavior when executing similar actions (the ChooseFromMenu() and ChooseFromList() methods).
Developing tools. You can search and replace in the ChoiceParameters property of configuration objects. The search and replace algorithm is modified for the ChoiceList and ChoiceParameterLinks configuration objects. The search and replace are performed:
  • For the ChoiceParameters property: in the Name and the Value columns (including fixed array elements). The search is performed on values of String type.
  • For the ChoiceList property: in the Presentation column and in the Value column if the value has the String type.
  • For the ChoiceParameterLinks property: in the Name column.
  • Every time the search string is found, the search/replace procedure is paused and a message prompting to resume the procedure is displayed.

Search in the LinkByType property of configuration objects is no longer supported.

Search and replace in the ChoiceParameterLinks property of configuration objects was performed only in the Name column. Search and replace in the ChoiceList property of configuration objects was performed only in the Presentation column. Search and replace was not performed in the ChoiceParameters property of configuration objects. Search could be performed in the LinkByType property of configuration objects.The search and replace operations in configuration object properties are now uniform to similar operations in texts.
Developing tools. The presentation of the ChoiceParameters property of configuration objects in the object properties editing window is changed. If a value of any property element is a fixed array, presentations of array values are used. The presentation of the ChoiceList property of configuration objects in the object properties window is changed. A presentation now consists of both list item values and their presentations (if the presentations are specified).If an element of a ChoiceParameters property was a fixed array, its presentation was a FixedArray string. For the ChoiceList property of configuration objects, the presentation in the object properties window was generated from the list item values only.Improved usability of ChoiceParameters and ChoiceList properties in Designer.
Managed form. Improved look and behavior of drop-down lists in text box fields that can be edited and contain data of reference type, enumerations, or system enumerations:
  • If a field contains data of reference type or an enumeration, the field includes the choice button, and the characters typed in the field do not match any choice list values, the Click show all to select item message is displayed in the list.
  • If the drop-down list is displayed and a value is selected in it, pressing Tab, Shift+Tab, or Enter selects the current value from the list. Clicking another form element does not select the current value; the list is closed instead (same effect as pressing Esc). The selection is not moved to the form element that was clicked.
  • If the drop-down list is not displayed and the characters typed in the field uniquely identify a choice list value, pressing Tab, Shift+Tab, or Enter selects this value. Clicking another form element also selects this value.

If the drop-down list is not displayed and the characters typed in the field match multiple choice list values, pressing Tab, Shift+Tab, or Enter opens the drop-down list. Clicking another form element also opens the drop-down list.

The drop-down list had a different look and behavior. Improved usability of text box fields that contain data of reference type, enumerations, or system enumerations.
Accumulation registers. You can enable the aggregates mode for any turnovers accumulation register, regardless of the actual presence of aggregates in metadata. In the client/server mode you can create new optimal aggregates (and remove outdated ones) when aggregates are being rebuilt in 1C:Enterprise mode. This change is not implemented in 8.3.2 compatibility mode.Developers had to add aggregates in Designer to keep the list of optimal aggregates up to date.Simplified support of optimal aggregate list: you only have to rebuild aggregates on regular basis.
Managed form. In text boxes containing data of reference type, only the color of the text presentation of the value is changed on element activation.In text boxes containing data of reference type, the color of the entire field changed on element activation.Better text box usability. A tooltip can be displayed in a text box linked to data of reference type if the text box is first in the tab order of the form.
Developing tools. Configuration repository. You can perform quick comparison of selected configuration objects. This option is available if you use a repository, and also from the compare and merge configurations window. Selective comparison is implemented for the following objects: modules, templates, pictures, WS-references, schedules, register aggregates, exchange plan content objects, styles, desktop workspaces, maps, forms, online help pages, predefined items, command interface fragments, and role rights. To run the selective comparison command, right-click anywhere in any of the repository dialog boxes or in the compare configurations window, and then click Perform selective comparison with the configuration object. Selective comparison of configuration objects is only available for object versions added to the configuration repository using 1C:Enterprise version 8.2.9 or later.This feature was not provided. When comparison was initiated for a specific object, full comparison of two configurations was performed. The focus in the comparison window was set to that object.Improved usability of configuration repository. Optimized comparison procedure when it is performed for a single configuration object.
Operating with DBMS. Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later is now available.

All of the required settings are specified automatically by the installation program of the patched PostgreSQL version unless a cluster created by the standard PostgreSQL version is found on the computer.

Integration between a cluster created using the standard PostgreSQL version (without any 1C patches installed) and PostgreSQL with patch version 9.2.1-2.1C or later was not available.1C:Enterprise supports clusters created by the following versions of PostgreSQL DBMS:
  • PostgreSQL 8.1.5-X.1C - 9.1.2-1.1C
  • PostgreSQL 9.2.1-2.1C
  • Standard version of PostgreSQL provided that the cluster locale is identical to the infobase locale.

You can upgrade or downgrade 1C:Enteprise without upgrading or downgrading the associated PostgreSQL instance; this does not require any manual configuration.

Note that once you migrate to a new PostgreSQL version, you cannot use 1C:Enterprise version 8.3.2 or earlier. This only applies to new infobases that were created using PostgreSQL 9.2.1-2.1C. Do not create infobases using PostgreSQL 9.2.1-2.1C if you are planning to access them from earlier platform versions.

Managed form.If the ChoiceDataGetProcessing event handler of the enumeration manager returns an empty list and the formal parameter StandardProcessing returned by this handler is set to False, the returned list is used for filling the choice list. This change is not implemented in 8.3.2 compatibility mode.If the ChoiceDataGetProcessing event handler of the enumeration manager returned an empty list and the formal parameter StandardProcessing returned by this handler was set to False, the client application filled the choice list by all enumeration values.The system behaves as expected when a developer decides to disable selection of enumeration values.
Standard functions. In the default event log form, filter presentation is localized.In the default event log form, filter presentation was always displayed with Russian names of event log columns.The filter presentation is uniform with other platform features.
Configuration repository. Optimized the reference integrity check algorithm for configuration repository operations (storing and retrieving) on objects that are deleted from the repository and objects that reference to deleted ones. In some cases, it is not necessary to lock objects that contain references to objects being deleted during the deletion. The reference integrity check algorithm used when deleting objects from the repository is uniform with the reference integrity check algorithm used when deleting objects from a configuration that is not bound to a repository. This change is not implemented in 8.3.2 compatibility mode.The reference integrity check algorithm for configuration repository operations was not optimized. The reference integrity check algorithm used when deleting objects from a repository was different from the reference integrity check algorithm used when deleting objects from a configuration that was not bound to a repository.Eliminated problems that occurred when deleting objects from configurations because of the reference integrity check differences. Storing deleted objects to the configuration repository is optimized.
Managed form. In the managed mode of the thick client, if the In list editing mode is selected for a configuration object, calling the OpenValue() method or clicking the Open button in the text input area opens the regular list form, provided that the following conditions are met:
  • The In list editing mode is selected.
  • A regular list form exists and it is selected as a default or additional one.
  • Using regular forms in the managed application is allowed in this applied solution.
  • The list or object managed form that is used as a default or additional one is missing.

In all other cases, this opens the object form.

This change is not implemented in 8.2.16 compatibility mode.

In the managed mode of the thick client, if the In list editing mode was selected, calling the OpenValue() method or clicking the Open button in the text input area opened the managed list form.To display configuration objects that have the In list editing mode set, or for editing their elements, the system opens the regular list form. This behavior is more consistent than before.
Development tools. The following changes are implemented in the configuration comparison feature:
  • The parent node of predefined data elements is excluded from the comparison.
  • Missing help data is considered identical to empty help data.
  • Additional properties of the ManagedForm managed form element that make sense only in 1C:Enterprise mode are excluded from the comparison.
When configurations were compared:
  • The node to which predefined data items were subordinate was included into the comparison.
  • Missing help data was considered different from empty help data.
  • Additional properties of the ManagedForm managed form element that make sense only in 1C:Enterprise mode were included into the comparison.
The configuration comparison is perfomed as expected.
Managed form. When a choice list is generated for form fields linked to data of EnumRef type, it is based on the choice parameters and choice parameter links of the form element.

This change is not implemented in 8.3.2 compatibility mode.

When a choice list was generated for form fields linked to data of EnumRef type, the choice parameters and choice parameter links were not taken into account.The choice list generation for enumerations is uniform with other similar system features.
Internet-enabled functionality. For the InternetMailProfile object, the SMTPAuthentication property (which is obsolete) is set to SMTPAuthenticationMode.Default.

This change is not implemented in version 8.2.16 compatibility mode. 

For the InternetMailProfile object, the obsolete property SMTPAuthentication was set to SMTPAuthenticationMode.None.The default settings of the authentication method is the safest among those supported by the mail server.
Internet-enabled functionality. If the SMTPSecureAuthenticationOnly property of the InternetMailProfile object is set to TRUE, authentication attempts are performed independently of other settings.

User authentication on the SMTP server is not performed in the following scenarios:

  • The SMTPUser property of the InternetMailProfile object is an empty string.
  • The SMTPAuthentication property of the InternetMailProfile object is set to SMTPAuthenticationMode.None.
  • The POP3BeforeSMTP property of the InternetMailProfile object is set to TRUE.

User authentication on the SMTP server was not performed if the name of the SMTP server user was not specified (the SMTPUser property of the InternetMailProfile object).User authentication on the SMTP server can be performed using a POP3 server if the SMTPSecureAuthenticationOnly property is not set. The value of the SMTPUser property of InternetMailProfile object does not affect this behavior. At the same time, the authentication is not performed if the mail server does not support the secure authentication methods.

When connecting to a mail server, you can exclude insecure authentication methods from the list of available ones.

Software licensing. If a license acquisition dialog box appears at the start of the client application, the first page of the dialog box specifies which kind of license (server or client) the application requires. A hyperlink to 1C:Licensing center contact information is displayed on the license registration pages and on the page that appears when license activation is not successful. A dialog box that displays 1C:Licensing center contact information is added. When a user types a PIN code or a response from a licensing center operator in the license aсquisition dialog box, once they have completed a text field, the cursor moves to the next field automatically. 

 

If a license acquisition dialog box appeared at the start of the client application, the first page of the dialog box did not specify which kind of license (server or client) was not found. The license registration pages and the page that appeared when license activation was not successful only contained information how to find 1C:Licensing center contacts in the printed documentation. When a user typed a PIN code or a response from a licensing center operator in the license aсquisition dialog box, the cursor did not move to the next field automatically.Improved usability of license acquisition dialog box.
Spreadsheet document. Web client. The web client now supports text orientation in spreadsheet document cells.The web client did not support text orientation in spreadsheet document cells.Extended formatting capabilities for spreadsheet documents in the web client.
Server cluster. When a cluster service is reassigned from one cluster manager to another, the service status is replicated to the new cluster manager and the service is shut down on the former cluster manager, which releases the resources used by the service. The status is replicated for the following services: object locks, numbering, and background restructuring. In the technological log, the <SRVC> event is implemented. It describes the following operations with cluster services: starting, stopping, and various alerts. Descriptions of operations being executed are generated in the Descr property. Each cluster manager stores its session data in a dedicated directory. You can choose how a working process is selected when a new connection is created: by available performance or by available memory. If the selection is performed by available memory, either the working process that currently maintains connections to the infobase is used, or the working process that is running on the server and has the maximum amount of available memory. In the cluster properties, the Load balancing mode property is implemented. For the IClusterInfo object, the LoadBalancingMode property is implemented. For starting a background job, the working process that maintains the session that initiated the background job is selected with the highest priority (this rule is ignored if the selection is performed by available memory). You can specify a priority for each assignment rule. If several identical assignment rules are found during assignment rule selection and all other conditions are equal, the rule with the highest priority is used. Assignment rules now have the Priority property. For the IAssignmentRule object, the Priority property is implemented. In the cluster mode of the server cluster administration utility (rac), the load-balancing-mode parameter is implemented for the create and update commands. Similar changes are implemented in the Java server administration API. When determining available working process performance, the CPU load of the working server and the number of threads in the execution queue are taken into account, in addition to other factors.In some cases, used resources were not released after the reassignment of services. The status was not replicated for the following services: object locks, numbering, and background restructuring. In the technological log, there were no events that described operations with cluster services. Data belonging to all sessions was stored in a single directory, which could lead to access collisions. When a background job was created, the working process for handling the job was always selected by available performance. If several identical assignment rules were found during assignment rule selection, the rule that was applied could not always be determined unambiguously. When available working process performance was determined, the CPU load and the number of threads in the execution queue were not taken into account.Increased fault tolerance of clusters. Improved quality and manageability of load balancing between cluster servers. A new setting ensures  efficient memory usage when a cluster maintains a large number of infobases with a small number of sessions from each infobase. 
Managed form. For unavailable groups, colors of the title and border (line) are changed.For unavailable groups, the title and border (line) had different colors.The look of unavailable groups is uniform with the look of other unavailable elements.
Applied objects. Common attributes / Data separation. Access rights. Data exchange. Mobile application. Predefined data is available for configuration objects included in separator contents in the Independent and Shared mode. Predefined items can be linked to any data elements of matching type. The linking is optional. If data elements are not linked, the predefined data is considered empty. For configuration objects that can contain predefined data, the PredefinedDataName property is implemented. Support of predefined data items that refer to deleted predefined items is implemented. Identical references to predefined items are never generated, even for objects included in separator contents in the Independent mode, and even for items that belong to different areas. The GetPredefinedItemName() method is declared deprecated is only supported for compatibility purposes. Predefined data is registered in exchange plans like any other data. You can manage creation and update of predefined data in the infobase using the new configuration object property PredefinedDataUpdate and the new methods GetUpdatingPredefinedData() and SetPredefinedDataUpdate(). The global context method InitializePredefinedData() is implemented. Using this method, you can create data objects for predefined items that are not linked to any data (in the current data area). Access rights and restrictions are specified simultaneously for the Predefined and PredefinedDataName fields. These features are also implemented for the mobile platform. The new access rights InteractiveDeletePredefinedData, InteractiveSetDeletionMarkPredefinedData, InteractiveClearDeletionMarkPredefinedData, and InteractiveDeleteMarkedPredefinedData are implemented. They specify whether editing of predefined data is allowed.

Restrictions for editing predefined data in charts of accounts and charts of calculation types are eliminated. Predefined data can be marked for deletion, and it can be completely deleted. A chart of accounts must be included into the contents of all separators that contain all extra dimensions used in the chart. The infobase restructuring process is modified. This change is not implemented in 8.3.2 compatibility mode.

Predefined data was not available for configuration objects included in separator contents in the Independent and Shared mode. Predefined data could not be linked to any existing data object. Each predefined item had identical references in all data areas. During data exchange in a distributed infobase, predefined data was replicated only together with applied solution configuration changes. Creation and update of predefined data were not available.You can use predefined data in all separation modes. Predefined data management is more flexible than before.
Interface. In the help topics, links to external resources are opened in the default web browser of the operating system.In the help topics, links to external resources were opened in the built-in web browser of 1C:Enterprise.Improved usability of viewing the resources that are opened by clicking links in the help topics.
Interface. For new users, the interface mode is set to Forms in tabs, provided that the platform version compatibility mode is not used and the interface compatibility mode is set to Version82 or Version82TaxiAllowed.For new users, the interface mode was set to Forms in separate windows.The Forms in tabs interface is the default option for new users. This interface mode provides better usability.
Interface. For a text box in a managed form table, the drop-down list is always opened at the start of editing.For a text box in a managed form table, the drop-down list was opened at the start of editing only if the editing was started using the mouse.Quick access to the drop-down list is implemented for text boxes located in managed form tables.
Common attributes / Data separation. 1C:Enteprise script. After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state matches the state that the data area had when it was accessed for the first time. In particular:
  • Tables of enumerations are not modified.
  • If the version 8.3.2 or later compatibility mode is set, predefined data values revert to the values specified in Designer or to the default values. If the compatibility mode is disabled, predefined data items will be created on the first attempt to access them.
  • In the exchange plans, the values of ThisNode element attributes revert to the default values.
  • Values of nonseparated constants revert to the default values, while values of separated constants are deleted.
After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the data area state did not match the state that the data area had when it was first accessed:
  • Tables of enumerations were removed.
  • For nonseparated objects, the predefined data values were saved.
  • In the exchange plans, the values of ThisNode element attributes were saved.
  • Constant values were preserved.
After deleting data from a data area (or deleting an infobase) by using the EraseInfoBaseData() method (or the /EraseData command-line option), the state of the data area now reflects its initial state much better than it did in the previous platform versions.
Application appearance.New splash screens are implemented for Designer, client application, Autorun program, and the installation program. The splash screen size (and the size of the applied solution splash screen template) is 600 x 255 pixels.Splash screens that were used for various parts of the system had different looks. The size of the applied solution splash screen template was 305 x 110 pixels.The new splash screens better fit the new user unterface.
Managed form. When a value is entered or selected in a text box, it is converted to the text box value type, and then the value presentation is displayed in the text box. This change is not implemented in 8.3.2 compatibility mode.When a value was entered or selected in a text box, the resulting text displayed in the box might not match the entered or selected value.The system behaves as expected. Eliminated incorrect system behavior.
Client application. The message that is displayed before updating a client application using an insecure connection is clarified. The message was not clear enough.The message describes the situation more clearly.

Table of contents


Comments
0
Add comment