13

The simple process of setting item level permission is not available for SharePoint 2013 workflows. The only way I was able to do was through REST api called under Appstep. There are 2 calls made: BreakRoleInheritance AddRoleAssignment This blog by Yuri Leontyev​ ​ over at spssite.pro can be a good start. Excerpt: BreakRoleInheritance​ ...


11

The critical component when failing over a Workflow Farm to a New SharePoint Farm (In the same domain or otherwise) is that the new SharePoint Farm must have the same Realm as the original one. Realm is by default identical to the SharePoint Farm ID, but can be changed using Set-SPAuthenticationRealm -Realm FarmIDoftheOriginalFarm. Few Caveats: You will ...


11

You can use the following cmdlets: $site = (Get-SPWebapplication -IncludeCentralAdministration | ?{$_.IsAdministrationWebApplication}).Sites[0] $wfmProxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq "Workflow Service Application Proxy"} $wfmProxy.GetWorkflowServiceAddress($site)


7

I found resolution to this issue, like everything else the log entries were bit confusing and the resolution was fairly simple. Following two services are responsible for all the communication betweek workflow clients and workflow manager farm. This two services are setup for "Automatic (Delayed Start)". This services didnt start when the servers were ...


7

I had this issue in past when configured the workflow manager. In my situation, I ends up doing the following. I removed the workflow manager service application using this command...Get-SPWorkflowServiceApplicationProxy | Remove-SPServiceApplicationProxy Now i I run the same register command with -force parameter like this.Register-SPWorkflowService -...


5

This is because SharePoint 2013 Workflows are hosted on Workflow Manager. So you need to add a new workflow subscription to Workflow Manager. I found the following articular useful to workout how to do this. Although this uses the CSOM rather than PowerShell. Working with the SharePoint 2013 Workflow Services Client Side Object Model Here is a ...


5

This issue occurs because of the Workflow Resource Management Store version value at [WFResourceManagementDB].[dbo].[StoreVersionTable] is still 1.0.2.0 despite you have installed CU3 that should work with Workflow Resource Management Store version 1.3.0.0. To overcome this issue , you will need to make the two version identical at [WFResourceManagementDB].[...


5

There is no "upgrade" to workflow 2013 engine. It's an optional addition to a SharePoint 2013 farm. Even after setting up workflow manager 2013, you will still have the 2010 workflow engine available. You will just also have the 2013 workflow engine available. Since Workflow Manager 2013 is not currently installed on your 2013 farm, you must begin ...


5

To register a workflow service to a specific site collection you should run Register-SPWorkflowService cmdlet that requires providing the below parameter values -SPSite it denotes to the site collection URL that you need to use the workflow service on it. Note: It seems that each site collection needs to be registered with workflow service. But ...


5

Whether to go with HTTP o HTTPS for WFM in a SharePoint 2013 Production Farm? It's heavily recommended to go ahead with HTTPS By the way, You have 4 possible scenarios to install Workflow Manager for SharePoint farm Workflow Manager is installed on a server that is part of the SharePoint 2013 farm. Communication takes place by using HTTP. Workflow Manager ...


5

As a short answer, It's possible but NOT supported as well as it will NOT achieve High Availability! The supported Workflow Manager topology consists of 1 server or 3 servers. Only 3 servers workflow farm topology provides High Availability and The farm with 2 or 4 servers can be built! However, it’s NOT supported, and it will NOT provide High ...


4

I know this is a bit old, but I figured this can be helpful for other people that may run across this post. I resolved the issue by using the WFFarm and SBFarm PowerShell commands. Be sure to run this from the account that has elevated privileges on the SQL Databases (usually the farm account): $WF = Get-WFFarm ##Current WF Config $WF.AdminGroup = "domain\...


4

Okay, after weeks of struggling here I found the solution. I just need to activate Workflow can use app permissions in Site Settings and create elevated permission. I followed this link: Create a workflow with elevated permissions by using the SharePoint 2013 Workflow platform Hope this helps!


4

You can't trigger 2nd workflow automatically (for now, maybe MS will solve recursion issue in the future), but there is a workaround to call it manually from 1st workflow described here: http://blogs.msdn.com/b/sridhara/archive/2014/08/19/fix-sharepoint-2013-workflow-recursion-prevention-part-1.aspx You need to have at least May 2014 CU for this to work. I ...


4

I found solution. The problem was caused by library Microsoft.Activities.dll (which is by default placed in c:\Program Files\Reference Assemblies\Microsoft\Workflow Manager\1.0\). After some update, it has a newer version then Workflow Manager Backend. I found, I had 1.0.40131.0 version of workflow manager backend (c:\Program Files\Workflow Manager\1.0\...


4

Just an issue with the parameter type; the itemID needed to be the ID, not the GUID. Documentation here: https://msdn.microsoft.com/en-us/library/dn683475(v=office.12).aspx


4

Got in touch with MS about this - as I thought, the 2013 workflows aren't exposed to the IMP interface because of the different engine type. You use 2010 workflows or nothing.


4

Workflow Manager is only required for the new '2013' style workflow (.NET 4.0) functionality. SharePoint 2013 still has the 2010 workflow engine baked in. If you only require the older 2010 style workflow functionality there is no requirement to add Workflow Manager to the farm. Note that Workflow Manager is required if you wish to use 2013 style ...


4

There are 4 possible scenarios to install Workflow Manager for SharePoint farm : Workflow Manager is installed on a server that is part of the SharePoint 2013 farm. Communication takes place by using HTTP. (Impact Low Performance & Security) Workflow Manager is installed on a server that is part of the SharePoint 2013 farm. Communication takes place by ...


4

Is it possible to start a workflow, from JSOM? Yes, it's possible. Do I need Workflow Manager in order to start workflows from JSOM? Yes, Workflow Manager is a mandatory prerequisite to be able to Start workflow via JSOM. otherwise, you will get Null object when executing SP.WorkflowServices.WorkflowServicesManager Is Workflow Manager available for ...


4

Keep in mind WFM is more or less a dead-end product, so lack of updates would be expected. There is one additional CU, CU5, which is available from Description of the Cumulative Update 5 for Workflow Manager 1.0.


4

Looks like permission issue, Please make sure Service accounts (Running the services) has right permission on the Workflow & Service Bus databases. also try to stop the SB host and then start it. using Stop-SBHost & Start-SBHost.


3

You need to run these commands in the workflow manager powershell console not SharePoint power shell console. On the Workflow manager server: Start > All Program > Workflow Manager > Worfklow Manager PowerShell from here run as administrator. I did the testing on my laptop when i Install the Service Bus 1.1 after i am able to run the Set-SBfarm ...


3

Before your foreach loop, assign a new dynamicValue to the d/results property of the GatePassDetailsProperties dynamicValue (or reuse and reassign the current dynamicValue). Then, for each item, you'll be able to get Title, Nationality, JobTitle, PassportNo as the top-level property. Also, make sure your assignments are going to variables and not the ...


3

I struggled with the SP.WorkflowServices.WorkflowServicesManager as well, trying to do the same thing (start a workflow from a button on the Display form). I don't remember exactly what my problems were, but I ended up resorting to using the REST API and jQuery AJAX: function getWfSubscriptions() { var listID = _spPageContextInfo.pageListId; var ...


3

The Workflow Manager farm can be a hassle to get right, but I assume when you browse to http://localhost:12291/ with IE running as Administrator, you see the underlying XML notation? Also, when you look at the Workflow Service Application Proxy in Service Applications on URL http://CentralAdminURL/_admin/WorkflowServiceStatus.aspx, you see Workflow is ...


3

if you do a get-command from the powershell do you see it listed in there similar to this screenshot: if not then follow these process Configuring SharePoint 2013 to support workflow Management Service y default, in SharePoint 2013, Workflow Manager Service is not configured. Workflow Manager Service has to be downloaded, installed and configured manually ...


3

If you want to get SharePoint 2013 Workflow (subscription) you need to get it from WorkflowInstanceService and not from SPListItem. This is what I did to get instance of that Workflow and check its status. You will need to have this reference Microsoft.SharePoint.WorkflowServicesBase and using Microsoft.SharePoint.WorkflowServices; directive. public void ...


3

As the reported PowerShell error "The term is not recognized", you are using Windows Powershell, not SharePoint management shell. In Windows Powershell, before running the SharePoint cmdlet, you should add SharePoint Snapin as the following Add-PSSnapin Microsoft.SharePoint.PowerShell Also, make sure that you have installed the Workflow Manager ...


3

In short, Yes, it is supported. For more details check, How to install and configure Workflow Manager on Windows 2012 R2 Workflow Manager Supportability with SharePoint Server


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