Explanation
When creating a new test case in UiPath Orchestrator, you can choose a source for the test data that can be imported through arguments and used when running the test case1. The source can be one of the following options: None, Existing Data, File, Data Service, or Test Data Queue2. The option that restricts dynamic data update once the test case is published is File. This option allows you to upload a file (such as Excel or JSON) that contains the test data2. However, once the file is uploaded, you cannot modify or replace it without republishing the test case3. Therefore, the test data is static and cannot be updated dynamically. The other options allow dynamic data update in different ways. For example, Data Service allows you to use an existing table from Data Service as the test data source and filter it by using a SQL query2. You can update the table in Data Service and the changes will be reflected in the test case without republishing it4.
References: Test Cases documentation, New Test Case window description, Updating the test data sets forum post, Data Service documentation.

Explanation
The Get Text activity is used to extract the text value of a specified UI element. It does not use any of the scraping methods by default, but it can be configured to use the Full Text method in the Properties panel. The Full Text method is able to capture hidden text from an application, as well as the entire visible text and editable text. The Full Text method uses an internal OCR engine that works with most applications and languages.
References:
Get Text activity documentation from UiPath
Screen Scraping Methods documentation from UiPath
Text scrapping forum post from UiPath Community
How to: Scrape the Whole Text, Including Hidden Elements from a Terminal Window article from UiPath Knowledge Base

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.

Explanation
The Excel Application Scope activity interacts with a Microsoft Excel file in the following way: it works with xls and xlsm files and Excel must be installed. The Excel Application Scope activity opens an Excel workbook and provides a scope for Excel activities. When the execution of this activity ends, the specified workbook and the Excel application are closed2. The Excel Application Scope activity can work with xls (Excel 97-2003 Workbook) and xlsm (Excel Macro-Enabled Workbook) file formats3. However, the Excel Application Scope activity requires Microsoft Excel to be installed on the machine where the automation is running, as it uses the Excel interop assembly4. Therefore, the Excel Application Scope activity cannot work with xlsx (Excel Workbook) files or without Excel installed.
References: Excel Application Scope, File formats that are supported in Excel, and Excel Application Scope - UiPath Activities Guide from UiPath documentation and Microsoft support.