Mobile settings reference

Custom app details

This section lists the general options for your custom mobile application. This information is shown to users when viewing the custom mobile app on their device or in the app store, such as Apple App Store or Google Play Store. This information helps users locate your app when performing a search in the given app store.

Note: Fields marked with an asterisk are required.

Field	Description
App name	The name of the custom mobile application.
App URL	The Pega 7 Platform application instance to be used by the custom mobile app.

Branding

This section is used to customize the image files that display as the splash screen and icons for your custom application on a mobile device and in an app store. See Branding assets to learn more.

Field	Description
Image buttons	Lets you select the color branding scheme based on the button selected. The Custom button lets you customize icons and splash screens for the custom mobile app by uploading an asset ZIP file with your own set of icons and splash screen images.
Upload Assets Zip	Lets you to upload a new assets ZIP file containing an own set of icons and splash screen images for the custom mobile app. See also Contents of the assets package.

The fields in this section are used for obtaining the necessary certificates and files for distributing your custom mobile app in the Google Play app store. They also let you set debugging options for the Android custom mobile app.

Note: Fields marked with an asterisk are required.

Field	Description	Notes
Version	Used to identify the version of your mobile app.	Example: 1.0.1. Select the Auto-increment the last number on the version with each build option from the Actions menu, to auto-increment the version number automatically with each build.
App ID (Package Name)	A unique string used to identify the Android app. This value is case-sensitive and must start with an uppercase or a lowercase letter. You may use the underscore character ('_'). At least one period ('.') must be used to separate different parts.	The following is an example of an App ID: com.example.my.android_app
Signing certificate	A certificate used for signing entries, such as installer packages, email messages, and similar items. It must consist of a P12 file containing a single private key and a single public certificate generated for signing.	You can either upload or select an existing P12 file to use for your Android app by clicking New.
Server API Key	A key used by the server to authenticate with the Google Cloud Messaging (GCM) services. The Google Cloud Messaging Server API Key is obtained from the Google Developer Console listed under the "Public API access" section.	Only needs to be defined, if the mobile app requires the push notifications capability. Setting both this value and the Sender ID value enables push notifications in the Android mobile app.
Sender ID	A Google Cloud Services (GCM) identifier used to authenticate an Android app with the Android Push Notification Integration services. The Google API Sender ID is obtained from the Google Developer Console listed as the "Sender ID".	Only needs to be defined, if the mobile app requires the push notifications capability. Setting both this value and the Server API Key value enables push notifications in the Android mobile app.
Enable debugging (Android)	Enables debugging of web contents in the Android custom mobile app. For the Android platform, it also makes a distribution with debugging information.
Select logging level	Sets the log level for the Android custom mobile app, while in a development, QA, or a production stage, to one of the following: Silent, Error, Warning, Info or Debug.	If set to a value higher than Silent, you will be able to examine the logs directly from the custom mobile app login screen, to troubleshoot any problems with signing in that are not related to wrong credentials. This setting also defines the default log level for Pega Mobile Client's launchbox.Logger.

The fields in this section are used for obtaining the necessary certificates and files for distributing your custom mobile application in the Apple App Store. They also let you set debugging options for the iOS custom mobile app.

If using push notifications, in addition to the fields listed below, you must also upload an An Apple Push Notification service (APNS) certificate as a P12 file.

Note: Fields marked with an asterisk are required.

Field	Description	Notes
Version	Used to identify the version of your mobile app.	Example: 1.0.1 Select the Auto-increment the last number on the version with each build option from the Actions menu, to auto-increment the version number automatically with each build.
Mobile Provisioning file	A provisioning profile is a set of digital certificates which associates a developer, an app ID and device ID(s), and is deployed to a device in order to allow the application to be installed and run for testing and distribution. The provisioning profile is usually distributed as a file with *.mobileprovision extension. Apple allows you to create the several types of provisioning profiles.	You can either upload or select an existing P12 file for your iOS mobile app by clicking New.
App ID (Bundle ID)	A string used to identify one or more iOS apps from a single development team. This value is case-sensitive and must start with an uppercase or a lowercase letter or a digit. You may use the hyphen character ('-'). At least one period ('.') must be used to separate different parts.	An example of an App ID (Bundle ID) is the following: com.example.my.ios-app
Signing certificate	Code signing your iOS app assures users that it is from a known source and the app has not been modified since it was last signed. Before your app can integrate app services, be installed on a device, or be submitted to the Apple App Store, it must be signed with a certificate issued by Apple. The certificate comes as a P12 file containing a single private key and a single certificate generated for signing.	You can either upload or select an existing P12 file for your iOS mobile app by clicking New.
Push notifications certificate	A certificate generated for push notification capability in iOS apps. It is used by a Pega 7 Platform server to communicate with Apple Push Notifications service (APNs). The certificate comes as P12 file containing a single private key and a single certificate generated for push notifications.	You can either upload or select an existing P12 file for your iOS mobile app by clicking New.
Enable debugging (iOS)	Enables debugging of web contents in the iOS custom mobile app.
Select logging level	Sets the log level for the iOS custom mobile app, while in a development, QA, or a production stage, to one of the following: Silent, Error, Warning, Info or Debug.	If set to a value higher than Silent, you will be able to examine the logs directly from the custom mobile app login screen, to troubleshoot any problems with signing in that are not related to wrong credentials. This setting also defines the default log level for Pega Mobile Client's launchbox.Logger.

This following options are available when you click Settings.

Versioning

This section contains the following fields:

Field	Description
Auto-increment the last number on the version with each build	Lets the system automatically increment the last version number with each new build.
Publish to users via smart app banner	Enables the creation of a custom banner prompting users to download the custom mobile app in a browser.
Icon for app banner	The icon to use as the custom banner image.

Compatibility

This section contains the following fields:

Field	Description
Set app version compatibility	Lets you configure the supported version range of Pega Mobile Client under the Android and iOS platforms.

Publish

This section contains settings for the AMP Manager when you click External Device Manager settings. AMP Manager is a separately licensed software used for distributing your custom mobile 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.

Field	Description
URL to AMP Manager	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.
Publisher name	The name of the publisher for the custom mobile application.
Description	Short text describing the mobile application.