From a0726f5bb30afa38f1a8105380a82f493a2f6c38 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Jeglinsky?= Date: Wed, 28 Jan 2026 15:28:20 +0100 Subject: [PATCH] fix link --- guides/integration/calesi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/integration/calesi.md b/guides/integration/calesi.md index ef2a44ff7..cc78832aa 100644 --- a/guides/integration/calesi.md +++ b/guides/integration/calesi.md @@ -590,7 +590,7 @@ npm add @capire/s4 ## Consuming APIs -Given the imported APIs we next use the definitions within our own models. For example, in the XTravels application we want to combine customer data obtained from SAP S/4HANA with travels, and flights data from xflights with respective bookings, like a [mashup of own and imported entities](#mashups-with-local-entities). With the integrated models given, we can already run the integrated application, as most integrations are [mocked out of the box](#mocked-out-of-the-box) by CAP runtimes. For the real non-mocked integration, [custom code is required](#required-custom-code), of course, which we'll deep dive in in the last secion of this chapter. +Given the imported APIs we next use the definitions within our own models. For example, in the XTravels application we want to combine customer data obtained from SAP S/4HANA with travels, and flights data from xflights with respective bookings, like a [mashup of own and imported entities](#mashed-up-models). With the integrated models given, we can already run the integrated application, as most integrations are [mocked out of the box](#mocked-out-of-the-box) by CAP runtimes. For the real non-mocked integration, [custom code is required](#required-custom-code), of course, which we'll deep dive in in the last secion of this chapter. ### Consumption Views