I've been working with Workflow Manager (in SharePoint 2013) for a while and about to finish a project with few 2013 workflows. Few issues listed below:
- Calling custom SharePoint WCF service from workflow running in SharePoint requires 'anonymous access' to be enabled. If anonymous access is not enabled then the workflow gets access denied error.
Problem Reported.
- Modifying and redeploying workflow from Visual Studio 2012 doesn't update workflow. Though few reported workarounds but these works sometimes, sometimes don't.
Problem Reported.
- After installing March Update, sometimes workflow manager can't access database.
Problem Reported.
- Enough activities are not there to work for a big projects. For example, if someone would like to call an external service with URL encoding some parameters, there's no activities to encode URL inside workflow.
Problem Reported.
- Even if workflow activities exist, they don't have enough options to configure. For example, n SingleTask activity in SharePoint, there's no way not to send 'assignment' notification for a task. When a task is assigned to a user, user get notified whether whether notification is disabled in the list level or not. Problem Reported.
These are all the issues I've been through for my current SharePoint 2013 project. And the scariest thing is that when you deploy workflow in test/prod and it fails, you get mad to find out what went wrong. If the workflow fails you need to search through your whole farm, workflow manage event viewer, log files, sharepoint log files, workflow database etc.
I would really like to know when the workflow manager will be ready enough? Is there's release plan for major bug fixes or improvements? If we would know what going to be fixed/released and when, we could plan for our projects accordingly whether we'll use workflow 2010 or 2013 in our next SharePoint 2013 projects.
Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com