Support Article

Pega Mobile enablement through Mash up SDK API

SA-3653

Summary

User posed the following queries:

Does MASH UP SDK have any limitations for SFDC gadgets and IAC Port let Gateway?
What is the suggested approach for the existing application architecture to support for mobile enablement?
User is using IAC gateway. Any Performance issues foreseen while accessing the application in Mobile through SFDC Extender?
Currently user is using Pega 7.1.5. User is willing to upgrade to Pega 7.1.6 and wants to know if any other SDK API's are required

Following are the answers for the mentioned queries:

The Mashup SDK is for a different channel than the SFDC gadgets & IAC Gateway. Mashup SDK is for mobile only. It is actually a package of native code that can be dropped into a developer tool for iOS and Android development (so is Objective C and Java).
It depends on the use case and what the customer is trying to mobilize. But a high level we recommend using the responsive capabilities of the Pega 7 UI to create a UI that works and looks great on mobile devices. Then if the use case requires a mobile app, one can use the hybrid mobile wrapper to create a mobile app. User can either use the Pega7 app from the app store. Or starting in 7.1.6, one can create a custom branded mobile wrapper for the application.
See #1. These are separate technologies for different channels.
Pega 7.1.7 is just released, so one can upgrade to this release to take advantage of the latest Mashup SDK with a responsive UI created in Pega. Pega-Mobile and SFDC extender is not a supported product configuration. Pega answer for SFDC mobile enablement is Pega 7.1.6 as base PRPC 7.1.6 OTB is mobile enabled.

Published February 17, 2016 - Updated October 8, 2020

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.