Regulatory and background tasks 1C 8.3. Universal regulatory task

When working in 1C, there are many routine operations that must be launched or to form on schedule performing this or that action, for example: conducting documents or data load in 1C from the site.

I recently posted an article: it's time to automate it:

Regulations and background tasks

The task mechanism is designed to perform any applied or functionality on a schedule or asynchronously.

The task mechanism solves the following tasks:

• The ability to define regulatory procedures at the system configuration phase;
• Execution of specified actions on a schedule;
• Performing a call for a given procedure or asynchronously function, i.e. without waiting for its completion;
• Tracking the progress of a certain task and obtaining its completion status (values \u200b\u200bindicating the success or not successful implementation);
• Receiving a list of current tasks;
• Ability to wait for the completion of one or more tasks;
• Job management (ability to cancel, lock execution, etc.).

The task mechanism consists of the following components:

• Metadata of regulatory tasks;
• Regulatory tasks;
• Background tasks;
• Job scheduler.

Background tasks & are designed to perform applied tasks asynchronously. Background tasks are implemented by the built-in language.

Rules' tasks & are designed to perform applied schedule tasks. Regulatory tasks are stored in the information base and are created on the basis of metadata defined in the configuration. The metadata of the regulatory task contains such information as the name, method, use, etc.

The regulatory task has a schedule that determines which moments of time must be carried out by the method associated with the regulatory task. The schedule is usually set in the information base, but can also be specified at the configuration stage (for example, for predefined regulatory tasks).

The task scheduler is used to plan the execution of regulatory tasks. For each regulatory task, the planner periodically checks whether the current date and time of the schedule of the regulatory task is true. If it matches, the scheduler assigns such a task to execute. To do this, according to this regulatory task, the planner creates a background task that performs real processing.

With the description, I think, enough - I will proceed to implement:

Creating a regulatory task

Method name - The path to the procedure that will be performed in the background task on a specified schedule. The procedure must be in the overall module. It is recommended not to use typical common modules, but create your own. Do not forget that background tasks Executed on the server!

Using - a sign of using a regulatory task.

Predefined- Indicates whether the regulatory task is predefined.

If you want to work as a regulatory task immediately after the room in the database, specify a sign Predefined. Otherwise, you will need to use the Task Console processing or call the task to start programmatically.

Number of repetitions in case of emergency completion - How many times have a restart of the background job, if it was performed with an error.

Repeat interval when an accident failure - What frequentness will be configured to restart the background task if it was performed with an error.

Setting the schedule

schedule Task performance:

Features of execution of background tasks file and client-server versions

Mechanisms for performing background tasks in file and client-server variants differ.

In the file version It is necessary to create a selected client process that will make the performance of background tasks. To do this, in the client process, the function of the global configuration context context function should be occupied. Only one client process on the information base must perform the processing of background tasks (and, accordingly, cause this feature). If the client process is not created for processing background tasks, then when software access, the task manager will be issued to the job mechanism. The client process that performs the processing of background tasks is not recommended for other functions.

After the client process performing the processing of background tasks is launched, the remaining client processes get the opportunity software access to the mechanism of background tasks, i.e. Can run and manage background tasks.

In the client-server version To perform background tasks, a task scheduler is used, which is physically in the cluster manager. The scheduler for all the background tasks assigned to perform the background tasks receives the least loaded workflow and uses it to perform the appropriate background task. The workflow is tasked and notifies the scheduler about the results of execution.

The client-server version has the ability to block the execution of regulatory tasks. Blocking the execution of regulatory tasks occurs in the following cases:

• The information base has a clear blocking of regulatory tasks. Lock can be installed through the cluster console;
• The information database is set to block the connection. Lock can be installed through the cluster console;
• From the built-in language, the method of setting monopular () with the truth parameter is called;
• In some other cases (for example, when updating the database configuration).

Starting and viewing rules for regulatory tasks You can download here.

" In it, we will look at new features that do not concern the system interface, but significantly expand the provided functionality of the "1C: Enterprise 8" platform.

Applicability

The article discusses the "1C: Enterprise" platform version 8.3.4.437. All the functionality described in the article is updated to the editorial office 8.3.11.

Other innovations in "1C: Enterprise 8.3"

We will continue to get acquainted with the innovations of the 1C: Enterprise 8.3 platform.

Background and regulatory tasks in the File Information Base

In many typical platform configurations 8.2 There was a constant in which the user was specified under which tasks were performed in the file.

When the system is started, under this user, the expectation handler has occurred, which for a certain periodicity caused the embedded language method. PerformingPackets ().

Such an approach created additional difficulties and inconvenience to use regulatory tasks in the file database.

It could be especially critical when working with such configurations as "Complex Automation" or "Managing Production Enterprise"In which the regulatory tasks play a rather important role.

If it is FileIb then
=
Constants. Usually Full-planeThe WoversVariant. Focus();
If a gLNAGEVENED("Glotting user") =
Customer clipThen
// In the interval of seconds call the procedure for working with regulatory tasks
SupportedLentyLentyFyle FileVession();
IntervalTrack=
Constants. IntervaltlasprosarlamentAdnayaTaniyvifylevarisa. Pour();
If a IntervalTrack\u003d Uncertain
OR IntervalTrack\u003d 0 then
IntervalTrack= 60 ;
Ended;
Connectographicing("SupportedLameDadantedLameFilevation",
IntervalTrack);
Ended;
Ended;

In the platform 8.3 The work of background and regulatory tasks in the file information database is implemented without using the global context method PerformingPackets ().

Background and regulatory tasks are performed directly in one of the client applications (thin, thick client) or the web server extension.

The background task run by any session is performed by the same client application that initiated it.

Background tasks are performed sequentially, i.e. On one client application at one point in time, only one background task may be performed (including regulatory).

Regulatory tasks are performed only by one client application. To manage the start of regulatory tasks, the command line key is intended. AllowExecuteScheduledjobs..

Regulatory tasks are performed first in order to start the client application that does not prohibit the execution of regulatory tasks (for the prohibition of the session must be launched with the command line parameter AllowExecuteScheduLeDjobs -off.).

When this session is completed, execution proceeds to any of the remaining sessions running.

If the client application string explicitly indicates the need to start regulatory tasks (in command line Specified AllowExecuteScheduledJobs -Force), Regulatory tasks begin to be performed on it, regardless of the availability of other sessions.

Processing regulatory tasks occurs once every 60 seconds.

Note that regulatory tasks applied solution (In the file) started to be executed no earlier than 1 minute after the client application is launched. Starting with the edition 8.3.8, this time was doubled, and therefore the regulatory tasks begin to be made to the maximum 2 minutes after the client launch (in the file).

This solution is due to a decrease in the delay when the application starts. In addition, in release 8.3.7, the ability to quickly determine that the current session is a background task session. This is implemented at the expense of the new method of global context to get theseansinformational base (), as well as a new method at the information base session. OPENDFONEVENATION ().

The following is the code that illustrates the above described:

To enlarge, click on the image.

Calculation of checksums

In the platform, mechanisms appeared to calculate the control sums.

Recall that the checksum (hash) is a certain value calculated by the data set by using a specific algorithm and used to verify the integrity of the data when they are transmitted or stored.

Hischai can be used to check the identity of the data (for example, it is necessary to make sure that it is not damaged when transferring the file; check if there were changes to the file, and if so, then load it to the database again).

To do this, an object was implemented in the platform ChechirovatedAvailable on the server in a thick client, external connections, as well as on a mobile application server.

This object has two methods: Add () and To add a file()who update the hash sum with the data transmitted in the parameters.

Platform 8.3.4.437 Supports the calculation of the following hash functions: CRC32., MD5, Sha1, SHA256.. But functions Sha1and SHA256.not supported on a mobile platform.

Consider a simple example. It is assumed that on the server in the program directory there is a file " ragent.exe.". It is necessary to calculate MD5-Summage for this file.

To do this, create external processing, on the form of which will be placed Calculate. The handler contains the following code:

& Svalette
Calculate procedure (command)
Result \u003d. Calculate server();
Report (string (result));
Extrudresses
&On server
Function Calculate server()
Hash \u003d new Chechirovated(.Md5 hashfunction);
Hash.Daddlindile(Catalog Program() + "Ragent.exe");
Return Heshe.Hesumum;
Endfunction

In the editorial platform 8.3.10+ in the method Add () Object Chechirovated It became possible to use the stream of binary data, which significantly simplified their use in solving various application tasks to update hash-sums.

Work with secure versions of protocols SMTP / POP3.

In the platform 8.3 There is an opportunity to use protected versions of protocols. SMTP / POP3. (Terms are found SMTPS / POP3S. or Sslsmtp / sslpop3.).

For object InternetPootpofil New properties implemented:

• Usesslsmtp;
• Usesslpop3.;
• UnderstandingAutentificationSmtp;
• UnderstandingAutentificationPop3.

Properties AuthenticationSmtp.and AuthenticationPop3.object InternetPootpofilas well as enumerations PODSMTPAutentificationand POPOP3Anauthentificationuse it is not recommended - they are supported for compatibility.

Using a secure protocol SMTPS.makes it possible to send mail from 1C.Using mailbox Google.

Consider an example. On the form, we have a field for entering the subject of the letter and the address of the recipient, and to enter the text of the letter - the field of the formatted document.

To enlarge, click on the image.

Pressing the button Sendthe following code will be executed:

& Svalette
Procedure Send (command) mail \u003d new online pub; Profile \u003d new InternetPootpofil;
Profile. PressReserSmtp.\u003d "Smtp.googlemail.com";
Profile. Usersmtp.= “[Email Protected]” ;
Profile. Pallsmtp.\u003d "PASSWORD";
Profile. Usesslsmtp\u003d Truth;
Profile. Portsmtp \u003d 465; Attempt
Mail. Conference(Profile);
An exception
Report (Description ());
Refund;
Celebrations; Postal informantExter= “” ;
Attachments \u003d new structure;
Text.ChelchHTML(Postal informantExter, Investments ); Postalization\u003d New Internet puberty;
Postalization. Practitioners. Add(To whom);
Postalization\u003d Topic;
Postalization. Whites. Add(Postal informantExter,
TytextapochetovoP.html.); Mail. Address ( Postalization); Mail. Follow();
Extrudresses

Note that in our example if the SMTP server could not send electronic message addressee (-am), then method Mail. Send (Postal Communication) generated an exception. This caused certain inconvenience from developers, because The reason for the generation of exception was not obvious.

In the editorial board 8.3.9, this behavior has changed, and now the send method () returns compliance, the key of which is the addressee, and the value - diagnosis from mail Server. This allows you to accurately determine the reasons for the unsuccessful email sending to each of the addressees. In compatibility mode with version 8.3.8, the behavior has not changed.

Two-sided printing

In the platform 8.2 The platform itself did not manage the double-sided seal, it was possible to manage this feature only using the printer driver.

In the platform 8.3 The ability to control bilateral seal for a table document, a graphic scheme (from the built-in language and interactively) and text document (Only interactively).

In the embedded language, system listings appeared:

• Typid softener(No, DVORSOPE, DORAVED);
• (Auto, Mirror Power, Mirror Slab, Understand).

And in objects Timberand Graphicshemproperties appeared Two-sided printingand Alternating distributionStranitsaWith which you can change the location of the printed pages.

In the editorial office of the platform 8.3.9, a new meaning was added to the system listing of tidylon Use the nastyprinter. Choice this value Allowed to use the printer settings when printing system documents. In compatibility mode with version 8.3.8, the behavior has not changed and the corresponding printer settings are ignored.

The information base publication dialog on the web server is more functional. Now publishing the configurator allows you to set all file settings. default.VRD..

To dialogue publishing a web client and Web services through the configurator is implemented:

• the ability to manage the availability of Web services by default (attribute pointenablecommon. Element wS.);
• the ability to control the execution of background tasks in the file (attribute allowExecuteScheduledjobs. Element wS.).

If flag "Publish Web Services by default" On the tab "Basic" Installed, when updating publishing, selected Web services will be published automatically.

Otherwise, Web services will be marked as nonposable. This flag matches the attribute pointenablecommon.element wS.in file default.VRD.Designed to configure the web client and Web services.

Attribute pointenablecommon.the WS element is responsible for the possibility of using Web services in this information base, which are published without explicit use of the use permissions (attribute enableelement point).

If the attribute is important true., then all Web services for which the attribute value is clearly not specified. enableelement pointwill be allowed for use.

Otherwise, the use of such Web services will be prohibited.

Setting "Background tasks in file mode" corresponds to the attribute allowExecuteScheduledjobs.wS element in file default.VRD..

Attribute allowExecuteScheduledjobs.manages the ability to execute regulatory tasks to the web server expansion for the information base file.

The attribute can take the following values:

• off- In this case, the web server extension will not perform regulatory tasks. Performing regulatory tasks will be the client application (if any), which connects directly to the information database, without using a web server.
• force- In this case, the web server extension will perform regulatory tasks.
  If the value of this attribute is not specified, the regulatory tasks will perform the application with which the first connection to the information base will be performed.

The publication window on the web service in the current release of the platform has become even more convenient and ergonomic. Now the parameters describing the OpenID authentication are made on a separate tab.

Numbering of information base objects

In the platform 8.3 recycled mechanism automatic numbering information base objects. Monitoring the uniqueness of the number or code (including the number or code obtained as a result of automatic generation) is always done during the entry of the object.

The text of the uniqueness of the uniqueness of the number or code is added to the indication of which number or code is not unique.

The use of the liberated number or code has changed. The new number or code is assigned without using the released numbers or codes, if there are already issued numbers or codes with a large (in order) prefix of the number or code.

Aggregate Language Language Language Data Layout System

In the language of expressions of the data layout system, new aggregate functions are implemented:

• Everyone();
• Any();
• Standard alternate degeneration ();
• StandardLonions Creatures ();
• Dispersion exhibition ();
• Dispersion sensor ();
• Covariance receptacle ();
• CovariarationSebors ();
• Correlation();
• REGRESSIONALLON ();
• Regressing ();
• Regressionicism ();
• RegressionR2 ();
• Regressing formed ();
• Regressing average ();
• Regressing averagesXX ();
• Regressing average ();
• Regressing averagesXY ().

As can be seen from the names, these are statistical functions, it means that the developers have the opportunity to create complex reports without resorting to the development of procedures for calculating statistical data.

To enlarge, click on the image.

As can be seen in the figure, there are no new features in the drop-down list, but if you manually enter them, the error message will not be, and the report will be formed:

It is also of interest new feature ClassificationABC (). The result of the function of the function will be the class number, starting from 1 (1 corresponds to the class A, 2 - class B, 3 - class C, etc.).

We will demonstrate the work of this function. Create a new external report "Classification of goods" Based on the request:

CHOOSE
Costdranovanovari.Thovar,
Costbarovanovari.Colism
OF
Document. Source. TastersAS Costbatovaratovari

Determine the new calculated field Class:

To enlarge, click on the image.

We will configure resources as follows:

To enlarge, click on the image.

In user mode, the report looks like this:

In conclusion, we note that from the editorial board in the 1C 8.3 platform 8.3, the SCD mechanism is constantly improved and refined, and within our "newcomer" article data changes are not possible. Yes, it seems unnecessary, because, working on actual version Platforms, you can always take advantage of various reference systems to help with the analysis of a particular aspect of the operation of this mechanism.

In addition, do not forget about our separate course, the professional development of reports in 1C 8.3 on the data layout system, which takes over all the subtleties and pitches to the atom when working with this mechanism. Look at the demo yourself and.

So, let's summarize the results. Up to this point, we got acquainted with the new features of the "Taxi" interface and managed forms, as well as with some previously provided capabilities of the platform itself. Now it's time to see what comfortable opportunities The developer in the configurator has become available.

Often, when registering, there is a need to periodically perform certain actions without user intervention. Regulatory and background tasks in 1C - those mechanisms that are provided for this purpose in the eighth version of the program and allow:

• Set up timely prereparation of documents;
• Calculate the remnants and results;
• Ensure the frequency of mailing list;
• Check and delete irrelevant data.

Background and regulatory task - what it is and where it is configured

The regulatory task is the mechanism laid in 1C, which allows you to configure and, in accordance with the laid scheduled and frequency, perform a specific sequence of actions.

The background task is an action generated by the regulatory operation and not requiring direct user participation.

Creating a regulatory task occurs in the configurator mode:

• In the configuration tree window, we find the corresponding branch (Fig. 1);

• Click the Add button;
• In the window that opens, you must specify a name that allows you to identify an object in the configuration;

Fig.2

• Opposite the inscription "Schedule" (Fig. 2) there is an inscription "Open", clicking on which the Time Settings and Periodicity Opening window opens (Fig. 3);

Fig. 3.

• You must also fill out the "method name" (the name of the procedure caused from the general module and the describing algorithm of the behavior of the program will be entered here;
• The "Name" and "key" fields allow you to group objects;
• The "Usage" flag indicates the activity of the regulatory operation;
• "Predefined" should be installed if the handler must start immediately after it is added to the database, otherwise, the launch can be made from the corresponding processing (about it below);
• The parameters "Number of Repeats" and "Interval Repeats" describe the behavior of the program in the event of an exceptional situation when performing a background task.

So, using the mechanism of regulatory operations, you can set the schedule and the main actions of background tasks. Let's now consider their features.

Features of background tasks

The main feature of this mechanism is that the background process is performed asynchronously.

What does it mean. The fact is that with a synchronous model of work, in case of execution, any algorithm is blocked user interface. In our case, the user can continue to enter and edit the data, even if the procedure is running. The asynchronous programming model involves the separation of computing streams.

Thus, the background tasks in 1C can generate their processes, distributing the calculations on various servers entering one cluster.

Features of work in client-server mode

• Execution and control planning is carried out by the scheduler from the server cluster;
• In case of an execution request, the scheduler is looking for workflows of a cluster with minimal load and distributes tasks to them;
• Each process can perform several parallel computing;
• After the task is received, the process is connected to the base and performs the algorithm in it;
• The process reports the planner about the results.

Background tasks in file mode

Prior to the version of the platform 8.3.3.641. Working with background tasks in the file version represented some difficulties:

1. It was necessary to launch a separate session, which would work around the clock, replacing the planner;
2. This session was to periodically execute the execution method ().

After updating, each start of thick and slim clientsIn the event that in the start settings (Fig. 4) in the "Additional" field, the AllowExecuteScheduLedJobs key is specified, initiates an additional connection stream to the database, which does not affect the user to work, but only performs background operations.

Fig.4.

It should be borne in mind that even in the file version of work, the background processes do not allow for interactive work with the user (official messages, warnings, issues will not be displayed). That is, it is necessary to encode them as if they will be executed on the side of the server.

How to disable regulatory tasks

Unused tasks can be disabled, simply by removing the checkbox to "use" in the object properties.

In the case when the administrator needs to prohibit the use of regulatory and background operations for the entire base as a whole (for example, it is not stored by several databases, of which only one basic, and the rest are used only for development) it is necessary to use the database administration utility. You can also install the "Install the blocking of regulations" in the database created on the server.

In addition, on ITS disks there is a special processing of the "job console", which allows you to edit the schedule background processes And change their activity.

Regulatory tasks in 1C are designed to perform certain procedures on a schedule, with some frequency.

Regulatory tasks are stored in the information base, have a start-up schedule. The start-up itself is fully automatically performed if the information base is the client-server. If the base is file, then the following steps must be performed:

• allocate a special user to perform regulatory tasks;
• the base should be opened under this user, in which the function periodically must be performed Performing acknowledge ().

Creating a regulatory task

Regulatory tasks - 1c configuration metadata object. Located in the General group. Consider the parameters and properties of regulatory tasks.

Method name- The path to the export procedure in the overall module that will be performed on a given schedule. The procedure must be executed on the server. In this regulatory tasks with something similar to the object Subscribe to an event.

Key - allows you to create several regulatory tasks of the same type. For example, performing data synchronization between multiple information bases can be implemented using one metadata object. RegulationAt the same time, several (by the number of exchange bases) will be created by the regulatory tasks. Different these regulatory tasks will be different Key. At the same time, only one task with the same key can be performed.

Using - The flag showing whether the regulatory task is enabled.

Predefined- Here you can draw an analogy with predefined elements of the reference book. Predefined elements Created in the configurator and apply to users in operation. Conventional user elements creates himself. With the regulatory tasks in the same way: if it is predetermined, then it exists and can be executed on a schedule immediately after creating in the configurator. If the flag Predefinednot installed, the user needs to create one or more regulatory tasks of this type (for example, through Task console).

Number of repetitions in case of emergency completion - Determines how many times the background task is being restarted if it has been completed with an error.

Repeat interval when an accident failure - Determines which frequency to restart the background task, if it has been completed with an error.

Software work with regulatory tasks

In these examples, we will consider working with conventional, not predetermined, regulatory tasks.

Software creation of a regulatory task

// Create a task
"Mareliamentation") ;

// Install the key of the regulatory task (not required)
The task. Key \u003d "key-out";

// turn on the regulatory task
The task. Use \u003d truth;

// write a regulatory task
The task. Write down ();

Software Obtaining Regulatory Task to change parameters

In this example, we assume that there is only one regulatory task of this type. If the tasks are several, then knowing, it is not difficult to enter the corresponding changes to the code.

"NameGellamentation"] ) ) ;

If tasks. Quantity ()\u003e 0 then
Task \u003d tasks [0];

Otherwise
Task \u003d Regulatory applications. CreaterementName ( "NameGellamentation") ;

Ended;

// Regulatory task is in a variable task. You can change its parameters.

Call dialogue change schedule for regulatory task

There is a special type of dialogue to work with the schedule of regulatory task. We still assume that we have only one regulatory task of this type.

// Get an array with the regulatory tasks of the desired type
Tasks \u003d Regulatory applications. Operational fees (new structure ("Metadata", Metadata. Regulatory applications [ "NameGellamentation"] ) ) ;

// if the task exists, then by the condition it is one
If tasks. Quantity ()\u003e 0 then
Task \u003d tasks [0];

// if the tasks do not, create it
Otherwise
Task \u003d Regulatory applications. CreaterementName ( "NameGellamentation") ;

Ended;

Schedule \u003d task. Schedule;

// Create a dialog for changing the schedule of regulatory task
Dialogress \u003d new dialographersparement (schedule);

// Show the user dialogue and process schedule changes
If dialogress. OpenModally () then
The task. Schedule \u003d dialogress. Schedule;
The task. Write down ();
Ended;

Often, users complain that "1C 8.3 slows down": the forms of documents are slowly open, the documents are held for a long time, the program is launched, reports and so on.

Moreover, such "glitches" can occur in different programs:

Causes can be different. This is not restored to conduct documents, a weak computer or server, the server 1C is incorrectly configured.

In this article, I want to consider one of the easiest and most common reasons for the slow work of the program. This instruction It will be relevant for users of file databases by 1-2 users, where there is no competition for resources.

If you are interested in more serious optimization of client-server versions of the system, visit the site section.

Where in 1C 8.3 Reliable tasks

I did not have time to upload a program as in 1C many background tasks. You can see them by entering the "Administration" menu, hereinafter - "Support and Service":

Get 267 video tutorials for 1C for free:

Here it looks like a window with the tasks performed:

And so full list All regulatory tasks that are launched:

Among these tasks, such as "", downloading various classifiers, check the relevance of the version of the program and so on. For example, I have almost all these tasks. I do not conduct foreign currency accounting, the version control itself, the classifiers load as needed.

Accordingly, in my (and in most cases in your) interest to disable unnecessary tasks.

Disable regulatory and background tasks in 1C 8.3