Hot answers tagged designer-workflow
The solution as i found recently, is to use the 2010 workflow to send the email, this is not bound by the restrictions that the 2013 workflow is in only sending to users known by the tenancy (i.e. those with accounts). In my case i did all the main bulk of the workflow in 2013 with loops and all the nice new features, then used a really simple parameter ...
The issue was that my email address was somehow not unique enough in SharePoint even though it should only point to one person (me). I changed my user approverstring concatenation to split users up with "Login names, semi-colon delimited" and changed the approval to "Start with [approverstring] as String"
The Collect Data From User action outputs a list item ID as a variable. This is the item id of the task. You can use that variable to look up to the task list who modified the task item.
Check if you are looking for something like this: # URL of the Site $web = Get-SPWeb -Identity "https://sharepointsrv/site1" $manager = $web.Site.WorkFlowManager # Name of the list $list = $web.Lists["Shared Documents"] # Name of the Workflow $assoc = $list.WorkflowAssociations.GetAssociationByName("On Item Created","en-US") $data = ...
We are in a similar situation. We recognized that in some case our permissions are unqiue but allways the same :) (unique permissions in some flow was always setting the same 2 AD groups). This is helpful as we can move these items down into a folder that has the unique permissions without having to assign it to each item individually, reducing the amount ...
The problem that you might be having, is that your image is stored locally on the computer you are using. Know that when you create workflows and send emails, it is running on the server farm. So unless the image is also stored on your server, it will not appear in the email address, as the server cannot reference that image. Try putting the picture into ...
Only top voted, non community-wiki answers of a minimum length are eligible