v.0.9.1 Release

Well, another quick release, as I introduced a bug in the last one:
Using self-contained executables (which contain all relevant DLLs etc.) was meant to make it easier for people to use PowerDocu. However, it also broke how certain other resources (Word styles, connector icons) were used - the application was no longer able to find them. This has been fixed in this release

As a bonus, I'm also including an update check from this release onwards! Whenever there's a new version, PowerDocu will tell you and point you in the direction of the latest release!

As usual, two files are made available as part of the release:

• use PowerDocu-v.0.9.1.zip if you have .NET Core installed on your machine
• use PowerDocu-v.0.9.1-selfcontained.zip if you don't have .NET Core installed on your machine or if you aren't sure

v.0.9.0 Release

After 6 months, we've finally got a new release! Here's what has been added/changed:

General

• A new, dedicated PowerDocu icon! Gone is the default icon that was used for the application.
• The generated executables are now single files! Instead of having the powerdocu.gui.exe hidden between dozens of other libraries and executables, we now have a single (albeit larger) EXE file. flowdocumenter and appdocumenter executables have been dropped for the moment, as they likely didn't see any usage
• Improved performance in Word for larger generated documents. This also means that we are now supporting Office 2013 onwards 51a902b
• smaller bugfixes

Canvas Apps

• in the Variables section for App documentation, we now also list the screen (besides the control name) on which the control (that is using the variable) is located
• added some app statistics at the top of the app documentation (number of screens, variables, collections, ....)
• started to document custom app logos in the app documentation
• added remaining control icons (Mixed Reality, AI, maps, ...)

Flows

• added some Flow statistics at the top of the Flow documentation (number of variables, actions)
• Update referenced Rubjerg.Graphviz package to latest version, so that the files that were previously manually included are now getting added automatically 480273c

v.0.8.0 Release

This latest release focuses on improvements for AppDocumenter. This release contains the following improvements:

• AppDocumenter - instead of a single, very large Word document, the tool now creates 2 documents: an overview document with high-level information on variables, collections, datasources, resources and controls. And a detailed document that contains the same information as the overview document as well as detailed information about each of the controls.
• AppDocumenter - showing colours visually (actual colour is shown instead of just using the 'text')
• AppDocumenter - grouping control colour properties together
• AppDocumenter - grouping control properties under the properties' categories
• AppDocumenter - showing app resource images directly in the documentation
• FlowDocumenter: fixing issue #26

Full Changelog: v-0.7.0...v-0.8.0

v.0.7.0 Release

• This is quite likely the biggest release since I launched the very first version - while you could previously only document Power Automate Flows, you can now also document Power Apps canvas apps!

Here's what has been added since the last version:

• Document Power Apps canvas app with AppDocumenter! Available as console application as well as part of the PowerDocu.GUI windows application. Included in the documentation are:
  • General information about the app and its properties
  • A list of all global variables and collections, and additionally information for each of them where they are used (which control and which specific control property reference them).
  • A list of all data sources used, as well as a list of all resources
  • An overview of all screens in the app. For each screen, a list of all controls used on it are listed (with icons!)
  • A detailed list of all the controls and all their relevant properties

This is the first release that contains AppDocumenter. While FlowDocumenter is in a quite stable state, AppDocumenter is still considered as an early draft and will undergo various bug-fixing and improvements.

Got any feedback or recommendations? Share them in the Discussions or Issues!

v.0.6.1 Release

This is mostly a bugfix release. It contains the following:

• Using templates didn't work properly and threw errors. This release fixes this issue
• one small new addition: comments added on actions weren't documented previously, but they are now!

v.0.6.0 Release

This release took a bit longer to be published as it contains some bigger updates that required more review and testing. Here's what's in it:

• The generated graphs now use a better top to bottom layout. Previously, while the layout was mostly working topdown, sometimes nodes/containers were added to the right of others, even resulting in some "zig-zag" flows. Now, the generated graphs avoid this and show the proper flow of the Flow from the top down to the bottom without jumping left and right
• The number of connections and the number of actions are now shown in the generated documentation
• Previously, variables were shown in a simple list. Now, more details are shown per variable, including where in the Flow they are used! If you have a large Flow and want to see where a specific variable gets used, this is where you can find a list of those actions
• Tables are now using full document width! Previously, they used whichever width was required for their content.
• Actions now include a section on any conditions for the subsequent action(s). For example, you may configure a specific action only to run if the previous action Failed. This is now shown in the documentation for the previous action
• Some general improvements for the generated Word documentation to enhance compatibility with Word Online. Sometimes documents couldn't get opened or edited online, sometimes the Tables didn't show properly (see e.g. #22). This should now hopefully be a thing of the past, as the generated document is now more stable

You can see a small presentation with visual details of the improvements and updates on my LinkedIn post: https://www.linkedin.com/posts/modery_improvements-flowdocumenter-v060-activity-6872360030369394688-Mxzf

v.0.5.0 Release

Bigger gap between releases this time as I was busy with other things in my life, but finally completed testing and verifying the latest release which contains the following:

• Use an existing Word document (.docx) to use as the template for the generated documentation
• Updated the GUI slightly to use icon buttons (and also make it possible to select the Word template)
• Implementation of a simple notification system as part of the processing: basically, the console application and the GUI are now able to show in more detailed what's happening during the processing
• Added the timestamp of when the documentation was generated to the Flow Metadata section

As usual, for any comments and feedback, please log an issue or discussion item

v.0.4.1 Release

This release mainly fixes some bugs with only some minor improvements, including

• properly parsing connection references (e.g. #19 )
• showing Trigger details in the table format (#15)

v.0.4.0 Release

A smaller update that contains the following improvements:

• Actions are now listed in alphabetical order
• added a new section that lists all Variables towards the beginning of the documentation
• Flows with a lot of depth (deeply nested actions) couldn't be parsed. Increased the MaxDepth from 64 to 128, which should be sufficient (see #17)
• Fixed a case where edges between nodes/clusters were missing (see #16 )

Full Changelog: v-0.3.0...v-0.4.0

v.0.3.0 Release

This release contains a range of valuable improvements and additions.

Windows application PowerDocu.GUI added to start Flow processing

Previously, the console application had to be used to generate documentation for a Flow. In this release, we now make PowerDocu.GUI available, a Windows application that helps to generated documentation without having to use the console application.

Processing exported Solutions

Previous versions only allowed to parse a single exported Flow. However, very often Flows are contained in Solutions, and there may even be multiple Flows in a Solution. It is now possible to use either a Flow package or a Solution package as input. For a Solution package, all of the Flows contained inside will be processed and documented, each with its own set of documentation.
Visit the Examples page to see a documented Solution

Improved Graphs

The graphs in previous versions were often not very clear when it comes to order of execution, as the arrows pointing from one component to another were not always correct. With this release, this issue has been fixed. More information is listed in (#5)

Less raw JSON output, more tables!

Parsing has been improved, and details of the Flow (especially actions) are now shown in table format instead of simple JSON output.

New Contributors

• @cakriwut made their first contribution in #13

Full Changelog: v-0.2.0-alpha...v-0.3.0

For any issues or suggestions, please provide your feedback as an Issue or Discussion