Finally it is time for another SCN blog 😉
After my last blogs about SAP Mobile Documents (SAP Mobile Documents in Action & SAP Mobile Documents Strengthens the Position of SAP NW Knowledge Management) and the SAP NetWeaver Portal (SAP NW Portal Star: Vote for btexx/sotric) quite a lot has happened at SAP and btexx, so I am happy to share some insights/experiences about the main topics that we were working on in the last months…
Mainly I will focus on explaining you potential use cases of a SAPUI5 based Mobile Portal and how it can interoperate with the latest version of SAP Mobile Documents.
SAPUI5 based Mobile Portal
The SAP NetWeaver Portal provides a great infrastructure to build a mobile version of your existing Corporate Portal. Based on that infrastructure and the new SAPUI5 User Interface technology we built a mobile version for our Intranet Template Portal.
Based on a Market Assessment we focused on the following Mobile Portal Use Cases
- Mobile Portal Content
- News, User-Profiles, etc.
- Mobile Portal Applications
- Search and Workflow-Management (Mobile UWL)
- Mobile Self Service Applications
- Mobile HCM (Leave and Time Management) via SAP Gateway Services
- Mobile Document Consumption and Exploration
- Usage and deep Integration of SAP Mobile Documents
- Integration possibilities of (SAP) Native and (SAP) Web Apps
- Integration/Consumption of SAPUI5 apps provided by SAP, e.g. FIORI Apps
The following screens give you a visual impression of our SAPUI5 based Mobile Portal, more screenshots can be found on our website.
Cross Device Support of SAPUI5 for Mobile
SAPUI5 based UWL (Universal Worklist) for Approvals like Leave Requests, etc.
Deep Integration with SAP Mobile Documents
To provide our customers a good user experience and to eliminate system barriers between our web based Mobile Portal and the native SAP Mobile Documents Client we contacted the SAP Mobile Documents team and got pretty soon in a constructive working mode to exchange ideas how one could overcome the typical interoperability challenges between different mobile apps.
In the following 2 parts you will find further information about our functional use case and the implemented solution.
Video / Use Case of the SAP Mobile Documents Portal Integration
- Michael Miller of the fictional energy company sotric is on the road and wants to find information about the annual financial figures of the power plant in Bergen
- Furthermore Michael wants to synchronize the project management document folders, so that he can work with this documents although he has no connectivity on the airplane
- To solve this task Michael is using his Mobile Portal with SAP Mobile Documents Integration
Have fun with the short video which is covering the described use case!
Technical Use Cases
- SAP Mobile Documents Integration into the Mobile Search
- Launching of SAP Mobile Documents with different Input parameters
Before I go into the technical details I would like to thank the SAP Product and Development Team of SAP Mobile Documents for the close cooperation in discussing the required interfaces with us to achieve the shown use case! Thanks for the great Co-Innovation!
The magic word for the parameterized launch of native Apps is URL Schemes. With URL Schemes the developer of a native mobile app can specify how and with which parameters his app can be launched. On the website handleOpenURL: Shared Interapp Communication on iOS you find a good overview of available URL schemes for existing apps.
SAP Mobile Documents URL Scheme Syntax
Following you will find a sneak preview of the hidden and yet unofficial URL Scheme syntax of SAP Mobile Documents Version 1.0 SP2
- Syntax: mobiledocs://[version]/[action]?obj=[Object-ID-Ressource]&rep=[Object-ID-Repository]
- [version] = Denotes the scheme version for SAP Mobile Documents, current version is = v1
- [action] = Action is an action the client performs on the provided parameters
- select = navigates in the specified folder and selecting the specified document
- open = opens the specified document, showing the content
- [Object-ID-Resource] = The CMIS Object ID of a file or folder. For KM resources this is the GUID
- [Object-ID-Repository] = The Mobile Documents Repository ID
Have fun exploring the possibilities of the URL scheme syntax! Currently SAP is planning to support and document the URL scheme syntax with the next support package, which will be SP3.
I hope you found the provided information valuable! I am looking forward to your feedback or questions…
Based on the connection between user perspective, SAP technology and process know-how, btexx implements user-friendly solutions that make companies more efficient and users happy.
SAP Mobile Documents Use Cases
Find more Business use cases adressed by SAP Mobile Documents here: http://scn.sap.com/docs/DOC-56573