ANSWERS RATED A+
✔✔Tracepoint - ✔✔Breakpoints with set logged messages. When the tracepoint is
reached during debugging, the message is logged at trace level. Conditional tracepoints
have a set condition or hit count, and a logged message. The message is logged when
the condition is met the number of times stated in the hit count field
✔✔Call Stack Panel - ✔✔Debugging panel that displays the next activity to be executed
and its parent containers when the project is paused in debugging.
The panel is displayed during execution in debug mode and it gets populated after using
Step Into, Break, Slow Step, or after the execution was paused because an error or a
breakpoint was encountered.
✔✔Locals Panel - ✔✔Debugging panel displays properties or activities and user-
defined variables and arguments. The panel is only visible while debugging. Right-click
an argument, variable or property of the currently executing activity to add it to the
Watch panel and monitor its execution throughout the debugging process.
✔✔Watch panel - ✔✔Debugging panel that is only visible during debugging. It can be
set to display the values of variables or arguments, and values of user-defined
expressions that are in scope. These values are updated after each activity execution
while debugging.
Variables or arguments can be added to the Watch panel in the following ways:
---In the Watch panel, click the Add Watch field and type the name of the variable or
argument;
---In the Locals panel, right-click a variable or argument and select Add to Watch;
---In the Variables or Arguments panel, right-click a variable or argument and select Add
Watch.
✔✔Immediate panel - ✔✔Panel that is only visible during debugging, and it can be used
for inspecting data available at a certain point during debugging. It can evaluate
variables, arguments, or statements.
✔✔Test bench - ✔✔Debugging option that allows for the creation of automation building
blocks, which can then be tested and added to the final workflow. It is used for testing
activities, working with variables and debugging the process. All this is done in
workflow, a temporary sequence that's not part of the current project and that is
discarded when closed.
✔✔Methods of extracting PDF text - ✔✔-Read PDF Text: (Reads all characters from a
specified PDF file and stores them in a string variable)
-Read PDF with OCR (Reads all characters from a specified PDF file and stores it in a
string variable by using OCR technology)
,✔✔Email best practices - ✔✔-Outlook and Exchange activities are easier to use since
they don't require connection parameters.
-If Outlook is configured, it's usually your best choice since it requires the least amount
of setting up while offering extra features and being compatible with any email protocol
-System.Net.Mail.MailMessage
✔✔Capabilities of Orchestrator - ✔✔-Provisioning (creates and maintains connection
with robots)
-Deployment (ensures the delivery of the workflows for execution, either immediately or
using schedules)
-Configuration (enables the creation, configuration and maintenance of groups of robots
and the execution of tasks)
-Queues (the data that needs to be processed is broken down to indivisible operations
called transactions. Queues can store any number of transactions and they facilitate
their distribution, execution and monitoring)
-Monitoring (keeps track of robot identification data and maintains user permissions)
-Logging (stores and indexes the logs to an SQL database and/or ElasticSearch)
-Inter-connectivity (acts as the centralized point of communication for 3rd party solutions
or applications, and can be used for storing activity packages, libraries and other
assets)
✔✔Benefits of orchestrator - ✔✔-Accessibility and version control
-Transactional processing
-Efficient planning and execution
-Securely storing assets
-Monitoring
✔✔Environment (orchestrator) - ✔✔A group of robots configured in Orchestrator.
Processes can be allocated to individual robots, but it's more effective to allocate them
to environments. A robot can be part of more than one environment, provided they are
in the same service
✔✔Organization unit (orchestrator) - ✔✔An entity in Orchestrator that corresponds to a
business unit. The same Orchestrator instance can have multiple organization units
configured, each of them having separate robots, environments, queues, assets and so
on
✔✔Package (Orchestrator) - ✔✔A project developed in UiPath Studio that is published
to Orchestrator. Multiple versions of the same project can be stored and used. Any
version of it can be downloaded from Orchestrator, in the .nupkg format
, -active: deployed to at least an environment;
-inactive: not deployed (this type can be deleted)
✔✔Process (orchestrator) - ✔✔A package that has been allocated to a certain
environment
✔✔Processes page (orchestrator) - ✔✔Enables you to deploy an uploaded package as
a new process, manage previously created processes, and keep all your processes up
to date with the most recent package versions. This helps you distribute packages
across all users and robots in your organization and execute processes faster from the
Jobs page.
✔✔Steps of deploying a process - ✔✔1) Click add (Deploy window is displayed)
2) Select package
3) Select package version
4) Select environment
5) Click create
✔✔Job (orchestrator) - ✔✔A process that has been sent for execution to some or all of
the robots in the environment. (To start a job, simply navigate to Jobs from the menu on
the left, choose a process and either select the robots you want to execute the job from
the environment, or allocate the job dynamically)
✔✔Execution target options (orchestrator job) - ✔✔-Specific robots: option enables you
to execute a job on a certain robot only
-Allocate dynamically: enables you to execute the same process multiple times on
whatever robot becomes available first. Jobs are placed in a pending state in the
environment workload based on their creation time. As soon as a robot becomes
available, it executes the next job in line.
✔✔Tenant (orchestrator) - ✔✔Enables you to isolate data, with only one instance of
Orchestrator. This feature facilitates automating different departments from your
company and ensures the desired authorization of Orchestrator data per department.
✔✔Schedule (orchestrator) - ✔✔A process that is configured for an execution that is not
immediate, but according to a schedule. Multiple configurations are possible when it
comes to schedules
✔✔Asset (orchestrator) - ✔✔A piece of data stored in Orchestrator for the use of robots.
Single value can be accessed and used by all robots. Value per robot can only be used
by the indicated robot:
-Text (Strings)
-Bool (true or false values)