Introduce workflow-based approval for Category Delete and Cascade Delete operations when governance workflows are enabled.

Hi Andrea,

One alternative worth considering: cascade delete is a separately grantable permission, so an organization with strict change control can simply not grant it to anyone. All deletions then run through bulk delete, which is fully workflow-enabled — approval, audit and change control included.

Bulk delete is arguably the better fit anyway: the approver reviews an explicit list of artifacts, whereas a cascade delete resolves its scope at execution time, so the approver would be approving an operation rather than a defined change set.

Your feedback is documented and we will revisit if similar requests come in.

Best regards,
Michal

Hi Michal,

Thank you for your explanation.However, I am not fully aligned with the conclusion.While I agree that cascade delete should be restricted to a limited number of privileged administrators, the concern is not only who can execute the action, but also the potential business impact when the action is executed, even by an authorized administrator.In many enterprise environments, especially those with strict governance and compliance requirements, sensitive operations often require a second level of validation or approval regardless of the user's administrative privileges. The objective is not to compensate for an incorrect permission model, but to provide additional safeguards, auditability, and change control for operations that can affect a large number of business assets.A confirmation dialog helps prevent accidental clicks, but it does not provide the same level of governance as a workflow-based approval process.For this reason, I still believe that workflow support for cascade delete would bring value to organizations operating under strict governance models, particularly in regulated industries and large-scale deployments.I understand that this is not currently planned, but I would appreciate if this feedback could remain documented and be reconsidered should similar requests arise from other customers.

Best regards, Andrea

Inviato da Outlook per iOS
________________________________
Da: IBM Data and AI Ideas <726b2eb248fd4e7adc43d816-bigblue@iad-prod1.mailer.aha.io>
Inviato: Tuesday, 04 August 2026 15:27:38
A: Andrea Pagano
Oggetto: [EXTERNAL] Michal Szylar responded to idea CPDIDEAS-I-3285 Introduce workflow-based approval for Category Delete and Cascade Delete operations when governance workflows are enabled.

Hi,

Thank you for submitting this idea and for the detail you provided.

Cascade delete is intentionally restricted to a small number of entitled administrators and is not normally granted to end users. The capability was introduced to cover edge-case scenarios such as bulk maintenance or correcting invalid imports, and it additionally requires the entitled administrator to explicitly confirm the action before it proceeds.

Given these safeguards, we don't see sufficient justification for building workflow/approval support around it. Instead, our recommendation is to review the permission model configured for the customer, so that cascade delete is assigned only to the roles that genuinely require it.

We're closing this as not planned for now, but happy to revisit if a concrete scenario emerges where the existing admin-level safeguards prove insufficient.

Best regards,
Michal