#Microsoft50
We have looked into SAP documentation and SAP recently recommended using ${body} instead of ${in.body}. In order to identify which artifacts are using this code in an efficient time, especially since we don’t yet have a full Git pipeline. (~500 iflows in our current Integration Suite CI capability). We implemented the search code tool. By specifying ${in.body} as the search parameter, the tool scans all iFlows, identifies where this string is used, and returns the names of the relevant iFlows.
We have looked into SAP documentation and SAP recently recommended using ${body} instead of ${in.body}. In order to identify which artifacts are using this code in an efficient time, especially since we don’t yet have a full Git pipeline. (~500 iflows in our current Integration Suite CI capability). We implemented the search code tool. By specifying ${in.body} as the search parameter, the tool scans all iFlows, identifies where this string is used, and returns the names of the relevant iFlows. https://help.sap.com/docs/cloud-integration/sap-cloud-integration/using-camel-simple-expression-language Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
