Search: go-forward-1

Vision: Going to Account/API Keys, generate and copy an API key. akaBot Studio: paste the key in the API

at the pipeline having key 1. Get Document Status To get specific document status. There are 2 field you need

akaBot Studio and akaBot Vision by API key. ))) * akaBot Vision: Going to Account/API Keys, generate

-20220420200751-1.png||cursorshover="true"]] === **Import Document** === (% class="box infomessage

documents at the pipeline having key 1. === **Get Document Status** === (% class="box infomessage

. No Column/Label Description 1 Action Available actions to manage the Agent. Includes: Edit: allows you

button. No Column/Label Description 1 Agent Group The Agent Group to which the Agent belongs. 2 Name

requests created, go to the Agent tab > View agent detail > Select Verification tab. d. Create/Update

[1] Agent

[1] Agent

as below. [[image:image-20221031154319-2.png]] |=No|=Column/Label|=Description |1|**Action

by clicking the** eye** button. [[image:image-20221031154549-3.png]] |=No|=Column/Label|=Description |1

..." notification shown in the top right corner. To view all the Verification requests created, go to the **Agent

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

Configuration form. If select No proxy or Auto detect option, go to step 3. If select Manual proxy option, you

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

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

Explorer, go to %localappdata%\akaBot\Logs\ In akaBot Agent, choose Setting button. In Setting screen

: Updating We can find these logs by: Open File Explorer, go to %programdata%\akaBot\Logs\ In akaBot Agent

the FormatMessage function with the FORMAT_MESSAGE_FROM_SYSTEM flag. Error name Code ERROR -1 SUCCESS 0

using the activity [[Log Message>>doc:Activities.[1] Core Activities.Activities.Log Message.WebHome

user can define using activity [[Log Message>>doc:Activities.[1] Core Activities.Activities.Log

and higher (Warn, Error...) can be seen in Output panel. To change how details the logs showed: 1. Open

page listing all existed tasks as below: No Column Description 1 Actions/View Depending

 of each task. No Column Description 1 Action Available actions to manage the Log of said Task. Included

, State of Tasks No Column /Label Description Type Maximum Input Requirement 1 Search box Search

[1] Task

[1] Task

]] |=No|=Column|=Description |1|Actions/View|Depending on the status of the task, the system will allow you

task. [[image:image-20230704144337-1.png]] |=No|=Column|=Description |1|Action|Available actions

-20221028104328-27.png]] |=No|=Column /Label|=Description|=Type|=Maximum|=Input Requirement |1|Search box|Search

. No Column Description 1 Action Options off all actions that can be performed on the schedule. This includes

Grouping of Agent for deployment purposes. Workflow The workflow that is going to be scheduled to execute

Requirement 1 Search box Enter any keyword related to the schedule you want to search String No limit 5

have created previously. [[image:image-20221028105802-35.png]] |=No|=Column|=Description |1

of Agent for deployment purposes. | |Workflow|The workflow that is going to be scheduled to execute

|=Description|=Type|=Maximum|=Input Requirement |1|Search box|Enter any keyword related to the schedule you

Triggers provide a uniform mechanism for subscribing to events from the Connector platforms. It gives you the flexibility to automatically start automations or workflows in Orchestrator. 1

the necessary information on job execution is displayed. 8. Deleting a trigger Go to the Triggers tab

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

: Appendix Server endpoint: https://idp.akabot.com/ or http://idp.akabot.io Get API Key: Step 1: Go

will follow the API Details below API Details 1. Import Document Purposes: Documents can be imported

/]] or [[http:~~/~~/idp.akabot.io>>url:http://idp.akabot.io/]] 1. **Get API Key:** Step 1: Go to {serverEndpoint

?** == [[image:attach:IDP Sequence (1)-Page-1.drawio.png||cursorshover="true"]] === **a. Import Document** === The user

.  [[image:image-20230221102727-1.png||cursorshover="true" height="226" width="1097"]] Then user can upload

Depending on the way it was shared, the idea undergoes trough different review phases 1. Review an Idea a. An Idea Approver reviews the idea After an idea has been shared with akaBot Hub, an Idea

the detail idea, go to Edit then scroll down to the bottom of idea to assign Process Owner b. The Process

it was shared, the idea undergoes trough different review phases == **1. Review an Idea** == **a. An Idea

status and can be accessed in **Workspace** -> **Automation Pipeline** [[image:image-20230223092408-1

, go to Edit then scroll down to the bottom of idea to assign Process Owner ))) **b. The Process

of string arguments that represent the attachments you want to send alongside the email. Forward Mail Message (MailMessage) - This message to be forwarded. This field only supports MailMessage objects. Input

. [[image:image-20220505162242-1.png]] (* is mandatory) == **Properties** == **Attachments

the attachments you want to send alongside the email. **Forward** * **Mail Message (MailMessage) **- This message to be forwarded. This field only supports MailMessage objects. **Input** * **Account (String