Message: The Log Message
Level: Defines the log severity
Timestamp: The exact date and time the action was performed
FileName: The name of the .xaml file being “executed”
JobId: The key of the job running the process
ProcessName: The name of the process that triggered the logging
ProcessVersion: The version number of the process
WindowsIdentity: The name of the user that performed the action that was logged
RobotName: The name of the robot (defined in Orchestrator)

When we want to use a method which does not generate an output (for example, Reverse) and therefore cannot be used in an Assign activity. –> This is for the Invoke Method Activity

False – When using VB.NET code in Invoke Code activity, the assemblies must be added to the Import panel for them to function when executing the code. In Studio, the Name Spaces panel is used to add/delete namespaces.

In the success section of the SetTransactionStatus.xaml workflow, the status is updated as successful.
In the business exception section of the SetTransactionStatus.xaml workflow, the status is updated as failed.
In the system exception section of the SetTransactionStatus.xaml workflow, the status us updated as failed (application type).

Go to the Studio Backstage View > Start > Library. This opens the New Blank Library window.

The Project Panel displays the tree view with the Project folder, Dependencies, and the NewActivity.xaml which contains the actual workflow.

A Library is a package which contains multiple reusable components. Libraries are saved as .nupkg files and can be installed as dependencies to workflows using the Package Manager.

Interactive/Complete – Waits all of the UI elements in the target app to exist before actually executing the action.
To assess if an application is in the Interactive or Complete state, the following tags are verified:
Desktop applications – A wm_null message is sent to check the existence of the , , , or  tags. If they exist, the activity is executed.
Web applications:
a. Internet Explorer – The  tag is used to check if the Ready state of the HTML document is set to Complete. Additionally, the Busy state has to be set to “False”.
b. Others – The  tag is used to check if the Ready state of the HTML document is Complete.
SAP applications – First the presence of the  tag verified, after which a SAP specific API is used to detect if the session is busy or not.
Target – identifies the UI element the activity works with.
Interactive – Waits for the target app to indicate readiness, although some assets may still be loading.

Priority takes precedence over the deadlines, if there is a deadline.
No deadlines always go last, based on priority.
High priority always go first, if they have a deadline, and based on deadline. 

Being generic types, if the string variables come first, then the entire function will be string. If the Int32 variable comes first, then the entire function will be Int32.
Note* –> If the Int32 function comes first out of the 2 parenthesis functions, an error will be thrown. Write Line: Cannot add System.Double to System.String
The string function must come first, then the Int32 function can follow.

Being generic types, if the string variables come first, then the entire function will be string. If the Int32 variable comes first, then the entire function will be Int32.
Note* –> If the Int32 function comes first out of the 2 parenthesis functions, an error will be thrown. Write Line: Cannot add System.Double to System.String
The string function must come first, then the Int32 function can follow.

Step Over

Compare Files may be used for comparing differences between two .xaml files, either processes or libraries, as long as they contain similar workflows.
When comparing changes between two .xaml files, Workflow Diff shows added or removed activities, variables, arguments, or modified activity properties. Default values for properties are not visible in the Show Changes window.

True. Clicking stop will send a signal. If there is no receiver for the signal, then the job will not be stopped.

jobs
queues
tasks
delays

Variables Naming Convention has the ST-NMG-001 ID:
ST – reveals that the rule is built into Studio.
NMG – shows that the rule is part of the Naming Rules category.
Rules part of Project Anatomy Rules category have the ANA abbreviation, those part of Design Best Practices the DBP, and so on.
001 – is the rule number

An Application Exception describes an error rooted in a technical issue, such as an application that is not responding.
Such a situation is, for example, a project which extracts phone numbers from an employee database, creating queue items for each of them. These items are then to be processed and inserted into a financial application. If, when the transaction is attempted, the financial application freezes, the Robot cannot find the field where it should insert the phone number, and eventually throws an error.
These kinds of issues have a chance of being solved simply by retrying the transaction, as the application can unfreeze.
A Business Exception describes an error rooted in the fact that certain data which the automation project depends on is incomplete or missing.
Such a situation is, for example, a project which extracts phone numbers from an employee database, creating queue items for each of them. These items are then to be processed and inserted into a financial application. If a certain phone number is missing a digit due to human error, the queue item containing it becomes invalid. This causes the automation to throw an exception, as the Phone Number field in the financial application does not accept a queue item that contains an incomplete number.
Retrying the transaction does not yield any chance of solving the issue, and there are other better courses of action, such as notifying the human user of this error.

The related queued jobs ARE limited.

Enable and disable rules
Change the default action for each rule
Configure rule parameters
Access the documentation page for each rule

Studio Logs – studio traces are diagnostic log messages generated by studio, containing information related to its behavior
Setup Logs – track events related to installing UiPath Studio. when running the windows installer (UiPathStudio.msi), all errors are logged in the Event Viewer.
Orchestrator – Diagnostic Logs generated by UiPath Orchestrator regarding its behavior.
Robot Logs – Track events related to the robots themselves and their context or the execution of processes.

This activity requires at least two of the three fields to be in use. You cannot run it only with the Try field completed.

An Application Exception describes an error rooted in a technical issue, such as an application that is not responding.
A Business Exception describes an error rooted in the fact that certain data which the automation project depends on is incomplete or missing.

Studio Logs – studio traces are diagnostic log messages generated by studio, containing information related to its behavior
Setup Logs – track events related to installing UiPath Studio. when running the windows installer (UiPathStudio.msi), all errors are logged in the Event Viewer.
Orchestrator – Diagnostic Logs generated by UiPath Orchestrator regarding its behavior.
Robot Logs – Track events related to the robots themselves and their context or the execution of processes.