> For the complete documentation index, see [llms.txt](https://docs.novacura.com/marketplace-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/marketplace-documentation/flow-platform-extensions/explore-extensions/bulk-deploy/documentation.md). # Documentation ### Glossary | Term | Definition | | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Item | A collective term for Applications, Portal Pages, and Automations. | | Deploy | The process of moving a committed application or page to a specified environment(s), making it available for use. This involves transferring a deployable version of the application or page to the target environment, where it can be accessed by users. | | Undeploy | The process of removing a deployed application or page from a target environment(s), making it unavailable for use. | | Rollback | The process of reverting a deployed application or page in a target environment to a previously deployed version | ### Application Service Overview This service enables users to perform deployment-related operations on multiple items simultaneously, including Applications, Portal Pages, and Automations. The service supports the following bulk operations: #### 1. Bulk Deployment Deploy multiple committed items to one or more specified environments, making them available for use. **Best for:** * Promoting multiple committed items across environments. * Deploying application changes in bulk. #### 2. Bulk Un-deployment Remove multiple deployed items from one or more specified environments, making them unavailable for use. **Best for:** * Withdrawing items from selected environments. * Removing deployed versions without deleting committed versions. #### 3. Bulk Rollback Revert multiple deployed items to their previously deployed versions within specified environments, where applicable. Items are eligible for rollback only when: * A previous deployed version exists. * The item is not currently deployed as version 1 only. {% hint style="info" %} Items that are not deployed to any environment or only have version 1 deployed are not eligible for rollback. {% endhint %} By allowing multiple items to be processed in a single operation, this service reduces the effort required to manage deployments across environments and helps ensure consistency when promoting, withdrawing, or reverting changes. ### Key Functionalities * Deploy multiple items to one or more environments in bulk. * Un-deploy multiple items from one or more environments in bulk. * Roll back multiple items to their previously deployed versions in one or more environments in bulk. ### Workflow ### 1. Select Organization Choose the organization from the “**Organization**” list selection menu.
### 2. Select Application Package Choose a package from the Application Libraries list selection menu.
### 3. Select Items Choose an item or items from the given list to deploy/ un-deploy/ rollback.
* Items that are selectable are grouped by Applications, Portal Pages and Automations. {% hint style="info" %} The date/time and author displayed for each non-development environment corresponds to the committed version currently deployed in that environment. It indicates when that respective version was committed and by whom, not when it was deployed or who performed the deployment. {% endhint %} * Items that cannot be selected because they do not have any committed versions are displayed in a separate list below. These items must be committed before they can be deployed or un-deployed. ### 4.1 Rollback to Previous Version Rollback selected items to their previously deployed versions.
#### 4.1.1 Select Environments to Rollback Versions (List Multi Selection Input) Displays the list of environments to which the selected items and their versions can be rolled back. The environments shown are filtered based on the environments available for the selected items that are eligible for rollback. #### 4.1.2 Selected Items Eligible for Rollback (List Presentation) Displays a list of selected items eligible for rollback. The items will have the following the information: * Name * The current deployed version and the version to which the item will be rolled back in each selected environment, displayed in the format Current Version *→* Previous Version * Items are grouped by their type: Applications, Portal Pages, Automations #### 4.1.3 Non-Eligible Items (List Presentation) Displays selected items that cannot be rolled back. Items are considered non-eligible when: * No version has been deployed to any environment. * Only version 1 has been deployed to at least one environment. #### 4.1.4 Available Actions * **Back -** Go back to the previous step. * **Review Rollback -** Proceed to the next step to review rollback items. {% hint style="info" %} This action is hidden when no eligible rollback items exist. {% endhint %} #### 4.1.5 Confirm Rollback Deployment
**Selected Items Eligible for Rollback (List Presentation)** Displays selected items eligible for rollback, filtered based on the environments selected in the previous step. **Available Actions** * **Back -** Go back to the previous step. * **Rollback -** Rollback selected item versions in the selected environments. ### 4.2 Deploy Latest Version Deploy the latest versions of selected items.
#### 4.2.1 Select Environments to Deploy To (List Multi Selection Input) Displays the list of environments to which the selected items and their versions can be deployed. The environments shown are filtered based on the environments available for the selected items. {% hint style="warning" %} Ensure that the latest versions of selected items are free of errors before deployment. Errors may cause deployment failures. {% endhint %} #### 4.2.2 Selected Items (List Presentation) Displays a list of selected items for deployment to their latest committed versions. The items will have the following the information: * Name * The latest committed version number, committed date and committed author * The current deployed version and the latest version to which the item will be deployed with to each selected environment, displayed in the format Current Version → Latest Version * Items are grouped by their type: Applications, Portal Pages, Automations #### 4.2.3 Available Actions **Back -** Go back to the previous step. **Review Deployment** - Proceeds to the next step to review items before deploying their latest versions to the selected environments #### 4.2.4 Confirm Deployment
**Selected Items (List Presentation)** Displays a list of the selected items and their latest committed versions to be deployed, filtered by the environment(s) selected in the previous step. Items are grouped by their type. **Available Actions** * **Back -** Go back to the previous step. * **Deploy -** Deploy the latest versions of selected items to the selected environment(s). ### 4.3 Un-deploy Item Versions Un-deploy versions from environments
#### 4.3.1 Select Environments to Un-deploy From (List Multi Selection Input) Displays the list of environments to which the selected items and their versions can be undeployed from. The environments shown are filtered based on the environments available for the selected items that are eligible for un-deployment. #### 4.3.2 Selected Items Eligible for Un-deployment (List Presentation) Displays selected items that can be un-deployed. Items include: * Item name. * Committed version number deployed in each environment. * Commit date. * Commit author. {% hint style="info" %} The version number, date, and author displayed for each environment represent the committed version information rather than the deployment information. {% endhint %} Items are grouped by type: Applications, Portal Pages, Automations #### 4.3.3 Non-Eligible Items (List Presentation) Displays a list of selected items and versions that are not eligible for rollback because no version has been deployed to any environment or only version 1 has been deployed to at least one of the environments. Items are grouped by their type. #### 4.3.4 Available Actions * **Back -** Go back to the previous step. * **Review Un-deployment -** Proceed to the next step to review items before undeploying. {% hint style="info" %} This action is hidden when no eligible items exist. {% endhint %} *** #### 4.3.5 Confirm Un-deployment
**Selected Items Eligible for Un-deployment (List Presentation)** Displays selected items eligible for un-deployment, filtered based on the environments selected in the previous step. Items are grouped by type. **Available Actions** * **Back -** Go back to the previous step. * **Un-deploy -** Remove selected item versions from the selected environments. ### 5. Post-Deployment Screen The final screen displays a confirmation message indicating that selected items have been: * Deployed. * Undeployed. * Rolled back.
**Download Item Summary (File Gallery)** From this screen, users can download a Summary Excel file containing information about items processed during the operation. The summary includes details about items that were: * Deployed. * Undeployed * Rolled back. * **Available Actions** * **Exit Application -** Close the application. * **Back to Item Selection -** Return to the item selection view. ### Limitations This application service has the following functional limitations: * Committing new item versions is not supported. * Committing and deploying new Automation versions is not supported. * Deploying specific historical versions of an item to selected environments. * Validating items for errors prior to deployment. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.novacura.com/marketplace-documentation/flow-platform-extensions/explore-extensions/bulk-deploy/documentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.