A linear process in UiPath is a type of process that is executed only once and does not involve any looping or branching logic. It is suitable for simple scenarios where the input data is fixed and the output is predictable. A linear process can be designed using a Sequence or a Flowchart diagram, but it does not use any Flow Decision, Switch, While, Do While, or For Each activity. If the process needs to process additional data, then the automation must be executed again with the new data as input. Reference: Framework for linear process or single transaction, How to modify ReFramework to Linear Process, Workflow Design, Difference between Linear process and Transactional process
Question 2
Which logging level includes the following information by default?
1. Execution Started log entry - generated every time a process is started. 2. Execution Ended log entry - generated every time a process is finalized. 3. Transaction Started log entry - generated every time a transaction item is obtained by the robot from Orchestrator. 4. Transaction Ended log entry - generated every time the robot sets the transaction status to either Success or Failed. 5. Activity Information log entry - generated every time an activity is started, faulted or finished inside a workflow. 6. Arguments and Variables Information log entry - show values of the variables and arguments that are used.
Correct Answer: A
Explanation:
The Verbose logging level includes the following information by default: Execution Started log entry - generated every time a process is started. Execution Ended log entry - generated every time a process is finalized. Transaction Started log entry - generated every time a transaction item is obtained by the robot from Orchestrator. Transaction Ended log entry - generated every time the robot sets the transaction status to either Success or Failed. Activity Information log entry - generated every time an activity is started, faulted or finished inside a workflow. Arguments and Variables Information log entry - show values of the variables and arguments that are used. The Verbose logging level is the most detailed one and it is useful for debugging purposes, as it provides a lot of information about the execution flow and the data used by the robot. However, it also generates a lot of log entries, which can affect the performance and the storage space of the robot and Orchestrator. Reference: [Logging Levels]
Question 3
Where is the TransactionNumber incremented in the REFramework?
Correct Answer: B
Explanation:
The TransactionNumber is incremented only in the SetTransactionStatus.xaml workflow, which is invoked at the end of each transaction. This workflow updates the status of the current transaction item in Orchestrator and increments the TransactionNumber by one. The TransactionNumber is used to keep track of the number of transactions processed by the robot and to get the next transaction item from the queue.
Reference: [SetTransactionStatus.xaml]
Demo Practice Mode
You are viewing only the questions marked as Demo.