|Functionality||After||Before||Result of changes|
|Configuration properties.||Version 8.2.16 is added to the list of available values of the Compatibility mode property.||Compatibility modes were available for the following platform versions: 8.1 and 8.2.13.||1C:Enterprise provides compatibility of configurations developed using version 8.3.1 or later with previous platform versions.|
The client application for Linux operating system is available. It includes thin client, thick client, and Designer. It supports file and client/server operation modes. Thin client can connect to infobases using a web browser. Limitations of the client application for Linux are listed in the documentation.
Installation of multiple 1C:Enterprise versions is not supported.
Shortcuts for noninteractive startup application, thin client, and thick client are added to the application menu of Linux desktop environment. They are located in the Finance subsection of the Office section.
|Only the 1C:Enterprise server and the web client were available for Linux operating system.||You can develop applied solutions and run client applications on Linux operating system.|
|Thin client access over the Internet.||
The thin client is now HTTPS-enabled, thanks to client certificate support. The following client certificate storage options are supported: file, Windows certificate store, and NSS certificate store.
The following command line options for specifying certificate parameters are implemented: HttpsCert, HttpsCA and HttpsNSS.
Client applications for Linux operating system do not support Windows certificate store, and HttpsCert, and HttpsCA command line options.
|The thin client was not HTTP-enabled, and client certificates were not supported.||The thin client is HTTP-enabled, and client certificates are supported.|
|Web links.||Web services can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).||Web services could not operate using HTTPS with client certificates.||Web services are operational in cases when the server side requires a client certificate to use HTTPS.|
|Internet-enabled functionality.||HTTP and FTP connections can operate using HTTPS with client certificates (from a file, Windows certificate store, or NSS certificate store).||HTTP and FTP connections could not operate using HTTPS with client certificates.||HTTP and FTP connections are operational in cases when the server side requires a client certificate to use HTTPS.|
|1C:Enterprise script.||You can calculate the value of hash function by MD5 and CRC32 algorithms using the DataHashing object.||Calculating the hash function required the use of third-party (add-ins, etc.) tools.||You can 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.|
|External data sources. Common attributes / Data separation.||A common attribute can include an external data source. Connection parameters for such external data sources are stored by separator values. If a separator is not used in a session, the separator is treated as an independent value for storing connection parameters. Data located in tables of external data sources is not separated by separator values.||Common attributes could not include external data sources.||You can specify connection parameters for each data area in the infobase. This provides you with the option to access either different infobases with the same structure, or a single infobase with different connection parameters.|
|Managed form.||You can specify data located in a specific row of a form attribute that has table structure (except dynamic lists) as a value of a managed form field or table.||This feature was not provided.||You can implement such interface features as displaying report settings in separate form fields.|
|External data sources.||Operating system authentication is available when working with external data sources. The SessionOSAuthenticationChange access right is implemented. It allows or denies changing the operating system authentication setting both in user settings and in current session parameters.||This feature was not provided.||You can establish connection to external data sources if the only authentication method available is operating system authentication.|
|Applied objects. Display of information.||
User presentations for data base objects of the following types: Catalog, Document, ChartOfAccounts, ChartOfCalculationTypes, ChartOfCharacteristicTypes, BusinessProcess, Task, ExchangePlan, Table. Implemented the PresentationFieldsGetProcessing and PresentationGetProcessing event handlers for object manager modules of these types.
This change is not implemented in version 8.2.16 compatibility mode.
|Modification of database objects using script tools was not allowed.||Custom presentations for database objects. The option to obtain presentations for external data source tables when the field that provides the presentation is not specified. The option to obtain presentations of objects that include localized data.|
External data sources.
|You can search for references to objects of external data source tables using the FindByRef() global context method or Find references to object standard function. The search is performed both in infobase tables and in external data source tables.||Searching for references to objects of external data sources tables using the FindByRef() global context method or Find references to object standard function was not available.||You can search for references to objects of external data source tables.|
|External data sources.||The AllRefsType() method is implemented for the ExternalDataSourceTablesManager object.||This feature was not provided.||Implementation of missing features for working with external data sources.|
|External data sources.||The OpenValue() global context method allows opening the following value types: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey.||The OpenValue() global context method did not allow opening the following value type: InformationRegisterRecordKey and ExternalDataSourceTableRecordKey.||Implementation of missing features for working with information registers and external data sources.|
|Database configuration update. Server cluster.||Background database configuration update is implemented. Supported in client/server mode only. Available when the data structure is modified. Does not require long-lasting exclusive access to the infobase. The exclusive access is required at the final stage of the background update for a short period of time. Database configuration update service is implemented in the server cluster. A system background job, which is used for the background database configuration update, is implemented. The following events are implemented in the event log: _$InfoBase$_.DBConfigBackgroundUpdateStart, _$InfoBase$_.DBConfigBackgroundUpdateFinish, _$InfoBase$_.DBConfigBackgroundUpdateCancel, _$InfoBase$_.DBConfigBackgroundUpdateSuspend, and _$InfoBase$_.DBConfigBackgroundUpdateResume.||Database configuration update related to the change of data structure was possible only in the exclusive mode.||The update of database configuration with significant changes in the data structure does not cause long application downtime for end users.|
|1C:Enterprise script. Working with files. Web client.||
The TempFilesDir() method is implemented for the web client. The method is available when the file system extension is installed.
The UserDataWorkDir() method is implemented. It provides access to the user directory created by the system. The method is available for thin, thick, and web clients. In the web client the method is available when the file system extension is installed.
The DocumentsDir() method is implemented. It provides access to the default document directory of the operating system. The method is available for thin, thick and web clients. In the web client the method is available when the file system extension is installed.
|Standard catalogs (user data directory and document directory) were inaccessible for standard tools. In the thick and thin clients the access could be implemented using third-party tools, which reduced 1C:Enterprise portability between operating systems and client applications types.||Access to certain standard directories on the client computer, which allows storing user file data in designed locations without using third-party tools.|
|Display of information.||
Formatted strings are available (FormattedString type). You can use formatted strings as:
||Displaying text that included various formatting styles was only available for HTML documents and formatted documents.||Improved text presentation capabilities and usability.|
|1C:Enterprise script. Managed form.||
The URLProcessing handler is implemented for the form field Label, form field Decoration of Label type, and managed form.
The handler is called if the following conditions are met: there is a formatted string in any of the specified form fields, it contains a hyperlink, and the Hyperlink property of the form element is set to False.
|Implementing presentation of an entire form element as a hyperlink was allowed, but including multiple hyperlinks in a single field was not allowed.||The option to handle each hyperlink contained in a formatted string separately.|
You can use navigation links to commands of the global command interface. Using a link executes the command.
Support of navigation links to commands is implemented for the GotoURLGotoURL() global context method.
|This feature was not provided.||Using a link can execute a command, and this feature can be used in the script.|
The URL property is implemented for managed forms. It is used for obtaining a link to the default object form.
The AutoURL property is implemented for the managed form. The GetURL() method of the ClientApplicationWindow objects returns a value of the URL property (if the AutoURL property is set to False) or the standard link to the default form.
|This feature was not provided.||You can specify the value of the navigation link obtained from the client application window.|
|1C:Enterprise script. Common attributes / Data separation. Applied objects.||Document journals can be included in contents of common attributes, which are not used as separators. For compatibility purposes, in infobases created in 1C:Enterprise version 8.2, the value of the Use property of the the common attribute content element is set to Do not use for document journals.||Common attributes could not be displayed in document journals.||Common attributes can be displayed in document journals.|
|Display of information. Managed form.||
Implemented the following style fonts: SmallTextFont, LargeTextFont, ExtraLargeTextFont.
For the Font type the Scale property is implemented. It specifies increase or decrease of the font size relatively to the original size.
|The only method of specifying font size in a managed form was setting absolute font size.||You can specify the size of the form font relatively to the base font of the form, without using absolute font size values.|
|Server cluster. 1С:Enterprise script.||The SafeCallMemoryLimit property is implemented for the IWorkingProcessInfo object. It specifies the amount of memory (in bytes) that the application can use during a single server call. The SafeWorkingProcessesMemoryLimit property for the IWorkingServerInfo object is implemented. It specifies maximum amount of memory (in bytes) available for all running processes on a given working server.||No tools for limiting memory usage were available. It might cause problems in some situations - for example, when users customized reports that selected large amounts of data.||Server stability improved. If a specific session consumes a large amount of memory, it does not cause emergency shutdown of the entire server cluster. Instead, the client application that causes the memory consumption is shut down.|
|Server cluster. 1C:Enterprise script.||While a working process is executing a script in the client/server infobase mode, the stack is monitored to prevent it from overflowing.||Infinite recursion might lead to emergency shutdown of the working process of the server cluster.||Stability of server cluster operation improved.|
|Server cluster. 1C:Enterprise script.||
For the ISessionInfo and IInfoBaseConnectionInfo objects the following properties are implemented:
Similar properties are implemented in the cluster console for the list of sessions, list of connections, and connection properties dialog.
|This feature was not provided.||Monitoring tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.|
|Technological log. Server cluster.||
Extended the list of properties for the <call> event of the technological log when the event is generated for the rphost process (the process property is set to rphost), and also when the rphost process performs a call to virtual system resources. The following properties are added:
||The listed properties were absent from the <call> event.||Technological log tools help to determine elements of the applied solution that lead to unnecessary consumption of memory and disk space.|
|Common attributes / Data separation. 1C:Enterprise script.||
You can delete data from a specific data area or from the entire infobase. The following data can be deleted:
The Administration right is required for deletion. The deletion can be performed:
The _$InfoBase$_.EraseData event is implemented in the event log.
|It was impossible to delete a specific data area.||You can delete a data area that is no longer needed (for example, data belonging to a subscriber that stopped using the system).|
|Server cluster. Software licensing.||The licensing service is implemented for the server cluster. The license search algorithm is modified.||The licensing service was not present.||You have the option to bind a software license to a specific computer, which is intended for running the licensing service only and will not be subject to hardware changes.|
Dumping configurations to files and loading configurations from files is implemented.
Most objects are dumped to .xml files. Modules are dumped to the text files. Pictures are dumped to files in their original format, help information is dumped to .html files. Vendor configurations are dumped to configuration files (.cf). Ordinary forms and interfaces are dumped to binary files.
Dump configuration to files and Load configuration from files commands are added to the Configuration menu. Dump configuration files and Load configuration files commands are removed from the Configuration menu, but you can restore them using the main menu settings dialog.
The DumpConfigToFiles and LoadConfigFromFiles command line options are implemented.
Limited set of data was dumped and loaded: modules, help information, templates, rights, and pictures. Other configuration data was not dumped.
Dump configuration files and Load configuration files commands from the Configuration menu were used for dumping and loading data.
|You can analyze and modify configurations using third-party tools.|
|Display of information. Managed form.||You can specify the background color for form group extensions of regular groups and pages using the BackColor property. If the background color of a group is different from Auto and the group is displayed as a Group box, the group box (including the title) is filled with the specified background color.||The option to specify background color for form groups was not provided.||The color highlighting of groups improves visibility of form elements and the overall usability of forms.|
|Common attributes / Data separation.||New global context methods for managing the safe mode of data separation are available in 1C:Enterprise script: SetDataSeparationSafeMode and DataSeparationSafeMode. They duplicate the functionality of the safe attribute in the zone tag of the default.vrd file.||Switching to the safe mode of data separation was only available by editing the file default.vrd and only if the web server connection to the infobase (the HTTP protocol) was used.||The new methods enable safe execution of code fragments called from sessions that do not use separator values (but are intended to run in specific data areas, without any way to change the area accidentally).|
|Event log. OpenID authentication.||In case of successful or unsuccessful OpenID authentication the Session.Authentication or Session. Authentication error events are generated in the event log.||OpenID authentication events were not written to the event log.||You can obtain information about OpenID authentication events from the event log.|
|Event log. OpenID-authentication.||For infobases that are OpenID providers the OpenIDProvider.PositiveAssertion event is implemented. It is generated in case of a positive response to the authentication request. If the response to the authentication request is negative, the OpenIDProvider.NegativeAssertion event is generated in the event log of the infobase.||This feature was not provided.||Improved tools for administration of OpenID providers.|
|Developing tools.||You can view the values of the form element properties Font, TitleFont, FooterFont and ChoiceList in a separate window when editing of these properties is disabled.||These properties could not be viewed if the object was not locked in the repository or was supported.||If an item is not locked in the configuration repository or is supported, you can view its font style and choice list without disabling support and without locking the object in the repository.|
When logon to or logout from an infobase that requires a client license is performed, the platform can notify an external application using web service methods. In response to logon notification, the external application can allow or deny the start of the session. This option is only available in client/server infobase mode. For specifying web service parameters, the following properties are implemented:
If a web service for external session management is unavailable, the system behavior is determined using the following properties:
The external session manager service is implemented on the server.
Parameters of invoked web services are listed in the documentation.
|The only option to limit the number of simultaneous sessions was appropriate modification of the applied solution. A platform mechanism for performing this task was not available.||A platform mechanism for monitoring the number of simultaneously used licenses for various applied solutions, which does not require modification of these applied solutions.|
|Web client. Add-ins.||You can use add-ins in Google Chrome and Safari web browsers (for operating systems of Windows family and Mac OS X). The Mac OS value is implemented for the PlatformType system enumeration. A file system extension is available for these browsers on operating systems of Windows family and Mac OS X. A cryptographic extension is available for these browsers on operating systems of Windows family only.||Add-ins, file system extension, and cryptographic extension were not supported for Google Chrome and Safari web browsers.||A file system extension and cryptographic extension (for operating systems of Windows family only) are available for Google Chrome and Safari web browsers. Add-ins can be created for all supported web browsers.|
Processing pictures from the script with help of the new PictureProcessor object. The following options are available:
||This feature was not provided.||
A way to process pictures before placing them in a spreadsheet document. Usage examples:
|Charts.||The managed form editor allows interactive setup for the following attribute types: Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema. You can open the interactive setup dialog box from the property panel of the attribute.||Only the following ways to set up the Chart, GanttChart, Dendrogram, SpreadsheetDocument, GraphicalSchema, and GeographicalSchema objects were available: through 1C:Enterprise script, or by putting a set up object to a template and then putting the object from the template to a form element at form creation.||This feature facilitates development.|
|Display of information.||
New parameter AU for the global context method NumberInWords(). It is only used in the English locale (en, en_XX). It defines the number notation, classic or compact.
In the classic notation "and" is always used between the word "hundred" (or "thousand" or "million") and the word representing the last two decimal digits. For example, 150 is "one hundred and fifty", while 100 is "one hundred" and 50 is "fifty". In the compact notation "and" is omitted.
|The compact notation was always used for converting numbers to English words.||Correct number-to-word conversion according to the common practice rule in European countries.|
|Chart of characteristic types.||You can use the ALLOWED keyword when retrieving a list of characteristics, provided that the list was defined using one of the following: the CHARACTERISTICS keyword of the query language or the dialog box for specifying object characteristics. If you retrieve the list of characteristics using a query, you have the option to use the ALLOWED keyword there.||The ALLOWED keyword was not used when retrieving lists of characteristics.||Data access restrictions are implemented for tables that store property lists (for example, charts of characteristic types).|
|Data composition system.||
Fields from data sets that are not connected can be displayed in details. For DataCompositionTemplateRecordsDataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects, the DataSets properties are implemented. The property value is an array containing names of data sets whose details are displayed.
The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords objects is deprecated. It is recommended that you do not use this property, although it is supported for compatibility purposes. Calling the DataSet property throws an exception if the DataSets property contains an array with more than one item.
It was impossible to display fields from data sets that were not connected.
The DataSet property of DataCompositionTemplateRecords and DataCompositionTemplateTableRecords contained the name of the dataset whose details were displayed.
|You can create complex analytic reports.|
|External data sources.||The FormGetProcessing event is implemented in the manager module of external data source table.||This feature was not provided.||The default form of the external data source can be redefined when the external data source is opened or obtained.|
|External data sources.||Hierarchical lists can be organized for object data of external data sources. The ParentField and UnfilledParentValue attributes are implemented for the Table metadata object. Hierarchical object tables can be used in the data composition system, queries, and dynamic lists.||This feature was not provided.||You can work with hierarchical data in external data sources.|
|External data sources. Working with queries. Data composition system.||You can use temporary tables when working with external data sources. Temporary tables are created directly in the database of the external data source. The following syntax is used for calling temporary tables:ExternalDataSource.<External data source name>.TempTable.<Temp table name>.||This feature was not provided.||You can create complex reports based on external data source tables.|
|Chart of characteristic types. Data composition system.||
When creating object characteristics using the Additional characteristics of metadata object dialog, if the list of characteristics is not obtained from the chart of characteristic types, the characteristic value type is defined by the attribute type specified in the Value field attribute of this dialog. If this attribute is not specified, the characteristic value type is Boolean.
When object characteristics are specified using the CHARACTERISTICS query language extension of the data composition system, if the TYPE property is not specified, the characteristic type is defined by the value type obtained in the CHARACTERISTICVALUES property. If the CHARACTERISTICVALUES property is not specified, the characteristic value type is Boolean.
When object characteristics were specified using the Additional characteristics of metadata object dialog or the CHARACTERISTICS query language extension, if the list of characteristics was not obtained from the chart of characteristic types, the characteristic value type was Boolean.
|You can store characteristic types in catalogs, and you can modify characteristic types using a complex type of the attribute that stores the characteristic value (e.g., type of information register resource).|
|1C:Enterprise script.||Serialization of value table index descriptions is implemented. The index content is not serialized, but restored during deserialization.||Value table indexes were lost during serialization/deserialization.||More complete restoration of value table state during deserialization.|
New types of charts are implemented:
The following properties are implemented for the Chart object: FunnelNeckHeight, FunnelNeckWidth, and FunnelSpace. These properties are applicable for the new charts types only.
|This feature was not provided.||New chart functionality.|
|Charts.||Antialiasing mode is implemented for charts. SplineMode and SplineStrain properties are implemented for the Chart object. These properties are applicable to the following chart types: line, stacked line, area, stacked area, normalized area, ceil graph, tape graph, waterfall, funnel, and 3D funnel, and also for the following chart types, which have the Indicator flag set for the series: column, 3D column, bar, 3D bar, stacked column, 3D stacked column, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.||This feature was not provided.||New chart functionality.|
|Charts.||You can connect series of charts with each other. For the Chart object the following properties are implemented: ValuesBySeriesConnection, ValuesBySeriesConnectionLines, and ValuesBySeriesConnectionColor. These properties are applicable to the following chart types: stacked column, 3D stacked column, stacked bar, 3D stacked bar, normalized column, 3D normalized column, normalized bar, and 3D normalized bar.||This feature was not provided.||New chart functionality.|
|Charts.||The semitransparency mode is implemented for charts. SemitransparencyMode and SemitransparencyPercent properties are implemented for the Chart object. These properties are applicable to the following chart types: area, bar graph, pyramid graph, ceil graph, tape graph, waterfall, funnel, 3D funnel, and 3D normalized funnel.||This feature was not provided.||New chart functionality.|
Data composition system.
|For the objects DataCompositionOutputParameterValues, DataCompositionGroupOutputParameterValues, DataCompositionChartOutputParameterValues, and DataCompositionAreaTemplateChartAppearance the following properties are implemented: ChartType.ValuesBySeriesConnection, ChartType.ValuesBySeriesConnectionLines, ChartType.ValuesBySeriesConnectionColor, ChartType.SplineMode, ChartType.SplineStrain, and ChartType.SemitransparencyMode. These properties are used for setting data composition template parameters.||This feature was not provided.||New chart management options in the data composition system.|
|Data composition system.||In the data composition system expression language the following aggregate functions are implemented: Every(), Any(), Stddev_Pop(), Stddev_Samp(), Var_Samp(), Var_Pop(), Covar_Pop(), Covar_Samp(), Corr(), Regr_Slope(), Regr_Intercept(), Regr_Count(), Regr_R2(), Regr_AvgX(), Regr_AvgY(), Regr_SXX(), Regr_SYY(), and Regr_SXY().||These aggregate functions were not provided in the data composition system expression language.||The new functions facilitate creation of complex analytic reports.|
|Data composition system.||In the data composition system expression language the following functions are implemented: ACos(), ASin(), ATan(), Sin(), Cos(), Tan(), Exp(), Log(), Log10(), Pow(), Sqrt(), Round(), Int(), ValueType(), and Type().||These functions were not provided in the data composition system expression language.||The new functions facilitate creation of complex analytic reports.|
|Data composition system.||New aggregate function Rank() in the data composition system expression language. The function returns a sequence number of the current record in the current grouping, provided that all records of the current grouping are sorted in the specified order.||This aggregate function was not provided in the data composition system expression language.||The new functions facilitate creation of complex analytic reports.|
|Data composition system.||New aggregate function ClassificationABC() in the data composition system expression language. The function returns the class number: 1 – class "А", 2 – class "B", 3 – class "C".||This aggregate function was not provided in the data composition system expression language.||The new function facilitates creation of complex analytic reports.|
The Merge command is added to the shortcut menu of a spreadsheet document. It is also accessible through a keyboard shortcut Ctrl+M.
|Merging cells of a spreadsheet document was only available by using the menu command Table - Merge or clicking the corresponding toolbar button.||Improved usability of spreadsheet documents containing a large number of merged cells.|
|Charts.||The Indicator property is supported for the tape graph chart: when antialiasing is disabled, the series with the Indicator property set are displayed semitransparently on the entire chart area, overlapping other series.||This feature was not provided.||New chart functionality.|
|Managed form.||You can specify the Arbitrary type for a subordinated attribute of a managed form attribute (e.g., column of a value table, column of a value tree, etc.).||It was impossible to store some data types (such as a references to external data source tables) in subordinated attributes of managed form attributes.||You can store references to external data source tables in subordinated attributes of managed form attributes.|
|Display of information.||You can manage duplex printing of spreadsheet documents, graphical schemas (using script and interactively), and text documents (interactively only). System enumerations DuplexPrintingType and PagePlacementAlternation are implemented.||This functionality was only available from a printer driver.||You can explicitly specify the duplex printing option in some use cases.|
|Developing tools. Tools for publishing the web client and web services.||In the dialog for publishing to the web server you can edit all tags present in the default.vrd file. You can edit custom default.vrd files in this dialog. The descriptor parameter of the webinst utility allows you to perform publishing by template. The generated default.vrd file is used as a template.||A limited set of tags present in the default.vrd file was available for editing in the dialog for publishing to the web server. The option to publish by template was unavailable in the webinst utility, which limited the capabilities of automatic publication. E.g., publishing of web services using the utility was impossible.||You can edit all tags of the default.vrd file interactively, and you can create templates for the future automatic publication. Using templates allows publishing web services using the command line utility.|
|Client application installation.||
You can set up the update of thin client distribution kit and downloading the list of common infobases using an HTTP connection or a web service.
If versions of client and server applications do not match, the thin client is downloaded and installed automatically.
The following parameters of the 1cestart.cfg file are implemented :
You can specify a link to the thin client distribution kit in the following configuration files:
|The automatic update of the thin client and downloading of list of common Infobases were only available in a local network.||You can update the thin client distribution kit and download the list of common Infobases without creating common directories. This allows you to obtain an up-to-date version of the distribution kit and the current list of Infobases from a remote network.|
|Working with DBMS.||
DBA rights are not required for creating Infobases in Oracle Database. The following actions cannot be performed without DBA rights:
||DBA rights were required for creating Infobases in Oracle Database.||Increased security of DBMS operations. New scenario of creating an Infobase without DBA rights, provided the database (data schema) already exists.|
|Working with the Internet. 1C:Enterprise script.||
Encoding of text strings is implemented (the global context method EncodeString()). It simplifies the following operations:
Decoding of text strings is implemented (method DecodeString()).
|This feature was not available.||Easier generation of URLs containing non-English characters.|
You can create a self-extracting archive (SFX archive) of a client application and upload it to a web site. You can include the client application distribution kit and the 1CEStart.cfg configuration file, which is used for installing the client application, into the archive. The created executable file is only intended to run on Windows operating systems.
The self-extracting archive is generated using the 1CEClientSetupMake.exe utility, which is distributed via ITS (http://its.1c.ru/db/metod81#content:4914:1).
|This feature was not provided.||Simplified installation of client applications on the client computer for Infobase access over the Internet (instead of using the web client).|