It is much better to work on tools way after they have matured because then nothing is changing any more.
We have jumped head first into support the pipeline concept because we think it is something that will help SAP customers to work on. And it does simplify a lot of the migration journey.
It can be complicated to setup and create the correct artifacts. That is why we build in as a part of the migration journey. If you are exploring pipelines as a part of your migration, sign up for Figaf Migration edition and then try migrate some interface and see how it works.
Since the update 1.0.6 3 changes have happened to simplify the setup of pipelines.
Pipeline changes
Point-to-Point connection
This allows you to skip using the XSLT for Interface and Receiver determination. I think this is going to be one of the most popular scenarios.
You just create two entries in the Partner Directory.
This is supported you just set a check mark in the P2P scenario and it will be generated.
You can only use this if the message is only being sent to one receiver interface. You can just exclude the other flows.
It then produces two String parameters. One to show the system and one to show the process direct url.
Then the message skips directly to Outbound processing.
Update of XSLT based processing
In 1.0.6 there was also a change in the way the Interface scenarios was configured. Here it looked like the following
Where the new is the following.
The System name has been added to the interface determination. This is because PartnerId (Pid) is limited to 60 characters.
Alternative partners
There is also a change on the Alternative partners that can be used to configure longer PID into shorter PID. We have not implemented this yet since it will require the support for the DevOps process.
But we will add it as we get more feedback on how Figaf can simplify your operations with the tool.
Download failed messages
We have normally been requiring messages to be processed and successful for it was possible to create a test case on it in our SAP PI/PO testing. This was causing some problems when there was already an error because no system was connected.
So now you can select if you want to be checking for messages in the SAP PI/PO Agent setting.
