I have a question about a situation I have with a new xCBL integration, but can happens with any other xml formats.
In our 6.5 WM, we have a doc type ‘xCBL 3.0 Order Request’ created and we have some customers using it. Each customer send us their identifier in the same path, so in the Extract tab, the SenderID is defined with that path, and after the good processing rule can be triggered. In the options tab, the xCBL schema is defined to format transaction data.
Now, we have a new integration with xCBL 3.5. First thing I noticed, those documents are really similar and I can’t find a way to distinguish them and create a new document type ‘xCBL 3.5 Order Request’. Secondly, that new customer send us its identifier in a different path.
For the document type, I wanted to update the ‘xCBL 3.0 Order Request’ to ‘xCBL 3.x …’ and update the schema as 3.5 since all the 3.0 fields are existing on 3.5 But how can I handle the SenderID recognition with multiple xml path? I can’t create a new document type only for that customer as an exception as the result will be an ambiguous document type found…
Thanks for your help