Answered

How to Document the Flow you created in Visio

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

How can we create a Visio document (like we could from SharePoint Designer) to provide documentation to management about what a flow does. I know you can do it manually, but I would like to make it professional like with the same Icons used in the Flow and can not find them anywhere to download. Also this will take up a lot of time when it was simple in SharePoint Designer.

Example: These guys, I guess I could take a screenshot, but they will not look as nice

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

v-micsh-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous,

Based on what I know, there is no corresponding images to download for those triggers or actions used under Microsoft Flow.

If you would like to generate a Visio document, then the best approach that would work is to capture the screenshot when performing Microsoft Flow testing.

You may consider submit this as an idea under Microsoft Flow idea forum, as a content request for those images or icons used within Microsoft Flow.

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Regards,

Michael

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Thank you @v-micsh-msft, I found someone already posted this in Ideas: https://powerusers.microsoft.com/t5/Flow-Ideas/Export-Flow-to-Visio/idi-p/23205

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Looks like what's been published just goes from Visio to Flow -- what about taking what's in Flow, and getting that into Visio? It seems like the implementation required maintaining BOTH the Visio and the Flow versions of the diagram, but the one in Flow is the authoratative one since it has additional context not found in Visio once deployed and operating. Personally, I would have enabled the "export to Visio" capability first and taken some steps to improve the Flow authoring experience where specific pain points exist.

Is the strategy to grow Visio into the unified design surface for Flow? that's the only case I can think of for why export to Visio would be de-prioritized. Thoughts?

Was this reply helpful? Yes No