Cascade Delete BOE and Resources

Feature Request: Cascade deletion of BOE-related resources

Summary:
Enable automatic cascade deletion of all BOE‑linked elements (such as resources, travel, and other cost items) when a BOE is deleted from a proposal. This ensures that removing a BOE also removes its dependent items in a single action, keeping the proposal clean and consistent without additional manual cleanup.

Problem Statement:
Currently, when a BOE is deleted from a proposal, any associated elements (resources, travel entries, and other related items) remain in the proposal. Users must manually identify and remove each of these dependent items, which is time-consuming and prone to error. This can lead to orphaned data, inconsistent proposal structures, and incorrect cost or resource calculations if associated elements are overlooked.

Proposed Solution:
Implement a cascade delete mechanism for BOEs within a proposal:

• When a user deletes a BOE, automatically identify and delete all elements that are explicitly assigned to that BOE (e.g., resources, travel, and other linked cost items).

• Provide a confirmation dialog summarizing what will be deleted (BOE + count or list of associated elements) so users understand the impact before confirming.

• Ensure that only items directly tied to the deleted BOE are removed; elements shared with or linked to other BOEs or proposal structures should be preserved.

• Optionally provide an audit log or activity record noting the BOE deletion and the associated elements that were removed.

• If any element cannot be safely deleted (e.g., referenced elsewhere), clearly indicate this to the user and preserve those items with appropriate messaging.

Benefits:

• Reduces manual cleanup effort when removing BOEs from proposals.

• Minimizes the risk of leaving orphaned resources, travel entries, or cost items that distort proposal data.

• Improves data integrity and consistency across proposals by keeping BOE structures and related elements aligned.

• Speeds up proposal maintenance and iteration, especially for complex proposals with many BOEs and linked elements.

• Enhances user confidence and satisfaction by making BOE deletion behavior predictable, transparent, and efficient.