Search: get-file-info

Get Event Info Monitor Events

* [[Get Event Info>>url:https://docs.akabot.com/bin/view/Activities/Events/Activities/Get%20Event%20Info/]] * [[Monitor Events>>url:https://docs.akabot.com/bin/view/Activities/Events/Activities/Monitor%20Events/]]

Comment Out Continue Convert Secure String Copy Directory Copy File Create Directory Delete Get Data from Clipboard Get Files Get OCR Text Image Exists Is Match Log Message Matches Message Box Move Directory Move File OCR Scope Path Exists Read Text File Remove Log Fields Replace Save Image Select File

/]] * [[Get Data from Clipboard>>url:https://docs.akabot.com/bin/view/Activities/%5B1%5D%20Core%20Activities/Activities/Get%20Data%20from%20Clipboard/]] * [[Get Files>>url:https://docs.akabot.com/bin/view/Activities

/Activities/%5B1%5D%20Core%20Activities/Activities/Copy%20Directory/]] * [[Copy File>>url:https

Choose event types that will occur in that folder Check box Yes 3 File Filter Gets or sets the filter

, 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

|(% style="width:139px" %)File Filter|(% style="width:489px" %)((( Gets or sets the filter string used

of created triggers by status, name, type, description == **Create a new trigger** == === 1. Create a File

will be shown as below: [[image:image-20230421172542-2.png]] **Step 2**: Choose the **File trigger** option

Staff can get the result of documents in akaBot Vision by exporting them. After documents are confirmed, a staff can export results. In this article, we will show how to export documents Step 1: Go

: Staff  choose file type that staff wants to export then click "OK" button

Staff can get the result of documents in akaBot Vision by exporting them. After documents are confirmed, a staff can export results. In this article, we will show how to export documents (% class="box

))) [[image:image-20221021140817-3.png]] (% class="box infomessage" %) ((( **Step 3: **Staff  choose file type

: Attribute Type Description Required id string Document Id want to get info Yes Output: If success

in akaBot Vision work? a. Import Document The user has to log in to akaBot Vision to get token

(token and files need to be uploaded) to IDP Server then IDP Server will respond the documentIds

parameters: |**Attribute**|**Type**|**Description**|**Required** |id|string|Document Id want to get info|Yes

has to log in to akaBot Vision to get token in the API Key in the Account section below the user's

:#e74c3c" %) (% style="color:#000000" %)and sending request information (token and files need

and then periodically check and get all ready files. For this mode, the user can follow 4 steps below: Step 1: The user

is also for mass processing but smoothier where you don’t have to set up job to check and get file

from a human to correct or confirm. Operation Model There are 3 modes to get output from the akaBot

. This model is for mass processing where you input many files and then periodically check and get all ready

you don’t have to set up job to check and get file periodically. For this model, the user can follow 2

. == == == **Operation Model** == There are 3 modes to get output from the akaBot Vision system: 1. **Single Invoice

ecosystem. When using these activities, you do not need to import files to akaBot Vision or export, change

key field of IDP Scope. Import Document To import files into the specified pipeline. There are 3 fields you need to focus on: File path: the file you want to import. Pipeline key: the pipeline

in the akaBot ecosystem. When using these activities, you do not need to import files to akaBot Vision

" %) ((( To import files into the specified pipeline. There are 3 fields you need to focus on: ))) * File path: the file you want to import. * Pipeline key: the pipeline that the file is imported to. The key is the ID

Description Mandatory. The description of the queue. 4 In progress The item was processed with the Get

was processed with the Get Transaction Item or the Add Transaction Item activity; when an item has this status

transactions in the queue. File size limited to 256kb by default. No 7 Output Data JSON schema

of the queue. |4|In progress|The item was processed with the Get Transaction Item or the Add Transaction Item

of the queue. |2|Description|The description of the queue. |3|In progress|The item was processed with the Get

|Specific Data|JSON schema for the specific data of all transactions in the queue.| |File size limited

fixed [Fixed] Activity Get File now has default values filled in for the "date from" and "date

Page As Image" activity no longer opens the PDF file in the background after execution

(java32). == **Bugs fixed** == * [Fixed] Activity Get File now has default values filled

is no longer present. * [Fixed] "Export PDF Page As Image" activity no longer opens the PDF file

. These are gathered and stored in a Log File. The overall operation of gathering and storing Logs is called Logging

information. Info Information about robot progress. Usually includes when we enter/exit a workflow, when data

not useful and needed in production. By default, we can view the logs down to Info level; that means, only

. These are gathered and stored in a **Log File**. The overall operation of gathering and storing **Logs** is called

. |Warn|Any important data that we need to stand out from the rest of the log information. |Info

in production. By default, we can view the logs down to Info level; that means, only the logs with Info level