We have the 2505 release. We have been working a lot on the TPM and the migration part. But mostly focused on closing many smaller issues.
Improvements
This release have been focusing on improving a lot of the small gaps that have frustrated us and our users in the development process.
- Improved test message polling to fetch messages in a more structured way getting rid of the Unfinished status.
- UI enhancements to make it a bit clear what you are exploring.
- We did in 2504 patches add better memory usage so please upgrade to it using the latest deployment templates.
- API improvements for automating transports
Trading partner overview
We have spend a lot of time to improve the TPM experience in the tool. I don’t think there is any other places you can get a better overview of your TPM agreements.
Now you can see which agreements is linked with which iFlows, MIGs and MAGS. If you click them you got directly to the objects. You can also filter on the columns. This makes it much easier to understand what is connected.
We also have improved a lot around the experience of migrating to the items.
We have also improve the testing part to support messages that require CONTRL/997 in the flow.
Partner Directory binary viewer
One of the things that frustrated me was the lack of ability to see what was in Binary partner directory entries in zip files. It was pretty complicated to get to view it. Now you can view them easily in Figaf.
You can also see what the difference is between two versions.
We don’t recommend updating this but since it is most of the time TPM content it should not be modified because it will be overwritten for each new deployment.
Migration to Integration Suite
We have added numerous small improvements to the migration that have been frustrating.
* as allowed header when migrating B2B.
Support converting extended receiver determination to pipeline
We do have some challenges if users have Extended Receiver Determination where you would be using a message mapping.
We have decided not to migrate it as a message mapping thought it would be possible in the pipeline concept. I think that it is going to be a pain to maintain. And I think in general you should be able to do the same check in XSLT. So it will be a manual task to add rules.
Pipeline XSLT improvement
You can now see if you are changing an XSLT in the process. You can now see if there already is an XSLT and what the change would be.
Once you have migrated you can see the different iFlows created, now you can also see the partner directory entries created. This way you can easily adjust it if needed.
Pipeline migration with alternative partners
With the new version of pipeline concept alternative partners is the way going forward. We have therefore created the alternative partner translation for the scenarios.
You can now define the partner id to be used for the configuration, then the Inter
Navigation
We have made it easier to search for special in the tracked object. You can filter on specific object types like iFlow or script collection.
