Search: file-change-trigger

, 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 trigger option, the configuration screen of file trigger will be open as below: Step 3: Fill

[3] How to use Desktop Trigger

[4] Desktop Trigger

[3] How to use Desktop Trigger

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, the configuration screen of** file trigger** will be open as below: [[image:image-20230421172821-3.png||height

/Trigger/Agent 5 Organization Unit Selection Menu Change the active Organization Unit 6 Language Change

Menu Access the following options and pages: Settings: On this page, you can change the user details such as First Name, Last Name, Email and the display language. Password: On this page, you can change

functionality |4|**Quick create**|Quickly create a Task/ Schedule/Workflow/Trigger/Agent |5|**Organization Unit Selection Menu**|Change the active Organization Unit |6|**Language**|Change the display language

the following options and pages: //**Settings**: On this page, you can change the user details such as First

Triggers provide a uniform mechanism for subscribing to events from the Connector platforms

. Prerequisites Before you can configure Triggers, make sure the following conditions are met: The App Connect is enabled and provisioned for your tenant The Triggers tab is displayed in the Integrations window 2

[4] Triggers

(% class="akb-page-with-toc" %) ((( (% class="akb-page-content" %) ((( **Triggers** provide

configure Triggers, make sure the following conditions are met: * The App Connect is enabled and provisioned for your tenant * The Triggers tab is displayed in the Integrations window == **2. Creating your

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

. This field will be used in other activities. Export Document To export file and change status if you

Automation Type is Always, then export them and change the status. Import all the files in a folder

file and change status if you want. There are 3 fields you need to focus on: ))) * Document key

in the akaBot ecosystem. When using these activities, you do not need to import files to akaBot Vision or export, change the status manually. There are 6 activities: (% class="box infomessage" %) ((( To connect

Yes Trigger* Recurrence Select the cycle for the schedule by: Minute/ Hourly/ Daily/ Weekly/ Monthly

to re-trigger a schedule Textbox No Parameters No Holiday Settings Holiday schedule Radio

Edit, change the desired profile, and then select Save. To copy a specific schedule in the list

| |(% colspan="5" %)Trigger* |Recurrence|Select the cycle for the schedule by: Minute/ Hourly/ Daily/ Weekly

fields that allows users to create a CronTrigger to re-trigger a schedule|Textbox|No| |Parameters

-20230312200330-41.png]] , select **Edit**, change the desired profile, and then select **Save**. To copy

. Save changes and exit Press ESC then type: “:wq” 2.1.5 Step 5: Configure Tomcat log 1. Open the file

level if needed. Ex: ERROR 5. Change other config: maxFileSize: Limit the size of each file. Ex: 100MB

settting 3. Save changes and exit Press ESC then type: “:wq” 4. Configure for the file application

of all archive files. Ex: 20GB (% style="margin-left:40px" %) 6. Save changes and exit (% style

"]] 3. Save changes and exit Press ESC then type: “:wq” 4. Configure for the file **//application

increasing of the file size and decrease the performance. To stop this, change the configuration

7. Update below code in the file: server.port: 5601 server.host: "0.0.0.0" 8. Save changes

. Save changes and exit Press ESC then type: :wq 2.4.2.5 Step 5: Configure Tomcat log 1. Open the file

: ERROR 5. Change other config: maxFileSize: Limit the size of each file. Ex: 100MB. maxHistory

:40px" %) 3. Save changes and exit. (% style="margin-left:40px" %) 4. Open the file ///opt/tomcat/conf

the total size of all archive files. Ex: 20GB (% style="margin-left:40px" %) 6. Save changes and exiT

: Orcl == (% style="color:#e74c3c" %)1.3. File Storage requirements(%%) == Please make sure that you

to notify various users, such as when a new queue item is ready for processing, a trigger fails, or a process is changed. Notes: Your application must be web-hooked and compatible with akaBot. After

solution to notify various users, such as when a new queue item is ready for processing, a trigger fails, or a process is changed. Notes: Your application must be web-hooked and compatible with akaBot. After

of history. Step 3: Save changes and close the file. Step 4: Open the file %TOMCAT_PATH%\conf\server.xml

: Step 6: Save changes and close the file 4.2.2. Other settings Step 1: Navigate to the path

totalSizeCap property controls the total size of all archive files. Ex: 20GB 4. Save changes and close file

" width="1045"]] Step 6: Save changes and close the file **4.2.2. Other settings ** Step 1: Navigate

="673"]] 3. Change the setting in rolling log file as below: * maxFileSize: Limit the size of each

archive files. Ex: 20GB [[image:1714720244392-526.png||height="401" width="775"]] 4. Save changes

failed by following guidelines 4. Installation Process Download all files in latest releases version here Use MobaXterm to ssh to your remote server Upload the above files to your home directory. For example, ~/dataservice Change directory: cd ~/dataservice Set execute permission: chmod +x setup.sh Set

utf8_bin ; {{/code}} === **4. Installation Process** === * Download all files in latest releases version

-20230630133051-1.png]] * Use MobaXterm to ssh to your remote server * Upload the above files to your home directory. For example, ~~/dataservice * Change directory: cd ~~/dataservice * Set execute permission: chmod