Hello all, 

when creating TranslationBatches for Content-Apps and checking 'Include Subnodes' the created Batch recursively includes all relevant i18n Fields (equivalent behavior to Pages-App).

But the document created for TranslationSubmission currently uses 'XliffTransporterImpl#doExportForApp' which then calls protected '#export' once and only includes i18n Fields for the current node. After that '#isProcessed' compares 'path' and 'configPath' properties and therefore skips all other i18n Fields that have been initially added for the TranslationSubmission (since they all match those properties but have different values in 'link' property). 

The resulting sourceDocument only contains i18n fields of the parent Node but not its child nodes although all relevant i18n fields are available in the TranslationSubmission Object. 

Is this current behavior intentional and if so is there any other way to properly use 'Include Subnodes' for Content Apps as well? 

Thanks in advance and best regards, 
Florian