Version 8.3.3

If a form has a vertical scroll bar and the command bar is located above or below all form elements and occupies the entire form width, the area being scrolled does not include the command bar.

#Region and #EndRegion preprocessor instructions are implemented. These instructions are ignored during script execution. A template for creating a script fragment with line grouping is added to the set of standard templates.

• Microsoft SQL Server Analysis Services
• IBM InfoSphere Warehouse
• Oracle Essbase

Requests to OLAP sources and errors that occur during the request execution are recorded to the EDS event of the technological log.

The following pictures are added to the picture library: ExternalDataSourceCube, ExternalDataSourceCubeDimensionTableObject.

The information on characteristic of client computer monitors is passed through at the session start and when the RefreshInterface() method is called.

This feature is not used in dynamic lists.

This change is not implemented in 8.3.2 compatibility mode.

• A client handler only
• A client handler and a server procedure (to be executed outside of a context) that is called from the handler
• A client handler and a context server procedure that is called from the handler

A context server procedure cannot be generated for those client handlers where calling context server procedures is not recommended.

To disable them, use the DisableStartupDialogs command-line option for the 1cv8.exe/1cv8 file.

If the command-line that starts a client application or Designer contains errors that led to displaying these dialog boxes in earlier platform versions, the dialog boxes are not displayed; diagnostic messages are generated instead. These messages are recorded to the file that stores service messages (the Out command-line option).

Exclusive access to an area prohibits the following actions:

• Creation of new sessions with the same set of separators.
• Access to the area-contained data from enveloping areas.
• Setting exclusive access in enveloping areas.

Setting shared managed locks for an area is ignored if exclusive access is set for this area.

• devices with screen resolution below 140 DPI
• devices with screen resolution from 140 to 180 DPI and Apple devices with standard screens
• devices with screen resolution from 180 to 270 DPI
• devices with screen resolution over 270 DPI and Apple devices with Retina screens

Each picture corresponds to specific screen settings of the target device. It is recommended that you use the PNG format for the archived pictures and you create the archive without compression. For the Picture object, the ChoiceSet property is implemented.

For the purposes of software cluster administration:

• ISecurityProfile object is implemented.
• ISecurityProfileVirtualDirectory object is implemented.
• ISecurityProfileCOMClass object is implemented.
• ISecurityProfileAddIn object is implemented.
• ISecurityProfileExternalModule object is implemented.
• ISecurityProfileApplication object is implemented.
• ISecurityProfileInternetResource object is implemented.
• For the IServerAgentConnection object, the following methods are implemented: GetSecurityProfiles(), RegSecurityProfile(), UregSecurityProfile(), CreateSecurityProfile(), GetSecurityProfileVirtualDirectories(), RegSecurityProfileVirtualDirectory(), UnregSecurityProfileVirtualDirectory(), CreateSecurityProfileVirtualDirectory(), GetSecurityProfileCOMClasses(), RegSecurityProfileCOMClass(), UnregSecurityProfileCOMClass(), CreateSecurityProfileCOMClass(), GetSecurityProfileAddIns(), RegSecurityProfileAddIn(), UnregSecurityProfileAddIn(),CreateSecurityProfileAddIn(), GetSecurityProfileUnSafeExternalModules(), RegSecurityProfileUnSafeExternalModule(), UnregSecurityProfileUnSafeExternalModule(), CreateSecurityProfileUnSafeExternalModule(), GetSecurityProfileApplications(), RegSecurityProfileApplication(), UnregSecurityProfileApplication(), CreateSecurityProfileApplication(), GetSecurityProfileInternetResources(), RegSecurityProfileInternetResource(), UnregSecurityProfileInternetResource(), and CreateSecurityProfileInternetResource().
• For the IInfoBase object, the following properties are implemented: SecurityProfileName and SafeModeSecurityProfileName.
• The type of the SafeMode parameter (used in the Create() and Connect() methods of external report and data processor managers and in the SetSafeMode() global context method) was changed from BOOLEAN to STRING. The type of value returned by the SafeMode() global context method was changed from BOOLEAN to STRING. When this parameter (or returned value) has STRING type, it stores the security profile name.

Similar changes are implemented in:

• Cluster administration utility (rac) – the profile mode is implemented, and the update command of the infobase mode is modified.
• Java API for server administration.

For example, you can use security profiles to organize individual temporary storage directories for each data area, or describe the list of Internet resources available for use in a specific infobase.

TestedCommandInterfaceButton, TestedCommandInterfaceGroup, and TestedWindowCommandInterface. For tested objects, the GetObject() method is implemented. Its set of parameters is similar to that of the FindObject() and FindObjects() methods. If the object is not found, the GetObject() method raises an exception. Methods for testing user messages are implemented. The list of properties and methods for managing tested objects is extended. You can get the form name, the current window, the command interface, and so on. You can get the information on the last error that occurred in the tested client application. For the TestedApplication object, the methods GetActiveWindow() and GetCurrentErrorInfo() are implemented. For the TestedClientApplicationWindow object, the methods GetCommandInterface(), GetUserMessageTexts(), and ChooseUserMessage() are implemented. For the TestedForm object, the FormName property and the methods FindDefaultButton(), CurrentModified(), and GetCommandBar() are implemented, while the Close() method is moved to the TestedClientApplicationWindow object. For the TestedFormField object, the methods CurrentModeIsEdit() and GetEditText() are implemented, and the methods BeginEditCurrentArea() and EndEditCurrentArea() are modified. For the TestedFormTable object, the method CurrentModeIsEdit() is implemented, and the methods ChangeRow(), EndEditRow(), GotoPreviousRow(), GotoNextRow(), Expand(), and Collapse() are modified. For objects that describe tested form elements, the methods GetToolTipText(), CurrentVisible(), CurrentEnable(), CurrentReadOnly(), GetContextMenu(), and GetCommandBar() are implemented.

You can edit user settings of a dynamic list in a separate group of the form that displays the dynamic list. For that purpose, the User settings group property is implemented. Dynamic list settings can be edited in a separate common form, which is specified using the Default dynamic list settings form configuration property.

For the DynamicList object, the SettingsComposer property is implemented, which is similar to the corresponding property of report objects.

This change is not implemented in 8.3.2 compatibility mode.

Only usual groups with displayed titles can be collapsed.

Hiding form items that are rarely used is available. This decreases the amount of data that is displayed to an end user. To view the hidden data, an end user can expand the group.

Developers no longer have to close modal dialog boxes many times when they attempt to perform mass modification of objects that cannot be modified (for example, objects stored in a configuration repository that are not locked).

The Taxi interface includes a large number of changes, with the following highlights:

• A whole new view: enlarged fonts, increased spacing between elements in forms, modified color scheme and form element layout, enlarged form elements.
• Improved application navigation: focus on a single-window functionality, single purpose panels (such as history or favorites), switching back and forward between previously opened windows, and so on.
• Extended main application window settings: developers can define the content and location of panels for the applied solution, at the same time users can arrange these panels as they like.
• A system form for the full-text search.
• The form navigation panel is located in the upper part of the form.
• The message window is located in the lower part of the form and is only visible when there are messages to display.
• The performance meter is displayed in a separate application window panel, not in a separate window.
• In the History panel, records are grouped by days with their opening time displayed. You can search for history items and add them to Favorites.
• In the Favorites panel, you can search for items, rename them, and "pin" important ones at the top of the list.

Use the iTaxi command-line option of the client application for the forced start of this interface mode (provided that using Taxi is allowed in the applied solution). You can also switch between interface modes using the client application settings window. The following configuration properties are implemented:

• InterfaceCompatibilityMode - specifies which interface modes are available in the applied solution.
• ClientApplicationInterface - stores the list of panels used by default in the client application, as well as their positions.
• DefaultSearchForm - specifies the search form that is used for the full-text search in application data. If the form is not specified, the system full-text search form is used.

A brand new look for the calendar. For the managed form calendar field, the following properties related to the new features are implemented: HeightInMonths, WidthInMonths, and ShowMonthsPanel. These properties are only used in the Taxi interface. For the ClientApplicationInterfaceVariant object, the ClientApplicationInterfaceVariant property is implemented (it is used for getting the interface mode), and the global context method ClientApplicationInterfaceCurrentVariant(). The ClientApplicationBaseFontCurrentVariant() global context method is implemented. It gets the size of the base font in the client application. For the UserWorkFavoritesItem object, the Important and Presentation properties are implemented. In the Taxi interface, the Desktop is renamed to Start page (the related commands are renamed accordingly). The Dashboard section of the section pane is used for accessing the command interface. In the Taxi interface:

• The All actions menu is renamed to More.
• The default presentations of standard commands in forms are changed, as well as command presentations in the command panel and in the More menu.
• The presentations of form item groups are changed.

The link to the start page (desktop) of the applied solution has the following format: e1cib/navigationpoint/startpage. Start page (desktop) settings are stored with the settings key StartPage/WindowSettings (for Taxi interface, StartPage/Taxi/WindowSettings). In the managed form editor, switching between interface 8.2 and Taxi modes in the preview window is implemented.

parameters of the function or procedure that is being edited in the module text editor. If the method has several syntax variants, you can select the required variant. Automatic parsing of procedure and function comments for displaying them in context tooltips is implemented. Procedure and function comments can be sorted for displaying in the context tooltip. The comment format is described in the documentation and complies with the applied solution development standards. Procedure and function templates that comply with this format are included into the distribution kit. The option that shows or hides the context tooltips is implemented in Designer. In the source code editor, you can open the context tooltip by pressing Ctrl+Shift+Spacebar.

The following changes are implemented in the background restructuring procedure:

• You cannot create, edit, or delete exchange plan items if the exchange plan requires the restructuring. The restructuring is performed during the processing phase.
• You cannot create, edit, or delete chart of characteristic types items if the chart is specified as an extra dimension for a chart of accounts and this chart of accounts requires restructuring. In this case the restructuring of the chart of characteristic types is performed during the processing phase.
• The SetPredefinedDataUpdate() method cannot be called during the background restructuring.

All charts of characteristic types and exchange plans were restructured when the changes were applied (during the background restructuring).

• In the Forms in tabs form opening mode, print status forms are opened in separate windows.
• The form is opened in a modal window so that users cannot interact with the interface during printing.
• The form cannot be closed by clicking the "X" button.

The form cannot be resized.

• Text box
• Text document field
• Formatted document field
• Spreadsheet document field

Insertion from the Primary Selection clipboard (available by pressing the middle mouse button) is supported in text boxes.

This change is not implemented in 8.3.2 compatibility mode.

Users do not have to select from a single value in the type selection dialog box.

• Event log:
• The set of commands in the form command bar is changed, as well as the command presentations.
• The procedures for enabling and disabling the filter are revised.
• You can view log entry data by clicking the link in the corresponding log column.
• You can filter records by date and time.
• Find references to object:
• You can search for references to a reference that is found (from the context menu).
• Manage full-text search:
• The form is revised.
• Enabling or disabling full-text search is performed without opening additional forms.
• Post documents:
• The form is revised.
• Active users:
• You can open the event log filtered by user by clicking a hyperlink in the User column.

Improved usability of standard functions.

• Simultaneous connections from a large number of client applications.
• Connection of a new client application to a cluster that already runs a large number of sessions.

Improved performance and scalability of 1C:Enterprise servers.

• By period
• By dimensions
• By dimension

The Active field is the last one in these indexes. After changing the compatibility mode, full infobase restructuring must be performed for rebuilding indexes. This change is not implemented in 8.3.2 compatibility mode.

Improved performance of dynamic lists filtered by multiple attributes (including the deletion mark).

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 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).

This change is not implemented in 8.3.2 compatibility mode.

• 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.

This change is not implemented in 8.2.16 compatibility mode.

Configurations dumped using earlier platform versions cannot be loaded.

Configurations dumped using earlier platform versions cannot be loaded.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

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.

• 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.

• 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.

• 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.

• 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.

This change is not implemented in 8.3.2 compatibility mode.

This change is not implemented in version 8.2.16 compatibility mode. 

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.

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

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.

• 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.

• 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.

When one or multiple files are obtained from the infobase using the GetFile() or GetFiles() method, the View right was not checked for the attributes that stored the file data.

In the Java-based administration server interface, the IWorkingServerInfo interface included the setName() and setClusterMainPort() methods. These methods did not perform any actions and there were no error messages when these methods were called.

In the server cluster administration utility (rac), the security-level option was available for the infobase update command. The value specified in this option was never used and no error messages were displayed when the command was run with this option.

In the Java-based administration server interface, the IInfoBaseInfo interface included the setSecurityLevel() method. This method did not perform any actions and there were no error messages when this method was called.

Linux.

Linux.

• If a file name does not contain wildcard characters (? or *), the file is added to the archive.
• If a file name contains the wildcard characters (? or *), an exception is generated.

The behavior of the ZipFileReader object is modified. If the user under whose account the system is running does not have rights for viewing the list of files in the directory containing the archive file, the archive is opened in the read-only mode. This change is not implemented in 8.3.2 compatibility mode.

• New configuration repository database structure is used.
• The optimized method for interaction with configuration repository server is used.

If the compatibility mode is disabled, only 1C:Enterprise version 8.3.3 or later can be used to access the repository. The command line option ConfigurationRepositoryClearCache is implemented in Designer. It is intended for clearing the local configuration cache. The option to stop the execution of repository operations by pressing Ctrl+Break is implemented (this does not depend on repository compatibility mode).

• All scheduled jobs are executed in a dedicated client application (by default, it is the first session started).
• A background job started by a session is executed by the client application that started it.
• Within a client application, a single background job is performed at a time (this includes scheduled jobs).

For specifying the client application that will execute scheduled jobs, the AllowExecuteScheduledJobs command-line option is implemented for the client application. The Background jobs check box, which is located in the Autoattach dialog box in Designer, affects the attachment to background jobs both at server and at client.

This change is not implemented in 8.3.2 compatibility mode.

The Background jobs check box, which is located in the Autoattach dialog box in Designer, only affected attachment to background jobs at server.

• /usr/share/fonts/truetype/msttfcorefonts
• /usr/share/fonts/msttfcorefonts
• $HOME/.fonts

The system automatically searches for required dynamic libraries when functions from these libraries are used. If the required font or dynamic library is not found, an error message is displayed. The operating system setup instructions for Linux are provided in the documentation.

This change is not implemented in 8.3.2 compatibility mode.

• Catalogs
• Documents
• Charts of characteristic types
• Charts of calculation types
• Business processes
• Tasks
• Charts of accounts
• Exchange plans

While objects are being written or deleted, they will be temporarily locked by all attributes specified in the DataLockFields property and the Ref field. For objects being written, attribute values available at the beginning of the writing process are used. For objects being deleted, current attribute values are used.

This change is not implemented in 8.3.2 compatibility mode.

This change is not implemented in 8.3.2 compatibility mode.

• The AppAutoInstallLastVersion command-line option of the non-interactive startup utility.
• The AppAutoInstallLastVersion parameter in the 1CEStart.cfg and 1CESCmng.cfg configuration files.

When the client application version does not match the 1C:Enterprise server version, or when a specific 1C:Enterprise version is required to access an infobase, the new version is always installed unless the required version is already present at the client computer. The Install new application versions automatically check box is added to the infobase startup settings dialog box.

• In the startup utility configuration dialog box, a specific 1C:Enterprise version is selected for all infobases.
• A specific version of the client application or interactive startup utility is started.

If you specify the Any ref type for an attribute (such as a resource or dimension) in Designer, the type is converted into one of the following in the configuration data model:

• The {http://v8.1c.ru/8.1/data/enterprise}AnyRef type if the configuration includes multiple metadata objects that form the Any ref type.
• The type that corresponds to reference data type if the configuration includes a single metadata object that forms the Any ref type.

This change is not implemented in 8.3.2 compatibility mode.

If you specified the Any ref type for an attribute (such as a resource or dimension) in Designer, it was always converted to the {http://v8.1c.ru/8.1/data/enterprise}AnyRef type in the configuration data model.

The former constructor and method syntax is supported for compatibility purposes.

• Choice list - from the choice list property of the text box.
• Quick choice list - for the quick choice property of the configuration object.
• Choice values – values matching the text entered by the user.
• Choice history - for reference fields and enumeration fields. Note that the history is not available for fields that contain configuration objects with the quick choice option enabled.

During the text input in a text box, the platform displays unique items from all these lists (if they are available for the text box). For managed form fields, the ChoiceButtonRepresentation property is implemented. It describes whether the button that opens the choice form is present in the field. The DropListButton property of managed form fields is no longer available; it is left for compatibility purposes. The StartListChoice event of text box objects is never called. This change is not implemented in 8.3.2 compatibility mode.

• History of choices in the fields of the given type (with the given parameters)
• Choice values
• Quick choice list, and so on

• Microsoft Internet Explorer version 7.0;
• Safari for Windows;
• Mozilla Firefox version 16 and earlier for Windows and Linux.

• Microsoft Internet Explorer version 7.0;
• Safari for Windows;
• Mozilla Firefox version 16 and earlier for Windows and Linux.

For add-ins intended for use with all supported Mozilla Firefox versions, you have to add several add-in versions to the archive:

• For Mozilla Firefox version 18.0 or earlier
• For Mozilla Firefox versions 19.0 to 21.0
• For Mozilla Firefox version 22.0 or later

It is recommended that you specify only the minimum version of the web browser in the add-in manifest file.

Documentation on creating add-ins is updated. Read more. Examples are added, new versions of adapters for web browsers.

Adapters for Mozilla Firefox versions that are no longer supported by the developer (versions 3.6, 4.0, and 5.0) are removed.

• Full-text search
• Search by substring or by the beginning of the string
• Instant or background search

You can specify each of these options in Designer, in the configuration object properties. The full-text search is performed only among the configuration object attributes that are selected in the "input by string" options of the configuration object. If a filter is applied during the input by string, the filter is converted (whenever possible) to a full-text search query in order to increase the search performance.

For external data source tables, you can only select the search modes (by substring or by beginning of the string, and instant or background). In the file mode, the background search can be performed only when any other background or scheduled job is not being executed. For the AutoComplete and TextEditEnd event handlers, the formal option Parameters is implemented. It contains settings for getting choice data and allows you to manage this process by changing the properties of the structure that is passed in this parameter.

• Full-text search
• Search by substring or by the beginning of the string
• Instant or background search

The full-text search and search by substring were available in ChoiceDataGetProcessing handlers.

• Full-text search
• Search by substring (as an alternative to the search by the beginning of the string)
• Background search (the search is running while the user is typing the search string)

• External data source table record (ExternalDataSourceTableRecord);
• External data source record set (ExternalDataSourceTableRecordSet).

This change is not implemented in 8.3.2 compatibility mode.

• ExternalDataSourceRecord;
• ExternalDataSourceRecordSet.

• ExternalDataSourceTableRecord;
• ExternalDataSourceTableRecordSet.

• GetTotalsPeriod()
• SetTotalsPeriod()

• GetMaxTotalsPeriod()
• SetMaxTotalsPeriod()

• Title

• TitleText

The names of the UsualGroupRepresentation system enumeration items are changed. For compatibility purposes, the previous names are supported.

• Line
• Margin
• GroupBox

• WeakSeparation
• NormalSeparation
• StrongSeparation

• GetApplicationCaption
• SetApplicationCaption

• GetClientApplicationCaption
• SetClientApplicationCaption

• DesktopCommandInterface

• MainSectionCommandInterface

• DesktopWorkingArea

• StartPageWorkingArea

• Common/DesktopSettings
• Desktop/NavigationPanel/CommandInterfaceSettings
• Desktop/ActionsPanel/CommandInterfaceSettings

• Common/StartPageSettings
• MainSection/NavigationPanel/CommandInterfaceSettings
• MainSection/ActionsPanel/CommandInterfaceSettings.

• DesktopSettings

• StartPageSettings

• ЗавершитьРедактированиеТекущейОбласти()

• ЗакончитьРедактированиеТекущейОбласти()

For Android-based devices, the minimum RAM size is 256 MB.

Android-based devices required 100 MB of RAM to run 1C:Enterprise.

The following geolocation functions are implemented: GeographicCoordinates, LocationData, LocationProviderInformation, LocationTools, AddressData. The LocationTools global context property is implemented. Global context methods GetAddressByLocation(), GetLocationByAddress(), and ShowOnMap() are  implemented. The GeographicalSchemaCoordinates type is renamed to GeographicCoordinatesp; it is used in geolocation functions. The GeographicalSchemaCoordinates type name is supported for compatibility purposes.

The MultimediaData and MultimediaTools objects are implemented to support processing multimedia features. The MultimediaTools global context property is implemented.

• The Document and Output properties are not supported.
• The OnClick event is fired only during the attempt to switch to a new page. At this time, all properties of the EventData parameter except Href contain the UNDEFINED value. The Href property contains the address of the new page.

This functionality is similar to the PC-based platform functionality.

• Setting timeouts for interaction with network resources
• Using characters that do not belong to the ASCII character set in user names and passwords
• Generating URLs and getting values from them according to the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt) when custom text is added to a URL
• Generating HTTP requests, processing responses, and interacting with REST services from 1C:Enterprise script

The attempt to assign a value to a fixed structure item raises an exception. In value tables, serialization of index descriptions is implemented. The index contents are not serialized but restored during deserialization. The hash function value can be calculated based on MD5 and CRC32 algorithms using the DataHashing object. This functionality is similar to the PC-based platform functionality.

• Measure time intervals more precisely. For example, this can be handy for getting the duration of a specific action.
• Use fixed structures in a similar way to other fixed collections.
• Restore the value table state in more detail during its deserialization.
• Quickly determine whether a data set was modified in any way, regardless of data volume, from the script and without using any third-party tools.

• Edit data stored in specific rows of form table data in separate fields.
• Get fast access to managed forms with dynamic lists located on different pages.
• Ensure that the behavior of the mark that indicates that the field must be filled is the same for all attribute types.
• Specify font size in a form relative to the form base font, without using absolute font size values.
• Improve form usability by highlighting group colors.
• Create a handler for each hyperlink represented as a formatted string.
• Use more appearance customization options in managed forms.

When the size of a usual group is limited, the algorithm used for resizing group items is the same for all item types.

• Get nonstandard data presentations in various scenarios.
• Get document numbers in a uniform way, regardless of the method used to obtain the document numbers: either from the document itself or from the document journal. 
• Generate default values in the same way as they are generated on the PC-based platform.

This functionality is similar to the PC-based platform functionality.

• Funnel
• 3D funnel
• Normalized funnel
• 3D normalized funnel

The antialiasing mode is implemented for charts.

You can connect series of charts to each other.

The semitransparency mode is implemented for charts. 

The Indicator property is implemented for the tape graph chart.

This functionality is similar to the PC-based platform functionality.

This functionality is similar to the PC-based platform functionality.

The algorithm for horisontal cell placement in different rows is modified.

This functionality is similar to the PC-based platform functionality.

• Improve usability of reports that contain areas with left or top fixation.
• Improve usability of spreadsheet documents.

This functionality is similar to the PC-based platform functionality.

You can use a formatted string as:

• Data for the "label field" form items
• Title for form items of decoration type
• MessageText parameter of the DoMessageBox() method
• QueryText parameter of the DoQueryBox() method

The TextReader and TextWriter objects are implemented. This functionality is similar to the PC-based platform functionality.

The content of the mobile platform distribution kit is modified.

• The Modality usage mode property is set to Use.
• The Interface compatibility mode is set to Version 8.2.