Finisher FormEngine definition fails with nested options
If a finisher is configured by nested options (similar to
databaseColumnMappings of the
SaveToDatabase finisher), an error will occur while the FlexForm of a form plugin is being built. This causes the option in question and all other following options to be skipped entirely.
This is caused by e.g.
option.nestedKey being looked up in
TYPO3.CMS.Form.prototypes.standard.finishersDefinition.MyFinisher.FormEngine.elements which causes
ArrayUtility::getValueByPath() to throw an exception. Due to this, no element configuration is found and the option is skipped.
As a workaround I have set the relevant options to empty values in my form definition.