Hot answers tagged

2

After researching this error, I noticed there was no simple solution. Each person solved the errors in different ways. I have mentioned every solution I found. The easiest solutions are listed first. Solution 1: The new changes to the SharePoint 2013 workflow, there was also changes made to which account is used to write logs to the Workflow History list. ...


2

The meaning of the lookup action in your screenshot is to find the “Manager” field from the second list which the value of this column (is returned as email address type) is equals to the value of “Responsible People” field of the current Item (is returned as string type). I logged the different returned value type of a person field for your reference: ...


2

It looks like at some point, you tried to configure Workflow Manager to work with SharePoint (so you can create/deploy/use 2013 mode workflows). To do so, you set up Workflow Manager (a dedicated -free- product) and then connected SharePoint to it. Workflow Manager generally sets up on http://<WFserver>:12291/, where WFserver is the Web server you ...


2

You don't get workflow scheduling with the ootb workflow engine. We had a very similar requirement where list items needed to be checked daily to see if they were due/overdue and send notifications as such in O365. It was a workflow previously but didn't work well. We converted it to a console application that is scheduled to run every day. The console ...


2

I would personally just restart the approval workflow so that the first person rejects the item. This way the workflow status and history accurately reflect the intent should it ever need reviewed.


1

I don't think workflows would be the best approach for this. Is there a reason why the documents need to be checked out? If it's to prevent other users from modifying the original documents, you might look at removing the ability for users to modify content instead. I haven't attempted with going backward in versions, but have a look at Export-SPWeb and ...


1

I don't believe this is possible. SharePoint designer actions are limited in scope to the current site's artifacts. In Codeplex you have the SPDActivities that among others enables you to copy or move items and files across sites. http://www.codeplex.com/SPDActivities Source


1

Out of the box, SPD doesn't allow you to do this. As a solution, you can use 3rd party components. I would recommend you to use Workflow Actions Pack it contains Copy Document from Library workflow action which can do it. I'm one of the developers of the product, so I'm glad to recommend it.


1

I would suggest a timer job or a console application to handle this. Pausing until a date won't have a huge performance impact as the workflow gets serialized to the database until it is time to do something. This big problem is that if that date changes, it doesn't affect the workflow that is currently running on the item. We have converted several ...


1

No out of the box solution. You need to create custom solution for the same like Timer job or Visual Studio workflow. PFA url to create and deploy timer job. http://www.codeproject.com/Tips/634208/Create-and-Deploy-Custom-Timer-Job-Definition-in-S


1

I've been stuck on the same problem as Emaborsa. It's not well documented but Status and FormData (and Completed) are important fields. Status field in particular has to be set to "Approved" even though the field's valid choices for my install shows as <Field Type="Choice" ID="{c15b34c3-ce7d-490a-b133-3f4de8801b76}" ...


1

An issue is solved! I tried the same WF at a site level (previously it was at a list level) and it completed without any problems. After that, I recreated a list and bound the WF to it. Now I suppose that the issue was related to some permissions on the original list. Thanx! Alexander


1

Instead of pointing at /SiteAssets/mydata.txt I pointed at /_api/web/GetFolderByServerRelativeUrl('/SiteAssets')/Files('mydata.txt')/$value and used these headers: Accept: application/octet-stream Content-Type: application/octet-stream X-RequestDigest: <obtained in an earlier request> I was then able to process the response (which I left as JSON) ...



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