Hi Community,

It has been suggested to place my idea here by Studio support team. We have a customized XML parser, which we deployed for Sales Force Service Cloud (SFSC) Knowledge management platform via TMS/ManTra connector (the connector is an SDL product).

SFSC apparently has some length restrictions on some of their fields, and import of translation via the connector fails if translation exceeds the length restrictions. I have run some tests in order to make some suggestions/solutions to our client, but it turns out that length restrictions and associated QA checks do not work for content wrapped in CDATA. Length restrictions and associated QA checks do work when I remove CDATA wrapper.

Length restriction information is being specified using XPATH under XML file type > Parser > any element > Edit > Advanced > Length restrictions

Here is how length restrictions on CDATA sections should hopefully work:

Since CDATA sections are designed for character data, I would like lengths of content within CDATA sections to be a number of characters of a character stream, as if the data is a string of characters, disregarding any markup within.

FYI. CDATA as defined by W3C here: https://www.w3.org/TR/xml/#syntax

In a CDATA section, character data is any string of characters not including the CDATA-section-close delimiter, " ]]> ".

Thanks for considering!

Thanks,

Naoko