Task Ownership Not Acting As Expected

This question is answered

I am trying to create a process where at different stages different people have ownership of a case.

Workflow assigns the current case owner tasks.

It starts with a supervisor who creates the case enters some information into the case form.

Workflow assigns that supervisor two tasks which the supervisor must complete and then assign the case to a support agent and click a box on the case form to see that phase 1 is complete.

If we look at the completed activities prior to the phase 1 completed being checked we see the supervisor as the owner of the completed activities.

Once the case is assigned to a support agent and the phase 1 is completed field is checked then workflow assigns a couple of new tasks to the support agent.

The weird thing that is happening is once the case ownership is changed from the supervisor to the support agent the ownership of the two tasks the supervisor completed are shown as now being owned by the support agent.

I want the completed activities to show who completed each task.

Is this a bug or am I doing something wrong?

Thanks.


Rick Bellefond
RB Data Services
www.rbdata.com


 

 

 

Verified Answer
  • It sounds like the problem is probably caused by the relationship behavior of the case:task relationship. The default relationship behavior is 'Parental' this means that when the case is assigned, shared, unshared, reparent, deleted or merged the same action is applied to the case's tasks.

    You can change the behavior to 'Configurable Cascading' and then change the behavior for the assign action to 'Cascade Active'. The result of this would be that closed tasks would not get reassigned but open tasks would.

    Here's an article that explains more: msdn.microsoft.com/.../gg309412.aspx

    Neil Benson, Slalom Consulting
    http://uk.linkedin.com/in/neilbenson
    @customery

  • Hi Neil,

    First of all, thanks for responding to my post.

    I think you very well may be right but will not be able to try it until I get back to the office on Monday.

    Getting it so that closed tasks would not get reassigned but open tasks would is exactly what I am trying to do.

    Once I can get it to do that I will come back and say it answered my questions.

    Thanks again.

    Rick Bellefond

    RB Data Services

    www.rbdata.com

All Replies
  • It sounds like the problem is probably caused by the relationship behavior of the case:task relationship. The default relationship behavior is 'Parental' this means that when the case is assigned, shared, unshared, reparent, deleted or merged the same action is applied to the case's tasks.

    You can change the behavior to 'Configurable Cascading' and then change the behavior for the assign action to 'Cascade Active'. The result of this would be that closed tasks would not get reassigned but open tasks would.

    Here's an article that explains more: msdn.microsoft.com/.../gg309412.aspx

    Neil Benson, Slalom Consulting
    http://uk.linkedin.com/in/neilbenson
    @customery

  • Hi Neil,

    First of all, thanks for responding to my post.

    I think you very well may be right but will not be able to try it until I get back to the office on Monday.

    Getting it so that closed tasks would not get reassigned but open tasks would is exactly what I am trying to do.

    Once I can get it to do that I will come back and say it answered my questions.

    Thanks again.

    Rick Bellefond

    RB Data Services

    www.rbdata.com