My UiPath 1 Flashcards
(24 cards)
A developer decided to create a process using a STATE MACHINE.
What is the correct EXECUTION SEQUENCE of the parts in the State activity?
- Entry
- Exit
- Trigger Action
- Destination state
State machines
1. State - Entry
2. State - Transition: Trigger Action
3. State - Transition: Condition Eval
4. State - Exit
5. Destination (Entry)
Note:
Transition Condition Eval is logged after State Exit
but it’s evaluated before it
Queue items processing order
Queue
-
YES deadline:
1.1. Priority
1.2. Deadline
1.3. FIFO -
NO Deadline:
1.1. Priority
1.2. FIFO
.
(docs)
Within any given queue the transactions are processed in a hierarchical manner, according to this order:
- Items that have a Deadline, as follows:
1.1. in order of Priority;
1.2. set Deadline if same Priority. - Items with no Deadline, in order of Priority, and
2.1. First In, First Out if same Priority.
Logging levels
- Off
- Critical
- Error
- Warning
- Information
- Trace
- Verbose
Verbose: All Trace level + Workflow Tracking logs
REFramework
MaxRetryNumber
vs
Max # of retries on the queue
MaxRetryNumber
* Must be 0 if working with Orchestrator queues.
Retry count in the queue
* Only gets used if the config retry count is set to 0
* Otherwise, it uses the config setting
Queues
The Queue Item status is updated in
-
GetTransactionData.xaml
Get Transaction Item activity which retrieves the Transaction Item from the queue and sets its status to In Progress -
SetTransactionStatus.xaml
Set Transaction Status activity is used to set the status of the Transaction to either Successful or Failed
ClassicUI
Key Classic UI Activities’ properties
-
ContinueOnError | (bool) Default: false
Specifies if the automation should continue even when the activity throws an error.
If the value is set to True, the execution of the project continues regardless of any error.
Note: activity in Try Catch and ContinueOnError = True: no error is caught when the project is executed. -
DelayAfter | (int) Default: 300 milliseconds
Delay time (in milliseconds) after executing the activity. -
DelayBefore | (int) Default: 200 milliseconds
Delay time (in milliseconds) before the activity begins performing any operations.
ClassicUI Sync Activities
RetryScope usage and properties
Retries the contained activities as long as the condition is not met or an error is thrown.
-
NumberOfRetries | (int) DEFAULT = 3
The number of times that the sequence is to be retried. -
RetryInterval | (int) DEFAULT = 5000 ms
Specifies the amount of time (in seconds) between each retry.
Two levels:
-
Action blocks
Place the activity to be retried. -
Condition blocks.
Place an activity that returns a Boolean value to determine if it should be retried
(EX: Element Exists , Image Exists , Text Exists, Check True, Check False)
Note:
If this activity is included in Try Catch and ContinueOnError =True, no error is caught when the project is executed.
Selectors
Full Selectors
vs
Partial Selectors
Full selectors:
- Contain all the elements needed to identify a UI element, including the top-level window
- Generated by the Basic recorder
- Recommended when switching between multiple windows
Partial selectors:
- Generated by the Desktop recorder
- NO INFO about the top-level window
- Activities containing partial selectors are enclosed in a container that contains a full selector of the top-level window:
Attach Browser, Attach Window, (Get Active Window?) - Recommended when performing multiple actions in the same window
Extract data/text from PDF
- Extract all text data from PDF files
* Read PDF Text (PDF)
Reads all characters from a specified PDF file and stores them in a string variable.
* Get Full Text (Ui Auto | Scraping)
Extracts a string and its information from an indicated UI element using the FullText screen scraping method.
* Read PDF With OCR (PDF)
Reads all characters from a specified PDF file and stores it in a string variable by using OCR technology. -
Partial text data extraction from PDF files
* Get Text (Ui Auto)
Extracts a text value from a specified UI element.* **Get Visible Text** *(Ui Auto | Scraping)* Extracts a string and its information from an indicated UI element using the Native screen scraping method. * **Anchor Base** *(Ui Auto)* A container that searches for a UI element by using other UI elements as anchors. * **CV Get Text** *(Computer Vision)* Extracts the text from a specified UI element.
UIAuto
Input Capability Methods
Compatibility
- 100% | Hardware Events
- 80% | SendWindowMessages
- 99% WA / 60% DA | Simulate Type/Click
- 100% | ChromiumAPI (only Chrome/Edge)
WA = Web app, DA = Desktop app
UIAuto
Input Capability Methods
Speed
- 50% | Hardware Events
- 50% | SendWindowMessages
- 100% | Simulate Type/Click
- 50% | ChromiumAPI
Recommended: Simulate Type/Click (fastest and bg work)
Input Capability Methods
HotKey Support
- YES | Hardware Events
- YES | SendWindowMessages
- NO | Simulate Type/Click
- YES | ChromiumAPI
Input Capability Methods
Background Execution
- NO | Hardware Events
- YES | SendWindowMessages
- YES | Simulate Type/Click
- YES | ChromiumAPI
Input Capability Methods
Auto Empty Field
- NO | Hardware Events
- NO | SendWindowMessages
- YES | Simulate Type/Click
- YES | ChromiumAPI
Input Capability Methods
Design Experience
- CLA / MOD | Hardware Events
- CLA / MOD | SendWindowMessages
- CLA / MOD | Simulate Type/Click
- CLA | ChromiumAPI
CLA = Classic, MOD = Modern
Attended Features
Background Process Template
- For ATTENDED PROCESSES that can run in parallel on the same Robot, together with one foreground process*
- MUST NOT contain activities that require user interaction (e.g. Click or Type Into)
-
A process may be turned into a Background Process if no activities with UI interaction.
[Project Settings > Starts in Background = Yes]
(and vice versa) - Background Process runs in Session 0 when started from Orchestrator on an Unattended Robot.
Attended Features
Run Parallel Process
- Only ATTENDED PROCESSES on local machine (run local packages, ORCH procs if connection avail)
- Asynchronous mode: parent proc only responsible starting children procs. After that, they run independently from each other.
- Logs for parent and children are written individually in the local log files and Orchestrator. They both contain complete information about each execution.
- A separate job is created for each process, as opposed to the Invoke Process activity (creates only one job).
- If a child process is invoked but not found, an error is logged (name of the child, the path where Robot searched, details as WindowsIdentity and machineName). Exception is thrown and additional details are being logged.
- If error occurs in the child process after it has been invoked, the parent is not aware of it and continues its normal execution.
Activty params: see link below
Attended Features
Studio Triggers
Trigger Based
Attended Automation
- Template based on a Sequence to monitor certain triggers such as a mouse or keyboard event and deploy an automation.
- This sequence contains a Trigger Scope activity named Monitor Agent Action that contains triggers for clicks, keystrokes, and hotkeys, a Get Source Element activity to retrieve UiElement objects and a container for adding event handling logic.
- The template allows you to configure triggers and add other trigger activities based on the project needs.
- These triggers are monitored simultaneously and the Event Handler is executed once for any occurring event.
- The Use Foreground activity allows running a specified set of activities in the foreground.
Attended
Attended Features
User Event Activities
- Click Trigger
- Key Press Trigger
- Click Image Trigger
- System Trigger
- Hotkey Trigger
- Mouse Trigger
- Get Event Info
- Monitor Events
- Get Source Element
- Replay User Event
- Block User Input
- Use Foreground
- Element Attribute Change Trigger
- Element State Change Trigger
Attended Features
Trigger Scope
- Composed of the Triggers and Actions containers. This allows to define a set of triggers in the first, followed by a sequence of activities to execute based on trigger response.
- Only supports User Events activities
- You can define TriggerArgs to be used in the next activity sequence
- in order to interrupt, the Break activity should be used. This allows the workflow to continue execution
Options: SchedulingMode
- Sequential: Actions are executed one after another.
- Concurrent: Action executions can overlap.
- OneTime: Execute one action and exit.
Notes:
- Trigger received while a process is paused: it fires after the process resumes.
- Included in Try Catch and ContinueOnError =True, no error is caught when the project is executed.
Attended Features
Picture in Picture (PiP)
- Run attended processes in collaboration with the Robot. A process started in the Picture-in-Picture mode runs in an isolated Windows session, thus allowing you to use the machine while the process is running.
- Start a process in Picture-in-Picture mode either from the Debug tab in Studio, from StudioX, or directly from the UiPath Assistant from the Contextual Menu docs image of a process.
- Admin rights are needed to enable Picture-in-Picture on the machine. (Only the first time Picture-in-Picture is used)
-
Can be disabled by command line (machine level, for all users)
UiRobot.exe PiP --Disable -
Using PiP for Invoke activities
[Invoke Process, Invoke Workflow and Run Parallel Process] have the option to choose where to start the new process.
Misc > Target Session > set Picture in Picture -
Default timeout to start a process in PiP session is 60 seconds.
* If the login in the picture in picture session takes more than that, a timeout error is thrown.
* Can be changed using UIPATH_SESSION_TIMEOUT environment variable on the machine.
* Maximum value UIPATH_SESSION_TIMEOUT = 180 seconds.
* When using the Robot in Service-Mode, make sure to set the UIPATH_SESSION_TIMEOUT variable as a system environment variable and restart the Robot Service.
Known issues: see link below (end of page)
UiAuto Properties
AlterIfDisabled
The property instructs the target activity whether or not to interact with disabled elements.
Is only taken into consideration if the SimulateType or SimulateClick are enabled.
You can find it for the following activities:
- Click
- Type Into
- Type Secure Text
- Check
- Select Item
- Select Multiple Items
- Set Text
UiAuto Properties
CursorMotionType
Specifies the type of motion performed by the mouse cursor.
- Instant - The cursor jumps to the destination. By default, Instant is selected.
-
Smooth - The cursor moves in increments.
Has no effect if SendWindowMessages or SimulateClick are enabled.
UiAuto Properties
WaitForReady
Wait for the target to become ready, before performing the activity.
- None – does not wait for the target to be ready.
- Interactive – waits until only a part of the app is loaded.
- Complete – waits for the entire app to be loaded.
