| Enhancement | More information on installation failures
You can now drill down for more information on blueprint installation failures, making it easier to find the cause.
 Viewing current blueprint installations
| CPT-4956 |
| Enhancement | Deleting blueprint versions
It's now possible to delete a specific blueprint version or the blueprint itself. To delete a specific version, access the blueprint manifest and use the versions dropdown to see all available versions - each is now associated with a delete option.
Deleting a blueprint version
| CPT-4971 |
| Enhancement | Email notification for bulk blueprint updates
When the bulk update feature is used to force blueprint updates for selected installations, an email notification is generated upon completion. This email is sent to the email address associated with the user who triggered the update, confirming successes and/or failures.
Bulk blueprint updates (force)
| CPT-4955 |
| Enhancement | Cancel pending bulk blueprint updates
Having triggered a blueprint update for multiple installations, the update jobs are queued and completed as soon as possible. Typically, this happens very quickly, but if you're updating lots of profiles with a complex blueprint, you may see pending updates. You now have the option to cancel any pending updates.
Viewing current blueprint installations
| CPT-4957 |
| Enhancement | Improved visibility for blueprint publish status
When a blueprint is published (either after an initial build or an update), it is queued for upload to your private marketplace, and a notification is generated upon completion.
To prevent timing conflicts, an 'update in progress' banner is displayed at the top of the manifest for the duration of the publish process. During this time, the blueprint is locked - it can't be changed or installed until the upload is complete. You will always see this behaviour for new blueprints. For updates to existing blueprints, you'll only see the banner if you switch to the manifest for the latest version before it has finished uploading.
Building a private blueprint
| CPT-4970 |
| Change | Maximum number of blueprint versions
A limit of 10 versions per blueprint is now enforced. This works on a first-in-first-out basis; if 10 versions exist and you attempt to publish another, you are prompted to delete the oldest version first. Note that if the oldest version is also the active version, you must set a later version to be active before a new one can be published.
Changing the active version for a blueprint
| CPT-4971 |
| Change | Naming convention for blueprint versions
Blueprint versions are now identified by a unique number, rather than a name.
Building a private blueprint
| CPT-4963 |
| Change | Deleting a blueprint
If you choose to delete an entire blueprint (rather than a specific version), you must now confirm the action by entering the blueprint name in full.
Deleting a blueprint
| CPT-4971 |
| Change | Opening a new blueprint draft
When you choose to open a draft to update an existing blueprint, a change has been made so an empty manifest is displayed (previously, existing flows and resources were shown but not included unless selected again).
Updating blueprints
| |
| Bug | Blueprint installs page
Fixed the following issues with the blueprint installs page: - Pagination was not working as expected. You can now step through page numbers correctly.
- Item selections were not retained when stepping through pages. Current selections now persist.
- Searching by name did not return the expected results. Search now works as expected.
Viewing current blueprint installations
| CPT-4994 |
| Bug | Bulk install status updates
Fixed an issue where the status for updated company profiles was not updated consistently on the installs page.
Blueprint updates (force)
| CPT-5012 |
| Bug | Bulk install status updates
Fixed an issue affecting blueprints that included process flows using a run process flow shape to call a sub-flow, and configured to use latest version of the flow. In this scenario, updating the sub-flow and then republishing the blueprint resulted in the older version of the sub-flow being called.
Updating blueprints
| CPT-5002 |