View online demo
- Taxi interface development
- Client application reliability improvements
- Third-party software integration development
- Mobile platform development
- New development tools
Taxi interface development
Dynamic list search improvements
The dynamic list search is refactored. The following improvements are added:
- Full-text search
- Search in all list columns
- Highlighting of the search string in the text
- Search by number, which ignores leading zeros
- Search by the current value
- Automatic displaying of search string values
- Search history
Period selection dialog improvements
The period selection dialog is significantly refactored. It is oriented to quick execution of the most frequent action: month or month range selection. Also, the option to select one of the predefined periods (last week, this month, and so on) is added.
1C:Enterprise script-based start page setup
The option to specify start page forms and their positions using 1C:Enterprise script is implemented. This option is handy for applications that display forms for entering initial balances at the beginning, and once the balances are entered, hide these forms to display different ones.
Client application reliability improvements
Maintaining connection when a user does not perform any actions
The idle connection timeout is increased. If a user is inactive for a long time, when a client computer enters hibernation mode, the session is not terminated but also enters the hibernation mode. Once the user resumes their activity, the session is resumed. Administrators can set the timeout for terminating hibernated sessions.
Long action support
During a lengthy 1C:Enterprise server operation a web browser or a web server can close the connection due to its inactivity. When performing read operations, client 1C:Enterprise applications can repeat their requests automatically.
And now this option is also available for data modification operations. In most cases, in the event of an error or network connection loss the client application continues its functioning. The client application displays a dialog box prompting to repeat the request, cancel the request, or exit the application. It automatically repeats the request after 60 seconds.
Third-party software integration development
Automatic REST interface for applied solutions
The option to publish automatic REST interface for applied solutions to the web server is implemented. Third-party systems can access it using HTTP requests for reading and changing data, as well as creating and deleting objects. Therefore, integration of applied solutions with third-party tools does not require modification of applied solutions.
Automatic REST interface is suitable for solving the following tasks:
- Integration of applied solutions with web sites and online stores
- Implementation of additional functionality using third-party software, without changing applied solution configuration
- Import and export of applied solution data
- Integration of applied solutions with corporate systems, perhaps even without additional programming
HTTP services in applied solutions
The option to create proprietary HTTP services is implemented. HTTP services have several advantages compared to SOAP services that are also available in the platform:
- Easy development of client applications
- Less data volumes to transfer
- Lower computation load
- HTTP services are resource-oriented, while SOAP services are action-oriented.
The first three factors are very important for mobile applications.
Editing data in external data sources
The options to add, edit, or delete external data source data is implemented. Both interactive data changes and data changes using 1C:Enterprise script are available. This feature supports data versioning, as well as data locks and transactions.
Mobile platform development
Mobile application-specific functionality improvements
New features that include interactions with frequently used mobile applications ae implemented:
- Phone book and contacts. This includes creation, modification, and deletion of records.
- Smartphone calendars and events. This includes creation, modification, and deletion of calendars and events, setting reminders, specifying periodicity and the list of meeting attendees.
- Dialing phone numbers, sending and receiving SMS and MMS messages, viewing call history.
- Sending email messages using the built-in email client of the smartphone operating system.
Background jobs are implemented for the mobile platform. As a result, synchronization of mobile applications with the main infobase can be performed in background, without interrupting user work.
A set of objects for support of custom queries in mobile application dynamic lists is implemented. This makes mobile application query functionality similar to that of desktop applications.
You can also use the queries for reading data. This ensures that the logic of data operations is preserved across the desktop and mobile platforms.
Running mobile applications on device emulators
Android Debug Bridge (ADB) commands are integrated in Designer. This provides mobile application developers with the option to run their applications on devices connected to their PCs or on a virtual Android device.
Each chart type features one or several animation options. When displaying a chart for the first time, the platform selects a random animation option for it. This provides better look and feel for charts.
Event log improvements
The event log is significantly refactored in order to increase the performance of event log requests and improve data storage reliability. The event log format is changed. Methods for archiving and clearing selected log parts are added to 1C:Enterprise script.
New development tools
Full-text search options in Designer
The full-text search for configuration objects is implemented in Designer. It is handy for developers of large configurations. The new search algorithm quickly finds the objects and displays them directly in the window where the search is initiated. The new search is available in:
- Configuration tree
- Property palette
- Type selection dialog box
- Configuration object selection dialog box
Also, a quick filter by current subsystem and a quick filter by objects locked in the repository are implemented in the configuration tree.
Commands for automatic conversion of modal methods and script fragments
A set of commands for searching the configuration for modal calls and checking whether these calls can be converted to nonmodal blocking calls is implemented. These commands also provide the option to convert the found script fragments automatically or semi-automatically, in order to eliminate modal calls.
A set of commands that make 1C:Enterprise script fragments easier to read and understand is implemented. Refactoring commands include the following:
- Extracting a script fragment to a new procedure
- Creating a procedure description based on a standard template
- Finding all usage instances for a function, procedure, or variable
- Renaming a function, procedure, or variable in all usage instances
Query builder for managed applications
Query builder for managed applications is implemented. The query generation is peformed without using modal calls.
Also, the object model of the query schema is implemented in 1C:Enterprise script. So, the creation or modification of a query can be performed in terms of sources, tables, filters and so on, instead of combining text strings that describe query conditions, as it was done before.
Complete list of changes
Next page: New features in version 8.3.4
The full list of changes is available in file V8Update.htm.
On Windows, if the platform is installed in the default folder, the file is located in Program Files\1cv8\8.3.5.<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/