The BlackBerry Dynamics SDK provides a powerful set of tools designed to allow developers to focus on building useful productivity apps rather than learning how to secure, deploy, and manage those apps. Using the Blue Cedar Platform, you can integrate valuable services with the BlackBerry Dynamics SDK, including secure communications, inter-app data exchange, single sign-on authentication, identity and access management, and secure connectivity and storage.

BlackBerry UEM is a multi-platform EMM solution from BlackBerry that provides comprehensive device, app, and content management with integrated security and connectivity, and helps you manage devices for your organization.

This page lists the BlackBerry Dynamics features that are available when you use the Blue Cedar Platform to integrate mobile apps with BlackBerry Dynamics. In most cases, the feature is available after you integrate BlackBerry Dynamics on the Blue Cedar Platform; you manage and configure the feature with the BlackBerry UEM. Each table links to relevant documentation for Blue Cedar and for BlackBerry.

BlackBerry Dynamics features

BlackBerry Analytics

BlackBerry Analytics is a cloud-based portal where you can view statistics and reports about your organization's BlackBerry Dynamics apps. BlackBerry Analytics (included with Dynamics, but requiring a separate license) delivers event data from the app to the BlackBerry Analytics Engine and to display in the BlackBerry Analytics dashboard.

https://docs.blackberry.com/en/endpoint-management/blackberry-analytics/latest/administration-guide/hxc1484595314214

Support note: Blue Cedar support for BlackBerry Analytics SDK is deprecated. BlackBerry Analytics is part of BlackBerry Dynamics SDK now.

BlackBerry AppKinetics

AppKinetics is a means of exchanging data and commands securely between two BlackBerry Dynamics apps running on the same mobile device, such as when an app requires another app to securely view files, open URLs, or send email. One app initiates communication by sending a request to another. The second app performs the intended service requested, such as displaying a PDF, opening a URL, or sending an email. This target app must be a BlackBerry Dynamics app such as BlackBerry Access or BlackBerry Edit. The security of data isn't compromised during exchange.

Specifically, Blue Cedar supports these app-based mobile services. Follow these links to see a list of apps that are providers for these services:

If you want your BlackBerry Dynamics app to use the Shared Services Framework, the UEM administrator must specify the app package ID (Android) or bundle ID (iOS) in the BlackBerry Dynamics app settings in the management console. Contact your organization’s administrator to provide this information. For instructions for specifying the package ID or bundle ID for an app, see Manage settings for a BlackBerry Dynamics app in the UEM Administration Guide.

Note: AppKinetics is available only for Android apps integrated using the Blue Cedar Platform.

Blue Cedar PlatformBlackBerry UEM
​Implementation tasks

Run a workflow containing the BlackBerry no-code integration step on the app.

From the Policies and profiles > BlackBerry Dynamics > Profile Name configuration:

Select Data leakage protection > Do not allow copying data from non BlackBerry Dynamics apps into BlackBerry Dynamics apps.

Documentation

Extension - BlackBerry Dynamics

No-Code Integration - BlackBerry (step)

Distribution - BlackBerry UEM (step)


RequirementsBlue Cedar Platform with Mobile Client 4.10.12 or laterBlackBerry Dynamics SDK version 8.0 or later


BlackBerry Dynamics App Configuration

You can use the BlackBerry UEM (for both managed and unmanaged devices) to configure app management for Blue Cedar-integrated apps written to AppConfig.org standards. 

Blue Cedar PlatformBlackBerry UEM
​Implementation tasks

Run a workflow containing the BlackBerry no-code integration step on the app.

Download the Blue Cedar AppConfig XML template and edit it for app-specific configuration details.

Upload the Blue Cedar AppConfig XML template file to your BlackBerry UEM account, and apply it to apps and users in your UEM project.

Documentation

Extension - BlackBerry Dynamics

No-Code Integration - BlackBerry (step)

Distribution - BlackBerry UEM (step)

Manage settings for a BlackBerry Dynamics app
RequirementsBlue Cedar Platform with Mobile Client 4.10.12 or laterBlackBerry Dynamics SDK version 8.0 or later

BlackBerry Dynamics Launcher

The BlackBerry Dynamics Launcher appears as the blue BlackBerry icon located in your BlackBerry Dynamics apps. It allows users to switch quickly between the BlackBerry Dynamics app that is currently open and any other BlackBerry Dynamics apps on your device.

Blue Cedar PlatformBlackBerry UEM
​Implementation tasks

Include the BlackBerry Launcher library by enabling BlackBerry Launcher in the BlackBerry no-code integration step.

Run a workflow containing the BlackBerry no-code integration step on the app.

Within BlackBerry UEM:

  1. Choose your custom BlackBerry Dynamics app.
  2. On the BlackBerry Dynamics tab, click on the version number in the version table (typically 1.0.0.0).
  3. Expand and check Launchable Service, and Save.
  4. For iOS apps, make sure the iOS Bundle ID is set correctly on the iOS tab.
  5. For Android apps, make sure the Android package name is set correctly on the Android tab.
  6. Click Save.
Documentation

Extension - BlackBerry Dynamics

No-Code Integration - BlackBerry (step)

Distribution - BlackBerry UEM (step)

About the BlackBerry Dynamics Launcher Library
RequirementsBlue Cedar Platform with Mobile Client 4.10.12 or laterBlackBerry Dynamics SDK version 8.0 or later

BlackBerry Dynamics Watermark

The BlackBerry Watermark feature (part of the BlackBerry Launcher library) provides the possibility to add a watermark to the app screens in an app integrated with BlackBerry Dynamics SDK. Such a watermark contains the username of the logged user and the current date and time, to protect against data leakage by deterring users from taking photos of potentially sensitive information and by giving your organization a means to trace a data leak.

Blue Cedar PlatformBlackBerry UEM
​Implementation tasks

Include the BlackBerry Launcher library by enabling BlackBerry Launcher in the BlackBerry no-code integration step.

Run a workflow containing the BlackBerry no-code integration step on the app.

​Create a BlackBerry app policy definition file with a DLP watermark policy setting.

Upload the app policy for your app in UEM.

Documentation

Extension - BlackBerry Dynamics

No-Code Integration - BlackBerry (step)

Distribution - BlackBerry UEM (step)

Add a watermark to the screens in a BlackBerry Dynamics app 
RequirementsBlue Cedar Platform with Mobile Client 4.10.12 or laterBlackBerry Dynamics SDK version 8.0 or later


BlackBerry Persona

BlackBerry Persona collects data from BlackBerry Dynamics apps and determines a user's current risk level. The service then takes action to adapt device and app behavior to that level of risk. For example, if a user's current risk level is high, BlackBerry Persona can limit the user's access to work apps and disable certain device features. BlackBerry Persona protects the integrity of work data by dynamically responding to a user's real-world context, adapting a security policy based on user geolocation, device, time, IP address, and BlackBerry Dynamics app identifiers.

A BlackBerry Dynamics app using BlackBerry Persona requires Location Services on the device. BlackBerry Persona can be enabled and disabled by UEM admins for users, and users can also change the Location Services setting on their devices once the app is installed and activated. 

If you submit the BlackBerry Dynamics app to the Apple App Store with the BlackBerry Persona feature integrated, please clarify:

  • The location data is being collected as an optional feature of the app.
  • The data is linked to a user’s identity, but is not used for tracking purposes.

Licensing note: BlackBerry Persona requires a separate licensing agreement with BlackBerry in addition to BlackBerry Dynamics. 

App signing note: On iOS, BlackBerry requires an "Access WiFi Information" capability to be in the provisioning profile, which is used when signing the integrated app.

Blue Cedar PlatformBlackBerry UEM
​Implementation tasks

Make sure BlackBerry Persona is enabled (the default setting).

Run a workflow containing the BlackBerry no-code integration step on the app.

Follow these steps to enable Persona: 

Steps to configure and use Persona Mobile

Documentation

Extension - BlackBerry Dynamics

No-Code Integration - BlackBerry (step)

Distribution - BlackBerry UEM (step)

Using the BlackBerry Persona Analytics portal

RequirementsBlue Cedar Platform with Mobile Client 4.10.12 or laterBlackBerry Dynamics SDK version 8.1 or later