Release 2021-04-23 of the Blue Cedar Platform adds BlackBerry enhancements, including an SDK change and distribution to a UEM instance installed behind a firewall. In addition, a uniquely incremented build number now allows the same app version to be integrated multiple times. See the referenced online documentation pages for more information, or click Help when you’re logged into the Blue Cedar platform.


BlackBerry enhancements

BlackBerry Dynamics SDK updates

A new BlackBerry SDK version is now available for integration through the Blue Cedar Platform.

  • The Blue Cedar No-Code Integration Service for BlackBerry Dynamics now integrates these SDKs:
    • BlackBerry Dynamics SDK release v9.1.0.35 for iOS and Android
    • BlackBerry Launcher Library v3.2.0.195
  • BlackBerry AppKinetics is now available for iOS as well as Android. 
  • The BlackBerry Persona feature is enabled by default and can be disabled per app in the App Enhancement / BlackBerry step of a workflow.

See Integrating BlackBerry Dynamics features with Blue Cedar Platform for more information.

What do I need to do?

You can optionally re-run any existing workflows that contain a BlackBerry no-code integration workflow step so that you can update existing apps with the latest enhancement, and distribute them. If you choose not to update your existing apps, they'll continue to work as before, using the previous SDK integration. Otherwise, future workflows and workflow runs will automatically include the new SDK features.

BlackBerry private UEMs

The Blue Cedar Platform supports mobile app distribution to private BlackBerry UEMs behind a firewall.

What do I need to do?

To set up distribution to a firewall-protected BlackBerry UEM, you must enable the Blue Cedar extension for BlackBerry UEM and add the firewall information to the extension configuration. For details, see Extension - BlackBerry UEM.

App build number change

A no-code integration step (such as BlackBerry) produces a unique build number that is distinct and separate from the official app's version number. This unique build number allows the app to be uploaded for distribution even when the mobile app's version has not changed. This is useful when running a no-code integration step multiple times on the same app version.

  • The app build number increments in ascending order.
  • The build number persists within the App container, even if the workflow associated with that App container is deleted.
  • The app build number applies only within a single App container on the Blue Cedar Platform: if you import the same original binary in a different App container, its build number increments with its own workflow runs, and resulting binaries are distinct.
  • Only the no-code integration step changes the build number; there is no change for other workflow steps, such as when the app is signed.

What do I need to do?

You don't need to do anything, but you'll see the build number change on the Blue Cedar Platform for each workflow run on a particular app binary. 

Resolved issues


BCP-6115Uploading a Mobile Provisioning Profile in the BlackBerry UEM step is now optional.


BCP-5983Fixed a minor issue that displayed available extension titles differently based on selected filters.
BCP-6109Minor fixes for search results and behavior in Apps list.
BCP-6058Added the ability to edit extension configurations for all available extension types.
BCP-6059Added the ability to allow refreshing the current screen by double clicking the current tab on the sidebar.
BCP-5932Minor styling updates to App Versions titles to display version/build number information consistently. 

Organizations and users

BCP-6100Minor improvements to handle users' attempts to delete their own accounts. Deleting the current user while logged in displays a message and logs out the current user if the user confirms.
BCP-6098Fixed an issue where all users within an organization didn't show up under the Users tab.
BCP-6088, BCP-6089Fixed issues where updating an organization's logo didn't auto-refresh each image.