Hi @bradley just to be clear, are you saying if we decide to delete a task it should let you delete it even if there are underlying dependency or it should delete the dependencies as well if we decide to go ahead and delete the task ? 

Great question! Here’s an example of what I mean in general:

Let’s also say I needed to add a step between C1 and C2. I’d like to be able to just delete C2 and everything after it, without having to delete the action, then Final Rule Results, and then C2. I think I should absolutely get a warning that I’m going to delete a bunch of stuff (just like when you delete a field, it checks dependencies) but I’d like the option.

I can see the concern for Data Designer, where you could also have reports built off of a now MDA object, but that’s also where this request comes in: 

If I can be a bit greedy here, I’d like the option to delete OR hotswap out a task in a Rule/DD branch.

Again, there will still be some potential gotchas with Data Designers and their MDAs but that isn’t much different than today, where deleting a single field or the last task in a DD causes problems, this just makes making changes earlier in a design much easier.

Does that answer your question?

Hi @bradley just to be clear, are you saying if we decide to delete a task it should let you delete it even if there are underlying dependency or it should delete the dependencies as well if we decide to go ahead and delete the task ? 

Great question! Here’s an example of what I mean in general:

Let’s also say I needed to add a step between C1 and C2. I’d like to be able to just delete C2 and everything after it, without having to delete the action, then Final Rule Results, and then C2. I think I should absolutely get a warning that I’m going to delete a bunch of stuff (just like when you delete a field, it checks dependencies) but I’d like the option.

I can see the concern for Data Designer, where you could also have reports built off of a now MDA object, but that’s also where this request comes in: 

 

If I can be a bit greedy here, I’d like the option to delete OR hotswap out a task in a Rule/DD branch.

 

Again, there will still be some potential gotchas with Data Designers and their MDAs but that isn’t much different than today, where deleting a single field or the last task in a DD causes problems, this just makes making changes earlier in a design much easier.

Does that answer your question?

Yes this does, thanks for the detailed explanation, I will share this feedback with my team to evaluating the best solution for this problem.