Any experience in using “Custom XML (Legacy Embedded Content)” for Adobe Experience Manager (AEM)?

Former Member
Former Member

I'd like to use that custom xml filter as an FTS filter but for some reason, I have hard time to associate it to the FTS filter.

Any hint on how I should do that?

Parents Reply
  • Former Member
    0 Former Member in reply to Eric Bishop

    So, quite a few things to answer :)

    We are getting the files from AEM directly as xml file (like 00e82765-6c7b-4795-a8a6-d0a8588bbace.xml) and the content look like the following:

    <?xml version="1.0" encoding="UTF-8"?><translationObjectFile fileType="PAGE" sourcePath="tubudu">

     <translationObjectProperties>

       <property isMultiValue="false" nodePath="tubudu">To be translated</property>

     </translationObjectProperties>

    </translationObjectFile>

    Where the value inside <propery></property> is to be translated.

     

    We are heading to the latest of WS very soon but we are still running with WS 10.4.3.

     

    Thanks!

Children