Search: type-into

conditional clause (If, Else, Switch) to complete the process. Types of logic in a process In Process

; enter the input condition and expression type in definition session Case A Logic Case is a control

. Drag and drop in the process, user choose case type (Decision case, Default Case) and enter

[7] Types of logic in a process

(If, Else, Switch) to complete the process. == **Types of logic in a process** == In Process Designer

and expression type in definition session |Case|((( A Logic Case is a control structure alike Logic Switch

, user choose case type (Decision case, Default Case) and enter corresponding values.

Configure Automation Type for pipeline Staff can configure the Automation Type for each pipeline

: Choose Automation Type and set conditions for required fields and data formats The Automation Type

that all documents need to be reviewed and confirmed by human CONFIDENT: On CONFIDENT automation type

[2] Configure Automation Type for Pipeline

Configure Automation Type for Pipeline

Automation Type for pipeline ** == (% class="wikigeneratedid" id="HStaffcanconfiguretheAutomationTypeforeachpipelinebyfollowingthesesteps" %) Staff can configure the Automation Type for each pipeline by following these steps (% class

Automation Type and set conditions for required fields and data formats ))) * The Automation Type will have

conditional clause (If, Else, Switch) to complete the process. Types of Operator  when designing a process

[8] Types of Operator when designing a process

(If, Else, Switch) to complete the process. (% class="wikigeneratedid" %) == == == **Types

1. User Name Type Description id Integer login String Username firstName String lastName

Array[OrganizationUnit] List ous 2. Robot Name Type Description id Integer key String name String description String machineName String userName String password String type RobotType 3

" %)**. User**(%%) == |Name|Type|Description |id|Integer| |login|String|Username |firstName|String

,..) |organizationUnits|Array[OrganizationUnit]|List ous == (% style="color:#000000" %)**2. Robot**(%%) == |Name|Type

|String| |password|String| |type|RobotType| == (% style="color:#000000" %)**3. OrganizationUnit

type. Must be of the same type as the selected Entity Type Misc Display Name: The display name

. Output Output Record: The record created from the Data Service, stored in an Entity type object. This field only supports objects of types imported from Data Service and must be of the same type

that is to be created for the selected Entity type. Must be of the same type as the selected Entity Type ))) * **Misc

Service, stored in an Entity type object. This field only supports objects of types imported from Data Service and must be of the same type as the selected Entity Type. [[image:image-20230630131859-3.png

for the selected Entity type. Must be of the same type as the selected Entity Type Misc Display Name: The display

at Verbose level. Output Output Record: The record created from the Data Service, stored in an Entity type object. This field only supports objects of types imported from Data Service and must be of the same type

that is to be created for the selected Entity type. Must be of the same type as the selected Entity Type ))) * **Misc

Service, stored in an Entity type object. This field only supports objects of types imported from Data Service and must be of the same type as the selected Entity Type. [[image:image-20230630131836-2.png

Collection (ICollection)* - The collection in which to check if the item exists. This collection is of type

the specified item exists in the collection. TypeArgument (Dropdown List) - The type argument of the collection and the item you want to check for existence. You can select different options based on the Data type

** * **Collection (ICollection)*** - The collection in which to check if the item exists. This collection is of type

List)** - The type argument of the collection and the item you want to check for existence. You can select different options based on the Data type of the collection you use. **Notes:** Once

, type, description Create a new trigger 1. Create a File trigger Step 1: At the home screen, click the "New Trigger" button. The list of trigger types will be shown as below: Step 2: Choose the File

the information in the tab: Basic No Column/Label Description Type Maximum Is Mandatory? 1 Trigger Name Fill

of created triggers by status, name, type, description == **Create a new trigger** == === 1. Create a File trigger === **Step 1**: At the home screen, click the "New Trigger" button. The list of trigger types

.png||height="358" width="342"]] (% style="width:1043px" %) |=No|=Column/Label|=Description|=Type

A Pipeline is the basic document processing unit of the akaBot Vision. For every document type

" button in the upper left corner Step 2: Fill the pipeline name Step 3: Choose the document type. A document type is a predefined Extraction schema (this defines what akaBot Vision will extract from

document processing unit of the akaBot Vision. For every document type (such as invoices, packing lists

.png||height="356" width="549"]] **Step 3**: Choose the document type. A document type is a predefined

be changed later). (% class="box infomessage" %) ((( Note: The default Document type for a new tenant

Data Service Input Record: The record that is to be created for the selected Entity type. Must be of the same type as the selected Entity Type Misc Display Name: The display name of the activity. Public

Record: The record created from the Data Service, stored in an Entity type object. This field only

that is to be created for the selected Entity type. Must be of the same type as the selected Entity Type ))) * **Misc

the Data Service, stored in an Entity type object. This field only supports objects of types imported from Data Service and must be of the same type as the selected Entity Type. [[image:image-20230630131917