I continue my research to try to find the problem.
When this customer is submitting us is order is doing it by http to wm.tn:receive
Here is the contain of wm.tn:receive
I’ve made a copy of this flow and add an Exit Flow at the end. I also add a savepipeline and an exit at the beginning of the flow that is suppose to be executed with the processing rule. Once done, I submit the order to the flow “receive” (my copy). I look into TN and the Document Type, the Sender and the receiver were to “unknown” but the content contain the accents. No pipeline file was created for the second flow (with the processing rule)
The next step was to remove the exit from the flow “receive”. I submit the same order. In TN, the document type, the sender and the receiver were correct but the content do not include the accents (ex: “é” was replace by “Ã©”). A pipeline file was created.
Questions: What append between the end of “receive” and the beginning of the flow (with the processing rule)? What can change the accents into the content of this order in TN?
Notes: For some other customer there is no problem with the accents.
Here is the beginning of the order.
<?xml version="1.0" encoding="iso-8859-1"?>