@JoeCat
It is something that keep change with time. I keep finding better ways and smarter way, therefore it is good to start with one and then keep upgrading it with time.
I'm using company logo, I have a symbol that I'm using to identify that I created the WF. Title, client name, version keep updating the version if modifications were made, and then the date when it was updated
High level description of the automation, what it does or expected to do
Line of business
Keep annotation for each of the tools, what it does
Grouping part of the WF in containers and then naming what this is, such as transformation invoices data, setting up date, data preparation for output, etc - to get the idea what each part is doing.
Sometimes when needed adding notes
I will try to keep it need and organized, will Wireless most connections so it will be neat.
Add colours to containers to visualize then different sections of the automation
You should add anything that will help you remember what this automation does, when return to it after one year or longer so it will remind you what you did and where to find the different things, will speed up maintenance or update.
When updating a new version I'm saving as so I always have the original or previous version.
Building a WF is a creation, personal creation and need to fit you and reflect you, so work it out till you find what you like it to be to represent you.
