Tag Info

New answers tagged

1

One of the benefits of the 2013 workflows is that they will run in the cloud, but this benefit does not apply to a code based custom activity. Also, any deployment instructions that involve manually copying files to particular directories are problematic, as a year from now an admin may extend the farm with another server, and needing to also copy the dlls ...


1

Yes, as long as it stay a SharePoint 2010 workflow in SharePoint 2013. Just deploy it just as you would and you should be able to use it.


0

some times due to some workflows SharePoint designer may give above error. you can find the custom workflow by going through your site collection --> Galleries --> solutions and deactivate the custom solution. Your SharePoint Designer becomes free of that error.


0

you can save the confirmation date value in some variable and use for statement then Wait for Confirmation date' to be greater than so that you don't have nay null value.


1

To get the created by, you first need to get AuthorID. After that you need to use LookupSPuser to get the name of the user from the ID. For getting the Title, in entity type : List item of "Your list name". You should get the Title property.


1

I made some progress in achieving this. I am now using the app only token ('SharePoint App' user) to access the SharePoint online site from my custom WCF service. I am using following code: string realm = TokenHelper.GetRealmFromTargetUrl(sharepointUrl); string accessToken = TokenHelper.GetAppOnlyAccessToken(TokenHelper.SharePointPrincipal, ...


0

I also implemented Custom workflow activity using sandbox solution. I am basically calling custom & outside domain WCF service which does some sorts of file IO operations and it usually takes longer to execute. I never encountered timeout issue with this so far. I agree with Chris that it may be the server where your code is executing is slow. I could ...



Top 50 recent answers are included