SAP
In one of my previous posts, I provided the steps required to create the API for iFlow. Creating an API for iFlow: A Step-by-Step GuideThis guide aims to outline the steps required to create an API for iFlow and subsequently run the iFlow through the API. Step # 1. Develop an
SAP
Hey there! I want to address an issue that may arise in projects involving encryption/decryption within the SAP BTP iFlow and its embedded PGP engine. Scenario description Imagine you've installed the latest version of the gpg4win application (version 4.3.1) to generate public and secret keys
SAP
This guide aims to outline the steps required to create an API for iFlow and subsequently run the iFlow through the API. Step # 1. Develop an iFlow Begin by creating a simple iFlow. Deploy any changes made. Step # 2. Setting Up API Providers Navigate to the API section on the
SAP
This note contains an example of a Groovy script that may help the developer trace the payload within the iFlow, especially if it changes during its lifecycle. It is worth noting that the beauty of the script below is that it adds an attachment to the processed message that can
SAP
This brief note aims to highlight the possibility of overwriting standard iFlow header parameters, offering developers flexibility in addressing various requirements. Specifically, this discussion centers around the header parameters SAP_Sender and SAP_Receiver. See Headers and Exchange Properties Provided by the Integration Framework SAP allows developers to overwrite the
SAP
In this post, I'm going to provide the steps required to start using the RFC adapter within the iFlow on the SAP BTP Integration Suite. Step #1. Create the Remote-Enabled Function Module Create the FM that will be returning values from the ABAP system. Don't forget
SAP
The SAP BTP Integration Suite offers various adapters for integration flow developers to utilize. Among these are frequently used options such as HTTPS, SFTP, OData, and Mail. See Configure Adapter in Communication Channels In this post, I would like to demonstrate one of the adapters that could potentially be used
SAP
In this post, I would like to consider a sequence of steps required for restricting access to iFlows within the BTP instance. Preface As you probably know, an Integration Flow could be triggered via the generated endpoint URL that you can find in the corresponding tile on the Monitoring dashboard.
SAP
This post addresses a common challenge encountered when working with SAP BTP Integration Suite — specifically, passing parameters to iFlows using the 'Header' section of the message. Let's walk through an example to illustrate the issue. Step #1. Create the simple iFlow Begin by creating a straightforward