Choose to design IFlows to make it easy to maintain and more readable.
With growing complexities of the integration requirements as a developer it becomes imperative to design IFlow's:
- Readable: Which provides USERS clear understanding of steps on high level just by looking into the IFlow.
- Easy to maintain: While configuring on different environments it should be easy to update channel/parameter details.
There are many of such design consideration which we understand as we develop more and more simple/complex interfaces.
With help of this blogpost I am trying to highlight one such example where choosing the right design helps to achieve above mentioned consideration.
| IFlow Design | Configure Parameters | |
| Style1 |  |  |
| Style2 |  |  |
If you notice Style1 it might look tidier, with only one receiver but the downside is when we try to configure, it's difficult to understand which channel we are updating. Even to update we have to select the drop down on Adapter Type and if we have same type of adapter its not possible to differentiate between different channels. If there was an option which reflects channel names it would help but currently there is no label/tag which reflects channel name.
Whereas with Style 2 we can understand the difference based on the Receiver itself and not based on the adapter type. So for the developers or support team who is going to maintain the interface could find it easier to maintain.
Hope this helps! Keep Integrating !!
thanks and regards,
Praveen T
- SAP Managed Tags:
3 Comments
