While developing a test case using UiPath.Testing.Activities. which testing activity enables to include another activity within its body?
A. Verify Expression With Operator
B. Verify Range
C. Verify Control Attribute
D. Verify Expression
A developer is building a process that types data into input fields using the Hardware Events input method. Which property of the Type Into activity should be modified to reduce the pace at which the input string characters are typed into the fields?
A. Delay before
B. Delay between keys
C. Delay after
D. Alter disabled element
A developer needs to create a repetitive process in the REFramework. Following the best practices, which action(s) should be performed to defend against potential robot crashes such as "out of memory"?
A. Build a script that compares current CPU usage values to a threshold and clears data as needed.
B. After every transaction, clear the transaction data, close the applications, and re-open the applications.
C. Add a "Clear Collection" activity at the beginning of the Process.xaml workflow.
D. All "Invoke Workflow File" activities from the Main.xaml file should be marked with the Isolated option.
What is the default OCR engine used in CV Screen Scope?
A. UiPath Screen OCR
B. Microsoft OCR
C. Tesseract OCR
D. Microsoft Azure Computer Vision OCR
How can UlPath Orchestrator help address potential Issues before they become critical problems?
A. By sending customer feedback to UiPath developers.
B. Through proactive monitoring and alerting of detected issues
C. With immediate technical support for any detected Issue.
D. By automatically updating background processes.
A developer defines new log fields using the Add Log Fields activity. When will the custom log fields stop being added to the robot execution logs?
A. When the first Log Message activity is executed.
B. When a Remove Log Fields activity is used to remove them.
C. When a Log Message activity is executed with Log Level = Warn or higher.
D. When an Exception is caught and handled.
Explanation:
The Add Log Fields activity adds custom log fields to the Robot Execution Logs, which are
included in every Log Message execution throughout the entire workflow1. The custom log
fields can be useful for adding more information and visibility to the logs, especially for
transactional data processes2. However, the custom log fields are not permanent and can
be removed by using the Remove Log Fields activity, which takes the name of the custom
log field as an input1. The Remove Log Fields activity is usually placed at the end of a
transaction, to reset and remove the custom log fields for the next transaction2. Therefore,
the custom log fields will stop being added to the robot execution logs when a Remove Log
Fields activity is used to remove them.
A developer is working on an automation using the REFramework. Each transaction item
represents a piece of client information. For each customer, the automated procedure must
click the "Generate Shipment Details" button. This generates a table of shipment records
for each customer.
What type of exception occurs when the data is not accessible, the created table displays
only the header row, and processing for that client must be halted?
A. BusinessRuleException
B. NullReferenceException
C. ApplicationException
D. SystemException
Explanation:
When the data is not accessible, the created table displays only the header
row, and processing for that client must be halted, a BusinessRuleException occurs. A
BusinessRuleException is a type of exception that indicates a business logic error or a
validation error that cannot be resolved by retrying the transaction. For example, if the input
data is incorrect, incomplete, or outdated, a BusinessRuleException should be thrown. A
BusinessRuleException can be thrown by using the Throw activity with the following
expression:
VB New BusinessRuleException(“Message”) where Message is a string that describes the
error. A BusinessRuleException can be caught by using the Catch activity with the
following expression:
VB ex As BusinessRuleException where ex is a variable that stores the exception object. A
BusinessRuleException can be handled differently from other types of exceptions, such as
SystemException or ApplicationException, depending on the logic of the automation. For
example, in the REFramework, a BusinessRuleException sets the status of the transaction
item to Failed and does not retry the transaction, whereas a SystemException sets the
status of the transaction item to Retry and retries the transaction up to a specified number
of times.
What is a pre-requisite for running InitAllApplications Test Case?
A. Invoke InitAllSettings XAML file in Given.
B. Invoke SetTransactionStatus XAML file in Given.
C. Invoke CloseAllApplications XAML file in Given.
D. Invoke KillAllProcesses XAML file in Given.
Explanation:
A test case is a set of steps and expected results that verify a certain functionality or
behavior of an automation. A test case can be created in UiPath Studio or UiPath Test
Manager, and it can contain both manual and automated steps. A test case can be
executed manually or automatically, depending on the type of steps it contains.
A test case follows the Given-When-Then structure, which is a common format for writing
test scenarios. The Given section describes the preconditions or initial state of the system
before the test is executed. The When section describes the actions or events that trigger
the test. The Then section describes the expected outcomes or postconditions of the test.
The InitAllApplications TestCase is a test case that verifies the initialization of all the
applications that are used in the automation project. It is usually created in UiPath Studio,
using the Test Cases feature. The InitAllApplications TestCase can be linked to the
InitAllApplications.xaml workflow, which is a component of the REFramework template that
opens and logs in to all the applications that are required for the automation.
The pre-requisite for running the InitAllApplications TestCase is to invoke the
InitAllSettings.xaml file in the Given section of the test case. The InitAllSettings.xaml
workflow is another component of the REFramework template that reads the configuration
data from the Config.xlsx file and initializes the settings and assets for the automation
project. By invoking the InitAllSettings.xaml file in the Given section, the test case ensures
that the settings and assets are available and ready before opening and logging in to the
applications.
The other options are not pre-requisites for running the InitAllApplications TestCase. Option
B is incorrect, because the SetTransactionStatus.xaml file is not related to the initialization
of applications, but to the setting of the status of a queue item after processing it. Option C
is incorrect, because the CloseAllApplications.xaml file is not related to the initialization of
applications, but to the closing of all the applications that were opened by the automation.
Option D is incorrect, because the KillAllProcesses.xaml file is not related to the
initialization of applications, but to the killing of all the processes that are associated with
the automation.
What are the components that define a state within a State Machine in UiPath Studio?
A. Input Arguments, Output Arguments, and Variables.
B. Entry, Exit, and Transition Actions with Trigger Conditions.
C. Sequence, Flowchart, and Transactional Business Process.
D. Activities, Connectors, and Annotations.
Explanation:
A state machine is a type of automation that uses a finite number of states in
its execution. It can go into a state when it is triggered by an activity, and it exits that state
when another activity is triggered1. A state machine consists of states, transitions, and
actions1. The components that define a state within a state machine in UiPath Studio are:
• Entry Actions: These are the activities that are executed when the state is entered1. For
example, an entry action can be used to initialize a variable, display a message, or log
some information1.
• Exit Actions: These are the activities that are executed when the state is exited1. For
example, an exit action can be used to clean up some resources, close an application, or
update a status1.
• Transition Actions: These are the activities that are executed when a transition from one
state to another occurs1. For example, a transition action can be used to assign a value,
send an email, or invoke a workflow1.
• Trigger Conditions: These are the conditions that determine when a transition from one
state to another should happen1. For example, a trigger condition can be based on a
variable value, a user input, or a timer1.
In a UiPath State Machine workflow, which section of State activity is used to specify conditional/triggers logic and multiple outgoing transitions in a state machine?
A. Entry
B. Transitions
C. Triggers
D. Exit
Explanation: In a UiPath State Machine workflow, the Transitions section of the State activity is used to specify conditional/triggers logic and multiple outgoing transitions in a state machine. Transitions are expanded when you double-click them, just like the State activity. They contain three sections: Trigger, Condition and Action, that enable you to add a trigger for the next state, or add a condition under which an activity or sequence is to be executed. Transitions are represented by arrows or branches between states. They define the flow of the state machine and the rules for moving from one state to another. You can add multiple transitions from a state, but only one transition can be taken at a time, based on the trigger or condition that is met first.
What is the purpose of The Relative To feature in Computer Vision activities?
A. To compare the size and position of Ul elements in different applications.
B. To synchronize the timing of multiple Computer Vision activities in the same project.
C. To configure the target as being relative to an element, either a single point or an area selection in the application.
D. To create a fixed relationship between Computer Vision actions and Ul element positions.
Explanation: The Relative To feature in Computer Vision activities is used to configure the target as being relative to an element, either a single point or an area selection in the application. This feature enhances the accuracy and reliability of UI automation.
A developer implemented a process using the Robotic Enterprise Framework and an Orchestrator queue. The MaxRetryNumber from the "Config.xlsx" file is set to "1" and the Max # of retries from the Queue settings from Orchestrator is set to "2". At runtime, the first transaction item throws a Business Exception. How many times will the transaction be retried?
A. The transaction will not be retried.
B. The transaction will be retried only one time.
C. The transaction will be retried 2 times.
D. The transaction will be retried multiple times, until it will be processed successfully.
Explanation: The transaction will be retried only one time because the MaxRetryNumber from the “Config.xlsx” file is set to “1”. This parameter determines how many times a transaction item is retried when it fails with an application or a business exception. The Max # of retries from the Queue settings from Orchestrator is set to “2”, but this parameter only applies to the queue items that are marked as “Retry” by the robot. In the Robotic Enterprise Framework, the SetTransactionStatus workflow marks the queue items as “Retry” only if the MaxRetryNumber is not reached. Therefore, the first transaction item will be retried once by the robot and then marked as “Failed” in the queue, regardless of the Orchestrator setting.
| Page 3 out of 16 Pages |
| Previous |