v.2.0.0 Release

After a longer hiatus, I am excited to announce the next release of PowerDocu. While there are few functionality changes, the move from .NET Core 3.1 to .NET 8 as well as using the latest versions of all referenced libraries mean that this release receives an updated major version number to highlight the significance of these changes.

This release contains the following changes

** General**

• Updated to use .NET 8
• All referenced libraries have been updated to their latest versions
• Generated graphs (SVG, PNG) now use Helvetica font by default

Flows

• Adding a label to edges that are in a "Switch" and showing switch condition on Switch nodes, making it easier to see more details on the Switch options

Solutions

• Creating a Graph that shows the relationship between Dataverse tables in the solution
• Fix for issue #110

CLI

• it is possible to run PowerDocu.GUI.exe from a command line interface (also, Azure DevOps pipelines)! Thanks to @a1dancole , this functionality can now be tested. Check out #111 (comment) for a few more details - a more detailed guide will come in the upcoming weeks

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.1.2.4 Release

This release contains the following changes

Flows

• The generated graphs for Flows now try to follow the colour scheme from the Power Automate studio. This is an early version, and not all colours are correct yet. But it is a beginning, improvements to take place regularly from now onwards!
• The graph for Flows that had multiple parallel actions after a trigger was not correct, only one node was connected to the trigger (as reported in #102). This has been fixed. Additionally, merging parallel actions also weren't rendered correctly, this has been fixed as well

Solutions

• There was an issue with Dataverse tables not getting processed correctly (see #97). This has been fixed

Canvas Apps

• smaller fix that helps with app parsing (code in comments is no longer parsed, as it should be) modery/PowerDocu.Common@6e0a038

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.1.2.3 Release

Only 2 smaller bugfixes are included in this release

Flows

• Fixing issue #93, where trigger conditions were not properly documented

Solutions

• In rare cases documenting Dataverse tables ran into an exception. This has been fixed

Canvas Apps

• no updates

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.1.2.2 Release

Added 2 new features as part of this release!

Flows

• The sort order of Flow actions in the documentation is now configurable. You can choose to have them sorted by name (which is the default), or you can have them sorted by their order of appearance - that is, roughly from top to bottom (similar to how they appear in the designer).
• bug fix: Flow action descriptions were not always properly rendered if they contained invalid characters. This has been fixed

Solutions

• Dataverse tables are now documented with their columns! This first release provides the table's name and description, and some details for the columns in the table

Canvas Apps

• no updates

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.1.2.1 Release

This is mostly a bugfix release and contains the following stability improvements:

Canvas Apps

• no updates

Flows

• some Flows were not properly documented. Actions that were using arrays sometimes failed to be documented, sometimes the values were not documented properly. This should be fixed now. (#68)
• Notes on Actions are now rendered in the diagrams. Planning to make this a configurable option in the future

Solutions

• stabilised parsing of privileges
• stabilised parsing of solution details (mentioned in #53)
• started to prepare documenting Dataverse tables. No real big change here yet, likely in the next version

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.1.2.0 Release

This is a smaller release (and only while doing a final review before pressing publish did I realise that a v.1.1.1 might have been better) which only contains some smaller things

Canvas Apps

• no longer documenting the "TableDefinition" property for datasources, as it can become too large. Will possibly document it separately in the future, but skipping it for the moment
• datasources are now documented in separate Markdown files

Flows

• documenting the Foreach property of "Apply to each" actions, showing on which items the action runs

Solutions

• adding more detail to Security Roles. Table names are still showing the internal name only, to be enhanced in a future release
  

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.1.1.0 Release

Happy New Year & 新年快乐!

I initially planned to get this release done around Christmas, but it is now a month late due to some additional tricky bugs that took some time to get rid of (sadly there are still some other bugs left, which are hopefully going to be eliminated by version 1.2.0). But the new year brings us a brand new release with an exciting new addition: instead of documenting all properties in a Canvas App (many of which aren't actually modified), you can now decide to document only those that are changed from the default!

Here's what 1.1.0 includes:

General

• the PowerDocu.Common project has been moved into its own repository (https://github.com/modery/PowerDocu.Common) and is included as a submodule. This should allow some greater reusability in the future

Canvas Apps

• You can now decide if you want to document ALL properties of the components in canvas apps, or only those that were changed from their default values. For both scenarios, you can also choose if you want to document the default value (if it is different from the current value). Overall, this means that you can have a much leaner documentation (e.g. instead of documenting all properties, you can only focus on the changes)
• Bug fixes (#63, 42975f7, #71)

Flows

• Fixed bugs where not all actions were documented (#60 , #62)
• Fixed a bug where the action names sometimes broke the diagram layout (#73)
• Edges between actions are now shown as dotted red if the "run after" condition is not "success" (that is, if an action fails, times out, ...)

Solutions

• This is new! The first version of Solution documentation is now getting generated as well. It contains details on the components included in the solution (apps, Flows, Dataverse tables, ....), though a lot of it is still quite rudimentary (which means there are lots of GUIDs or internal names). But it is a start! It also contains some details about the dependencies of the solution

PowerDocu GUI

• The GUI has been revamped a bit to include some additional configurable settings, specifically for the changed values and default values for Canvas Apps.

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.1.0.0 Release

This released features the big milestone of the first major release! PowerDocu is now finally in a state that I envisioned it to be more than a year ago. Contained in this release are:

General

• It is now possible to create Markdown based documentation besides the existing Word documentation! This is available for both canvas apps and Flows. The generated output can then be used for example in Azure DevOps and GitHub (cf2a66e)
• You can now also use .docm (Macro-enabled Word document) and .dotx (Word template) besides .docx as input template
• Fixing a bug with Word templates (#54)

Canvas Apps

• Markdown based documentation! (9cc1606)
• Components and Containers are now shown with the correct icons (ac653ad) (8114621)
• smaller change to the way the individual controls are shown. Instead of listing all controls from A-Z, they are now getting grouped by Screen

Flows

• Markdown based documentation! (4275c7b) (2184d0e)

PowerDocu GUI

• Select which output format should be used (5f0a3db)

As usual, if you find any problems/bugs, please report them in Issues. For any feature suggestions or other recommendations and feedback, please use Discussions

v.0.10.0 Release

A brand new release with a few exciting new features:

PowerDocu GUI

• It is now possible to select multiple source files. Instead of processing file by file manually, you can now select multiple input files (apps, Flows, solution packages) to be processed
• Added the capability to download the list of connectors directly from the app (check out the new button!). PowerShell script will be kept as alternative
• The output into the notification area has been slightly improved, content now gets partially formatted to improve ease of reading
• The version number is now show in the GUI's title bar

Canvas Apps

• Adding parsing for context variables! Instead of only documenting global variables and collections, Context Variables (as used by UpdateContext and Navigate) are now identified and documented as well
• As we parse the Navigate function now, we also keep track of any navigation between screens. This is then used to generate a small flowchart similar to what is used to document Flow actions

Flows
No changes this time

General

• Moved package dependencies to the Common workspace
• bug fixes

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