[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1136
  • Last Modified:

Sharepoint Designer 2010 workflow email failing because of impersonation - Catch 22 ?

I believe this is a catch 22 but would like to know if there is a way around this.
I have created a owrkflow which copies an entry from one list to another, then deletes the entry in the original list. I originally gave Contribute the the Authenticated Users group on the first list - to allow them to create tickets, and Read access on the second list. Of course the workflow failed since they require Contribute on the second list to achieve this. I then used an impersonation step to run the step of copying the entry to the second list - this works fine ! The problem now is that the e-mail which is sent back to the Creator as part of the Workflow, is now attempting to send to the account under which the Impersonation is running - the Workflow Designer, instead of the Creator. I can work round this by removing the impersonation step, and giving Contributor to the Authenticated users on the second list, but they are then able to UPDATE tickets in the second list - NOT what is required.
Does anyone have an alternative way of doing this - it seems as if the Creator is being overwritten to show the account under which the Impersonation is run - and thus when the step to email the creator is run, it sees the creator as the impersonation account ?

Thanks to all who assist
0
TheGeezer2010
Asked:
TheGeezer2010
  • 2
  • 2
1 Solution
 
GeorgeGerguesCommented:
Very common .

But in general It is solved by
[1] Let the Workflow you have function the same without the last step of sending emails etc.
[2] Let the last step be a recording step : meaning , write to the destination list , the name or email of the person originating the process.
[3] Create another workflow on the second List (OnCreate) trigger the Email workflow to send the information/ communication to all parties.

it is easier when broken down in steps.

Best of luck
0
 
TheGeezer2010Author Commented:
Hi George

Thanks for rapid response !!

I am unsure what you mean so maybe if I break down the steps it may help.

On List 1. Workflow - Move HelpDesk Tickets(onCreate)

Steps

1. Build Dynamic String
2. Set Title field to Dynamic String
3. Copy current item to List 2 - this was where the impersonation step was
4. Delete current item from List 1

On List 2. Workflow - ProgressUpdates (onChange)

Steps

1. Email Requestor with details of update and Ticket URL - this is the part which is failing unless either impersonation step used, OR Authenticated Users have Contribute on this list.

I hope this clarifies the issue ?

Please advise what should be the revised steps.
0
 
GeorgeGerguesCommented:

You will need to create a new column in List 2 with , a place holder for the Source User Information

On List 1. Workflow - Move HelpDesk Tickets(onCreate)

Steps

1. Build Dynamic String
2. Set Title field to Dynamic String  ,
3. Copy current item to List 2 - this was where the impersonation step was
  3.1 Set the Source User field in List 2 with proper value.
4. Delete current item from List 1


On List 2. Workflow - ProgressUpdates (onChange)

Steps

1. Email Requestor with details of update and Ticket URL - this is the part which is failing unless either impersonation step used, OR Authenticated Users have Contribute on this list.
2 . email the Source from the  newly create List column in WF1.


Best of luck
0
 
TheGeezer2010Author Commented:
Sounds like a plan !! Will test and let you know.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now