We have been working hard to add some nice new features. We have been focusing a lot on the B2B migration journey but also added a smart way of to test your SAP Integration without using external tools.
B2B
B2B is one of the areas that we can see a huge value in improving and where we can contribute a lot of the process. It has been a focus area.
We hosted a webinar where we covered a lot of the areas. There is a 30-minute demo about this now works end-to-end. To migrate Operation Mapping and connect them with the Operation Mappings.
It is one of the areas where we still have many ideas for how to improve the setup. But we have already done a huge part of this.
Creation of Partner profiles
We found that one of the areas that was missing in the setup was the ability to have a good structure of naming of Systems and Communication channels. It was one of the areas you needed to a consisted naming.
We have now created a screen to make it possible to create partners with some simple information. Once you create the partner everything will be created after it.
Once you create the partner it will get all the correct values like identifiers
Also, more importantly, 3 systems with a predicable naming will be created for Dev, Test and Production making it possible to
You will need to fill in the details for the communication channels your self on all 3 systems. But this is a good way to simplify how you are creating your partners.
We have also made it easier for you to see which Agreements a Partner profile have.
B2B Scenarios list
We have improved the B2B Scenarios list and added it under the new B2B point. This is your one view into what is configured in your agreement and where it lines to process direct flows and MAGs.
It is straightforward to search for specific content and navigate to the relevant agreement via this.
You can also search for partner and see all areas where the partner is used.
MAG versioning
Ever wondered what was the difference between two MAG version. You can now see the different versions of MAGs that you have. In you can compare the different MAGs you have.
Send Message event
As you work with SAP Integration you often need to create different request and be able to send them into the tool. As developers we would use Postman or Bruno for this. They are super helpful tools.
But it require extra steps and cannot always be run and you need to share iFlow credentials.
You can now create them easily and share your different collections making it easy for your to maintain the different ways to trigger iFlows. This is for a good way to test your iFlows.
You can then define the request based on the iFlow and it will then see the available end points. Then you can trigger the message with that payload.
You can also copy the request to reuse it or change the interface. There are probably a few ways we could improve this, but I would love to get your idea about it.
The idea is not to create a complete test tool. This is just a simple way for you to save some payloads that you can use in your iFlows and not have to use separate Postman/Bruno collections.
Other changes
- Ignoring of XML Attribute. You have elements like created as an attribute in the XML then you want to ignore that part.
- Show if the PI user is locked when performing connection tests. It is something that we face when connecting to On-Prem SAP PI that a user has locked an account.
- We know that a lot of customers are using the free text field Test case name and want to see it in different locations. Now you can see this from all the places you add test cases.
- Many other improvements around the app to simplify the journey.