Explanation
Both list and arrays are a collection type of variables that can store multiple values of the same data type. The main difference between them is if their size is fixed or not. Array has a fixed size, meaning that if you create an array containing 3 elements, you can't add more than 3 or reduce its size. List has a dynamic size, meaning that you can add or remove elements as you need. List also provides some methods that can be invoked to perform operations on the elements, such as sorting, reversing, finding, etc. Array does not have such methods, but it is more optimized for arithmetic computations.
References:
Differences between a list and an array - UiPath Community Forum
Array manipulation with UiPath (List, Dictionary, Array) - F-PenIT blog List Collection ArrayList - Activities - UiPath Community Forum

Explanation
DataRow
The REFramework is a template that provides a robust and scalable structure for building automation projects. It uses the concept of TransactionData and TransactionItem to handle the input data and process it in a loop1. The TransactionData is a collection of items that need to be processed, and the TransactionItem is a single item from that collection that is assigned to the robot in each iteration2.
The type of the TransactionItem variable depends on the type of the TransactionData variable. By default, the REFramework uses QueueItem as the type for both variables, assuming that the input data comes from an Orchestrator queue3. However, if the input data comes from a different source, such as an Excel file, a web page, or a SAP application, then the type of both variables needs to be changed accordingly4.
In your case, since the input data is a DataTable that contains vendor names and addresses, the appropriate type for the TransactionItem variable is DataRow. A DataRow represents a single row in a DataTable, and it can store multiple values in its columns. By using DataRow as the type for the TransactionItem variable, you can access and manipulate the vendor information in each iteration of the process.
References:
REFramework Documentation - UiPath Documentation Portal.
ReFramework - TransactionItem type - Help - UiPath Community Forum.
ReFramework for Tabular Data - RPA Component - UiPath Marketplace.
Transaction Item variable type - Studio - UiPath Community Forum.
[DataRow Class (System.Data) | Microsoft Docs].

Explanation
DataRow
The REFramework is a template that provides a robust and scalable structure for building automation projects. It uses the concept of TransactionData and TransactionItem to handle the input data and process it in a loop1. The TransactionData is a collection of items that need to be processed, and the TransactionItem is a single item from that collection that is assigned to the robot in each iteration2.
The type of the TransactionItem variable depends on the type of the TransactionData variable. By default, the REFramework uses QueueItem as the type for both variables, assuming that the input data comes from an Orchestrator queue3. However, if the input data comes from a different source, such as an Excel file, a web page, or a SAP application, then the type of both variables needs to be changed accordingly4.
In your case, since the input data is a DataTable that contains vendor names and addresses, the appropriate type for the TransactionItem variable is DataRow. A DataRow represents a single row in a DataTable, and it can store multiple values in its columns. By using DataRow as the type for the TransactionItem variable, you can access and manipulate the vendor information in each iteration of the process.
References:
REFramework Documentation - UiPath Documentation Portal.
ReFramework - TransactionItem type - Help - UiPath Community Forum.
ReFramework for Tabular Data - RPA Component - UiPath Marketplace.
Transaction Item variable type - Studio - UiPath Community Forum.
[DataRow Class (System.Data) | Microsoft Docs].

Explanation
The Queue Items should be processed by a single robot executing a Performer workflow in the following order:
EmployeeID1
EmployeeID4
EmployeeID8
EmployeeID3
EmployeeID6
EmployeeID9
EmployeeID5
EmployeeID2
EmployeeID7
A queue is a container that holds an unlimited number of items that can be processed by a robot1. A queue item can have a deadline and a priority, which affect the order in which the robot retrieves the items from the queue2. The Performer workflow is a part of the REFramework template that processes the queue items using the Get Transaction Item activity3. The order of queue execution is determined by the following rules4:
Items that have a deadline are processed first, in order of priority and according to the set deadline for items with the same priority.
Items that have no deadline are processed next, in order of priority and according to the rule First In, First Out for items with the same priority.
Based on these rules and the exhibit, the order of queue execution is as follows:
EmployeeID1 has the earliest deadline (2050-01-01) and high priority, so it is processed first.
EmployeeID4 has the same deadline as EmployeeID1, but normal priority, so it is processed second.
EmployeeID8 has the same deadline and priority as EmployeeID4, but it was added later to the queue, so it is processed third.
EmployeeID3 has the next earliest deadline (2050-01-02) and high priority, so it is processed fourth.
EmployeeID6 has the same deadline as EmployeeID3, but normal priority, so it is processed fifth.
EmployeeID9 has the same deadline and priority as EmployeeID6, but it was added later to the queue, so it is processed sixth.
EmployeeID5 has no deadline, but high priority, so it is processed seventh.
EmployeeID2 has no deadline and normal priority, so it is processed eighth.
EmployeeID7 has no deadline and low priority, so it is processed ninth.
References:
About Queues and Transactions documentation from UiPath
Processing Order documentation from UiPath
Performer documentation from UiPath
Order processing queue forum post from UiPath Community

Explanation
The Step Out action is used for stepping out and pausing the execution at the level of the current container.
Step Out completes the execution of activities in the current container, before pausing the debugging. This option works well with nested sequences1. In the exhibit, the Step Out action will execute all the activities inside the Sequence container and then pause at the next activity in the Main workflow. References: Debugging Actions from UiPath documentation.