11-17-2011 05:48 PM
For services, where the tasks happen concurrently, we want to send a 'closure mail' to the customer when all tasks are completed. As the tasks happen concurrently, we don't know which is the last one to complete. Can anyone tell me how we can specify the final task of sending closure mail?
Thanks.
11-17-2011 05:48 PM
We handle that by having all concurrent tasks executing under one task, let's call it "Concurrent Tasks". We then have the next high level task called "Closure notice"which actually sends the closure email. It only executes once all the previous tasks are complete. Hope this helps!
11-17-2011 05:48 PM
Hi Carol
From your explanation, I tried specifiying the tasks as follows:
Concurrent task (where subtask execute: at the same time (concurrently)
Mail Poland (child task) (where subtask = concurrently)
Agent (child task) (subtask = concurrently)
Closure (which executes the closure mail when above tasks are completed)
But it doesn't work. Even when the 2 child tasks are completed the main task 'Concurrent task' remains 'ongoing'. As such the next main task 'Closure' cannot be executed as it still awaits for the first main task to be completed. Can you please tell me what I did wrong or how the whole planning should be done? Thanks.
11-17-2011 05:48 PM
Hi Christine,
It looks like you've set this up correctly. Check the duration on your first task "Concurrent task (where subtask execute: at the same time (concurrently)". It needs to be 0.
11-17-2011 05:48 PM
Hi Christine,
Here's an example of what Carol is describing:
The critical component is that the parent should have "0" duration, no participants, and its child tasks must fire concurrently.
11-17-2011 05:48 PM
Hi Ed
I followed Carol's instruction and I think it's working. We're still testing.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: