> 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/cascade-delete/documentation.md).

# Documentation

### Glossary

<table><thead><tr><th width="245.81817626953125">Term</th><th>Definition</th></tr></thead><tbody><tr><td>Item</td><td>A collective term for Applications, Portal Pages, and Automations.</td></tr><tr><td>Asset</td><td>A component or module.</td></tr><tr><td>Dependent</td><td>An item or asset that needs and relies on another asset to function.</td></tr></tbody></table>

&#x20;

### Application Service Overview

This service enables users to **cascade delete from a selected organization**, these **items include; Applications, Portal Pages, and Automations** along with any assets that are exclusively associated with them.

Items and their assets can be deleted using the following methods:

{% stepper %}
{% step %}
**Individual item deletion**

A single item can be deleted independently without deleting any of the assets it uses. Before an item can be selected for deletion, it must be undeployed from all environments in which it is currently deployed.

Best for:

* Removing obsolete Applications, Portal Pages, or Automations
* Retaining reusable assets for future use
* Deleting items without affecting shared components or modules
  {% endstep %}

{% step %}
**Item and Asset Deletion**

A single item can be deleted together with any assets that are exclusively associated with that item. Assets that are shared with, or used by, other items cannot be selected for deletion and will remain in the system.

Best for:

* Cleaning up unused items and their exclusive assets
* Removing item-specific components and modules that are no longer required
* Reducing clutter within application packages
  {% endstep %}
  {% endstepper %}

{% hint style="info" %}
This service does not commit all assets used by the selected items. This service only deletes the selected item and any eligible item - exclusive assets.

It does not:

* Delete assets that are shared with other items
* Delete standalone assets that are not associated with an item
* Delete multiple items in a single operation

{% endhint %}

### Key Functionalities

* Delete Applications, Portal Pages, and Automations individually
* Delete an item together with assets that are exclusive to that item
* Identify assets that cannot be deleted because they are shared with other items

&#x20;

### Workflow

#### 1. Select Organization

Choose the organization from the “**Organization**” list selection menu.

<figure><img src="/files/oeJ307TpSJUPBd4Isdui" alt=""><figcaption></figcaption></figure>

&#x20;

#### 2. Select Application Package

Choose a package from the Application Libraries list selection menu.

<figure><img src="/files/2QJf81O7ASE3WCD43GIi" alt=""><figcaption></figcaption></figure>

&#x20;

#### 3. Select Item to Delete

Choose an item from the list to delete. Items are grouped by type:

* Applications
* Portal Pages
* Automations

<figure><img src="/files/eYBKnhju4OB5ez8RxxG5" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Items that are currently deployed in one or more environments cannot be selected for deletion. These items are displayed in a separate list and must be undeployed from all environments before they can be deleted.
{% endhint %}

&#x20;

#### 4. Select Assets to Delete

**4.1 Select assets to delete (List Multi Selection Input)**

Displays the highest-level item-exclusive assets used by the selected item. Each selected asset includes all dependent assets, which can be viewed in a tree structure within the pinned step. Each asset includes the following information:

* Name&#x20;
* The package in which it resides&#x20;
* The first two dependency levels of the assets used by that asset &#x20;

{% hint style="info" %}
If additional levels exist beyond the first two, an ellipsis (“…”) is appended to the name of the second-level asset
{% endhint %}

Assets are grouped by components and modules. All assets are selected by default and can be deselected as needed.&#x20;

<figure><img src="/files/Pj5sPjkX1eutGlmhkkWo" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This screen also displays assets that are shared with other items and are therefore not eligible for deletion. Each asset shows its name and the package in which it resides.&#x20;
{% endhint %}

**Available Actions**&#x20;

* **Back** – Go back to the previous step&#x20;
* **Export To CSV** – Download the list of all assets the selected item uses.&#x20;
* **View Asset Dependencies** – Navigates to a screen that displays the items that use the shared assets&#x20;
  * Will be hidden if no shared assets exist&#x20;
* **Delete** – Proceeds to the next screen where you will confirm the item and assets for deletion.&#x20;

&#x20;

**4.2 View Asset Dependencies (List presentation)**&#x20;

Displays the list of items that use the shared assets of the selected item. Each item is displayed with its type and the package in which it resides. Items are grouped by the name of each shared asset.&#x20;

<figure><img src="/files/IBT2poEeiBOPMq43yHPn" alt=""><figcaption></figcaption></figure>

**Available Actions**&#x20;

* **Back** – Go back to the previous step&#x20;
* **Export To CSV** – Download the list of items used by the shared assets.&#x20;

#### 5. Confirmation&#x20;

The final confirmation screen before the selected item (and any selected assets if available) are deleted. This screen shows the selected item’s type, last committed author, last committed version and last committed date.&#x20;

**Selected Assets to be Deleted (List presentation)**&#x20;

Displays a list of selected assets that will be deleted alongside the selected item. Each asset shows its name and the package in which it resides. Assets are grouped by type (e.g., Component, Module). &#x20;

<figure><img src="/files/AlqqGJrJ4lLMlwObtjWh" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Will be hidden if no assets were selected or if the item does not use any assets&#x20;
{% endhint %}

{% hint style="warning" %}
Review the information carefully and confirm your action by clicking **Confirm** to proceed with the **Deletion**.
{% endhint %}

&#x20;

#### 6. Post-Deletion

The final screen displays a confirmation message that the selected item (and assets if any) have been deleted.&#x20;

**Download Item Summary (File Gallery)**&#x20;

From this screen, you can download a Summary **.csv** file containing information about the item (and assets) that were deleted.&#x20;

After reviewing or downloading the summary, you can:&#x20;

* **Exit** the application, or&#x20;
* Click **Back to Item Selection** to return to the item selection view&#x20;

&#x20;

### Limitations

This application service has the following functional limitations:&#x20;

* Multiple items cannot be deleted in bulk&#x20;
* Standalone assets (or assets not used by any item) cannot be deleted. \
  \&#xNAN;*(This will be facilitated through another extension service called - **Clean Unused Assets**)*


---

# 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/cascade-delete/documentation.md?ask=<question>&goal=<endgoal>
```

`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.
