Search: state-machine-1

Last modified by admin on 2022/04/24 04:58

Results 1 - 10 of 24 next page » Page 1 2 3

[1] Agent

Last modified by admin on 2023/07/04 15:22
Rendered document content
), you cannot edit the Username, Machine, or Type. To access the Agent page, click “Agent” tab
. No Column/Label Description 1 Action Available actions to manage the Agent. Includes: Edit: allows you
machine Status The current status of the Agent. AVAILABLE - the Agent is connected to the Center
Title
[1] Agent
Location
[1] Agent
Raw document content
(executing a process), you cannot edit the Username, Machine, or Type. To access the Agent page, click “Agent
as below. [[image:image-20221031154319-2.png]] |=No|=Column/Label|=Description |1|**Action
. | |**Version**|The installed version of the akaBot Agent tool in the local machine | |**Status**|The current

[2] Workflow

Last modified by admin on 2023/07/06 13:44
Rendered document content
is linked to an Agent Group, it is automatically distributed to all the Agent machines that belong
on the Agent machines and execute works faster from the Tasks page. To access the Workflows page, you click
Workflow as below: No Column/Label Description 1 Action Available actions to manage the Log of said
Raw document content
to all the Agent machines that belong to that **Agent Group**. The Workflows page enables you to deploy
to date. This helps you distribute packages on the Agent machines and execute works faster from the Tasks
]] |=No|=Column/Label|=Description |1|Action|((( Available actions to manage the Log of said Workflow. Includes

HTTPS Enabling Configuration

Last modified by admin on 2023/11/29 13:39
Rendered document content
then trust it in your machine. 3.1. Prepare akaBot security certificate. Step 1: Open Java Security folder
, the certificate will be only effective in trusted Center & Data Service machine. Step 1: In the Center and Data
machines and repeat above step 1 and 2 to trust it in each machine. 3.2.2. Automatically (Organization
Raw document content
will be only effective in trusted Center & Data Service machine. **Step 1:** In the Center and Data Service
" width="587"]] Please **copy file “akabot.cer” to ALL Agent machines** and repeat above step 1 and 2
(% class="akb-page-with-toc" %) ((( (% class="akb-page-content" %) ((( = **1. Introduction

[8] Setting up Auto Login for Unattended Agent

Last modified by admin on 2024/03/04 15:23
Rendered document content
to view the docs for that particular version Setup 1. Windows Group Policy (gpedit.msc) Group Policy
the Secure Attention Sequence (SAS). Step 1 - Open Start Menu > type Group Policy or gpedit.msc Step 2
applications Remote Desktop Services must limit users to one remote session Step 1 - Open Start Menu
Raw document content
that user's state as locked or active. **Solution** : To allow 1 session for 1 user, please follow
for that particular version == **Setup** == === **1. Windows Group Policy (gpedit.msc)** === * Group Policy
"** **Allow service to simulate the Secure Attention Sequence (SAS).** **Step 1 ** - Open Start Menu > type

Center Installation Guide for Standalone Model on Redhat v9.x

Last modified by admin on 2024/05/03 16:27
Rendered document content
1. Before you start This document aims to guide you to install akaBot Center in Standalone model (all-in-one” model) which means that all necessary packages will be installed in only one machine
machine which installs akaBot Center (hereby, call it as akaBot Center machine) needs to fulfill below
Raw document content
machine as below image~: [[image:image-20230728180918-1.png||height="176" width="649"]] For other models
this guide to your akaBot Center machine to run for convenience and preventing syntax errors. 1. Due
to the akaBot Center machine to prevent syntax errors. 1. When updating configuration files, please follow

Setting Up Windows Server for High-Density Agents

Last modified by admin on 2022/12/15 10:38
Rendered document content
If you want to take advantage of the High-Density Agents feature on a Windows Server machine, you
Remote Desktop Session Host to enable the Windows Server machine users to access virtual desktops, session-based desktops, and RemoteApp programs. Add the users that are going to use the machine
Raw document content
desktops, and RemoteApp programs. 1. Add the users that are going to use the machine (and are going
, add users from your domain, under which the Agents will be able to access the machine. 1. Click **OK
to take advantage of the **High-Density Agents** feature on a Windows Server machine, you must first make

[4]Activation

Last modified by admin on 2023/12/07 09:27
Rendered document content
1. Activate akaBot Center Step 1 - Open your browser. Navigate to akaBot Center using your Center
the steps below to activate your akaBot Studio. Step 1 -  Start the Studio. In installing windows, choose
akaBot Center. (At Step 6, Part 1 - Activate akaBot Center) Network Options (Optional): If you use Proxy
Raw document content
(% class="akb-page-with-toc" %) ((( (% class="akb-page-content" %) ((( == **1. Activate akaBot Center** == **Step 1** - Open your browser. Navigate to akaBot Center using **your Center URL
. **Step 1** - ** **Start the Studio. In installing windows, choose option “akaBot Center” then hit button

[6] High-Density Agents Setup

Last modified by admin on 2022/12/19 09:20
Rendered document content
. In this article, we will show you how to set up Agent as below Step 1: Login Center Step 2: Choose the Agent
in Agent of physical machine which is used by human. In Console mode, instead of creating remote desktop
after login will have the same resolution as the current mornitor If the machine has no monitor
Raw document content
. In this article, we will show you how to set up Agent as below (% class="box infomessage" %) ((( **Step 1
-20221219091856-1.png||cursorshover="true"]] * **Windows Session** ** **Console** *** Choose the Console option if you want to run bot in Agent of physical machine which is used by human. *** In Console mode, instead

[1] Task

Last modified by admin on 2023/07/04 14:44
Rendered document content
, State of Tasks No Column /Label Description Type Maximum Input Requirement 1 Search box Search
displays by default all the tasks that are running, and the ones placed in a pending state, regardless
page listing all existed tasks as below: No Column Description 1 Actions/View Depending
Title
[1] Task
Location
[1] Task
Raw document content
in a pending state, regardless of whether they were started manually or through a schedule. On this page, you
]] |=No|=Column|=Description |1|Actions/View|Depending on the status of the task, the system will allow you
is located. |6|State|Current status of the tasks. Available statuses are: FAULTED: the tasks have encountered

[4] Triggers

Last modified by admin on 2023/10/02 16:38
Rendered document content
. It gives you the flexibility to automatically start automations or workflows in Orchestrator. 1
was successfully launched, in which case it shows the word Successful in the State column. NOTE: The Successful state only indicates that the job was successfully launched. It does not reflect whether the job
Raw document content
to automatically start automations or workflows in Orchestrator. == **1. Prerequisites** == Before you can
. Configuring your trigger** == To add a Trigger, you will have to: 1. Access the akaBot Center. 1
: Connectors, Connections, and Triggers.[[image:1696239499620-749.png||height="448" width="879"]] 1. Access
next page » Page 1 2 3
RSS feed for search on [state-machine-1]
Created by admin on 2022/04/17 14:38