cleanFiles/bookmap_SAP_Integration_Suite_in_a_Nutshell_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2024-08-27T13:32:13.000Z

How to Validate Integration Flows Using Design Guidelines

Modernizing Integration with SAP Integration Suite

SAP_MOOC_btp5_Lesson_7_DSAB_Video.mp4

Now let me demonstrate how to enable design guidelines in a tenant and validate the integration flows against them in a live environment. So here I am in the SAP Integration Suite landing page and you can configure these guidelines in a new tab within the settings. So I have to go to integration settings and let me open. So here you will see we have now a new tab with the name design guidelines. So here you can configure on a tenant level which all design guidelines you need right so you can enable or disable and if you see these guidelines are logically grouped in a category so like all the security standards related guidelines are grouped under this one all the memory footprint related guidelines are grouped under this one so there's a logical categorization is there so that you can easily navigate through all these guidelines and to change this, we have to just click on the edit so right now if you see all have been enabled let me click on the edit and I think yeah this low one I'll turn it off and yeah and this one also reset data for every branch also I'll turn it off and this I feel is good for my organization level design guidelines and I'll just save it. Although it is under settings page, but your tenant admin can also give this task to the integration lead, right? So the only thing that person has to do or the tenant admin has to do is to provide workspace design guidelines, configure role to that persona. And then that integration lead will take care of setting these guidelines on a tenant on organizations behalf, right? So this is what I have done. And now one more feature what is there is you can export, right? So it always makes sense that all your tenants in a landscape that is dev, test, broad, all have the same kind of design guidelines. So instead of configuring each tenant one by one, just configure in one tenant, export it and then import it. Yeah, so this is a very handy feature in that sense. So it looks like, yes, all the important features I have enabled and yeah, I'm good to go. Just one thing, although it is written mandatory, but even if your iFlows are not complying to these mandatory guidelines, it will not stop the deployment, right, as of today. So, but it is still recommended that you enable these guidelines and comply to these guidelines before deployment so that you can able to design robust integration flows. So as this has been enabled, Now what I'll do is I'll go to a design workspace and I can execute these design guidelines as we learned on a custom integration content or a pre-packaged content, both in edit mode or non-edit mode. So let me search for one pre-packaged content related to field service management. So this is the first package, integration of service in SAP S4 HANA Cloud with SAP Field Service Management. Here I see that we have 20 artifacts. And let me choose the one which is little complex. Okay, so this notify service order is the one as far as I remember, which has little detailed integration modeling. Yes, if you see here, yeah, this is your entire iFlow. And if I just double click, it will expand this property sheet. And here also you will see now new tab with the name design guidelines. So this is what we have embedded. And whatever the design guideline, which is coming here, it is coming from the settings page. So if you disable something, it will not come here. So it will at the end of the day, it will execute all the enabled guidelines for each iFlow, depending on which iFlow you're opening and executing. And let me click on the execute guidelines. As I'm gonna click on that, it'll take some time. it takes, it try to understand the full integration flow and try to match with these enabled guidelines. Let me, yeah, expand this. So if you see, there's a total in the applicability or compliance there are two status, right? Or one is non-applicable, inapplicability, that means in this iFlow, these guidelines is not applicable. Means you are not using those features which are applicable to this particular iFlow. So when it is not applicable, that means of course we have not checked for compliance as well so we can totally ignore this. Then the second category is applicable and compliant so that means this design guidelines is applicable for your integration flow and it is also compliant so you are doing the using the right practices here and the third one which we have to put most of the most of our focus is applicable but they are non-compliant. So these are the ones which we have to fix and you can also overwrite this in case, this is although not recommended, but in case you feel that hey this is something I like to ignore, then you can also use this option but as a good integration flow developer I'll not skip this one and I'll try to analyze so here is the button which opens it tells you the reason the KPI values and it also highlight the violated components if I click on that yeah it also navigates you to which to that particular flow so I'll show you again so here analysis and if I click on this one see automatically takes you that particular flow component where you can see where you can fix and you can add it and save and once you add it and save although it's a prepackage content you are not allowed to do though, yeah? But in a custom, so here you can maybe raise the concern or if it's your custom content, you can save it and once you save and rerun, it will show applicable and compliant. So this is all about this feature. This is a very important increment. So earlier what we used to have the design guidelines in the form of documentation, which sometimes people follow, don't follow, but now it is embedded. And here you can see in a programmatically way, whether you are really compliant to those guidelines or not and every increment, every tucked increment, we are trying to incorporate more and more such guidelines. Thank you.