Skip to main content
Skip table of contents

Extension - BlackBerry Dynamics

The BlackBerry Dynamics extension enables the Enhance service to add the BlackBerry Dynamics SDK to mobile apps without requiring code to be written. Enabling this extension gives you access to the BlackBerry step in the App Enhancement stage of your workflows. Click Add to enable the extension and then click the gear icon to configure.


This table presents a summary of the BlackBerry Dynamics extension—what it provides, what you need to know about enabling and configuring it, and what are the corresponding workflow steps and other relevant topics. The rest of this page provides configuration details. 

Services provided by this extension

The BlackBerry Dynamics SDK provides a powerful set of features to  to secure, deploy, and manage those apps. With the Blue Cedar Platform, you can use this no-code integration extension to add these services into your apps—without needing source code or developers.

See Enhance for BlackBerry (No-Code App Security Integration) for an overview of the features that are available when you add BlackBerry Dynamics via Blue Cedar Platform no-code integration.

Extension configuration

Unlike other extensions on the Blue Cedar Platform, the BlackBerry Dynamics no-code integration extension does not need to be enabled: it is enabled automatically and cannot be disabled. 

There is one configuration option: you can override the default root string for the GD App ID, which is a unique identifier for a BlackBerry app. The Blue Cedar Platform creates a default root for your organization. You can override that default here at the extension level; you can override a full GD App ID for a specific app in the workflow configuration. See below for details about the GD App ID.

Related workflow steps

Add the BlackBerry step to the App Enhancement stage of your workflows.

See App Enhancement - BlackBerry for details.

Other related topics 

BlackBerry-integrated apps can be managed with the BlackBerry UEM. Once an app has been integrated with BlackBerry Dynamics, you can then manage the app via the BlackBerry UEM.

The BlackBerry UEM distribution extension lets you include workflow steps in the Testing or Production stages to prepare the app for BlackBerry UEM deployment. See the extension (Extension - BlackBerry UEM) and workflow step (Distribution - BlackBerry UEM) for more information.

About GD App IDs

Each BlackBerry app has a unique identifier, known as the GD App ID. Together with the GD App Version, the GD App ID is used to manage end-user entitlement for your BlackBerry apps and to support certain features such as AppKinetics, where BlackBerry apps exchange data and commands.

The GD App ID and GD App Version are BlackBerry-specific metadata and are independent of Android package names or iOS bundle IDs, although they are formatted similarly. The "General Information" page for each app version shows an App Version, which is the release number, and an App ID, which is the Android package name or iOS bundle ID. Even though these IDs use reverse domain format, it is important to note which is which. As you run workflows and create new versions of apps, BlackBerry Dynamics needs to be able to distinguish those versions.

Format of GD App ID

The general form of a GD App ID is:

The value of your GD App IDs must follow these rules:

  • Must be in reverse domain name form
  • Must not begin with any domains belonging to BlackBerry: com.good, com.blackberry, com.rim, or net.rim
  • No uppercase letters

By convention, the GD App Version numbers are four integers separated by periods, for example, This version number should be independent of the app's versioning scheme in other contexts. For example, your GD App Version might be "" while the app's public release number is "2.1".

Default GD App ID generation on the Blue Cedar Platform

To simplify assigning GD App IDs to all the versions of your apps as you run workflows on them, the Blue Cedar Platform automatically derives GD App IDs based on your organization name and app name. 

ElementDefault valueNotes
GD App ID root​

This string becomes the default root for all GD App IDs in your organization. 

You can override the default root for the whole organization by customizing the extension, or you can override each GD App ID in the workflow.​

The organization name appears at the top left when you are on a screen with the main menu. 

Completing the GD App

When you add BlackBerry or BlackBerry UEM steps to the workflow for an app, the Blue Cedar Platform adds these elements to the GD App ID root:

  • app-name: The name of the App in the Blue Cedar Platform, that is, the name that appears in the App List, not the filename.
  • stage-name: The workflow stage name:
    • appenhancement for BlackBerry no-code integration
    • testing or production for BlackBerry UEM distribution

You can override the GD App ID when configuring any BlackBerry or BlackBerry UEM step of the workflow.​

Configure the extension (optional)

Unlike other extensions on the Blue Cedar Platform, the BlackBerry Dynamics no-code integration extension does not need to be enabled: it is enabled automatically and cannot be disabled. This means that the BlackBerry step is always available for workflows.

The only detail you can configure at the extension level is optional—you can override the GD App ID root.

  • From the Blue Cedar Platform main menu, select Extensions > No-Code Integration. The platform shows the BlackBerry Dynamics extension.

  • On the BlackBerry Dynamics card, click the gear icon to open the BlackBerry Dynamics screen. 
  • On the Configure BlackBerry Dynamics screen, confirm or edit the Root GD App ID. This root GD App ID is the default for all apps and workflows in your organization.
  • Click Save Changes.

Next steps

The BlackBerry extension is available in the App Enhancement stage of workflows. Whether you customize the GD App ID root or not, you can override the GD App ID when you add a BlackBerry no-code integration step to a workflow.

Related topics

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.