Hello, all. Here’s my setup. I have a simple SP2013 custom list with a couple of fields. When a new list item is added, the “Onboarding Status” workflow is triggered (only on adds, not mods). This is a SP2013 list workflow. I’ve grabbed a screenshot of the pertinent section of the workflow to aid with troubleshooting:
As you can see this parent workflow starts a loop that spawns a SP2010 site workflow on each iteration. Since this is a site workflow, it is lauched with parameters, which I have included in the screenshot.
This site workflow (Onboarding Tasker) has only one job: create an approval task with a title, assignee, and due date picked from parameters. I’ve specified that the call to the site WF should *NOT* wait for the that WF to finish (i.e. it starts the approval task and goes on with its life, looping back to the next iteration in the parent WF). This site WF is shown here:
(nothing fancy here, obviously)
This works fine unless I do one of two things:
1. Attempt to reassign the created task to another person. (workflow history indicates that the task is delegated to the appropriate person, the task assigned to the original person is completed, but a new task for the delegated person is never created.
2. Attempt to programmatically modify the task to change the value of a column I added to the WF task content type (RelatedItemId, type: number) using an Update list item action in the Task Behaviors, When A Task is Pending step (shown below). When this action runs, the task is canceled and nothing is logged to the WF History to indicate WTF actually happened.
Any ideas are greatly appreciated. Thank you.
?width=750?width=750
