Workflow form changed from InfoPath form to aspx form
For a workflow based on SharePoint Designer 2013 (WF4) and Windows Azure Workflow, SharePoint creates aspx forms instead of InfoPath forms that were created by SharePoint Designer 2010 (WF3.5)...
View ArticleSpecial characters shown as hexadecimal code
If a local variable name contains a special character (such as ? or #) in a SharePoint Designer 2010 (WF3) workflow, those characters are shown as a hexadecimal code. Special character or reserved...
View ArticleCan not use Assignments type field in WF3 workflow with Task Process
You can’t use Assignments type field as a parameter when you invoke a SharePoint Designer 2010 (WF3) workflow that has a Task Process related action in it. Workaround Use a SharePoint Designer 2013...
View ArticleSome of workflow actions/conditions aren’t available in SharePoint Designer 2013
Some of workflow actions/conditions aren’t available. Major reason for this disparity is because of the change in the workflow platform, which are shifting to SharePoint Designer 2013 (WF4) based from...
View Article
More Pages to Explore .....