Include FME Form Workspace Parameters for Last Save Date, Last Save Build, and History as metadata when published to FME Flow

Clarification: Although the Last Save Build for an FME Workspace is reported in the top of the job log in FME Flow, I would rather not have to execute the workspace to see this information - it would be helpful to see the Workspace Parameters for Last Save Date, Last Save Build, and History as metadata associated directly with the workspace sitting within its repository folder.

Often I continue to develop or improve a workspace but not publish every iteration directly to Flow.  Each of my workspaces include a large font annotation in the upper left that indicates the version (or date) of the changes.  Previously, we could view workspaces directly within Flow, and I could confirm which version of the workspace had last been published by quickly viewing this embedded annotation.  However the recent releases of Flow no longer allow for viewing a workspace - I now have to download the workspace from Flow and then open within Form, if I wish to view these annotations.

I tried including a User Parameter with the workspace for a “VERSION_DATE” and had to remember to update it prior to publishing the workspace into Flow.  The unfortunate consequence of this work around turned out to be if I did not go into Flow after publishing and overwrite the VERSION_DATE user parameter with the same value (in every automation that utilized that workspace), the automations would generate warnings at every execution that Expected parameters had not all been provided even though the parameter had a value provided during publishing, it had not been assigned within Flow - which seems to result in the Expected parameters warnings.