How to get Flow versions for a brownfield org?

[max-makarenko-immersive]

Hi,

First of all, thank you very much for this amazing tool! 🙏

I'm generating org documentation for a brownfield org. I'm not getting the Flow version history (which looks super cool in the presentations). If I understand correctly, that's because it only works if you have the pipeline and the history of commits for every Flow version, as Hardis generates the diffs between commits, right?
If yes, is there any way to override that? Or in other words: is there a way to generate documentation with Flow version histories if you are just starting out with a brownfield org that had no repo before?
I don't want to do fake commits for each previous version of each Flow in this very old org. 😅 I am okay with manually fetching different versions of all the Flows and putting them into a repo (or locally), but is there a way to tell Hardis to compare those files (and generate the documentation) instead of comparing commits?

Thank you again!
Max

[nvuillam]

@max-makarenko-immersive thanks for your thanks :)

As you guessed, the flow history is built from the git history, so if there has never been any git... this is currently not covered by sfdx-hardis ^^

but if you install sfdx-hardis monitoring, as it creates a new commit during the daily backup, everytime your flows will be updated in the future, you will see it in the generated documentation :)

Another solution could be to play with typescript to update the sfdx-hardis command so it can be based on tooling API and not metadata... but i'm not even sure this is possible, because as far as i know you can get the XML of the latest version of the flow, but not the XML of the previous ones 😇

[max-makarenko-immersive]

You definitely can pull the xml of any version, if you know that version exists (sf retrieve --metadata Flow:Flow_API_Name-2 where '-2' is the version you want). I'm not sure whether you can poll for the list of all existing versions, though. That's why I said I'm okay pulling them all manually.
Anyway, thank you for answering and once again — for this great tool! 🙏

[nvuillam]

Indeed you're right !
You can use tooling API to get the list of versions of a flow (according to ChatGPT)

sfdx force:data:soql:query \
  -q "SELECT Id, DeveloperName, MajorVersion, MinorVersion, IsActive, Status, LastModifiedDate FROM FlowVersionView WHERE DeveloperName = 'Your_Flow_API_Name' ORDER BY MajorVersion DESC, MinorVersion DESC" \
  -u MyOrgAlias --json

But it will retrieve you different flows files... so you might have to play with git commit + renamings etc...

If you do such script, you might create it from a new command sf hardis:doc:init-repo-history, that would:

• retrieve all flow versions in some temp folder
• for all flows
  • for all flow versions (descending order, starting by the oldest one)
    • copy flow version XXXX-2 in the repo /flows
    • rename it XXXX
    • git add XXXX.flow-meta.xml && git commit -m "XXXX flow version of date DDDD"

This will create many dumb commits with just a flow diff, but at least sfdx-hardis documentation will show you the history :)

Note: if you create a sfdx-hardis command (and i hope you will 😋 ), you can query tooling api using method soqlQueryTooling