Salesforce

WorldServer - SID not generated when using Custom XML (Embedded Content Processor) File Type with Embedded Content enabled

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Symptoms/Context
We have SID configured in the SID matches section of out  for Custom XML (Embedded Content Processor) File Type configuration. However, we noticed that the SID information is not getting saved in the Translation memory for our project when the embedded content processor is enabled in the File Type configuration. When embedded content is not selected/is disabled the problem does not occur. Why is this happening?
Resolution
The embedded processor does not support SIDs.

If you use any of the Embedded Content processors, the SID match will not be generated. The only way you can get it is if you use Legacy embedded content processor, present in the Custom XML (Legacy Embedded Content) File Type. The difference is that the legacy processor only changes the content of the segments (located inside paragraph unit marked with SID match), while the embedded processor takes the entire content of the specified element and sends it to different processing pipe - that is then represented as separate file element in the bilingual content.

The quickest resolution  is to use a Custom XML (Legacy Embedded Content) File Type. For instance, if you were using an HTML content processor in the Custom XML (Legacy Embedded Content) File Type, you will need to configure support for the used HTML tags using regular expressions. This will allow SIDs to be generated also for the embedded content.
Root Cause
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by