Hi,
I want to document the flows I create with PAD.
The more flows I create, the more I need to document them.
Can you tell me what you think of document them?
Kind Regards,
Toru
Announcements
Hi,
I want to document the flows I create with PAD.
The more flows I create, the more I need to document them.
Can you tell me what you think of document them?
Kind Regards,
Toru
Hi @Agnius
Thank you for your reply. I apologize for the late reply.
This issue has been resolved through communication with @VishnuReddy1997,
but it's unfortunate that there is no documentation function like other products.
I look forward to seeing you again.
Kind Regards,
Toru
The feature for creating flowcharts automatically only applies to cloud flows. No such thing exists for desktop flows. You will need to document them manually.
I would recommend creating an initial description and then a changelog, where you simply define the changes made with dates on when that was done. I generally don't do flowcharts, or, if I do, I only do them at a very high level, where minor changes would not affect them anyway. But a written description and a changelog is very important.
Hi @VishnuReddy1997 ,
It seems that my current contract does not allow me to transfer flows.
I could create flowcharts using Excel or similar, but I'm worried about maintenance when the number of flows increases.
I'll look into this a bit more.
Kind Regards,
Toru
Hi @Toru-san ,
I too heard about that.Please find the below link how you can do that.
(Note:- if you got your solution you can mark as solution and gives kudos)
Thanks & Regards
Vishnu Reddy
Hi @VishnuReddy1997 ,
Thank you for your reply.
I heard a rumor that you can transfer flows to Microsoft 365 Visio and document them.
I will check if I can use it with my current contract and give it a try. Thanks.
Kind Regards,
Toru
Hi @Toru-san ,
Yes, you’re right. As the complexity of flows increases, it becomes more important to have a structured way to document them. While Power Automate Desktop (PAD) does not have a built-in documentation feature like some other RPA tools.
As per now i am just building a flow chart and saving it.
(Note:- if you got your solution you can mark as solution and gives kudos)
Thanks & Regards
Vishnu Reddy
Hi @VishnuReddy1997 ,
Thank you for your reply.
I have already added the comment action and input.
I tried to turn my daily work into a flow this time, but the number of actions and subflows was more than I expected, and I sometimes forgot about them when I checked later.
It would be good to have a documentation function like other RPA products. Would you aware of this?
Kind Regards,
Toru
Hi @Toru-san ,
Documentation is very neccessary to debug,maintaince,understanding the code in the future.
Here are some tips on how to document your flows:
1.Comments: Use comments in your flows to explain what each step does.
2.Naming Conventions: Use clear and descriptive names for your flows and actions.
3.Flow Description: Include a description of what the flow does at the beginning.
4.Change Log: Keep a log of any changes you make to the flow.
5.Screenshots: Include screenshots of complex steps or configurations.
(Note:- if you got your solution you can mark as solution and gives kudos)
Thanks & Regards
Vishnu Reddy
Michael E. Gernaey
497
Super User 2025 Season 1
David_MA
436
Super User 2025 Season 1
Riyaz_riz11
244
Super User 2025 Season 1