How to wait for task & CC email with 2013 workflow?
-
23-12-2020 - |
Question
Goal
I'm trying to make a workflow (2013) in O365 that requires this flow:
- Create a task for UserA
- Email UserA to notify about the task, and CC UserB
- Wait for UserA to complete the task
Sounds simple, but I can't get past this. Here's what I've tried.
Approach A
Amazingly, it looks like these builtin steps are not capable of using the CC field. PLEASE correct me if I'm wrong; this is my preferred solution.
Assign a task
orStart a task process
Approach B
As a workaround to this seeming glaring oversight in the workflow framework, I've tried manually re-creating the task functionality. But now I can't tell when the task is done.
Assign a task
, don'tWait for task completion
, and do setWaiveAssignmentEmail
+WaiveCancellationEmail
Email
To: UserA, CC: UserB- I'm stuck here - how do I wait for the task outcome? (yes, I have the ID at least)
Can anyone explain how to wait for the task outcome, or give another approach that will meet the goal?
EDIT: Clarified that the purpose of the email (with CC) is to inform the user they have a task. Thus, it cannot happen after completion.
Solution
The "Wait for task completion" is an option under "Assign a task" window.
This task will wait until your workflow task completes. You can an add a send an email
action after this.
EDIT: Notify additional users about task assignment
Here is small algorithm that solves issue
Parallel Block Begin
Step: Assign a Task
Begin
Assign a Task: get Task ID
END
Step: Send an email
BEGIN
Wait until Task ID generates
email to the users
End
END
The workflow will look as follow
OTHER TIPS
when you use task actions in SPD it generates tasks in related task list. You can simply create another workflow on that related task list, which will send an email to the CC user. You can fetch any data from the item on which the workflow instance runs on by referencing it via [Workflow Item ID] field, which is available for task lists (i.e. Workflow Tasks) in SPD workflow designer. This is the cleanest approach which does not introduce any delays. Hope this helps.