App versions

Normally, the term “version” refers to distinct software build versions of mobile app binaries. On the Blue Cedar Platform, version refers to all the different instances or variants of an app associated to each distinct app binary version, such as the imported mobile app binary, the mobile app binary after a no-code integration step such as adding the BlackBerry SDK and even the signed binary,

You can have iOS and Android binaries within the same App Folder, and you can run the app Workflow on only one of these binaries at a time if desired. Each of those binaries can have its own software build number (which doesn’t change as the app progresses through the workflow).

The App Folders as a whole is not versioned. A workflow run produces new app binary versions. For example, an unsigned version integrated with the BlackBerry SDK and a signed version integrated with the BlackBerry SDK are both artifacts of the same workflow run.

For example, suppose you have a basic third-party app for business travel that you’ve already run through Blue Cedar’s no-code integration—but now there’s a new build from the app vendor, and you need to re-run your no-code integration on the new build:

• You can upload the new build but still keep the old one, all under the same App Folder grouping. You can run the same workflow on either or both binaries as needed. You might do this to use the same workflow on an older release while testing the newer release.
• Or, you can create a new App Folder with a different workflow and upload the new binary into that folder. You might want to do this if you’re changing UEMs or other integration points. A new App Folder with a different workflow includes independent versions, even if it's created with the same original app binary.

See managing apps and app versions for more information.

Interim app binaries generated as part of a multi-step workflow can be seen under Artifacts for a particular workflow run as described in About individual app binaries.