{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 我命由我不由天 的问题《How can I troubleshoot Sharepoint workflows?》','https://www.manongdao.com/q-695364.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'm a bit lost here and I can't find much documentation.
相关问题
- Sharepoint multiple connections to a web parts
- Trouble with OR in Sharepoint CAML
- List Microsoft Sharepoint Sites with Microsoft Gra
- How to use VBA or Powershell to export lists from
- redirect using itemreceiver sharepoint
相关文章
- Forcing a TFS2010 workflow build to FAIL instead o
- Contributing using git
- File Upload to SharePoint 2013 using REST API
- Passing file object to Web API from Javascript
- How can I iterate recursively though a sharepoint
- SharePoint, VirtualPathProviders and Application R
- Saving a document to SharePoint brings up “Web Fil
- Rehosted Microsoft Workflow Designer UI
Assuming you are talking about SharePoint Designer workflows? You can convert them into .NET workflows following these steps. From there, you can debug them. I haven't tried it myself (yet).
I guess you've already seen this :-)
Troubleshoot workflow errors
No one mentioned the obvious resource for SharePoint Debugging -- the ULS logs. A ULS viewer filtered on a level of "unexpected" will usually show you the logged cause for the failure.
.NET workflows or ones created using SharePoint designer?
I've only got latter experience and they aren't really easy to debug, you really just have to do them 1 step at a time and test up to each step.
You can view the workflow state as well in SharePoint when you go to the List Settings (sorry I don't have a WSS machine to look at currently).
This article has some great debugging tips for SharePoint. It gives a good general approach to development/debugging. Here are a few of the tools that are referenced:
As stated, your only real choice for debugging SharePoint Designer workflows is by either going through the painful process of converting them into .NET worklows, or doing things like writing out the History List after every single step so you can see what is failing.
However, even .NET workflows are very difficult to debug in VS2005. In VS2008, they added the ability to more easily debug workflows developed using that environment.