Process Builder OneView

How often have you gone back to a Process Builder flow and tried to see what all of your selections and settings are?  Have you struggled with trying to create documentation for your Process Builder flows?  How many screen shots do you need to take to try and share your Process Builder?

See below for some of the challenges you face when reviewing your Process Builder flows.

  • You need to hover just to see the full name or description of your Process Builder.Hover_1
  • You can’t see your full field names unless you hover over each one.
    Hover_2
  • Values and formulas are hidden as well until you hover over them.Hover_3
  • In order to see the full name of an action you need to click on it.Click_1
  • Certain settings are not visible unless you click to expand.Click_2
  • In order to see your Criteria logic, you need to deactivate, clone and edit your Process Builder.Click_3

I was frustrated with all the steps to go through just to see what I had already created in my Process Builder flows.  I wanted a better way to look at and document my Processes.

Realizing that the details of each flow were stored in my Salesforce organization as XML based metadata, I wondered if there was a way I could extract this data then recreate an entire flow diagram and a descriptive report of all of my criteria, actions, formulas and settings.

XML.PNG

I was able to extract all of my flow metadata into individual files using the developerforce.com Workbench utility.

Workbench

The next, and biggest, challenge I faced was what to do with that data and how could I put it into a format that was readable and useful.  I decided that Excel & VBA offered a way to parse the XML data and had the formatting power I was looking for to create the output I needed.

I started with the diagram itself.  I wanted to be able to see the full names of the Criteria and Actions on the diagram.

Diagram_1.PNG

With a lot of testing, I made sure I could handle multiple scheduled actions, different action types, large numbers of actions and different types of branching.

Diagram_2

 

 

The diagram is only a small part of everything you need to see to document your flow so I extended the output with a complete description of all of the steps and settings in the flow.

 

 

Details_1

Once I had the diagram and the details created, I added additional options to print the output or create PDF files, offer portrait or landscape orientation, wrap or shrink text to fit and scale to single or multiple pages.

OneView Screen.PNG

I also provided options to display the diagram and the details together on the same page.

 

Both_1
Diagram on Left side

 

 

Both_2.PNG
Diagram on Right side

 

This was a challenging yet interesting project and with this utility, I can now see my entire Process Builder flow in a single, easy to follow document.  It is truly OneView for your Process Builder flows.

Update: Process Builder OneView is now available as a subscription.  $99/year per user.

OneView Product Page

 

26 thoughts on “Process Builder OneView

  1. Hi Eric,

    What a great idea, the XML data into Excel looks great for the the OneView, I would like to use this, so I was wondering if you have an samples you could share for the VBA part in particular for Excel if ? or a download perhaps ? Apologies if I have missed this somewhere..

    Thank you

    Liked by 1 person

  2. Very clever solution to all of the hopping around that is currently needed to document processes. I too, like Chris, would be interested in using your solution -if this is something that you might want to share.

    Thanks for the article!

    Like

  3. Eric,
    This is terrific. How can i get access to try it out? Like Chris, I need a little more information around the edges to help me do this myself.

    Thanks for sharing,
    Jane

    Like

  4. This is really fabulous. Can you tell me more about how the licencing works? I’m an independent admin consultant – and so I have multiple clients and work with multiple orgs. It would be so helpful to be able to document and parse the PBs I create, but ideally, I’d rather not have to purchase a separate license for each client … Let me know if you’d be willing to discuss alternate licensing options.

    Thanks!

    Like

Leave a reply to Maria Belli Cancel reply