Search: update-file-permission

execute permission: chmod +x setup.sh After running the above commands, the script will copy files

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

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

. 1. GetRolePermisson Get Resources permission collections. Supported methods: Get Parameters Name

8. UpdateUser Update user information. HTTP method: Put Parameters Name Type Description userDTO

. UpdateWorkFlowVersion Update version of workflow. Supported methods: Put Parameters Name Type Description id Integer

. GetRolePermisson**(%%) == Get Resources permission collections. Supported methods: Get Parameters |Name|Type

:#000000" %)**8. UpdateUser**(%%) == Update user information. HTTP method: Put Parameters |Name|Type

**(%%) == Update version of workflow. Supported methods: Put Parameters |Name|Type|Description |id|Integer

step-by-step instructions on how to update & backup akaBot Studio, Agent & Center. 1. akaBot Studio

, CSS will be scoped Make sure you create a backup that contains 2 files from old version : application-dev.yml and application-prod.yml so you don't have to re-edit Step 3: Backup license file: Find

to update & backup akaBot Studio, Agent & Center. == **1. akaBot Studio & Agent** == * **Step 1

> Kindly follow all the steps to update <a href="https://docs.akabot.com/docs/network-installation#e-akabot

sure you create a backup that contains 2 files from old version : **application-dev.yml

with a failed_import status. This can happen, for example, when a document is too long, the document file is corrupted

into Multiple Documents It is often convenient to process multiple documents stored in a single file. Most

in a single file that combines all the scanned pages. AkaBot Vision can split a file automatically using

. This can happen, for example, when a document is too long, the document file is corrupted, or due

documents stored in a single file. Most commonly, you would scan many documents at once in a scanner with an automatic feeder, resulting in a single file that combines all the scanned pages. AkaBot Vision can split

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

to review documents then change it to "Confirmed" status by API Update Document Status before exporting data

with the input parameters (token, documentId that need to be extracted and file format that user wants to export

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

, it means that the user needs to review documents then change it to "Confirmed" status by API (%%)[[Update

]]** **to IDP Server with the input parameters (token, documentId that need to be extracted and file format

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

of the file you want to update. You can use this key from the import document activity. * Update to status

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

akaBot incorporates a role and permission-based access-control framework. Roles are sets of permission, which means that the permissions required to access and control specific Center resources are assigned to roles. In other words, Users were not given permission to certain resources but will get

="wikigeneratedid" id="H" %) akaBot incorporates a role and permission-based access-control framework. Roles are sets of permission, which means that the permissions required to access and control specific Center resources are assigned to roles. In other words, Users were not given permission to certain resources

: Updating We can find these logs by: Open File Explorer, go to %programdata%\akaBot\Logs\ In akaBot Agent

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

, but we can access them as file .txt later. Here are several ways to find the folder location: Open File

**Machine logs** Definition: Updating We can find these logs by: * Open File Explorer, go

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

, but we can access them as file .txt later. Here are several ways to find the folder location: * Open

. This page displays all available users and allows admin to add or delete, as well as update users

* ROLE_ROBOT A user can have more than one role. Details about permission for each role will be explained

permission for each role will be explained in the Role Management section. b. Create/Edit a User To create

. This page displays all available users and allows admin to add or delete, as well as update users

role. Details about permission for each role will be explained in Role Management. |7|Created date

: ROLE_ADMIN ROLE_USER * ROLE_ROBOT A user can have more than one role. Details about permission for each

to update the Config file later. Click “Next" Click "Execute" and wait till everything is finished. Click

the application.yml file Step 2 - Update the database connection by updating the datasource section (database server

command echo %JAVA_HOME%, the output should be a path that point to jdk 11 ex: C:\Program Files\Java\jdk

to update the Config file later. Click **“Next"** [[image:image-20220506134651-12.png]] * Click **"Execute

Automation Hub Configuration** === **Step 1 **- Open the application.yml file **Step 2** - Update

command **echo %JAVA_HOME%**, the output should be a path that point to jdk 11 ex: **C:\Program Files\Java