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

v.0.2.0-alpha Release

This updated release brings with it a few improvements:

• Better output of "Expression" nodes, which are e.g. used in Condition actions (If). Instead of the expression code, we are trying to display the expression in a table format.
• Handling of special characters in filenames - some characters (e.g. diacrits such as German Umlauts, Chinese, emoji, ...) don't work properly with file and folder names. They now get replaced with a dash (-)
• the output folder and the generated files are now created in the same folder as the Flow package (zip file) instead of the program directory
• you can now call the program from other locations as well (e.g. from a different folder). Previously, this didn't work as the related resources were loaded from a relative path from where the program was executed from
• Actions now contain links to "subactions and elseactions" (that is, any action that is to be considered "inside" the current action, such as the actions executed within a Condition (if) action) within the Word document

However, it is still considered to be an early version, and it is expected that it will not always run successfully. For any issues or suggestions, please provide your feedback as an Issue or Discussion

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

Initial alpha release v.0.1.0-alpha

This is it! The first version of FlowDocumenter is now available!

• Please refer to Installation & Usage on how to use the tool. Also, please review the tech requirements and choose either the regular version or the self-contained version
• Please provide feedback and report any issues that you can encounter! This way the tool can be enhanced and improved over time
• Most importantly, please keep in mind that this is an early version. It has been tested with a limited set of Flows, and it is far from being feature complete.

Looking forward to hearing your feedback!