Preparation for upgrade
Fiori App Usage Report is clearly showing which apps are the most important and which can be removed reducing the scope of upgrade.
List of the use cases¶
Explore what makes customers pick Fiori Tracker.
Learning about unused applications
Making the most of your system by identifying unused applications
Understanding apps value
Gathering information about what, when, and how often users run apps
Priority setting
Understand what should be the best use of SAP support team time
Testing progress
Determining the status of testing process
Apps out of scope
Project scope creep prevention
Building roles
Shape user roles to fit actual needs
SAP Fiori launchpad configuration - handover to support
Transferring SAP Fiori launchpad setup know-how after the implementation
Ensuring alignment with the authorization team needs
The app, catalog, and roles in Fiori Tracker form a clear blueprint, providing the Roles and authorization team with the clarity they need to configure the system.
Universal application identification
Clear identification of the applications in scope.
Scope control
Scope creep and impact on maintenance and support costs.
Fiori Launchpad Content requirements gathering
Single, shared point of truth accessible to all team members, enabling simultaneous edits.
Avoiding the pain of using spreadsheets for SAP Fiori content management
Content duplication, 1 to N mapping, and consistency
Recording test results
Recording test results.
Evaluating upgrade impact
Evaluating upgrade impact.
Adding an application to a user
Additional decisions on updating catalogs.
Clarity of responsibility
Diffused responsibility on the content that is shared.
Enforcing naming conventions
Consistent naming when different team members create and change content identifiers.
SAP Fiori setup transparency
Fiori Tracker as a documentation platform makes SAP Fiori setup specification transparent for all project members.
Comparing blueprint with system setup
Comparing blueprint with system setup.
Transparency of app technology categories
Insight into the app technology category to:
Tracking the history of changes in the app
Tracking the history of changes in the app.
Automation of access grating
Automated authorization provisioning based on the user requests.
Centralized test users lists with passwords
Instead of scrambling with e-mailed lists, you can rely on the Test User app.
Naming conventions
Here are two naming conventions for custom apps that user can consider: