- Development tools
- Performance improvements
- Touch screen support in the Taxi interface
- Mobile platform
- Integration with third-party systems
You can modify configuration modules by modifying any of their methods. The options include adding custom operations before or after method execution, as well as full replacement.
You can create event handlers that are not available in the original configuration.
You can create common modules in extensions.
You can create custom roles in extensions.
More options for roles adopted from the original configuration. You can allow or deny access to objects of the original configuration.
Extension applicability checks
You can check whether an extension can be applied before loading it to the target infobase. The options include interactive checks, 1C:Enterprise script checks, and automatic checks.
The order of extension attachment error disgnostics is changed in order to minimize extension development efforts.
A set of low-level tools for working with binary data is implemented. You can use these tools for serial processing of large data volumes. They also provide random access to relatively small volumes of binary data that are fully stored in RAM. The new tools address the following tasks:
- Communicating with specialized devices over binary protocols
- Parsing and manipulating files in a variety of formats
- Converting text data into binary data (this can be useful for sending reports)
- Performing operations wth binary data in RAM
Server call diagnostics
Diagnostics of incorrect context server calls are implemented. This helps to eliminate errors related to server calls from handlers where server calls are not recommended.
Reusing sessions greatly improves web service performance.
Two strategies are implemented:
- Automatic reuse of sessions available in the pool
- Session management using HTTP headers
You can select a strategy based on the specifics of the web services that you use.
Beta versions of 64-bit Windows applications
64-bit versions of all 1C:Enterprise applications and tools are implemented. This includes the thin client, the thick client, Designer, the database file integrity check utility, the database file conversion utility, and the configuration repository server.
64-bit applications have the following advantage: the amount of RAM that they can use is not limited. This simplifies work with large configurations in Designer.
The performance of operations with formatted documents that contain large volumes of data is improved.
The thin client now includes support of gesture-based scrolling and scaling. Scrolling is available for text documents, spreadsheet documents, text boxes, graphical schemas, planners, and formatted documents. Scaling is available for graphical schemas, geographical schemas, and spreadsheet documents.
For many controls, the tap area is enlarged.
Visual confirmation for tapping form buttons and command bar buttons is implemented.
The option to play a sound alert on a mobile device is added to 1C:Enterprise script language. You can use it to alert users when notifications are delivered directly to mobile applications.
New options for processing audio records. You can get audio record duration, as well as play, pause, and resume audio records.
Screen reader support
Screen reader support is available on mobile devices. You can select language, reading speed, and the pitch of a voice.
Processing of phone calls
On Android mobile devices, handling of the following phone call events is implemented: begin call, answer call, and end call. The call date and incoming or outgoing call number are available.
Waiting for suitable Internet connection
An event that occurs when Internet connection parameters change and an object that provides mobile connection parameters are implemented. You can use them to implement scenarios where applications wait for suitable Internet connections or check whether any Internet connection is available. For example, when an application detects a suitable connection, it can notify the user or perform postponed operations. If no connections are available, an application can skip data exchange.
Mobile platform interface usability
Support of collapsible groups is implemented. You can select the mode of displaying page titles: titles only, current page only, or both.
In text boxes, you can manage the visibility of select and clear buttons, height of multiline boxes, switching to the edit mode from 1C:Enterprise script, and data input modes supported by the mobile device.
Other usability improvements for tables, search boxes, and spreadsheet documents.
Data composition system
On the mobile platform, access to data composition system from 1C:Enterprise script is implemented. You can generate reports based on data composition schemas created in Designer. You can use 1C:Enterprise script language to set custom filters in the data composition system and get data from the database for further processing.
Tools for verification, repair, and backup of mobile infobases are implemented. Verification and repair options exactly match the options available on the desktop platform. Both interactive and automatic backups are available.
Add-in support is added to the mobile platform. You can create add-ins using the Native API technology just like you would create them for the desktop platform.
Improved TLS1.2 support
Improved support of TSL1.2. Applications can use this protocol even if the client certificate source is not specified.
Support of GOST encryption algorithms for TLS connections is implemented. This allows integration with public services that only support GOST encryption algorithms.
Canonical XML 1.1 support
Support of Canonical XML 1.1 standard is implemented. This simplifies communication with companies that use electronic document flow.
Complete list of changes
Next page: New features in version 8.3.8
For the full list of changes, see the file V8Update.htm.
On Windows, if the platform is installed in the default folder, the file is located in Program Files\1cv8\8.3.9.<build number>\docs\en\
On Linux, if the platform is installed in the default folder, the file is located in /opt/1c/v8.3/i386/docs/en/
On OS X, if the platform is installed in the default folder, the file is located in /opt/1cv8/188.8.131.522/docs/en/