My custom language plugin is currently using CreateFileFromInputAction to facilitate template-driven source file creation. For three of the four file types, this works great because the only real parameter is the file name (sans extension) which, like in most other languages, maps directly to the contained entity name (e.g., class name, page name, etc.). However, the fourth file type really needs two additional inputs to be complete. It's basically a database trigger which requires the name of the trigger itself, the name of the database object to which the trigger is attached, and the subscribed events.
In a perfect world all three of these parameters would be captured in the file creation dialog. As far as I can tell, if I want to take advantage of CreateFileFromTemplateAction and all the functionality it offers "for free", I only get two input fields, the text field for the name and the optional combo-box for the file sub-types. Before I implement my own file creation action that's essentially a CreateFileFromTemplateAction with a few additional inputs, I thought I'd check here and see if I'm just missing some simple way to do this in the current framework.