Skip to Content
Technical Articles
Author's profile photo Sami Lechner

mobilizing the intelligent enterprise with SAP Mobile Cards

SAP Mobile Cards available for Android and iOS enables me to access important information on the mobile device in a very convenient way. Through its native integration users have fast access to the enterprise information. And through the Action concept it allows building workflow applications for the mobile device.

Lets look under the hood how easy it is to build a card. A mobile card consist of two things a template and a pointer to the data. The data pointer consist a destination and a query. Once the card is deployed the Mobile Cards application than fetches the data in the user context so all existing enterprise authentication and authorisations rules are fully respected.

The response of the query can be OData or pure json.

The WYSIWYG data mapper you can map the json properties to fields in the template. There are several templates available and you can use HTML and JavaScript to customize those templates to fit to your enterpise.

To enable workflows an Actions can be added to a card. These Actions trigger a rest call to manipulate the business data. An action consists of a name, URL and Method type.

Once saved the mobile cards is available inside Mobile Cards Application for the users. This enables the Enterprise developer to build micro mobile apps in less a than day without compromising on the enterprise compliance.

for more information check out:

https://developers.sap.com/topics/mobile-cards.html

to stay tuned follow me Sami Lechner or at twitter

more details and help @ SAP Mobile

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Jeremiah Trahern
      Jeremiah Trahern

      Thanks for the very informative article!

      Is there a way to hide the other actions ("Share" and "Show Related Cards") when they are unrelated to the card I'm developing? If not, how would they function for a card which should only be seen by a particular user? Is there a security risk to allowing the user to send a link to the card to other users?