Tag Info

New answers tagged

0

I came here with the identical symptoms described in the question. This is what solved it for me: In the list that generates the task (So the one the approval workflow is triggered from) --> List Settings --> Advanced Settings: Under Item-level permissions --> Read access ensure that Read all items is selected.


1

Updating the work flow's wsp is little shady. You can use the Update-spsolution to upgrade it but what about the running instance of the Workflow? and it also depend what you change in the wsp. Check this for more information. Upgrade custom workflow in SharePoint


1

Update-SPSolution is what you need, assuming you did not add any new features to the workflow. If you did, you need to use Install-SPSolution Check out this link referencing upgrading workflows: https://msdn.microsoft.com/en-us/library/aa543659.aspx In both, the DLLs and the files will be updated in the GAC the same way, but if the solution has changed the ...


0

You should set the Required outcome to "Approved" and the Default outcome to "Rejected". The note below the Completion criteria says: "This option will make the workflow wait until a specified percentage of a particular outcome is received. If the required percentage is not achieved, it will return the default outcome."


0

Best option is to create an Event Receiver. It is like a database trigger. More info here: https://msdn.microsoft.com/en-us/library/ee231563.aspx?f=255&MSPPError=-2147217396


2

In Sharepoint 2013 one thing called App Step and that it is a mechanism provided to developers of SharePoint 2013-platform workflows (Designer workflows or Visual Studio workflows) to elevate permission of the workflow. you have to do following steps. Allow workflow to use app permissions. Grant full control permission to workflow. Develop the workflow to ...


1

Sharepoint workflows have always run under the context of the user who initiated the workflow process. There were ways to run as the system account in 2007 but that was removed. In 2010 there are impersonation steps that allow actins to run under the context of the person who publishes the workflow. I believe the impersonation steps exist in 2013 as well.


0

Ok, it was a little strange. So using item["Body"] = emailMessage.PlainTextBody; produces the field and text to appear 'normal' in your list. With line breaks and all. But I lost those line breakers when copying that data to another field. So I tried using item["Body"] = emailMessage.HTMLBody;. But now the data in my field looks terrible because shows all ...


0

You can't create DocSet with Sharepoint 2013 workflow but you can create DocSet with Sharepoint 2010 workflow. Kind Regards


-1

Refer my blogpost on this. I have provided sample code.


0

Here is a link for Workflow Email to the SharePoint 2013 Form Library Form item. [%Workflow Context:Current Site URL%]/_layouts/15/FormServer.aspx?XmlLocation=[%Workflow Context:Current Site URL%]NameOfYourLibrary/[%Current Item:Name%]&ClientInstalled=true&DefaultItemOpen=1


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 ...


0

Out of the box not available. You can try Copy Item Extended Activity available in code plex http://spdactivities.codeplex.com/wikipage?title=Copy%20List%20Item%20Extended%20Activity&referringTitle=Home


0

Unfortunately OOB this is not possible. As alternative I would like to offer have a look at Plumsail's Workflow Actions which contain "Create List or Library" and "Create List Item at Any Site" workflow actions. P.S.: I'm one of developers of the product and I definitely recommend to use it.


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) { ...


0

Recently I found myself in the scenario, that send mail using SharePoint Designer when when an item is modified by one of the users from the given list. After Googling it on internet I found this blog which was very helpful. Summary: In such scenario, instead of selecting People/Group from SharePoint site, select workflow lookup for a user, Select The list ...


1

First of all, you should use the ItemAdded event, instead of the ItemAdding, as in the latter you don't have access yet to the SPFile object. That said, here is how to get hold of the file that was added to the library: public override void ItemAdded(SPItemEventProperties properties) { var file = properties.ListItem.File; // open the file either as a ...


0

I have had similar issues with WaitForFieldChange in the past. The workaround I use in these cases is to use a WaitForItemEvent activity and set the EventName to "When an item is updated". The rest you can see in the attached image.


2

If you want to pursue this approach could try this trick. Create a dummy variable and set it equal to the Assigned To field but as a text string. Then you are able to test the 'is empty' against the dummy variable and apply your logic whether to email or not. It would give you some measure of control over what the user sees when they are assigned the ...


0

If you use a task list, then whenever a task is assigned to someone, an email is sent automatically to the assignee. This behavior is configurable from list settings > advanced settings


0

This error in my case was because i had cast exception from guid to string. Error was not self-explanatory nor pointing to exact cause. run time exceptions in the code might also throw this same error message. Because of run time issue it did not deploy the workflow and for the same reason we see activity named ------ was not found


1

I did find a solution.. However I don't know how practical it is. This is what I did: Installed Visual Studio 2012 on my Staging. Updated it with 'Update 4'. Installed office tool for VS 2012. Got the work flow code and deployed it via Visual Studio. (And the deployment worked). Retracted the solution via Visual Studio. Added the .wsp files manually via ...


1

I did find a solution.. However I don't know how practical it is. This is what I did: Installed Visual Studio 2012 on my Staging. Updated it with 'Update 4'. Installed office tool for VS 2012. Got the work flow code and deployed it via Visual Studio. (And the deployment worked). Retracted the solution via Visual Studio. Added the .wsp files manually via ...


3

Before modifying item, you should Disable event firing this.DisableEventFiring(); After finish updating you can Enable it using this.EnableEventFiring(); Identify if event is fired as part of Check-in if (properties.AfterProperties["vti_sourcecontrolcheckedoutby"] == null && properties.BeforeProperties["vti_sourcecontrolcheckedoutby"] != null) ...


0

Not sure how it works with authorization, but check this link for how to construct de REST Url: enter link description here Especially the schematic image is very useful.


0

The best solution to deploy a WorkFlow without using the design manager, is to deploy some event receivers and handle the items event. workflow or event receiver? How to: Create an Event Receiver Table of SharePoint Events


2

@Nk SP has provided the correct references that would help you to copy documents from one library to another including PDF documents. But regarding the last statement that you mentioned in question - "The trigger will be a user ticking a tick box" would not be possible with SharePoint Designer Workflow. SharePoint Designer Workflow is triggered on 3 events: ...


3

You can use the Copy List Item action to copy a document from one library to another. I suggest you these useful links: SharePoint Designer Workflow: Copy a document from one library to another SharePoint Designer Workflow: Move a document from one library to another


0

Try recreating State Service Application by executing following script: $serviceApp = New-SPStateServiceApplication -Name "State Service" New-SPStateServiceDatabase -Name "StateServiceDatabase" -ServiceApplication $serviceApp New-SPStateServiceApplicationProxy -Name "State Service Proxy" -ServiceApplication $serviceApp -DefaultProxyGroup


0

Try to Flush the BLOB cache. $webApp = Get-SPWebApplication "<WebApplicationURL>" [Microsoft.SharePoint.Publishing.PublishingCache]::FlushBlobCache($webApp) Write-Host "Flushed the BLOB cache for:" $webApp Flush the BLOB cache


1

You can use this function: function scriptStart(xSelectedItemId, xSubscriptionId) { //var xSubscriptionId = "{7d028513-b2ea-4ad0-a996-9b807f2beb2e}" console.log("scriptStartWF.js: Ribbonbutton script started, Workflow subscriptionId==" + xSubscriptionId + ", selected Item Id==" + xSelectedItemId) var scriptbase = ...


4

you can use $().SPServices <script type="text/javascript" src="/sites/sprc/Resources%20%20jQuery/jquery-1.3.2.min.js"></script> <script type="text/javascript" src="/sites/sprc/Resources%20%20jQuery/jQuery%20SP%20Services/jquery.SPServices-0.5.4.min.js"></script> <script type="text/javascript"> function StartWorkflow(ItemURL, ...


0

I have the same problem, and worked around it by starting a 2010 workflow from within my 2013 workflow. The 2010 workflow does the lookups and sets parameters with the looked-up values (usually the ID number from the parent list). These parameters are then available to the 2013 workflow.


0

This is the default behaviour. You can change it using following command stsadm.exe –o setproperty –propertyname declarativeworkflowautostartonemailenabled –propertyvalue yes


0

Hi please have a look at example below: public class WorkflowRepository { private InteropService _interopService; private WorkflowInstanceService _instanceService; private WorkflowSubscriptionCollection _subscriptions; public ClientContext Context; public WorkflowRepository(ClientContext clientContext) ...


0

Late to the party I know...but I had a similar issue to this where when my workflow would hit a different stage the approval status would switch back to pending. Because I like the built in approval functionality of a list I didn't want to give that up to roll my own approval workflow, instead I wanted to keep using that built in approval but there were ...


0

Go into your workflow in SharePoint Designer (assuming 2013 as you didn't specify), add an email action and set the desired target (To/CC/BCC) to whichever group you'd like from the 'Select from existing users and groups' list on the left and hit add. It should email the group directly. No need to involve a variable in the equation. If for some reason, you ...


0

In terms of iterating through all sites, in your site collection, and outputting the workflows associated, you can do the following powershell script. $site = Get-SPSite("your-site-url"); $site.AllWebs | foreach { $_.Lists | foreach { $_.WorkflowAssociations | foreach { write-host "Site:" $_.ParentWeb.Url ", List:" $_.ParentList.Title ", Workflow:" ...


0

You can have a custom activity for this https://executespwf.codeplex.com/ Or http://ilovesharepoint.codeplex.com/releases/view/60840


1

If you have SharePoint developper resources, you can create an Event Receiver. That ER would be attached to ItemDeleting and ItemFileMoving events to cancel them in case specific conditions are met. Go with an ER and not with a workflow: workflows are not immediate, they have a huge cost, they're visible in the UI, they're terrible to debug, their ...


1

Your lookup needs to be changed to: Where ID matches task:workflow item id See similar lookup here: https://www.premierpointsolutions.com/training/help-and-how-to-articles/create-a-detailed-custom-task-notification-with-a-sharepoint-designer-workflow/


0

If you can use the SharePoint designer tool, it will allow you to view all the workflows. Then you will be able to easily edit your workflow depend on your need. Some workflows in sharepoint 2007 will not be able to see/edit from the browser.


0

As Jonata has suggested, you can create 2 workflows. In first workflow, you can select "Start Automatically when item is created". So whenever new item added this workflow will trigger. In Second workflow, you can select "Start Automatically when item is modified". So whenever item is updated this workflow will trigger. Here you can check the condition ...


5

You can use the same workflow if you'd like. Just check if the created date is equal to the modified date - if they're the same, then it's just been created. If they're different, you're running in Modified mode.


1

You can use 2 workflow. One when item is created and another when item is updated.


2

The OOTB way to do this would be to create your workflow as you want it and add a stage at the end. In this stage put in a Pause action. You can set this for 1 day (or 24 hours). For your Transition to stage, have it redirect back up to the first stage. The downside of this would be that you have to manually start it that first time. It would also be ...


0

You can use a task scheduling tool such as SQL Server Agent or Windows Task Scheduler and have that execute a PowerShell script that start the workflow. And here is a link to run the workflow in powershell: http://www.thesysadminhimself.com/2013/09/sharepoint-start-workflow-all-items-powershell.html The only other option I can think of is somehow ...


0

This may possibly be a master page issue. Set your master page to the defaults (v4.master) and try to set the workflow again. Once you have created the workflow you can set it back to your preferred master page(s).


0

For reading you should get the results in a dictionary variable using Get Item from a Dictionary action. This action contains three parameters: Item by name or path – specifies the path where the item(s) resides Dictionary – the dictionary variable to retrieve the item(s) from Item – the variable to store the results in. In the Item by name or path ...


0

This seems to be a cache issue. Try to flush the DNS cache on your SharePoint Server (C:> IPCONFIG /FLUSHDNS) Then recycle your "Workflow & Service Bus Services" and then publish the workflow again and hopefully it should work.



Top 50 recent answers are included