Workflow designer instructions

1. Introduction to the workflow designer 1. Process Design

Custom process processing,

Instructions for use:

LNew Process

When the program enters the new process status (or click "model"-"New" in the menu or click "New Model" in the shortcut menu ")

Click "edit"-"Model attributes" to go to the model attributes editing page.

The flowchart is illustrated below:

1. Click "Start task" and the "Start task" is displayed as the selected status. In the design window, click a proper position to create a "Start task ". (A process can only have one start task)

2. Click "End Task", and the "End Task" is displayed as the selected status. Click the appropriate position in the design window to create the "End Task ". (One process can only end one task)

3. Click "normal task". The "normal task" is displayed as the selected task. In the design window, click a proper position to create a "normal task ". You can create multiple common tasks as needed.

4. Click "condition task". The "condition task" is displayed as the selected task. In the design window, click a proper position to create a "condition task ". You can create multiple conditional tasks as needed.

5. Click "Straight Line" or "line" and drag the task from the start to the next, connect the task to form a flowchart.

6. Select a task or consecutive tasks, and drag it to adjust its position to make the flowchart more beautiful.

7. Click "model"-"save" (or "save" of the shortcut button) to save the flowchart and set common tasks and condition tasks one by one.

LOpen Process

Click "model"-"open" (or "open" in the shortcut button) to display the model selection window,

Select the type on the left and list the models of this type on the right. Double-click the model record line to open.

After opening, you can edit the model or task attribute settings, or add or delete task nodes.

2. model attribute editing page

It mainly sets the model name and model category. If the model is disabled, the model status is selected and disabled.

The Field List is simple for model data. You do not need to create a separate table. You can use model fields to save simple data. (We recommend that you design an independent table for a model to store data)

 

3. General task editing page

It mainly sets the Task Name, processing forms, personnel permissions, page function operation settings, and so on.

General attributes: The Task Name, which should be concise and clear. If XML is used to edit the form, click the edit form button to go to the corresponding setting interface; if the page is self-developed, write the link address starting from the root directory; the number of stay days refers to the default number of days the task can stay for (that is, the processing time limit ); the return mode limits the items that can be returned or cannot be returned; skip when unattended processing is allowed. When this task does not have a corresponding handler, this task can be skipped when the previous task is processed in the next step; allow the same person as the previous processing personnel to skip the process of the previous task; allow to skip the next step: when the next step of this task is processed, the task will be sent to the next handler between the personnel selection and other preparation interfaces (after this option is set, the next task's allowed preparation Interface select the handler settings to be invalid ); select a handler on the "allow preparation" Page refers to the person who can select the handler when preparing the previous task for the next step (this setting cannot be specified by the handler who needs the previous task as needed).

Personnel permission settings:

NOTE: If multiple users perform parallel processing and all operations must be completed, select "all operations must be performed", as shown in the signature.

Add permission

Generally, role permissions are used (I .e., the handler is determined based on the role), and no restrictions are imposed on the Roles. If the department is the initiator, the role must be in the same department as the initiator; the same Department as the current processor specifies that the role must be in the same department as the processor of the previous task; the higher-level department of the handler at that time limits the role to be in the higher-level department of the handler of the previous task; the lower-level department of the handler at that time limits the role to be in the lower-level department of the handler of the previous task; the role must be in the same department as the handler of the previous task or in all lower-level departments as the former Department and all lower-level departments.

You can also specify a department or a specific person.

If you need to specify the persons already processed in other tasks, specify the persons in the process.

You do not need to specify the personnel permissions for the first task. If the task processing interface is defined to determine the next person, you can specify a role.

Page features:

This button is displayed when the button is selected as the task processing, and the name is displayed after the button.

An extension button is an extension button that can be defined on the development task interface.

Approval is an approval option that appears on the page. If you are allowed to enter an approval comment, a text box is displayed.

You can set a condition for entering a task. If the condition is not met, the task cannot enter.

4. Conditional task editing page

The basic attribute is to set the task name.

Transfer Conditions and steering: Set the steering conditions and specific steering tasks.

5. Auxiliary Functions

L export model, used to export model configurations (backup or import)

L import model, used to import the exported model configuration to overwrite the current configuration

L model check to check the correctness of the model configuration syntax (tasks, task connections, task permission settings, etc. We recommend that you perform this check after setting the process.

L simulate the process, execute the simulation process according to the input personnel, and feedback the execution results. We recommend that you perform this simulation after setting the process to check whether the process can be transferred as expected.

L The process ends and the execution statement or method is set for processing after the process ends.

L clear the model and clear the tasks and connections in the Model

L reload and reload (used to disconnect or reload data from the intermediate database)