A Pega CRM/CS application requires a mobile version of its Employee Portal which allows employees to create and monitor internal service requests. Access is online only and SSO is used for authentication.
In the third part of the series the various options for testing the mobile app are discussed, as well as the release management approach taken.
As mention in Part 1 using Pega Mobile Client both iOS and Android mobile apps were built and distributed to end users.
If devices with supported OSs (see list at time of writing this post below) and iOS/Android build certificates are available then deployment of a Pega mobile client app is straightforward. Simply build and deploy the app as described in Part 1. However, if an Android device is not available for testing then an emulator is the only way to test. If iOS device is not available or the required iOS certificate set is not possible then either Pega Mobile preview or an emulator must be used. (Preview only works for iOS).
Android studio (https://developer.android.com/studio) allows you to import the .apk file generated by the mobile channel landing page. (See Building The Mobile App in Part 1) and test using an emulator device.
Open Android Studio and then File->Profile or Debug APK
Configure new emulator with AVD Manager (on of the icons in upper right of studio)
Once installed you can launch the CMS App using start button as in image below.
Sign into CMS app making sure the roles/access group of operator is configured correctly. (See Figure 7 in Part 1 for details)
It is also possible to emulate iOS devices. It is much easier with a Mac but Windows options exist. Mobile preview, as well as actual devices (using Pega dev certificate set from GCS), were used for the CMS application described here. However the below links may provide helpful to others: