Tag Info

Hot answers tagged

2

You will need to create another field in the list by the name of Previous Owner. Don't display it in the view. Set it to the same value to Owner when the item is created by a separate workflow that is run when a new item is created. Then create another workflow that only runs when the item is updated and compare the values of the Previous Owner and Owner. ...


2

No direct way because SharePoint Designer workflow don't give us Previous values like Event Receivers does. If you don't want to follow Event Receiver path, then try below workaround You need to have a hidden field in the list (Say Previous Owner). Add logic in you New/Edit form to populate Previous Owner field with what value in Issue Owner field. (This ...


1

In your workflow, you would us an if/else branch to build a dynamic string (using the set workflow variable action) based on some condition. The key is to output the strings to the same variable. Then in your email body, you insert this variable into the body. Then when an item is submitted, based on the list metadata, it selects the appropriate string and ...


1

I don't think a workflow is going to get you there, they are pretty bad at aggregating information. I believe you want a digest alert on the list that runs daily. This will pull all the posts together into one email and send that off to whomever you specify.


1

You will need to publish the workflow. When you will open workflow in sharepoint designer, you will find the publish option in Ribbon in workflow settings


1

The basic thing to remember is that declarative workflows (the one’s created by SharePoint Designer) always run impersonating the user who started the workflow Declarative Workflows and User Context in SharePoint designer 2010 microsoft has introducted a concept called impersonation steps where a sections of the workflow can be run under the identity of ...


1

You can use below script for removing all Workflows Associated to a Particular List $SPSite = Get-SPSite "http://siteurl" $Web = $SPSite.OpenWeb(); $SPList =$Web.Lists["ListTitle"]; $workflowAssociations = $SPList.WorkflowAssociations; if($workflowAssociations -ne $null) { foreach($wf in $workflowAssociations) { ...


1

From what I can tell, using one multiple people picker to assign multiple permissions via an Impersonation step is not possible on SharePoint with out of the box options. The workaround I found was to create 10 different people picker fields and set the "Account ID" data to a separate Library column that is the data type "person/group." From there, you can ...


1

I actually figured out a way to do this. Will blog about it sometime soon, but in short: In SharePoint Designer, save the workflow as a template. Download the template (WSP) from the Site Assets library. Import the WSP into a Visual Studio project as described here: https://msdn.microsoft.com/en-us/library/ee231603.aspx Add this new workflow project to ...


1

I have accomplished this the poor mans way by Creating a final Stage called Done. The only thing the Done Stage does is Transition to stage Go to End of Workflow. Then it is easy enough in my List or Library to use views to show WF that are NOT in the Done Stage


1

SharePoint Designer workflows run as System Account but with their permissions trimmed down to impersonate those of the user that initiated the workflow. We faced a similar issue to yours in our SharePoint environment and identified that it was due to workflows being fired automatically by System Account. To get around this, we created an administrative ...



Only top voted, non community-wiki answers of a minimum length are eligible