История страницы
...
Visually, the blocks are not connected in any way. When adding blocks to the scheme, you must add connections between the blocks manually, using the block
Start block
The Start block is the starting point of the workflow.
...
The panel with workflow parameter properties opens to the right of the workspace of the Workflow Constructor and looks as follows:
Workflow parameter property panel
Each workflow parameter has its own panel on which it is placed:
...
Example of a parameter setting:
Types of workflow parameters
String
The value of a parameter of this type can be specified using letters of any alphabet, numbers and symbols.
...
The number can be positive, negative, floating point or fixed point.
Adding a workflow parameter
With the Add Parameter + button, several workflow parameters can be added to the Start block. Each new parameter will be numbered in order:
Deleting a workflow parameter
A workflow parameter can be deleted from the parameter list using the trash can icon located in the upper right corner on the property bar of the specific parameter to be deleted.
Finish block
The Finish block is used to indicate the process end point and, if necessary, to set the workflow result parameters. Any input and/or input parameters of the workflow/task/SF/subprocess can be used as result parameters.
...
For the workflow, the scheme of which is shown in the figure below, the robot output parameter “Addition of 2 numbers” is chosen as the final result of the workflow, which adds 2 numbers: the degree of the first workflow parameter and the area of a circle with radius equal to the second workflow parameter.
Robot block
The Robot block performs a robotic task. The block has 3 common properties:
- Robot name (filled in automatically after selecting the robot).
- Robot description (filled in automatically after selecting the robot).
- Block color (filled in by the workflow designer).
- Special launch:
- Host (to be filled in by the workflow designer after the robot has been selected)
- Account (to be filled in by the workflow designer after the robot has been selected)
- Input parameters (filled in by the workflow designer after the robot has been selected).
Selecting a robot
To select a robot as the executor of the task, click on the Select a robot button.
...
The Performance conditions parameter - if the wait for all radio button is selected, the block waits for the execution of all guides included in it. If wait for one is selected - the block expects at least one guide to be executed.
General properties
Once the robot is selected, the Robot block property panel will display:
...
The remaining properties must be filled in by the workflow designer.
Special launch
In a special launch, the designer is given the opportunity to choose:
...
This setting is also used to specify a specific machine to start the robot during operation. It is important in cases where access to information systems is restricted.
Input parameters
Fields for robot input parameters appear automatically based on the robot's internal specification. The designer only has to link them either to workflow parameters or to parameters of previous tasks.
...
This completes the work with the Robot block.
Screen form block
The Screen form block is used in the workflow as a user task.
...
| Properties | Purpose | |
|---|---|---|
| 1. | Task name | Filled in automatically after selection of SF |
| 2. | Description of SF. | Filled in automatically after selection of SF |
| 3. | Block color | Filled in by the workflow designer |
| 4. | Responsible | Selected by the designer from the list, the default executor is Initiator |
SF selection
To select an SF for a user task, click on the Select a screen form button.
...
are filled in by the workflow designer.
Choice of performer
Performer is an individual, an employee of the company and at the same time a user with the role of Task performer, who will work with the SF.
...
The user or group of users is also searched by the first characters entered.
Block color
Block color is a common optional property of any block. It is filled in the same way as for all other blocks.
Priority
The workflow designer can set the priority of a task to be used by its executor when selecting the next task, if several user tasks are in progress at the same time.
A task may have the following priorities:
- High.
- Medium.
- Low.
Deadline
The deadline is set in days, hours and minutes and is counted from the moment the task is available to a specific executor or group. If the deadline expires, the performer, workflow owner and workflow administrator will receive a notification that the deadline has expired, if they are all subscribed to this type of notification. Upon receiving such a notification, the workflow owner must find out the reason for the delay in execution and take the necessary measures to eliminate them as soon as possible.
Input parameters
The input parameter fields are created automatically based on the internal specification of the SF. The workflow designer only has to set the values of these parameters.
...
In this case, the task performer will see 2 fields in SF No.1 during work with the workflow parameter values that were set either by default or at startup.
Logical gateway AND
The logical gateway AND is designed to parallelize the workflow by branches. The number of parallel branches is unlimited and they must converge in one task (robotic or user).
...
- Block name
- Block size
- Color (to be filled in by the workflow designer)
- SF description
Logical gateway OR
The logical gateway OR is intended for branching a workflow based on a condition. The condition can be one or several.
The condition is set only after creating a connector with the subsequent blocks of the scheme. The number of block conditions to be set is equal to the number of connectors (workflow branches) coming from the block.
Condition constructor
In the scheme shown below, the OR block has two outgoing guides to the two Robot blocks:
...
Conditions can be edited at any time by clicking on the Gear. To delete a condition, click on the cross icon on the conditions panel or on the Bin in the condition builder.
Workflow block
The Workflow block is designed to use another workflow that has already been published to execute a business task. The configuration of this block is very similar to the work with the Robot block.
...
- Workflow name (automatically filled in after selecting a subprocess);
- Workflow description (filled in automatically after selecting a subprocess);
- Block color (filled in by the workflow designer);
- Input parameters (filled in by the workflow designer after selecting the robot).
Workflow selection
To select a workflow as the executor of the task, click on the Select a workflow button.
...
We used the search bar to select the workflow.
General properties
After selecting a workflow, the properties panel of the Workflow block will show:
...
The remaining properties must be filled in by the workflow designer.
Input parameters
Fields for subprocess input parameters appear automatically based on the internal specification of the subprocess. The designer only has to link them either to the main workflow parameters or to the parameters of previous tasks.
...
It is very easy to link the input parameters of a subprocess to the input parameters of a workflow or task. To do this, in the field for each input parameter of a subprocess, you need to select the desired workflow or task parameter from the dropdown list.
In our case we need to select the workflow input parameters a and b:
API block
The API block represents a link in the workflow to the REST API, which manages sending requests to an external server and processing responses from it.
...
| Parameter | Description |
|---|---|
| Name | This is the name or identifier of the block that is used to designate a specific REST API action |
| Description | This is a brief explanation describing the block |
| Block color | Block color coding that can be used for visual differentiation |
| Performance conditions | If the wait for all radio button is selected, the block waits for the execution of all guides included in it. If wait for one is selected - the block expects at least one guide to be executed. |
| REST service URL | This is the address of the web service or API to which the request is directed. The URL points to the specific resource or endpoint to be processed. |
| Authorization | This field specifies the authorization method used to access the REST API. It can be basic authorization, authentication using tokens, or another method |
| Token | This field is for specifying an authentication token that is required for authorized access to the REST API resource. The token is used to verify access rights to protected data. |
| Method | Specifies the HTTP method to be used when sending the request. GET Used to retrieve data from the server POST Used to send data to the server, for example, to create a new resource PUT Used to update an existing resource on the server DELETE Used to delete a resource from the server |
Get file | Checkbox to indicate whether the file should be retrieved |
Disable SSL verification | Checkbox to disable SSL certificate validation |
Selecting a proxy server | Here you specify the proxy server that will be used to send requests |
Results | Response Status - HTTP status code returned by the server that indicates whether the request succeeded or failed Response Headers - HTTP header information returned by the server, such as content type, response time, and more. Response Body - The main content of the response, which may include data in JSON, XML, text, or other format. |
Note block
The Note block does not affect the workflow and is intended for the workflow designer - present or future - who will take it to them for revision or rework.
...
Обзор
Инструменты контента