This blog post is a part of a series of blog posts related to SAP Cloud Platform Integration. The blogs so far are:
- My adventure in learning CPI || Part 1 || All about SAP Cloud
- My adventure in learning CPI || Part 2 || Deployment Models
- My adventure in learning CPI || Part 3 || Cloud Security
- SAP Cloud Platform Integration (CPI) || Part 4 || Know your tool
- SAP Cloud Platform Integration (CPI) || Part 5 || Content Modifier
- SAP Cloud Platform Integration (CPI) || Part 6 || Configuring Mail Adapter
- SAP Cloud Platform Integration (CPI) || Part 7 || Maintaining logs by using “Groovy Scripts”, even if the IFlow is not on trace mode
- SAP Cloud Platform Integration (CPI) || Part 8 || Working with Request Reply
- SAP Cloud Platform Integration (CPI) || Part 9 || SAP Cloud Platform Cockpit || All about Account, Tenant, and User ID
- SAP Cloud Platform Integration (CPI) || Fetching Report’s data from ECC to C4C via CPI (Alternative for Mashups in C4C/ Integration fo ECC, CPI, and C4C)
— o — — o — — o — — o —
SEND: You can pick this step from the palette Call –> External Call –> Send.
Send function can be used to configure a service call to a receiver system where no reply is expected. You will need a Send step in your IFlow whenever within an IFlow, before the end-step, you have an urge to make a service call to a receiver system. The receiver system can be connected via a Mail, SOAP, or SFTP adapter. In my instance, I have used a Mail Adapter.
The below is the IFlow which I shall be used to explain the “Send” step.
Now, let me explain how Send works:
1. Start Timer: Since there is no Sender System in this instance, I have used a Start Timer, which would trigger the message once it is deployed.
2. Request Reply: To know how the Request Reply works, click here.
3. Send: The Send doesnot have any configurations attached to it. You can just rename this step. As I have mentioned above, you can connect the “Send” to connect to receiver system. In my instance, I am using Mail Adapter. To know how mail adapter works, click here.
4. Content Modifier: To know how the Content Modifier works, click here.
Here, I have defined a Header element of type XPath which capture one of the fields coming in the payload from Request Reply (refer the screenshot below). The same Header Property has been called in the body of the email which shall be triggered in the next step.
EXPECTED OUTPUT: 2 emails shall trigger, 1) from the Send step, which would contain the entire payload coming in, 2) from the Content Modifier in 4.sdfs
Hope you had a good read.
If you wish to know more, or have any queries on this blog, then please feel free to drop a comment.
Thanks & Regards,