Business process task editing

Business process task objects are intended to reflect tasks assignments and the progress status of these tasks performed by business process members or regular users.

You can use tasks independently or as parts of business processes.

You can create any number of task types in a configuration. However, one task is normally created for all types of business processes.

The task structure and properties described in the configuration depend on the specifics of the business area being automated.

An important task characteristic is addressing attributes, which determine address space dimensions in the context of the automated business area. These addressing attributes are used to determine the performer that owns the task.

To define a specific performer, you can use three other task properties: Addressing, Main addressing attribute, and Current performer.

Each task type can have an unlimited number of regular attributes, addressing attributes, and tabular sections.

You can create multiple list, choice, viewing, and editing forms for each task.

Each task is characterized by its number, date, time, and name. For a task generated by a business process the name assigned to the task is identical to the name of the corresponding point of the business process.

Within a certain date, the order of tasks is defined by the task creation time.

Business process task properties

You can edit a task in the editor window.

Along with common properties inherent in all metadata objects, tasks have a number of specific properties.

Addressing
An information register can be assigned to a task. The task addressing attributes can be mapped to the register dimensions. This mapping allows to identify the value of the main addressing attribute of the task based on the data stored in the respective information register. Besides direct addressing of the tasks to specific performers, this allows addressing tasks by role.

Main addressing attribute

One of the addressing attributes can be specified as the main addressing attribute. In this case, this is the addressing attribute that points to a specific performer. If the performer is not specified, the addressing attribute is assigned a value based on the corresponding information register (see the Addressing property).

Current performer

This property references a session parameter that stores the current performer. The property is used for displaying the task list in the "By performer" mode.

Addressing attributes

This property specifies a set of addressing attributes that define the addressing system type and the number of dimensions for this task type in the context of the automated business area. One of these attributes can be defined as the main one (see the Main addressing attribute property).
The addressing attributes of a task can be mapped to information register dimensions. The system uses this mapping to identify the value of the main addressing attribute of the task if it is not specified. Besides direct addressing of the tasks, this allows addressing tasks by role.

Number length

This property determines the maximum length of the task number.

Number type

This property allows you to select the task number value type, Number or String.
The string type is useful when a sophisticated numbering system is used and the task number contains not only digits but also letters and delimiters.

Autonumbering

If you want task numbers to be assigned automatically, select this check box. One can correct an automatically assigned number.

Check uniqueness

If this check box is selected, the number of a newly added task is checked for uniqueness.

Autoprefix

This property allows you to use a business process number as a prefix for a new task.

Input by string

The input by string fields are formed on the Input fields tab.

Main forms

You can specify main forms for each action type on the Main tab of the Forms tab.

Generation

In the upper list, select objects that can serve as a basis for generation of a task of that type; in the lower list, select objects that can be created based on a task of that type.
During the generation the task is populated by the predefined procedure Filling(). To facilitate task entry based on other configuration objects, you can use the Generation settings wizard.
To start the Generation settings wizard, click the button in the bottom right corner.

On the Other tab you can specify fields used in managed transaction data locks and specify whether objects of this type are included in the full-text search.

1C:Enterprise Developer's Community