When an SAP Fiori app isn't displaying on the SAP Fiori Launchpad despite the user having the correct business role, several aspects need to be checked to troubleshoot the issue effectively:
* Check the restrictions for the role: It's essential to verify if there are any restrictions applied to the role that might prevent the app from being displayed. Restrictions can be based on various factors such as geographic location, department, or specific user attributes.
* Check the business catalogues assigned to the role: Business catalogues in SAP Fiori contain groups of apps related to specific business functions. If the necessary business catalogue is not assigned to the role, the app will not appear on the SAP Fiori Launchpad. Ensuring the correct assignment of catalogues is crucial for app visibility.
* Check the space and page(s) assigned to the role: With the introduction of spaces and pages in the SAP Fiori Launchpad, it's vital to ensure that the relevant space and page that should display the app are correctly assigned to the user's role. Spaces are higher-level groupings, while pages within those spaces contain the actual apps.

A business role is assigned to a business user to provide access to business tasks. A business role can contain one or more business catalogs, which are predefined by SAP and contain the actual authorizations that allow users to access the apps contained in the catalog. Each business catalog bundles authorizations for a specific business area. You can tailor the access according to the needs of the business and for compliance purposes using restrictions. References = Finding the Required Business Roles and Business Catalogs for a Solution Process, Defining Business Roles for Production, Business Roles and Catalogs

When you are recording actions for a custom process step in a test automate, you press the "Read" button on the recording panel in the following situations:
* To capture a value in a text field that should be stored as a variable. This allows you to reuse the value in other steps or test cases, or to compare it with an expected value1.
* To capture text in a message screen that can be used for data binding later. This allows you to extract data from the message screen and use it as an input for another step or test case2.
You do not press the "Read" button to capture an error message or a static label on the screen, as these are not values that need to be stored or used later. Instead, you can use the "Check" button to verify that the error message or the label is displayed as expected3. References = Using the Test Automation Tool for Automated Testing - SAP Learning, How to get started with the Test Automation Tool for SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Test Automation Tool- FAQs Blog Series #1.