|
Select whether you are working in an On-Premise or Cloud environment in order to get the correct instructions.
Best Practices:
- For better performance, applications should be converted to a standalone application when moved into production. This leverages standard caching techniques and will greatly improve the performance of the application.
- When leveraging the SAP Cloud Platform to host the applications, the OData Provisioning service is recommended to eliminate complexities with working with different servers, URLs and authentication mechanisms.
- The Fiori Launchpad on the Gateway server or the SAP Cloud Platform Portal in the cloud should be used wherever possible to ensure a consistent approach for end users to access all Fiori applications in the enterprise.
- For organizations where a FLP is not configured, an option for the AppBuilder launch pad is available. This will only provide access to applications built in the AppBuilder tool.
- Access to My Requests and My Approvals should be done through a custom Fiori Launchpad Tile that will display the actual count of active requests and approvals.
Internal Notes:
Where a customer has the Fiori launchpad...
Need to document deplyment options
Custom lauchpad where no Fiori launchpad
Quick deploy via URL
Full deployment via Pointing to Components
Steps for deployment
Standalone Apps - should this be a default?
ANdre's Notes----------------
Some notes:
- Instead of updating multiple services/path from the manifest.json file, the path and name from the neo-app.json was updated. Take note that the destination used is the GWaaS.
