Part 5 Content Fetching Report's Data From ECC To C4C Via Mashups in C4C Integr Part 4 Know Your Tool
Part 5 Content Fetching Report's Data From ECC To C4C Via Mashups in C4C Integr Part 4 Know Your Tool
A content modifier shall help you to modify the incoming message or payload,
by changing it's content that are involved in Message Processing (i.e. Message
Header, Message Exhange Property, or Message Body).
In the Message Header, and Message Exchange Property, you can declare Header
Element, and Property Elements, which can or cannot be included in the outgoing
Message to the next step, as shown in the screenshots below:
Header:
Property:
The scope of the element declared in the Header is beyond the scope of the
IFlow,
The scope of the element decalred in the Property is only within the IFlow i.e. the
property parameters are not handed over to the receiver.
${property.elementname}
${in.body}
As shown in the screenshot below, I have called the Header, and body, and since,
the received expects the output in xml, the tags have been maintained like wise.
Here, I have inserted a Groovy Script after every Content Modifier because I wanted to
see the payload after the IFlow is deployed. I shall share the script's content in the Part
7 of this series.
In the Content Modifier 2, below is the Header, Property, and Message Body:
As you can see in the screenshot above, I have used the code ${in.body} to call the
content of the previous i.e. Content Modifier 1.
Now, the output to this, after you have "Saved as version", and "Deployed" is below.
That is it about Content Modifier.