Finisher identifier unused for translations
The specific finisher identifier used in a form definition is currently only used to look up a finisher within
finishersDefinition. Internally another identifier is built based on the finisher class name which is then used e.g. to perform finisher option translations.
It would be very useful if the finisher identifier from the form definition was used or at least considered here. This would e.g. allow for using a common translation file for the
EmailToSender and the
EmailToReceiver finisher to have separate subject translations. Currently one is forced to set a separate translation file for each of these since the translation key is always the same. Thus with two finishers in a form you already need two separate translation files for this, the more forms you have the more translation files you need.