Search: set-agent-asset

To learn what has changed in akaBot Center, check out the release notes below. Bug fixes [Asset] Users were unable to update values in the "Value per agent" tab. [Process Builder] Users were unable

the edited data. [Asset] Information about the Assignee was not being saved, and occasionally, incorrect

in akaBot Center, check out the release notes below. == **Bug fixes** == * [Asset] Users were unable to update values in the "Value per agent" tab. * [Process Builder] Users were unable to add a new item

] Activities involving selecting a Start task and saving did not correctly save the edited data. * [Asset

for adding assets. [Add] Allow admin role to reset password [Add] Encrypt & decrypt credential (agent, asset) [Add] Enable OU audit

from agent incorrect order [Fix] Not refresh list OU of user when changed from browser other [Fix

availability** == * ((( [Added] Import/export function for adding assets. ))) * ((( [Add] Allow admin role to reset password ))) * ((( [Add] Encrypt & decrypt credential (agent, asset) ))) * ((( [Add] Enable OU

when change robot in schedule * [Fix] Cannot delete package * ((( [Fix] Log message from agent

The Asset Activities Pack contains all the activities used for creating automation projects. These activities enable the robots to: Set value to Asset on Center Get value from Asset on Center On Studio, Asset pack is inside Core pack See also: Release Notes Activities

[3] Assets

(% class="box" %) ((( The Asset Activities Pack contains all the activities used for creating automation projects. These activities enable the robots to: * Set value to Asset on Center * Get value from Asset on Center On Studio, Asset pack is inside Core pack ))) See also: * [[Release Notes>>path:/bin

to create/edit Common Value This means every agent can access the asset you are creating/editing Value Depending on the type you chose Enter/select the value of the asset Use case 11: Change agent’s password

(for more information, click here) Option 2: S1: In Asset tab, choose Name of agent you want to change

agent can access the asset you are creating/editing |Value|Depending on the type you chose Enter/select the value of the asset == (% style="color:#e74c3c" %)**Use case 11: Change agent’s password

:** S1: In **Asset **tab, choose Name of agent you want to change passwork, then click Edit button

akaBot Center credential by using a provided Asset Name and returns a username and a secure password

will be terminated. Default value: 30000 (milliseconds). E.g: 30000 Input Asset Name (String)* - The name of the asset to be retrieved. E.g: “Test_Integer” Misc Public (Checkbox) - If you check it, the data

Get Agent Credential

Get Agent Credential

by using a provided Asset Name and returns a username and a secure password. [[image:image-20220506112654

** * **Asset Name (String)*** - The name of the asset to be retrieved. E.g: “Test_Integer” **Misc

edit the name of the activity to organize and structure your code better. E.g: Get Agent Credential

related to automating activity. 3 Resources Include the list of Agent (Software agent that automates rule-based processes in the same manner as humans do), group of Agent for deployment purposes. 4 Asset Shared

and transactions statuses, and SLA predictions. 6 Monitoring Place to control and track Agent's activities and view

|Automation|Include all the components related to automating activity. |3|Resources|Include the list of Agent (Software agent that automates rule-based processes in the same manner as humans do), group of Agent for deployment purposes. |4|Asset|Shared variables or configurations that can be invoked in the design

to wait at most 30 seconds for the heartbeat to be submitted. To set up High-Density Agents on Windows Server machine, please see the Setting Up Windows Server for High-Density Agents and High-Density Agents

For a better use of a machines's computing power, Agents can be configured in High-Density mode

[3]High-Density Agents

akaBot Agent

. To set up High-Density Agents on Windows Server machine, please see the [[Setting Up Windows Server

/Setting%20Up%20Windows%20Server%20for%20High-Density%20Agents/]] and [[High-Density Agents Setup >>https

For a better use of a machines's computing power, Agents can be configured in High-Density mode

User have to config Agent Setting for each Agent in Center before running High-Density Agents. In this article, we will show you how to set up Agent as below Step 1: Login Center Step 2: Choose the Agent

and configure Agent Settings Windows Session Console Choose the Console option if you want to run bot

[6] High-Density Agents Setup

User have to config Agent Setting for each Agent in Center before running High-Density Agents. In this article, we will show you how to set up Agent as below (% class="box infomessage" %) ((( **Step 1

))) (% class="box infomessage" %) ((( **Step 4**: Choose and configure Agent Settings ))) [[image:image

(for more information, click here) Option 2: S1: In Asset tab, choose Name of agent you want to change

the suitable agent Parameters tab: Holiday settings tab: single choice Run continuously (default) Bypass

the unit Use case 3: Create/ edit a new Role Roles are sets of permission, which means

:]](%%)//)// [[image:image-20230425155109-39.png]] **Option 2**: S1: In **Asset **tab, choose Name of agent you want

]] == (% style="color:#e74c3c" %)**Use case 3: Create/ edit a new Role**(%%) == Roles are sets of permission

all information including: * Number of Agent (Available, Busy, Disconnected, Nonresponse) * Number

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

with no assigned Organization Unit does not have access to any type of resources. The same agent cannot

of entities make up an organization unit: * Agent group * Agents * Workflows * Tasks * Schedules * Packages Repository * Assets * Queue * Logs * Report ! Statistics are produced for each organizational

access to any type of resources. The same agent cannot be provisioned on two different Organization