Search: remove-log-fields

to existing" then choose other tags or add new tags then click "Apply" button Clear fields: Clear fields is used for removing tags of current documents. Staff choose option "Clear fields" then click "Apply

and remove these : Find and remove these is used for finding and removing specific tag in the tag list. Staff

then click "Apply" button [[image:image-20221027174657-4.png||cursorshover="true"]] * **Clear fields: **Clear fields is used for removing tags of current documents. Staff choose option "Clear fields

||cursorshover="true"]] * **Find and remove these** : Find and remove these is used for finding and removing

fields by clicking button "Add field" or remove fields by unticking some fields. If staff doesn't

" button Note: Staff can not add, remove and configure fields after saving. So please check carefully

Name, Base Model (optional) and Description (optional) Step 4: Create fields for models If staff

"]] (% class="box infomessage" %) ((( **Step 4**: Create fields for models ))) * If staff choose base model, this new model will get all the fields that the based model has and staff can add more fields by clicking button "Add field" or remove fields by unticking some fields. [[image:image-20230213141833-4.png

, use integers for Number fields. Click + Condtion to add as many conditions as you need. To remove

OR - to return the entries that match any of the conditions Define the conditions: Field - select the entity field to apply your condition to. Operator - select the condition. Value - enter the value for your

the entries that match any of the conditions ))) 1. ((( Define the conditions: * **Field** - select the entity field to apply your condition to. * **Operator** - select the condition. * **Value** - enter the value for your condition. The value must be of the same type as the field type. For example, use strings

can only add one by one Use case 2: Remove an OU In Organization Unit menu > click Delete button next to the OU name on the page to remove an OU Note: Delete an OU will delete all resources within

, click the Edit button corresponding to the Role in the Action column. Use case 4: Remove role S1

only add one by one ))) == (% style="color:#e74c3c" %)**Use case 2: Remove an OU**(%%) == In **Organization Unit **menu > click **Delete **button next to the OU name on the page to remove an OU **//Note

case 4: Remove role**(%%) == S1: To delete a role, you click the **Delete** button

an organization unit: Agent group Agents Workflows Tasks Schedules Packages Repository Assets Queue Logs Report

be in display there as below: As an Admin, you may view the details of specific OU, create, update, or remove

a user from an organization unit, open the Edit windows and hit the bin icon in the action field. Once

* Packages Repository * Assets * Queue * Logs * Report ! Statistics are produced for each organizational

of specific OU, create, update, or remove or filter the OU, as well as manage the users that are allocated

and hit the bin icon in the action field. Once all the information is filled/edited, hit **Save**. Your OU

the properties of a task and task log. DELETE: Remove the task CLONE: Create an identical task from the existing

or Edit a task, Start or Stop a task, and display the logs generated by it with just a click of the button

: the task has been stopped. * SUCCESSFUL: the task has been completed successfully. You can see the log

can also manually Create or Edit a task, Start or Stop a task, and display the logs generated

to perform some actions to manage the tasks: VIEW: to view the properties of a task and task log. DELETE: Remove the task CLONE: Create an identical task from the existing task By selecting the Checkbox

to edit the details of each Agent Delete: allows you to remove selected Agent from the Center By selecting

The username used to log in to the Agent machine Description Description of the Agent Created by The user

of the machine the Agent is registered on. 4 Machine Username The username used to log in to the Agent machine 5

// Delete: allows you to remove selected Agent from the Center By selecting the Checkbox on each Agent

**|The username used to log in to the Agent machine | |**Description**|Description of the Agent | |**Created

is registered on. |4|**Machine Username**|The username used to log in to the Agent machine |5|**Type

this stage, user can make changes to the text in each field that has been detected incorrectly In addition, akaBot Vision provides users with the capability to add or remove rows in a table To insert a row, you

Shortcuts When reviewing documents in akaBot Vision, there are multiple ways of moving between data fields

in each field that has been detected incorrectly [[image:image-20220420193327-2.png||data-xwiki-image

or remove rows in a table * To insert a row, you can click "+" icon * To delete a row, you can click "x

of moving between data fields, confirming them, and editing them. Over time, operators find the most

1. Create an Account Note: Although akaBot Vision currently supports Pre-trained data fields

by filling in all the fields or register with your current Google count by clicking "Sign up with Google

customizable, so you can add/group/remove pipelines as needed. Table of Content

currently supports Pre-trained data fields only for Invoice processing, the technology is documented

]] (% class="box infomessage" %) ((( Note: You can register by filling in all the fields or register with your

document type that needs to be processed. The left panel is fully customizable, so you can add/group/remove

switching, the UI will change to: Manage Properties: To configure more fields, click Manage Properties, make your selection, then click Update fields/Save Properties Common Continue On Error: Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values

will change to: * **Manage Properties:** To configure more fields, click Manage Properties, make your selection, then click Update fields/Save == **Properties** == * **Common** ** Continue On Error: Specifies if the automation should continue even when the activity throws an error. This field only supports