Related information
The Mobile tab on the application rule form lists settings for mobile functionality. As described in the table below, the first setting on this tab lets you select whether the application that is being built should be accessed using a Pega 7 mobile app or should be accessed via a (custom branded) hybrid mobile app, also referred to as the Pega Mobile Client. See also Application form - Completing the Mobile tab.
Note: The fields in the sections that are on this page that are marked with an asterisk (*) are required.
Field name |
Description |
|
Using Pega7 mobile app |
Indicates that your application is designated to be accessed using the Pega 7 mobile app. The Pega 7 mobile app is available for download from the Apple iTunes and Google Play app stores using the respective QR codes and links displayed on this tab. See also the PDN articles How to use the mobile barcode and QR code scanner and How to distribute a hybrid mobile application. |
|
Create custom mobile app |
Lets you create a custom hybrid mobile app that uses non-Pega branding. You must select this option to use the offline capability. The rest of this topic explains the fields that display after you click this button. See also the PDN article How to build and brand a hybrid mobile application for detailed usage instructions. |
Note: You must have a license for Pega Mobile Client in order to create a hybrid mobile application on this Mobile tab. Without this license, you can only use the default Pega 7 mobile app to access your application on a mobile device.
This section lists the general options for your hybrid mobile application. The information entered here is shown to users when viewing the hybrid client app on their device or in the app store, such as Apple iTunes or Google Play. Keep in mind that this information helps users locate your app when performing a search in the given app store.
Field name |
Description |
| Application name to appear on mobile devices | The name of the mobile application. |
| Application URL | The application instance to be used by the custom hybrid mobile app. |
| Prompt for alternative URL on app start | Allows the user to enter another PRPC instance during the start of the custom hybrid mobile app, instead of using the one specified in the Application URL field during design-time. |
| Publisher | The publisher of the mobile application. |
| Unique application identifier | The unique mobile application identifier. |
| Description | Short text describing the mobile application. |
| My app will be using push notifications | Enables using push notification with your hybrid mobile application. Selecting this option toggles additional fields under the iOS Settings and Android Settings sections. See PDN article How to use push notifications with a mobile application for more information. |
This optional section is used to customize the image files that display as the splash screen and icons for your hybrid mobile application on a mobile device and in an app store. See also Branding Pega Mobile Client .
Field name |
Description |
| Customize icons and splash screens | Enables you to customize icons and splash screens for the hybrid mobile app. |
| Upload Assets Zip | Lets you to upload a new assets ZIP file containing an own set of icons and splash screen images for the hybrid mobile app. |
The fields in this section are used for obtaining the necessary certificates and files for distributing your hybrid mobile application in the Apple iTunes app store.
Note: If using push notifications, in addition to the fields listed below, you must also upload an An Apple Push Notification service (APNS) certificate.
Field name |
Description |
Notes |
| Release version | Used to identify the version of your app. | Example: 1.0.1 |
| Distribution P12 file | Upload or select an existing file, or create a new P12 file to use for distributing your mobile app. | |
| Provisioning profile | Upload or select an existing file, or create a new P12 file to use for distributing your mobile app. | This field appears after selecting the My app will be using push notifications check box in the General section. |
| Push notifications P12 file | Upload or select an existing file, or create a new P12 file to use for distributing your mobile app. | This field appears after selecting the My app will be using push notifications check box in the General section. |
The fields in this section are used for obtaining the necessary certificates and files for distributing your hybrid mobile application in the Google Play app store.
Field name |
Description |
Notes |
| Release version | Used to identify the version of your app. | Example: 1.0.1 |
| Distribution P12 file | Upload or select an existing file, or create a new P12 file to use for distributing your mobile app. | |
| Google API Project Number | A Google API Project Number, obtained from the Google Developer Console listed as the "Project Number". | This field appears after selecting the My app will be using push notifications check box in the General section. |
| Google Cloud Messaging API Key | A Google Cloud Messaging API Key, obtained from the Google Developer Console listed under the "Public API access" section. | This field appears after selecting the My app will be using push notifications check box in the General section. |
This optional section is used to create a banner that appears in mobile web browsers prompting users to download your hybrid mobile application from an app store. See also Customizing Pega Mobile Client.
Field name |
Description |
| Publish to users via | Enables the creation of a custom banner prompting users to download the hybrid mobile app in a browser. |
| Icon for app banner | The icon to use as the custom banner image. |
AMP Manager is a separately licensed software used for distributing your application. The fields in this section are used for communicating between Designer Studio and AMP Manager when pushing or pulling user rights and distribution of your mobile application across various mobile devices.
Note: You must have an AMP Manager license in order to use the fields in this section.
Field name |
Description |
| URL | The path to your AMP Manager instance, for example:https://ampexample.com/mc/ws/api/1/ |
| Username | The username for your AMP Manager instance. |
| Password | The password for your AMP Manager instance. |