Deleting Modules from Branches

Delete a module from a branch to remove it from that branch without destroying the underlying module data. The module remains available in other branches, published versions, and the module's history.

Deleting a module from a branch is permanent and cannot be undone. The module is removed from the branch immediately. Other branches and published versions that include the module are not affected.

How Module Deletion Works

When a module is deleted from a branch, the platform removes the module from that branch. The module's underlying data and archived configurations remain intact. Other branches, published versions, and the module's history can still reference the module.

Delete a Module from a Branch

Deleting a module requires CAN_EDIT or CAN_MANAGE permission on the workspace.

From the Explorer

To delete a module from the Explorer panel:

1. Open the application in Module Builder and select the branch using the checkout pill in the tab bar.

2. Switch the module to Editing mode.

3. In the Explorer panel, hover over the module to reveal its options.

4. Select   (ellipsis) >   Delete Module.

5. In the confirmation dialog, type the exact module name to confirm.

6. Click Delete.

From the Module Builder Toolbar

To delete the currently open module:

1. Open the module in Module Builder and select the branch using the checkout pill in the tab bar.

2. Switch the module to Editing mode.

3. In the toolbar, select   (ellipsis) >   Delete Module.

4. In the confirmation dialog, type the exact module name to confirm.

5. Click Delete.

After deleting the module, it is removed from the Explorer panel.

When a Module Cannot Be Deleted

The platform blocks module deletion in the following cases:

Entry Point Module

The application's entry point module cannot be deleted. The delete action does not appear in the Explorer (ellipsis) menu. It also does not appear in the Module Builder toolbar. The entry point module is created when the application is first created and remains a permanent member of all branches.

Editing Lock

If another Creator holds an editing lock on the module, the delete action is blocked until the lock is released. If the Creator attempting the delete holds the lock, the platform releases it automatically when the delete completes.

Inbound Dependencies

If any other module, workflow, or test suite in the branch depends on the module being deleted, the delete is blocked. The error message names the following dependent elements:

Cannot delete module 'Checkout': it is a dependency of module 'Cart'. Remove those references first.

To proceed, remove the dependencies from those elements or delete the dependent elements first.

Owned Transforms

A module's transforms are removed with the module automatically. If any remaining workflow or test suite depends on those transforms, the delete is blocked. The error message names both the module dependencies and the transform dependencies separately as follows:

Cannot delete module 'Checkout': it is a dependency of module 'Cart'; its transforms are a dependency of workflow 'Onboard'. Remove those references first.

What Survives Deletion

When a module is deleted from a branch, the following remain intact:

• Other branches: The module remains in any other branch or published version where it exists.

• Module data: The module's underlying data and archived configurations remain in the database.

• Module history: The module's version history and audit trail are preserved.