Understanding Pega Mobile
|
|
Pega Mobile is an add-on product for PRPC 6.2 SP2 and later releases, offering mobile device users the capability to participate, collaborate, and monitor PRPC work from most major mobile devices, including tablets, phones, and iPods.
Access your application on a mobile device using a WebKit-based browser and the same URL and login as the desktop version of an application. You can also access the application using the free Pega Mobile app, available at on-line app stores, which delivers your PRPC application to your mobile device while giving you convenient access to native device features, such as the camera. The app also allows you to save multiple application configurations, including URLs, logins, and passwords.
For applications creating starting with Pega Mobile 4.1.1 and newer versions, you can download the Pega 7 mobile application, which enhances existing Pega-Mobile functionality and increases collaboration with desktop-based applications using Pega 7. This mobile app acts as a "hybrid" of features typical of both web-based and mobile device-based applications, allowing for a more seamless UI transition for users moving between using a desktop app and a mobile app. You can download the Pega 7 app for iOS in the Apple iTunes store, and the Pega 7 app for Android in the Google Play store.
The Pega-Mobile ruleset delivers an extensible portal, based closely on the Case Manager portal, that provides mobile device users with access to the PRPC application. Customizable navigation rules define how users move about the application. Navigation is controlled by main and toolbar navigation rules, and the list of items, actions, labels, and icons is completely configurable. You can even prevent display of navigation rules on phones and tablets.
Use a set of layouts and controls that are supported for use in sections and harnesses that render on mobile devices. Over 100 PRPC controls are mapped to mobile versions of those controls to facilitate the mobile rendering of existing applications.
Most existing harnesses and sections render on mobile devices with no additional work. However, if your application includes features not yet optimized for mobile devices, you may create a specialized version of the section rule that includes features that are optimized for mobile devices.
You can also circumstance your entire UI experience based on the device type. Use Save As to save the portal rule to a new name, and for the circumstance, enter property pxRequestor.pxDeviceType and the value phone or tablet. When you log in using this portal, the application determines the User Agent, and displays the portal, sections, harnesses, and flow actions with a user interface for the specified device type.
To test and debug your mobile application, use a physical mobile device when possible. Additionally, configure Apple's Safari or Google's Chrome with a specific User Agent, such as iPad or iPhone, so that you can run the mobile application on your desktop as it would appear on the tablet or phone device. The Mobile Clipboard is useful for examining property values, rule types, and identifying the Remote Tracer Session ID.
Refer to these PDN articles for more details on getting started using Pega Mobile:
If your application was developed in 6.2SP2 and uses rulesets ending in _mobile, and you want to operate in ABA mode for best performance, note that _mobile rulesets appear higher in the ruleset list in ABA mode than in rules assembly mode. While it is unlikely that this change affects results of your application, some analysis and testing is recommended.
|
Pega Mobile, portal |
|
Navigation rule — Completing the Node Details Action tab
|
|
Atlas - Supported user interface features for mobile applications
|