Mobilize your enterprise data using SAP Cloud Platform – Mobile Cards (Part 4)
This blog is part of a series which is related to the usage and configuration of Mobile Cards.
| Mobilize your enterprise data using SAP Cloud Platform – Mobile Cards |
|
Part 1 – Introduction and Usage of Automatic Instance Generation card template Part 2 – Using Server Managed cards and Default card templates Part 3 – Using Automatic Web Page Matching card template |
In this part of the blog, I am going to focus on SuccessFactors template cards. The templates are based on Server Managed cards discussed earlier.
SuccessFactors Template Cards
In this section, I am going to show how we can quickly leverage some of the SuccessFactors templates and create cards for employees to view their paycheck.
For this you would need access to a SuccessFactors tenant. I am using a demo tenant for this blog.
As an admin, I can view the payslip of Charles Braun in the SuccessFactors system.
Once you have managed to get access to SuccessFactors and checked the setup, its time to configure mobile cards. Navigate to the Template manager and create a new card based on “SuccessFactors My Paycheck” template.
This will create a card configuration with predefined values including the OData Endpoint. In the below config, I have changed the destination to point to my SuccessFactors tenant and also tweaked the URL to obtain the paycheck of a test user.
You can take the URL and test it against a demo SuccessFactors tenant
Copy the JSON output and paste is in the Sample Data tab. You don’t need to change anything in the editor/data mapping tabs if you wish to use the card templates without modification.
Save your card configurations. Open the “Mobile Cards” app and subscribe to the “PayCheck” card which has just been created. This will download a mobile card which displays the payslip of the user.
Importing Cards
I have exported all my cards and placed them in GitHub. You can download them and import it into your trial account. When creating a new card, select “Template Source” as Zip file and use the browse button to import the card. Ensure that the destination is set properly with your destination.
Thanks to Mark Wright for showing me this cool feature. This makes it easy to share cards between accounts. I believe this is how we transport cards too from DEV to PRD subaccounts.
Creating Custom Mobile Card Kit Client
As of 1806, Mobile service had a new feature to create a custom Mobile Card Kit client. This means you can create your own app which can be personalized with your App name/Launch icon etc.
In order to create your own Mobile Card kit client, navigate to the Cloud Build feature. If this feature is not visible, you can add it.
In the Configuration section, provide details of the App Name, Bundle ID, version, Launch icon and save the configuration.
If you are trying to create iOS app, you would need to be aware that Apple recommends (or requires) that the App Group and the Bundle ID match, with “group.” added to the beginning of the Bundle ID to form the App Group. This needs to be maintained when generating a signing profile. In my case, I have maintained the App ID as “com.sap.mobilecards” and Group ID as “group.com.sap.mobilecards” and generated a signing profile.
Note that the Bundle ID provided in the below screen must match the App ID “com.sap.mobilecards”.
In the Build History tab, click on the “Build” button. This will prompt you to select the signing profiles which have been configured in your account (under settings). Once the build process is complete, it will provide you options to install ipa/ipk file on your device.
The process is pretty much the same as creating a custom Fiori Client. I have posted a video on how to build a custom Fiori Client and it uses the same Cloud Build service.
Troubleshooting Tips
If you are not sure what’s happening with a card which is missing, the best place to start is to examine the logs. You can view the logs under Analytics > Log. If you want to increase the log level, you can find the option under settings
If you see a message “HTTP status from the backend is 401”, it could be that your user credentials are incorrect or that you haven’t provided sap-client parameter for the SAP system in the Query URLs.
Finally, when working with Fiori Launchpad and Automatic Web Page Matching card templates, ensure that the Mobile destination named FLP is added for your Fiori Launchpad.
Thanks for going through this blog series and I hope this has given you lot of ideas as to what you could do at your workplace to mobilize some of the processes. If you get stuck while implementing the cards, please do raise a question in the relevant forum and tag me.