Search: state-machine-1

personified."[1] Capra became one of America's most influential directors during the 1930s, winning three

-Freer_1-0" %)^^[[[1]>>url:https://en.wikipedia.org/wiki/Frank_Capra#cite_note-Freer-1]]^^ Capra became

/Signal_Corps_%28United_States_Army%29||title="Signal Corps (United States Army)"]] and produced [[propaganda

. 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

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

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

. 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

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

state for each Agent based on the input parameters and notifies the respective Agents about the pending

Integer False Agent Group ID robotId Integer False scheduleId Integer False state String False

and resources are exposed to be accessible with appropriate authorization. == (% style="color:#000000" %)**1

-20230307144502-1.png]] Headers: [[image:image-20230307144502-2.png]] Response: == [[image:image

: [[image:image-20230307144502-12.png]] [[image:image-20230307144502-13.png]] 1. 11. == (% style="color

The total number of tasks, including retried tasks, for each state: Successful Abandoned Failed Task

(% class="akb-page-with-toc" %) ((( (% class="akb-page-content" %) ((( == [[image:image-20230413161244-1.png]] == By default, the **Queues** dashboard is comprised of the following widgets, which can

)))|((( The total number of tasks, including retried tasks, for each state: * **Successful** * **Abandoned

when specific events occur on a machine. Perform window manipulation. Pick Target Element

the Robot to execute certain actions when specific events occur on a machine. * Perform **window

 **Selector Editor** wizard. [[image:image-20220509101433-1.png]] Click **Pick target element** button opens

, 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

), 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

[1] Agent

[1] Agent

(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

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

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