Docflow. User Tasks

The Task that await execution have the "In Process" status. Such Tasks are represented in special List View. The Tasks included in a Group can be executed sequentially or in parallel; the order of execution is set at the Schema design time. The user can start the execution process by clicking the Execute Task Action or invoking the Task's Detail View.

Very often Docflow process includes child Documents. In this situation, execution of the Tasks of the parent Document will be suspended while waiting until the child Document is processed. Such situation is shown in the figure below: subordinate Document "Transport Ticket" was created while the "Adamson trip proposition" Document was processed. The Ticket Validation Wait Task has the "In Process" status, but the Execute Task button is inactive. The framework waits for completion of the work with the subordinate Document.

docflow_13

Let's look at execution of some kinds of Tasks.

Create subordinate Document

The Schema for a Document can include the creation and processing of subordinate Documents. The creation of a subordinate Document is a standard Task supplied by the Xafari Docflow. This Task prompts the user to confirm values of parameters.

docflow_17

Note: You have to configure the prompt for confirmation for each individual parameter when designing the Schema.

After the subordinate Document is successfully created, it will appear in the general list of Documents. The Tasks assigned to the Document will be displayed in the Schema pane.

docflow_18

Approval signature

Approval of the Document is an important special case of the Docflow Tasks. Xafari Docflow provides a special Task, the Signature Task, for this purpose.

The Signature task is executed using the Signature Approval Helper. The responsible officer approves or denies the Signature, he also can comment on his action. If the Signature is denied, then supplying a comment is mandatory.

Depending on the result of approval, the Docflow process can proceed to various scenarios. The conditional process flow is determined at the time of designing the Schema.

The approval result is registered in the Current state property of the Document.

docflow_19

AutoForm

AutoForm it is a special kind of Task that is used for viewing and editing values of some Document Properties.

docflow_20

Starting the Business Operation

It is the kind of Task that allows to run the Business Operation. When the Business Operation starts, the framework prompts the user to confirm values of some parameters. The confirmation is requested for the properties that are input parameters of the Business Operation.

Note: You have to configure the prompt for confirmation for each individual parameter when designing the Schema.

Create Signature and Instruction

The end user can create two Tasks at runtime. Those are the Instruction and Signature Tasks. They can be added to the current Tasks group or created as a subtask.

Create Signature

To create Signature, use the Create Signature Action, click it and run the Wizard. In the first step, set the Signature destination: add to the current Task Group or subordinate. In the second step you will be prompted to set some Signature properties.

The process is shown in the figures below.

- Add Signature to current group:

docflow_14

- Add subordinate Signature:

docflow_15

Create Instruction

The current Task will be cloned, the Instruction will be added to the current Tasks Group.

Note: The possibility to clone the Task must be configured in the Application Model. You need set the IsClonable property to True when designing the Shema.

Use the Create Instruction Action to add the Instruction, click it and run the Wizard. The following Actions are similar to adding a Signature.

docflow_16