I do have a songbook with many flows in it and would like to create filenames based on fields in the flow info. Are there by chance any tokens available other than the one mentioned in the filename-options dialog in the print menu?
Daniel is meticulous in documenting everything that the team has implemented, in the Version History notes for each release.
I doubt they would implement something and not announce it. And if they did, no one would know! 
Can you explain exactly what you’re trying to do?
I’d like to export to filenames including the “Werknummer” from project info (that’s the German version) instead of using the flow number as the flows have them as the ID that should be in the filename.
Right now I see only flowname and flownumber which in my case generates wrong filenames that do not match the ID of the flow.
Does this make sense?
Would be great to have access to all tokens that can be used in the flow header template.
Maybe use (or include) werknummer as project filename ?
I think I found a workaround for my usecase: Entering the name of the flow with ID (e.g. 35_MyFlow) and then entering the project info later on (setting title to “MyFlow”). It will then not change the name of the flow (whereas entering the flow name will change the title in the first place).
This allows me to export with the ID without compromising the title that is used in the flow header template.
One can use any (otherwise) unused Project Info field to store a Work Number and then use that token where one wishes.