Search: state-machine-1

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

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

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

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

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

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

– High - 1 – Normal - 2 – Low. The default value is: (null) Queue Item States (DropDownlist) - Filters the state of the item. The following options are: All, New, InProgress, Failed, Successful, Abandoned

state, and reference. (* for Mandatory) Properties Common Continue on Error (Boolean) - A Boolean

an indicated queue according to multiple filters such as creation date, priority state, and reference. [[image:image-20220506113443-1.png]] (* for Mandatory) == **Properties** == **Common** * **Continue on Error

by their priority. Integers variables supported only. The priorities are: - 0 – High - 1 – Normal - 2 – Low

To learn what has changed in akaBot Center, check out the release notes below. Bug fixes 1

] The queue automatically transitions to the Expired state even though it was previously in the Successfully state. 11. [Webhook] Not displaying all events in Subscribed Events. 12. [Report] Does not export

in akaBot Center, check out the release notes below. == **Bug fixes** == ~1. [Workflow] Duplicated output

to the Expired state even though it was previously in the Successfully state. ~11. [Webhook] Not displaying all

there is no event. == **Updates** == ~1. [Task] When a task is triggered to run by Desktop Trigger, the source

by performing below steps: Step 1: In Settings screen ( if in the List Workflows screen then select Settings

actions to connect to the akaBot Center. Step 1: – In Settings screen ( if in the List Workflows screen

into Central Configuration form. Machine name: the computer name of current computer. The machine name

akaBot Agent** == To operate a bot, you need to follow below actions: 1. Configure network setting to open connection to the akaBot Center if needed. 1. Configure bot setting & connect to akaBot Center. 1. Get processes from akaBot Center or akaBot Studio. 1. Control the processes by running/stopping

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

(% 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

. 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

. 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

Use case 1: Quick navigation In the top of center, enter the workflow, agent group, agent … what

bot 1. Modify Asset (If you don’t need modify assets, please click here to find the way to run Bot

, or quickly search by the Search tab on the top of the page S3: Option 1: Choose Edit button

" %)**Use case 1: Quick navigation**(%%) == In the top of center, enter the workflow, agent group, agent

-20230425134819-1.png]] == (% style="color:#e74c3c" %)**Use case 2: Start running bot**(%%) == (% style="color:#000000; font-size:18px" %)1. Modify Asset //(If you don’t need modify assets, please click //[[(% class

, 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

[1] Task

[1] Task

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