Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Adjusting the Pega Mobile Client behavior with custom parameters

Suggest edit Updated on June 15, 2020

Pega Mobile Client™ parameters control the behavior of mobile apps on a mobile device. You can adjust the mobile app to your business needs, for example, by defining authentication, presentation, encryption, and debugging settings.

To adjust the mobile app, upload the following property files that pass additional parameters to the Channels and interfaces form:

  • The custom.properties file that includes Pega Mobile Client parameters.
  • The App-Info.plist file that includes iOS-specific parameters.

Setting a merge strategy

Property values set in the custom.properties file might conflict with settings made on the Channels and interfaces form of your Pega Platform™ application. In the case of a conflict, the custom values take precedence.

The way iOS-specific parameters from the App-Info.plist file are merged with the Pega Mobile Client's parameter list file depends on the type of values stored under each key.

  • Boolean, data, date, number, and string values always replace values that are in the Pega Mobile Client's parameter list file.
  • Arrays of strings are concatenated, and array elements remain unique.
  • Elements of an array value of the CFBundleDocumentTypes parameter replace the ones from the Pega Mobile Client's parameter list file.
  • Elements of the array values of the UTExportedTypeDeclarations and UTImportedTypeDeclarations parameters are appended to the parameters in the Pega Mobile Client's parameter list file. However, if an object with a specific UTTypeIdentifier value is already in the array, a new entry replaces an old one.
  • Elements of an array value of the UIApplicationShortcutItems parameter are appended to the parameters in the Pega Mobile Client's parameter list file. If an object with a specific UIApplicationShortcutItemType value is already in the array, a new entry replaces an old one.

Setting Pega Mobile Client parameters

Set Pega Mobile Client parameters by uploading a modified custom.properties file to Pega Platform. To obtain a sample custom.properties file, download the custom-properties.zip file.

  • To become familiar with the available parameters, review the custom.properties file.
  • To learn about individual parameter functions, read the inline comments.
  • To modify a setting, uncomment the line that contains the parameter, and change its default value.

Setting iOS-specific parameters

Set iOS-specific parameters by uploading a modified App-Info.plist file to Pega Platform. To obtain a sample App-Info.plist file, download the App-Info-plist.zip file.

  • To become familiar with the available parameters, review the App-Info.plist file.
  • To learn about individual parameters, refer to the Information Property List Key Reference on the iOS developer portal.
  • To modify the settings that apply to your use case, remove unnecessary parameters from the App-Info.plist file, and set the values for the remaining ones.

Uploading modified parameters

After you modify the parameters, place the custom.properties file in a root directory and the App-Info.plist file in the ios directory of the assets.zip file. You can use the assets.zip file when building mobile apps to upload branding assets.

For information about how to complete the upload, see Uploading branding assets and custom modules.

Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us