Solved

Debugging a sharepoint designer 2010 workflow

Posted on 2014-09-04
3
174 Views
Last Modified: 2015-03-19
Could anyone  suggest me how to debug the sharepoint designer 2010 workflows.
Like in visual studio we have break points option to debug a .net code.
0
Comment
Question by:asrithap
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 19

Accepted Solution

by:
Montoya earned 500 total points
ID: 40304333
there are a few methods.. here's a couple:

write to history log at set intervals. Write the value of your variable or write yourself a message. This tells you where things are in your workflow process.

The other method is essentially the same thing, but create a column with a text value. As a step for each workflow state, write a value to that column.

Values can be like:

started
criteria 1 met
email sent to user
list item written

etc...   the more checkpoints you add, the quicker you will get to what is going wrong.

The most expensive option would be:  Get Nintex workflow... wow, it's expensive, but the ROI is pretty sick. It also has a built in feature that can show you and/or the users exactly where the workflow process is... visually! It's pretty dang useful!
0
 
LVL 12

Expert Comment

by:Ramkisan Jagtap
ID: 40305394
Unfortunatley you cannot debug SharePoint Designer created workflows easily (unless you actually debug the SharePoint codebase).

I suggest you add some logging features to the Workflow, examine the ULS logs, check that your workflow history is cleaned up properly etc.

(If you updated your post with the Visio diagram of your Workflow it could possibly help us help you)
0
 

Expert Comment

by:Keyboard Cowboy
ID: 40677282
Most of us use a lot of Log statements to debug but the problem if the workflow fails, it may not write out all of the log messages for you to look at.  (You can trust that you'll see all of the log messages even though the log statement was executed).  this is only true for a failed workflow.
0

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Prevent SQL Injection 4 123
ASP.NET: Validation of Viewstate MAC failed 3 132
how to extract window origin in spring 2 83
Survey branching tutorial 11 75
Thoughout my experience working on eCommerce web applications I have seen applications succumbing to increased user demand and throughput. With increased loads the response times started to spike, which leads to user frustration and lost sales. I ha…
Real-time is more about the business, not the technology. In day-to-day life, to make real-time decisions like buying or investing, business needs the latest information(e.g. Gold Rate/Stock Rate). Unlike traditional days, you need not wait for a fe…
Wufoo.com provides powerful tools for surveying targeted groups, and utilizing data from completed surveys to find trends, discover areas of demand or customer expectation, and make business decisions on products or services.
Use Wufoo, an online form creation tool, to make powerful forms. Learn how to choose which pages of your form are visible to your users based on their inputs. The page rules feature provides you with an opportunity to create if:then statements for y…

737 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question