Flow Versions, Tokens, and File Name Ingredients

[alexcap]

I like to include both a project version and a flow version in my filenames (using comments for version-specific notes):

and on the pdfs:

Here’s how I currently do that.

Project Version in Filename

Getting the project version in the filename is easy, as I just use the Project file name ($f) ingredient. When I save a new version, I increment the version number in my filename, so this updates automatically when pdf filenames are created. I’m aware of the Save New Version function, but I don’t like it – instead of incrementing my existing version number, it just appends “-01” and then increments its own version number: “-02”, etc.

Project Version in PDF

To get the project version into the pdf, I had been using the projecttitle and projectotherinfo tokens, and setting the version number in Project Info > Other information. Since I needed to remember to change this field when I saved a new project file version (which you can see I forgot to do in the above screenshots), I will probably now use projectfilename instead, although I could do without the file extension.

Flow Version in Filename

This is where it really starts to get clunky. There are a few options for getting the new flow version into the filename.

1. Flow name $w ingredient
   a. Break the link between Flow title and Flow name, then the Flow Version can appear in the filename using $w.
   b. The problem here is that there’s no flowname token (as has been remarked elsewhere on the forum), so it can’t be included on the pdf the same way.
2. Hard-code flow version
   a. In the filename recipe, write the flow version number after $w (in this case you don’t break the link between flow name/title).
   b. This is obviously less than ideal since each flow may be on a different version.
3. Add after the fact
   a. Export the flows with $w - vN (or similar) as a placeholder and manually replace N with the correct version number

Flow Version in PDF

Here I can also use the Other information field with the flowotherinfo token. Again, this adds the burden of keeping it updated in more than one place.

Requests

1. Add a projectfilebasename (and/or projectname) token that has the filename without the extension
2. Add a flowname token
3. I’m not sure if a dedicated project/flow version field is necessary since Composition year, Other information, or some other unused field can fill that purpose, but I’d still want to have access to those (or at least more) fields in filename ingredients.

[sammys]

Is there any way to have the date appear in the PDF export’s filename in the format you use, e.g. so it would be “29 Nov 2024” rather than 2024-11-29 which is not very pretty.

Tokens don’t seem to work, e.g. {@datemonthshort@}.

Thanks!

[alexcap]

More date format options for filename ingredients would be great, too!