No one shouldn't have an access to delete Change Tasks once parent change is moved to submitted

[Nagurbee1]

Hello Everyone

Recently got a requirement of restricting access to delete change tasks once a change request is moved to submitted from draft state.

I have checked and observed that admin and change managers role users have an access to delete change tasks even after change request is closed, it's an OOB functionality.

I am trying to restrict the delete option once a change request is submitted even for admin users.

Could anyone suggest that how can we achieve it ?

Thanks in advance

Nagurbi

[M Iftikhar]

Hello @Nagurbee1,

OOB, admins and change managers can delete change tasks at any stage. To restrict this once the Change Request is submitted, you can:

1. Before Delete Business Rule (Best Option) 
   On change_task, check the parent Change Request’s state. If it’s not Draft, stop the delete with current.setAbortAction(true). This ensures no one (even admins) can delete.

2. UI Action Condition (Optional) 
   Hide the Delete button when the parent Change is beyond Draft. This improves UX but should be paired with the Business Rule.

3. ACL (Less common) 
   Possible, but admins can bypass ACLs, so not as strong.

Best practice: use a Before Delete BR for enforcement, and optionally hide the button for usability.

Thanks & Regards,  
Muhammad Iftikhar  

If my response helped, please mark it as the accepted solution so others can benefit as well. 

[Ankur Bawiskar]

@Nagurbee1 

you can update the OOTB Delete ACL to handle your logic.

what did you start and where are you stuck?

If my response helped please mark it correct and close the thread so that it benefits future readers.