Mats Hindhede

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mats Hindhede shared this idea  · 
  2. 225 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mats Hindhede supported this idea  · 
  3. 87 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Mats Hindhede commented  · 

    By far the most important thing to report on workflows is their name and location, of course. You need a proper list with the name and location of each workflow in the web app or site collection. This is an obvious need and SharePoint OOTB doesn't help you one bit with that. It's also surprisingly hard to script, since 2010 and 2013 WFs are handled differently. A script that lists 2013 WFs and their locations is quite different from a script that lists 2010 WFs, and also more complicated. Of course, you don't care if they are 2013 or 2010 WFs, that's just MS messing things up. You just want to know where the heck your workflows are, especially if there are hundreds or thousands. Apart from name and location, it would also be nice to know if the workflows are OOTB, SPD, 2010, 2013 or Nintex and who created them, how many running instances they currently have, how they are triggered etc.

    Mats Hindhede supported this idea  · 
  4. 40 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

Feedback and Knowledge Base