37.2.5. 1C:Enterprise startup

<< Prev   Next >>

37.2.5.1. General parameters

On this tab, you can select the application to be started, and user selection when starting 1C:Enterprise.

When starting 1C:Enterprise from Designer, the client to be loaded is specified in Application group.

If the mode is set to Select automatically, the 1C:Enterprise selects the client type depending on the configuration Default run mode and Run mode property of the user that starts the 1C:Enterprise. If configuration properties and user properties are not specifically indicating something, then:

• If the Default run mode property is set to Ordinary, thick client will be started in ordinary mode.
• If the Default run mode property is set to Managed application, thin client will be started.

If a specific client type startup is required at 1C:Enterprise startup from Designer, you need to set it manually (items under Select automatically). When specifying the start of the web, you can specify the web browser that will be started:

• Default web browser
• Microsoft Internet Explorer
• Mozilla Firefox
• Google Chrome
• Safari

When starting the web client from Designer, the platform version with an uploaded earlier infobase is checked. If the versions are different, the user receives a message suggesting to perform the publication again. If the answer is positive, an infobase publication dialog box is displayed. It's details are listed in the book.

If mobile client is selected as a client application, you can specify its mode: mobile client mode (Standalone mode is set to Do not use) or mobile client in standalone mode ( Standalone mode is set to Use). If Standalone mode is set to Auto, standalone mode will be used, if an application has standalone configuration components duly assigned.

The user that starts the 1C:Enterprise from Designer is defined in User group:

• Current. User from the user list.
• Name. A specific user is selected ( the /N command-line parameter analogue). The required user can also be selected from the list. To do it, use the "..." button, located on the right side of the field.
• If the Use operating system authentication check box is selected, the user will be selected using the operating system authentication ( the/WA command-line parameter analogue).

Data separation. Allows you to specify the separator's values in a way that is used to specify them for the /Z parameter. The string specified in this field must match the specifying separators values rule, however, it must not have quotation marks framing the values, when specifying these values in the /Z parameter. For example, if you specify the /Z "-1, +4" parameter in the command line, you must specify -1, +4 in the Data separation field. 1C:Enterprise stores different options for separator values input and allows you to switch between them.

Startup parameter. Startup parameter /C command-line parameter analogue) that is available for processing through the global context property LaunchParameter.

Low connection speed. Allows you to enable or disable the low connection speed mode at thin client startup. Check box selection is saved for the specified infobase. The check box is cleared for an infobase with slow connection speed startup mode not set at the base list. If the check box is selected, 1C:Enterprise starts using slow connection speed.

For an infobase with a slow connection speed startup mode set in base list, the check box is displayed in gray. If the check box is cleared, 1C:Enterprise starts using normal speed. The check box has the same effect as the /O command-line parameter.

Emulate delay on server calls. The check box enables emulation of the thin client operation under the conditions of significant time delays, that are caused by interactions with the server. This feature is turned off by default.

Call delay, sec. Defines the delay duration for each server call by a client application.

Data sending delay (sec/kB). Defines the delay duration when transferring data to the server. Time is indicated by 100 bytes of transferred data.

Data receiving delay (sec/kB). Defines the delay duration when receiving data on the server. Time is indicated by 100 bytes of received data.

You can also enable the server delay emulation mode in the command line: /EmulateServerCallDelay [-CallXXXX] [-SendYYYY] [-ReceiveZZZZ].

37.2.5.2. Additional parameters

Additional parameters on this tab can be helpful when developing applications (in particular, for debugging).

Service messages file. To save service messages to a file automatically, enter its name in the parameter (same as /OUT command-line parameter).

Do not clear file before startup. If this check box is selected, during the next startup, messages will be added to the specified file ( /OUT command-line parameter with NoTruncate key analogue).

Interface language. It is used to specify the national language of the interface ( /L command-line parameter analogue).

Session localization code. It is used to specify the session locale code (/VL command-line parameter analogue).

Do not display warnings on startup. If this check box is selected, the following startup messages are suppressed:

• Database configuration does not match stored configuration. Continue?
• Your computer capabilities are inadequate to edit configuration help. To edit help, install Microsoft Internet Explorer version 6.0 or higher.
• Your computer capabilities are inadequate to edit HTML documents, including help sections. To edit HTML documents, you must install Microsoft Internet Explorer version 6.0 or higher. HTML document editing will be unavailable during this session (parameter passed through the /DisableStartupMessages command-line key analogue).

Allow debugging mode. If the check box is selected, debugging is available when the application is started in 1C:Enterprise mode (analogue of the parameter specified in /debug -tcp or /debug -http command-line parameter).

Start debugging on startup. If the check box is selected, when starting 1C:Enterprise connection is performed automatically. When using HTTP protocol to debug, this setting is the same as when using the /debug - http -attach command line key.

Check 1C:Enterprise language circular references. If this check box is selected, the client application (thin or thick client) will check the circular references when operating with 1C:Enterprise language, when started from the Designer. This check box is an analogue of the command line /EnableCheckScriptCircularRefs key.

Display performance indicators. If this check box is selected, a button is added to Favorites and History panel when starting 1C:Enterprise. When clicking the button, a window with current statistics on interaction with 1C:Enterprise server is displayed (analogue of the /DisplayPerformance command line parameter).

Technician mode displays the Service and settings ‑ Functions for technician menu and can be used instead of the /TechnicalSpecialistMode command-line parameter. This command call displays a form with a list of all applied objects you can use (used in managed mode of thick client as well as thin and web client). The menu command is turned off by default.

If the Functions for technician command display is enabled, follow these steps:

1. Open the Functions for technician form by clicking Service and settings ‑ Functions for technician.
   The necessary configuration object is selected from the configuration objects tree.
   As an alternative to step 2, you can select required objects using the search string of the Functions for technician form.
   The double-click on the selected object of configuration or clicking Open is the last step. The selected form will be opened after this step is performed.

The search string is activated by Ctrl+F key combination or as of text typing start in the configuration object tree. When the search string is used the configuration object tree is switched to the flat list (without hierarchy) mode and returns to the tree mode when the search is aborted. The search with the help of this mechanism selects the configuration objects and forms which match the search string for display. No other objects will be displayed in the list. The search is aborted with the help of Ctrl+Q key combination.

The search is performed by representation and uses the following algorithm:

• Search is carried out by the beginning of the word.
• If a word contains letters and digits:
  • Sequence of letters is considered a separate word.
  • Sequence which contains digits only is deemed a separate word.
• In a word consisting of digits, leading zeros can be both significant and insignificant simultaneously.
• An item is deemed to be found (including if this item contains subordination) if one of the following conditions is met:
  • Item presentation contains all the words you searched for.
  • Item presentation contains at least one searched word and its parents contain the remaining words.

Therefore, if all registers whose presentation contains the word "expenses" must be found, you can specify "expenses register" in the search string and get the following result (for Sales management 11.4.3):

A usual search window (with the help of Alt+F key combination) can be opened if a search in the displayed information of the tree (group names and open tree branches) is necessary. In this case, the cursor will be on the first occurrence of the searched string and F3 (go to the next search result) and Shift+F3 (go to the previous search result) can be used to move in the search results.

In the Functions for technician window, you can also find Standard functions used for execution of some standard procedures: viewing the list of active users, deleting marked objects, and so on.

When the technician mode is enabled, several features useful for application debugging and maintenance become available:

• You can get a full name of any opened form in the managed application or command interface element. To do this, right-click the form header or command interface element and select Information for technician.

  This command is added to the context menu available for the following UI elements:

  • Form header Not supported in system forms
  • Element of open items panel
  • Element of functions menu
• You can get access to the opened form in Designer. It is possible only if the client application is started in debug mode in addition to the enabled technician mode. In this case, right-click the form or a command interface element and select Open in Designer. The same button will be available in the window that appears after clicking Information for technician.

  This command is added to the context menu available for the following UI elements:

  • Form header. Not supported in system forms.
  • Element of open items panel.
  • Element of functions menu.

In the context menu, the commands mentioned above look as follows:

The dialog box that displays the full form name looks as follows:

As already mentioned, the Open in Designer button is available only if the technician mode is enabled in the client application in debug mode.

Check server calls in event handlers. If this check box is selected, the command line startup parameter /EnableCheckServerCalls is added (from Designer) to the command line of 1C:Enterprise startup.

Selecting this check box in the startup settings is recommended if the application can potentially have handlers of form events, where context server calls are performed. Using them in this kind of handlers is not allowed. Breaking this rule can lead to errors in some cases of server calls usage. Mainly problems occur if the form items or its attributes change in such handler while in server call. As a result, unexpected behavior or non-obvious execution time errors may occur.

Run in batch mode. Allows you to start the client application in batch mode from Designer.

The Automated testing group is used to define the role (in terms of automated testing) of started client application when starting from Designer:

• Do not use. Started client application is not used in automated testing.
• Start as testing manager. The client application to be started will be used as the testing manager (the TestManager command line key will be used).
• Start as testing client. The client application to be started will be used as testing client (the TestClient command line key will be used). For interaction with testing manager, the port specified by the Port number for thin and thick client (TPort parameter for TestClient command line key) parameter will be used. For the web client, an ID specified in ID for web client parameter is used (TestClientID command line key) will be used.

37.2.5.3. Mobile application

This tab is used to set up the parameters required for 1C:Enterprise, in order to operate with Android SDK.

Use "Android debug bridge" to start a mobile application check box defines the method to be used for sending the configuration to the mobile device:

• If the check box is selected, the configuration is sent to the mobile device via Android Debug Bridge (ADB).
• If the check box is cleared, the configuration is sent via a web server.

Android SDK directory. Defines the path to the installed Android SDK. This parameter must be specified before performing any Android Debug Bridge operations.

Mobile platform. Contains a link to the mobile platform archive. This link will be used on the mobile device (or emulator). The archive must have an Android directory, with the following files in it:1cem-arm.apk(mobile platform for ARM architecture developer) and 1cem-x86.apk (mobile platform for ARM architecture developer).

The No devices available parameter group defines Designer behavior when no mobile devices are connected to the computer where Designer is operating. Or when an emulator is not started on this computer.

• Wait for connection. In this case, Designer will wait for a physical device connection or an emulator start. Waiting is performed with no timeout.
• Start device emulator. In this case, Designer will try to start an emulator specified in the nearby field. Emulator is created using the Android virtual device manager (included in Android SDK).
• Refuse starting. This will interrupt the performance of the action.

Hyperlink Virtual device manager is used for starting the AVD Manager application from the Android SDK directory.

<< Prev   Next >>