Pearson UiPath-ADAv1 New Attempt

The Visible property of the Excel Application Scope activity determines whether the Excel file is opened in the foreground or in the background. If the Visible property is set to True (default value), the Excel file is opened and displayed on the screen. If the Visible property is set to False, the Excel file is opened and processed in the background, without showing the user interface. This can improve the performance and speed of the automation, as well as avoid any interference with the user’s work. Therefore, to create a process that runs in the background and uses Excel activities, the Visible property of the Excel Application Scope activity must be configured to False. References: Excel Application Scope from UiPath documentation.

The Add Log Fields activity allows the developer to add custom information to the logs related to transactions for tracing purposes. The activity adds key-value pairs to the execution context, which are then included in all subsequent logs1. The custom information can be used for filtering, searching, or reporting purposes2.

Variables can be created from different areas or panels in the UiPath Studio interface, such as the body of an activity, the properties panel, the expression editor, or the variables panel. However, the activities panel is the only one among the given options that is a valid area for creating variables. The activities panel contains a list of activities that can be dragged and dropped to the designer panel to build workflows. By right-clicking a field in an activity and selecting Create Variable from the context menu, or pressing Ctrl+K, a variable can be created and assigned to that field. The variable’s type and scope are automatically determined based on the activity and the container it is part of.

References:

• Create Variables Tutorial in Studio | UiPath
• Studio - Managing Variables - UiPath Documentation Portal
• Managing Variables - UiPath Studio

The developer should store the relevant data in Orchestrator as follows:

• Upload individual invoice data as Specific Data in Queue Items. The Specific Data is a collection of key-value pairs that can store additional information for each queue item, such as the invoice number, date, amount, etc. The Specific Data can be added to the queue items using the Add Queue Item activity in the Dispatcher workflow. The Specific Data can be retrieved from the queue items using the Get Transaction Item activity in the Performer workflow. The Specific Data can be used to process each invoice separately in the finance system as a single unit of work3.
• Create an asset for the finance team’s email address. An asset is a global variable that can store a specific value, such as a text, a number, a boolean, or a credential. An asset can be created and managed in Orchestrator, and accessed by the robots using the Get Asset activity. An asset can be used to store a value that is common for all the queue items, such as the finance team’s email address. The asset can be used to email the unique output ID to the finance team after each invoice is processed in the finance system4.

References: About Queues and Transactions and About Assets from UiPath documentation.