Release 2021-02-26 of the Blue Cedar Platform adds streamlined server-side workflows for import and distribution. See the referenced online documentation pages for more information, or click Help when you’re logged into the Blue Cedar platform.
- Continuous app import from GitHub and GitLab
- Enterprise distribution of BlackBerry Dynamics-enabled apps
- Resolved issues
Continuous app import from GitHub and GitLab
If you use continuous integration and delivery pipelines on GitHub and GitLab, you can now include those updates automatically in your Blue Cedar workflows without having to manually check or shuttle mobile apps between systems. Your mobile app deployments will always include the latest updates from your build system.
What do I need to do?
Enable the GitHub or GitLab Import extension, configure it with project/repository details, and then add an Import step to your workflow. See Incorporating automatic app updates from GitHub and Incorporating automatic app updates from GitLab.
Enterprise distribution of BlackBerry apps
A new BlackBerry UEM distribution extension simplifies distribution of BlackBerry Dynamics-enabled apps. You can now set up a workflow to automate BlackBerry app distribution, instead of manually downloading the app and uploading it to the BlackBerry UEM. This automation is especially helpful when different parts of your organization control different phases of the app's lifecycle; the automation enabled by this step helps avoid potential confusion around shuttling different versions of the apps between groups.
What do I need to do?
Configure the BlackBerry UEM extension with details for your UEM. Then include a BlackBerry UEM step in the Production stage of your Blue Cedar workflow to make your apps available through your enterprise’s BlackBerry UEM App Catalog. You can automatically publish to your BlackBerry UEM, or choose to manually download an app prepared for BlackBerry UEM distribution and then publish it later.
|BCP 5436, BCP-5727||Added the ability to rename workflows on the workflow builder screen. Workflows by default are named after the main step in the App Enhancement stage.|
|BCP-5489, BCP-5530||Added the option to add an Approval step in any stage in a workflow after a configured step.|
|BCP-5531||The App-Ray service is now configured in a workflow as a step without any sub-steps. All existing App-Ray sub-step configurations are now converted to App-Ray steps to ensure backward compatibility.|
|BCP-5726||Extension-based workflow components are not shown as options in the workflow builder unless the extension is properly configured for the organization.|
|BCP-5731||Added the ability to save workflow changes even if the workflow isn't "ready to run." Errors and missing configurations must be resolved before running the workflow.|
|BCP-5729||Added a confirmation option to give you the ability to save changes to the workflow if you accidentally try to move from the workflow builder without saving.|
|BCP-5134||Fixed an issue that caused a Signing step to fail in the Production stage if it immediately followed a Signing step in the Testing stage.|
|BCP-5442||Updated mail notifications for signing and approval steps to include the link to the workflow that triggered the notification.|
|BCP-5440, BCP-5493||Added the ability to run a workflow on all available valid versions of an app at one time.|
Improved the information about the Signing step shown on the workflow run status page:
|BCP-4713||Fixed an issue where uploading an app binary with a different app version resulted in a warning indicating the version already exists.|
|BCP-5559||Fixed an issue where hovering over the App-Ray step did not display the duration correctly.|
|BCP-5478||Added an Import versions tab to the App List to show a list of versions available from external sources as enabled with Import extensions.|