Building a mobile solution to enable employee to get reports on their mobile device is often the first step into the mobile journey.
An example use case here could be that a sales manager (George) needs to see the top five sales orders in the system sorted by date. George wants to have a detailed set of information for each sales order.
With SAP Mobile Cards you can build such a solution in hours.
Design Phase:
Following the top down design approach, the next step is to clarify what data George wants to see on his device. The according OData query needs to be built to return the desired result. A designer needs to clarify with George how the data should be rendered on the mobile device to allow him to work efficient with it. The result should a layout describing which data should be rendered where on the screen.
Implementation:
Now the designer or a developer implement the chosen design in the Card Editor inside SAP Cloud platform mobile services. This implementation is done describing the layout with HTML. The styling happens via css. In order to allow the card to render the actual data dynamically handelbars are used to describe the place where data should be mapped in.
Once the design of the card is completed the developer can map the actual json objects in the data mapper inside the SAP Cloud Platform mobile Services. These json objects are from the response of the OData Query to feed the card.
The Card type “Automatic instance Card” is selected to render each sales rrder on a separate Card. So, for each sales order in the result set returned by the OData query a card will be rendered.
Operation:
To get this solution out the IT Admin (Dave) sends an email with 2 QR codes to George. The first QR code will link to the App store when scanned with the mobile device. Here George can download the SAP Mobile Cards application. The second QR code will feed all needed configuration into the SAP mobile Cards application. Now George only needs to enter his credentials and the micro app is up and running.
As a result, George will see the five latest sales orders. The Cards are offline on the device, so George can access the data any time anywhere. The data is based on a Query and it can and will update. So, George will always see the most actual data of the sales orders in his SAP Mobile Cards Application. If a new sales orders found by the query, it will automatically be added, and the oldest sales orders will disappear on the device. George will always have the latest set of five sales orders on his mobile device.
Interested in building this solution yourself in less than an hour on your SAP Cloud Platform trial account?
More information on SAP Mobile Cards can be found at:
to stay tuned follow me sami.lechner or at twitter
more details and help @ SAP Mobile
An example use case here could be that a sales manager (George) needs to see the top five sales orders in the system sorted by date. George wants to have a detailed set of information for each sales order.
With SAP Mobile Cards you can build such a solution in hours.
Design Phase:
Following the top down design approach, the next step is to clarify what data George wants to see on his device. The according OData query needs to be built to return the desired result. A designer needs to clarify with George how the data should be rendered on the mobile device to allow him to work efficient with it. The result should a layout describing which data should be rendered where on the screen.
Implementation:
Now the designer or a developer implement the chosen design in the Card Editor inside SAP Cloud platform mobile services. This implementation is done describing the layout with HTML. The styling happens via css. In order to allow the card to render the actual data dynamically handelbars are used to describe the place where data should be mapped in.
Once the design of the card is completed the developer can map the actual json objects in the data mapper inside the SAP Cloud Platform mobile Services. These json objects are from the response of the OData Query to feed the card.
The Card type “Automatic instance Card” is selected to render each sales rrder on a separate Card. So, for each sales order in the result set returned by the OData query a card will be rendered.
Operation:
To get this solution out the IT Admin (Dave) sends an email with 2 QR codes to George. The first QR code will link to the App store when scanned with the mobile device. Here George can download the SAP Mobile Cards application. The second QR code will feed all needed configuration into the SAP mobile Cards application. Now George only needs to enter his credentials and the micro app is up and running.
As a result, George will see the five latest sales orders. The Cards are offline on the device, so George can access the data any time anywhere. The data is based on a Query and it can and will update. So, George will always see the most actual data of the sales orders in his SAP Mobile Cards Application. If a new sales orders found by the query, it will automatically be added, and the oldest sales orders will disappear on the device. George will always have the latest set of five sales orders on his mobile device.
Interested in building this solution yourself in less than an hour on your SAP Cloud Platform trial account?
More information on SAP Mobile Cards can be found at:
to stay tuned follow me sami.lechner or at twitter
more details and help @ SAP Mobile
- SAP Managed Tags:
3 Comments
