In this small article, which is the beginning of the cycle "Development of 1C mobile applications", I will show you how you can quickly create 1C mobile app"Hello World", based on the 1C mobile platform.
To test the finished 1C mobile application, real device based on operating Android systems, using a mobile developer platform and HTTP debugging capabilities.
Apache web server installation
1. Download the compiled files of the Apache web server, version 2.2 (At the time of writing, the 1C platform could work only with the specified version). You can choose where to download from at: https://httpd.apache.org/docs/current/platform/windows.html#down section "". For example, we use the ApacheHaus website and download the archive depending on the bitness of your operating system.
Unpack the downloaded archive, along the path: "C: \ Apache22", make sure that port 80 on your computer is free and not occupied by another application. Next, using the "Command Line" (run as administrator), go to the directory "C: \ Apache22 \ bin" and execute the commands:
Httpd -k install
Httpd -k start
After that, the service "Apache2.2" will be installed and started, which can be checked in the browser at the address: http://127.0.0.1/ but instead of 127.0.0.1 use the IP address of your network card, through which the data exchange will take place, with the developed 1C mobile application.
If the installation was successful, you will see information about the server and the inscription “It works!”.
In folder with executable files web server, there is an application " ApacheMonitor.exe"Which serves handy utility to stop and restart the server. Link to this application we put it in the autoload of the operating system, for example, in the folder:
C: \ Users \ [UserName] \ AppData \ Roaming \ Microsoft \ Windows \ Start Menu \ Programs \ Startup
Installation of a mobile platform for 1C developers
2. Download and unpack the archive with a mobile platform for 1C developers, from the addresses available to you:
https://users.v8.1c.ru/distribution/total, http://online.1c.ru/catalog/free/18610155/, http://its.1c.ru/, or from torrent trackers.
The "Android" folder contains APK files (1cem-arm.apk and 1cem-x86.apk), select required type(arm or x86 (Intel)) depending on what architecture is used in the processor of your device.
Install the application on your device, before that enable the permission to install from unknown sources (Settings - section "Security").
Creating a configuration for a mobile application
3. On local computer create a new database and start the "Configurator". In the configuration properties, for the "Purpose of use" parameter, specify "Mobile device".
Create a general shape and place on it "Decoration - Lettering" with the text "Hello World" and the command "PressMe", with the handler:
& OnClient Procedure Press Me (Command) Report ("Hello World !!!"); End of Procedure
After, open "Options" (Tools - Options) and select the "Debug" tab, set the settings according to the screenshot:
Checking firewall settings
4. Check your firewall settings, TCP ports 80 and 45455 should be available. On the home computer I use " ESET Smart Security ", version 9, for it you need to go to" Additional settings", Select the section" Personal firewall ", then subsection" General "and" Change "rules.
Check on the mobile device access to the Apache web server and the 1C debugger, for this, in the browser, use the IP address of the network card through which data is exchanged with the developed 1C mobile application, examples of addresses: http://192.168.0.96 and http://192.168.0.96:45455
Setting up the 1C mobile application
5. Open the mobile platform to Android device and add a new application, configure as shown in the screenshot (use your IP address):
Testing of the 1C mobile application
6. Test your 1C mobile application "Hello World". Additionally, try placing a breakpoint in your button click routine.
In the future, I plan to continue this series of articles "Development of 1C mobile applications", where I will try to explain in a simple and accessible way what needs to be done to learn how to create 1C mobile applications.
Mobile platform "1C: Enterprise 8" is the name of the technology that allows you to develop solutions that work on smartphones and tablets Google android or Apple iOS. An important advantage of the 1C platform is that solutions are developed in one version for both mobile operating systems and then just exported to Android and for iOS without any additional modification and writing platform-dependent program code.
On the mobile device both the 1C: Enterprise platform and the infobase itself (configuration, in terms of 1C) are installed immediately. The infobase on the device contains a version of the file database (for storing various data with which the user works or will work) and the application itself (program byte code that is executed on a tablet or smartphone).
An example of a mobile client for the EDMS "Corporate document flow" created on the mobile platform "1C: Enterprise 8.3"
The platform supports downloading and deploying applications by users to their devices from stores App Store or Google play... At the same time, the distribution kit contains all the components necessary to get started.
Various solutions can be created on the basis of the 1C mobile platform, but the main solution is mobile off-line clients for accounting systems. These solutions are designed to support mobile users in remote workplaces. In this case, data exchange is carried out by means of regular synchronization with a central database. Data exchange is possible through the following mechanisms:
- Web services
- File sharing
- and other mechanisms
An alternative option is to work online in the web client mode.
The developed mobile application is a separate, complete software product and can exchange data with several central databases at once. For example, in one mobile application, you can implement access and work with documents from an accounting database and tasks from an enterprise document management system.
The practice of developing a mobile application 1C 8.3 (part 1)
In this article, we will talk about what I had to try and what kind of rake to step on before I managed to make a more or less normal application for tablets. The application was initially sharpened only for Android, based on the 1C: Orders configuration, and a mobile application for development.
Initially, the "wrong" approach was chosen with compiling the application and throwing it onto the tablet manually. Let me remind you that the Mobile App Wizzard is used to build mobile applications. Then, on one of the forums, a beautiful solution was found using a mobile application for development. This app is included with the installation of the mobile platform. At the time of development, the platform version 8.3.3.24 was used. In the "Android" folder, you can find the 1cem.apk file. This is the development mobile application. Its biggest plus, which saved us a lot of time, is that you can publish a mobile application on a web server, and on a tablet, specify a path like http: // [ Web server address]/[ Mobile app name].
On a tablet PC, in the settings of the added application, you can select the "Update from configurator" checkbox, and each time the application is launched, the application will try to connect to the web server and check for updates.
After the mobile application was deployed, the process of its finalization began.
What was required:
1. Set up the exchange between the central base and the mobile device.
2. Organize asymmetric synchronization: download data on the stock list, counterparties, stock balances and settlements from the central database, and download only customer orders from the mobile application.
3. Implement a simple interface for managers, where they can quickly view balances, prices and settlements.
At the testing stage, an intermediate base "Managed Application" was used, since the 1C: Orders demo application was originally designed for exchange with the Managed Application.
The first pancake came out lumpy. Literally. For the exchange with the central database, v82.ComConnector was used. I will not go into the details of its settings, there is a bunch of separate materials about this. I will go over only the difficulties that I encountered.
1. Using com- objects on a 64-bit server OS. To solve the problem, a wrapper was used COM + Applications, which is configured in Component Services.
2. Remote call Com from another server. The called server must have the role Application Server, and it should be configured COM + Network Access. In addition, the server Apache must have the appropriate rights (i.e. run as a service on behalf of an authorized user)
Having worn out with Com-connections, they decided to transfer the working base to web services.
Much has also been written about publishing web services, but it’s written about how it works. How it does NOT work, I will share below.
The working base is deployed on the 8.2 platform, the mobile application, respectively, on 8.3.
When publishing annex 8.3 first, and then 8.2. periodically snatched the "Stream format error" glitch in the 8.3 web client, or the error message "client and server platform versions are different." Republishing does not help, nor does restarting Apache. But disabling the publication and connecting again helps.
Next, I caught a funny error when authorizing a user (when creating ws Definitions). When testing on a computer, authorization with a long name is easy. When trying to authorize the same user from a tablet running Android, authorization ended before it started. Experimentally, it was possible to calculate that the length of the login in Cyrillic is limited to 22 characters. At the same time, a combination of Cyrillic characters and numbers allowed to log in with a login of 27 characters. There is a suspicion that this is due to the conversion of Cyrillic characters. So, for example, in the browser Firefox a string from Wikipedia "ivo "is converted to"».
Technologically, the mobile platform 8.3.3 currently has a number of limitations. The most anticipated innovation, in my opinion, is support for requests. But, since the mobile platform does not yet support arbitrary queries in dynamic lists, we had to "go the other way."
To solve the problem of displaying an item reference book with prices and balances, the following approach was used:
1. Two tables have been created in the form of an item reference book. The first one is dynamic list, actually the reference book itself. The dynamic list filter is configured to display only groups. The second table is the actual balances and prices. When a row of a dynamic list is activated, the table of values is filled on the server, which is then displayed in the second table. The object model was used to obtain prices and balances. All these dances with a tambourine were performed only because there is no method “when outputting a line” or “when receiving data”, which is usual for a fat client, and it is impossible to dynamically draw numbers in a column.
A similar approach was used in the form of selection
2. FormattedString is perfect for displaying a line with current prices.
Below is a sample code.
& OnServerWithoutContext Balance FunctionWhenActivatingRowOnServer (num) RecordSet = Information Registers.Prices of Goods.CreateRecordSet (); SetRecords.Selection.Product.Value = number; SetRecords.Selection.Product.Use = True; Recordset.Read (); FormattedString Array = New Array; For EachRecordSetStringFormattedLinesLoop.Add (New FormattedString (SetString.Price.Name, WebColors.Blue)); FormattedString Array.Add (New FormattedString ("" + String (SetString.Price) + "")); End of Cycle; Return New FormattedString (FormattedString Array); // Insert the content of the handler. EndFunction
3. To load directories, balances and prices into the mobile application, a web service was used, which at the input receives the structure of parameters, and at the output returns the storage of values. Another unpleasant discovery was the crash of the exchange with too long processing on the server side. The impression is that there is some kind of timeout, after which the application "thinks" that the connection has been interrupted (although, in fact, the data is still being processed in the working database via the ws-connection), and terminates the exchange with an error.
To avoid this, it was decided to split full exchange on portions with focus back to the mobile application. Those. first synchronize the nomenclature, then the counterparties, then the balances, etc.
4. To receive reports, the same approach is left as in the 1C: Orders configuration. The web service is called with parameters, on the server side of the working base is formed spreadsheet document, and then the ready-made spreadsheet document is returned to the mobile application.
I think everyone has already heard about the new features of the new 1C release. But people who are far from programming for mobile platforms may not understand some of the features. For this we have made this "easy" guide.
Update 12.08.2012 or 1C anneals.
Good afternoon. 1C has updated the mobile platform to 8.3.3.30.
The fun began, because Google also decided to update the SDK.
What needs to be done to make everything work.
1. The name of the base is not specified - we climb into the configurator and make the field open for editing.
3. We climb into the KFOR manager and download KFOR 17. It won't work without it.
4. We climb to the site dl-ssl.google.com/android/repository/tools_r20-windows.zip, unzip it into the SDK folder, look for the tools folder there first, rename it, and merge it into new folder tools archive.
5. Changes made in processing - attached to the header.
Update 06.06.2013
By combining intelligence with serg_gre, we installed how to write a confa for a mobile application, without bothering with compilation.
What is the idea - in fact, there are 2 types of apk files (these are the ones that are installation for the phone):
1.it is a compiled file that you compile yourself and follow the instructions in this article. After compilation, you get a confa, and now you can work with it, however, if you want to redo something, you will have to recompile and reinstall everything.
2. This is the initial apk, which is in the archive mobile8.3.3.24Android1cem.apk, and its trick is that you can write different paths to configurations there yourself. And it will automatically update the database when it connects to the server.
And so, this is MUCH more convenient. How to do it?
After you have created the configuration, you can publish it under a certain name for access via the web (how to do this - there are a bunch of articles, including mine), but we are interested in where everything is, before the publication begins.
Instead of publishing the database in our usual mode, we press in the configurator - Configuration - Mobile Application - Publish.
It's clear - we indicate the name of the base (I think there is no point in saying that it should be different from the name of the web access publication) and click publish. Let's say we gave her a name InfoBase.
To do this, go to 127.0.0.1/ InfoBase... Please note, without any wsdl there, and so on. If we see a hml diagram, then everything is ok.
After that, everything will be cool. Please note that this is how only the configuration is updated, not the data.
One question left, from the same observant serg_gres:
In the configurator - in the menu Debug - Start debugging - Mobile application.
The question is - what kind of animal is it? If anyone knows, welcome to Kammenty.
Maybe everyone knew about it, but as usual, what is in sight - many do not see :)
Update 05/30/2013
Came out a new version platforms - 8.3.3
I would like to highlight some of the features and changes in it.
License:
Mobile platform and mobile application licensing
Development tools for mobile applications and the 1C: Enterprise 8 mobile platform for development purposes are included in the commercial delivery of the 1C: Enterprise platform and are available to developers at no additional cost applied solutions, who legally owns the distribution kit of the 1C: Enterprise 8.3 platform.
Mobile applications developed by users and partners on the 1C: Enterprise 8.3 platform are currently allowed to be distributed without payment to 1C if the number of distributed copies does not exceed 50. For distribution more copies are required to be approved by 1C.
In the forum, in the corresponding branch - posted a complete list of changes from 1C. Please unsubscribe there on the glitches found.
From myself, I want to highlight several features that I liked:
On the mobile platform, it became possible to:
- Set a timeout when interacting with network resources;
- Specify more than ASCII characters in usernames or passwords;
- Form the URL (and get values from it) in accordance with the RFC 1738 standard (http://www.ietf.org/rfc/rfc1738.txt) in the event that arbitrary text is added to the URL;
- Programmatically form an HTTP request and process a response, interact with REST services.
- Get slices of the first / last at the very first and most recent (current) time moments at a higher speed.
However, all sorts of little things remained. For example, the information in the input field is shifted up, not much, but striking.
When you open the directory, the name is normal, and the picture of the props is moved upwards, which is very infuriating :) Although this may be by design. I created a report on the ACS - it did not appear in my mobile application.
The installed version of the program eats up 118 meters of phone memory.
Welcome to the forum :)
The first version of the article
1C released new platform 8.3.2, a feature of which is the ability to develop a configuration for mobile platforms. The bottom line is that after all the manipulations, you get ready-made packages .apk (for Android) and .zip (for iOS).
The main idea is that a 1C programmer can do this and fully control the development. You can place this file on Google Play or the AppStore, and people can download it.
The main features are described here http://v8.1c.ru/overview/Term_000000818.htm.
For android, the .apk file weighs from 38MB. Here it is worth paying attention to the fact that it loads all these megabytes into the phone's memory, so if you don't have about 50MB available on your phone's memory, then you won't be able to install it J.
Let's get down to the fun part, namely, let's try to create our own configuration. To do this, you need to update the platform to 8.3.2, and download the file http://users.v8.1c.ru/getdist.jsp?path=mobile/8_3_1_20/mobile.zip.
Unzip it into some daddy, then we need to install the Android SDK and Java SDK.
In chapter Java Platform, Standard Edition press JDK Download, check the box that you accept the license agreement and download the file according to your operating system. There shouldn't be any problems with the installation. After that, it is advisable to reboot. Please note - Java must be 1.6! On 1.7 everything will compile, but will not work :)
The Android SDK includes the tools you need to develop Android applications. It is recommended to download the EXE file, but I suggest downloading the ZIP version and unpacking it into a thread convenient for you (if there is no link to the ZIP, click the Other Platforms link).
Please note that this should be a directory "forever". And it's better not to move it anywhere, otherwise you will have to reconfigure the development environment. I propose to create somewhere android directory... It is highly desirable that the path to it be short. Ideal -: android. Let's remember this directory under a pseudonym. And unpack our SDK archive into it, we get android-sdk-windows.
Then we go there, and make sure that we have downloaded Android platform 2.2 - open the plus sign - SDK Platform, if not installed, then check the box and install.
Pay attention - the synonym and the comment - must be empty, since then the parser will not work adequately. Thanks to society for being vigilant :)
After that, unzip the archive that was downloaded to a folder with an adequate name.
We open the configuration in the mode managed forms and open the processing that was in the archive and fill in the fields.
Everything is a little fun here - first we select the file that we have saved, then we select the language, then we click on the magnifying glass, on the application view, we write the presentation.
If the language cannot be selected, then you have a comment or description in the configuration. Read above.
The application identifier is also critical, if it coincides with an existing one on the store, then the market will not allow it to be downloaded, but for now it makes no difference to us, and we will acquire it somehow, just keep in mind that the name should contain only the Latin alphabet (and it is advisable not to be capital letters).
Everything is no less fun here, in the location of the mobile platform we indicate the address of the unpacked archive, i.e. the upper folder, which also contains folders for Android and iOS.
We choose where the result will be recorded.
And here is the fun with the key. You have to understand that it is important file, if you have previously published the application on the market under one key, then in case of loss, it will be fun. But we'll leave that for now. And so, since we do not have a key, we need to create it, for this we essentially indicate the Login and Password of the key, then data about ourselves and form the key, then select it and click OK, if everything is fine, a console window will appear, which will describe the stages of the operation. After all this, you will receive files that you can download to your phone and install.
Please note that to install, you must disable the Install from known sources only function.
And lastly, nuances:
When developing a mobile application, it is necessary to take into account the limitations that
imposes a mobile platform in comparison with the 1C: Enterprise platform for
personal computer:
- A limited list of available configuration objects and mechanisms;
- Limited set of attribute properties;
- Limited set of managed form elements;
- Simplified implementation of some mechanisms (for example, dynamic list or desktop);
- Lack of conventional forms and normal launch mode;
- Lack of tools for debugging a mobile application;
I will attach a couple of pictures of the created conference. Do not forget that for tests, if you do not have an android, you can download http://bluestacks.com/. It looks pathetic there, of course, but for a start it will do.
If you have any questions - welcome to Kammenty.
Here you can download a test config from 1C for Android
https://play.google.com/store/apps/details?id=com.e1c.mobile.orders&feature=search_result.
It has already appeared for the UNF Conf, you can download it from the link:
https://play.google.com/store/apps/details?id=com.e1c.MobileSmallBusiness
However, it is empty, i.e. ready to work with your base.
Good afternoon, dear readers, we bring to your attention a short article on creating a simple mobile application based on the 1C: Enterprise mobile platform for Android without compiling it into an apk file.
To begin with, let's briefly define the basic concepts and software that we need for development.
1 basic concepts
Mobile platform- a tool that allows you to implement applications that operate on mobile devices under the control of operating iOS systems, Android, Windows Phone.
Mobile app - is the end result of the development . Installed on a mobile device and has the ability to exchange information with the main application in the Off-line mode. The following information transfer channels are available for exchange: File exchange, Email, Web services, etc.
The configurator acts as a development environment, the only thing that needs to be taken into account: not all configuration objects and system mechanisms are supported by the mobile application.
2.Software setup
2.1 InstallationWeb server
First, let's install the Web server. Work is possible with both Internet information services from Microsoft and with Apache... In our example, we will consider Apache because it is easier to set up and more stable in operation.
Using the " Next » go to the next window:
Into the fields "Network Domain" and "Server name" write “ localhost"(Or 127.0.0.1). This means that the server will run on the local computer.
In field « Administrator’ s Email Address» indicate mailing address, server responses will be sent to it.
Default Apache works with port 80. Many popular programs work with the same port by default, for example TeamViewer, Skype which in the future will not allow starting Apache... There are 2 options for solving this problem, disable the use of this port in these programs, or change the port for Apache.
To find out which programs occupy port 80, you need to run cmd.exe (click Start - type cmd into the search - right-click "Run as administrator") in the window that appears, enter the command netstat -ab.
In the screenshot, we see that port 80 is occupied by Skype.
Leave the default port 80. Press “ Next » choose a typical installation. Click " Next » , change the installation directory if necessary, in the next window, click " Install, after which the installation process will start.
After the installation is complete, an icon will appear in the system tray, if we double-click on it, the following window will open:
If you still have problems with the standard port, you can always change it manually, for this you need to go to the folder where it is installed Apache, select the folder " conf ", in it open the file " httpd.conf". Find the parameter in it "Listen" and change its values to the port you need, for example 8080.
After changing the port number, save the file and restart Apache... To do this, click on the icon in the tray.
with the left mouse button in the menu that appears, select " Restart».
Let's make sure that the Web server is working, go to the browser and enter http: // localhost: 8080 / (where 8080 is the port that we have set) in the address input field, the following page should appear on the screen:
2.2 Platform setup
For successful work, it is necessary that the following components are installed:
2.3 Installing the mobile platform
We download the mobile platform from the 1C website https://users.v8.1c.ru/. In our example, version 8.3.8.70 is used.
The downloaded platform is an archive that consists of the following folders:
- Android- contains files for building for Android;
- iOS- contains files for assembly for iPhone;
- Windows- contains files for assembly for Windows Phone;
- MobileAppMaker- contains configuration files "Application Builder".
Since we will develop the application for a device running Android OS, we are interested in the first directory.
Let's see its contents:
- 1cem-arm.apk - the most commonly used mobile developer platform for the ARM architecture;
- 1cem-x86.apk - mobile developer platform for x86 architecture, used for processors from Intel;
- prjandroid-arm.zip - a mobile platform for building mobile applications (for ARM architecture);
- prjandroid-x86.zip is a mobile platform for building mobile applications (for x86 architecture).
Install the mobile platform on the device, for this we copy the file "1cem-arm.apk" to the phone's memory, or if your device uses Intel processor, "1cem-x86.apk".
Let's go to the file manager on a mobile device, find our file and run it
During installation, you may receive a message about the blocking of applications not received from the Play Store.
In this case, you need to press the button " Settings"And in the window that appears, check the box" unknown sources» 
and repeat the installation.
2.4 Configuring
After all software set up, let's start developing our mobile application. Let's create a new information base and go into it in the configuration mode.
Go to the menu Service -> Options
and place the checkboxes as shown in the screenshot:
Do you have a question, need a consultant's help?
Next, we call the properties of the root configuration node and set the "Purpose of use" parameter as "Mobile device", the flag " Personal Computer"We remove. After that, the objects of the mobile application will become available. Some of the configuration objects will become unavailable.
2.5 Publishing Application Configuration
The next step is to transfer the configuration to the phone. To do this, first of all, we will create a directory, the path to this directory should be short, not contain spaces and consist only of the Latin alphabet, for example C: \ MobileApp. Further go to Configuration -> Mobile Application -> Publish ... In the window that appears, fill in the parameters:
- Name - The name of the mobile application. The name must not be the same as the thin client base publication name.
- Update mobile application - if this parameter is selected, then each time the configuration is updated, the configuration on the device will be automatically updated
- Directory - the path to the folder where the mobile application files will be stored.
Let's make sure everything works, go to the browser at http: // localhost: 8080 / Mobapp /, we should see the following xml file:
In the address field, enter the IP of the computer on which the configuration is published and the name of the publication itself, separated by a slash. In our example, a non-standard port is used, so the address will look like this:
Click the download button, after downloading the following settings window should appear:
We set the parameters:
- « Restart from configurator»- The application will be automatically updated when the XML configuration file located on the web server is updated.
- « Debugging Allowed"- it is possible to step-by-step debugging of the application on a mobile device from the Configurator on the developer's computer. Press the button " OK».
If after pressing the button " Download"A similar error occurs:
Now our database has been added on a mobile device, and we can launch it by clicking on it in the list of databases selection. The window that appears is blank because we haven't added any metadata objects yet. Let's get down to development.
- Setting up the exchange between the Central Bank and the mobile application
Suppose we have a certain source base that contains only one directory: "Nomenclature". And she must exchange information with our mobile application.
Let's go to the mobile application configurator, create a hierarchical directory called "Nomenclature". Let's add a list form.
Let's go to the work area start page and add the "Nomenclature" reference list form there, set the "Initial page template" parameter as "One column".
Press the button " Refresh», The application on the phone should be updated automatically. If not, then display the button on the panel and press it. The following window should appear on the screen:
The next step is to create a new IB. We will add the "Nomenclature" reference book to it, the structure of which will completely repeat the "Nomenclature" reference book of the mobile application. This base will act as the Source.
Let's create a new Web service, let's call it MobileExchange. Set the URI of the "MobileExchange" namespace in the properties. In this web service, add a new operation and name it "LoadProducts"
Now let's write a code that will return a list of products from the source database in the form xml file... Let's go to the properties of the "LoadProducts" operation and create new function from the field " Method name". Let's write the following code in the function:
Let's publish a web service, for this we go Administration -> Publish to Web -Server ... In the window that appears, set the name of the Web service "MobileExchange" and uncheck the "Publish thin client and a Web Client ". After that, press the button " Publish».
After publishing the Web service, go to the configuration of the mobile platform, open the "Nomenclature" reference list form and add a new command "Update nomenclature" to the command bar of the form. Before that, it is recommended to uncheck the “ Autocomplete»At this panel.
Create a new action for the "Update Nomenclature" command and write the following code:
We update the configuration.
This completes the development. Go to the custom configuration mode of the Source and fill in the nomenclature reference in an arbitrary way
We go to the mobile device, launch the application, and press the button "Update nomenclature". If everything is done correctly, then the following data should appear on the screen:
Conclusion
Let's summarize our work - we managed to set up and develop a mobile application from scratch and set up its exchange with another database. It should be noted that the 1C Mobile platform allows you to do this quickly and conveniently.
Problems
