For everyone who is accountable for iFlows.
And for everyone who builds them and keeps them running at night. Five roles, one panel – each sees what it needs first.
- 01
Developers
Build, review, test.
- 02
Integration leads
Standards and costs.
- 03
Architecture
Dependencies and the big picture.
- 04
Operations and AMS
Causes, not messages.
- 05
Newcomers and training
Learning on a real iFlow.
Fewer deploy loops. More certainty before the transport.
Building an iFlow today means: editor, XPath tester, Postman, monitor and back again. iFlowTailor puts the tools next to the editor and points them at the iFlow you have open.
At a glance
- Quick Review with Health Score1, jump to the step, report as Markdown.
- XML Workshop2 and payload tools3, without copying data into third-party online tools.
- Groovy Runner4 against the real runtime, without a deploy (Pro).
- Version Diff with a changelog suggestion5 in the SAP dialog (Pro).
- Header & property finder6: where a header is set, read and lost (Pro).
- In the works: Inline debugger in the editor7 and iFlow simulator without a deploy8 (Pro).
Before the transport to PRD
Open the iFlow, click “Check”: score 64, a certificate expires in twelve days, the script reads the body as a string. Check the fix in the Runner against the sample from the trace, run the test suite, get a changelog suggestion, save. One window.
A standard that reaches everyone.
Naming conventions as a PDF in the wiki, reviews by shouting across the room, costs only once the invoice arrives: if you are responsible for a tenant, you need numbers and a standard that checks itself.
At a glance
- Policy Studio and custom review rules9 (Team).
- Naming Studio10 with a compliance rate per package.
- Tenant Health with trend11, system map and clean-up (Team).
- Message flow analysis12: where traffic flows and where it grows (Team).
- Message Usage with a projection to month end13 (Team, Beta).
“Where do we stand – and is our message quota enough?”
Health Score and naming rate over time, billable messages projected to month end, clean-up candidates with reasons. One page for the conversation with management, without building slides.
The picture of the tenant that nobody else maintains.
Which iFlows depend on this system? Which credentials does this adapter use? What breaks if we rename the Data Store? The answers are in the tenant – iFlowTailor pulls them together.
At a glance
- Dependencies per iFlow14 down to keystore alias and value mapping.
- Tenant index and grep15 across all artefacts (Pro).
- Migration analysis, ISA-M, data lineage16 (Pro).
- Security Risk Radar17 across eight dimensions (Team).
“Who is actually still using the old endpoint?”
Grep across the tenant finds every occurrence in iFlows, scripts, XSLTs and parameters. The dependencies show which chains via ProcessDirect and JMS hang off it.
Causes, not messages.
If you run integrations, you don’t want to open a hundred failed messages in the morning. You want to know: which causes are there, what is new, what expires next week?
At a glance
- Error analysis by signature18 with a solution from 23 known error patterns.
- Deployments with drift, certificates with calendar export19, message monitor.
- Trace Explorer and Message Journey20 across several iFlows (Pro).
- Message forecast21 for days and hours (Pro).
- Endpoint catalog22 with protection and status, export as a Postman collection.
- Downtime optimizer23 for the best maintenance window (Team).
- In the works: root cause search, incident report and morning briefing24.
“What happened overnight?”
Three error signatures instead of 412 messages, one of them new: TLS handshake to the receiver. Cause and suggested fix sit right next to it, and so does the affected certificate – with its expiry date and the iFlows that use it.
From your first iFlow to your third – without the mistakes of the first.
If you are new to SAP Cloud Integration or moving over from SAP PI/PO, today you learn from books, blogs and whatever a colleague has time to explain. The Coach puts that knowledge where it is needed: next to the iFlow you have open.
At a glance
- Implementation Coach25 with build plan, live check and learning path.
- Restart guide26: error handling and retries, step by step.
- Quick Review1 with a reason for every finding – the why matters more than the number.
- Coach edition with group terms for training and trainee programmes.
Trainee cohort, first project
Describe the scenario, create a build plan, build. The Coach ticks off what is in place and reports that the Exception Subprocess is missing. Quick Review explains why. On Friday the learning path shows: error handling is solid, externalisation not yet – that is where next week starts.
Sources on this page
The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.
- 1
Quick Review: Health Score with 40 rules ↑Product · iFlowTailor product documentation, Rule catalogue and score formula (packages/rules), status after 1.1.0 · checked on 2026-11-04
- 2
XML Workshop ↑Product · iFlowTailor product documentation, Changelog 1.0.0, XML Workshop · checked on 2026-11-04
- 3
Payload tools, Groovy Lint and snippets ↑Product · iFlowTailor product documentation, User guide, Tools · checked on 2026-11-04
- 4
Groovy Runner ↑Product · iFlowTailor product documentation, Changelog 1.0.0 and helper iFlows · checked on 2026-11-04
- 5
Tenant Compare, version diff, changelog ↑Product · iFlowTailor product documentation, Changelog 1.0.0, version history and changelog generator · checked on 2026-11-04
- 6
Header & property finder, externalised parameters ↑Product · iFlowTailor product documentation, Changelog 1.2.0, Header & Property Finder and Externalised parameters · checked on 2026-11-04
- 7
Debugging in the editor (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section: inline debugger, run comparison, watched values, trace switch, variable inspector · checked on 2026-11-04
- 8
Testing without deploying (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section: iFlow simulator, trace as regression test, path coverage, contract check, test suite from specification, test gate, DEV against QA · checked on 2026-11-04
- 9
Team policies and custom rules ↑Product · iFlowTailor product documentation, Enterprise rollout and Security Whitepaper, section 5 · checked on 2026-11-04
- 10
Naming Studio ↑Product · iFlowTailor product documentation, User guide, Naming Studio · checked on 2026-11-04
- 11
Tenant Health, landscape and cleanup ↑Product · iFlowTailor product documentation, Editions, Team · checked on 2026-11-04
- 12
Message flow analysis ↑Product · iFlowTailor product documentation, Changelog 1.2.0, Message flow analysis · checked on 2026-11-04
- 13
Message Usage ↑Product · iFlowTailor product documentation, Changelog 1.0.0, Message Usage · checked on 2026-11-04
- 14
Dependencies ↑Product · iFlowTailor product documentation, User guide, Dependencies · checked on 2026-11-04
- 15
Tenant index and grep ↑Product · iFlowTailor product documentation, User guide, Tenant index · checked on 2026-11-04
- 16
Migration analysis, ISA-M, data lineage ↑Product · iFlowTailor product documentation, Editions, Pro · checked on 2026-11-04
- 17
Security Risk Radar ↑Product · iFlowTailor product documentation, Changelog 1.0.0, Security Risk Radar · checked on 2026-11-04
- 18
Error analysis by cause ↑Product · iFlowTailor product documentation, User guide, Error analysis · checked on 2026-11-04
- 19
Deployments, certificates, monitor, runtime data ↑Product · iFlowTailor product documentation, User guide, Operations · checked on 2026-11-04
- 20
Trace Explorer, Message Journey, heatmap ↑Product · iFlowTailor product documentation, Changelog 1.0.0 and user guide · checked on 2026-11-04
- 21
Message forecast ↑Product · iFlowTailor product documentation, Changelog 1.0.0, Message forecast · checked on 2026-11-04
- 22
Endpoint catalog ↑Product · iFlowTailor product documentation, Changelog 1.2.0, Endpoint catalog · checked on 2026-11-04
- 23
Downtime optimizer ↑Product · iFlowTailor product documentation, Changelog 1.2.0, Downtime optimizer · checked on 2026-11-04
- 24
Root cause search, incident report, ask the monitor, morning briefing (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section; editions, cut for debugging, testing and AI · checked on 2026-11-04
- 25
Implementation Coach ↑Product · iFlowTailor product documentation, Changelog 1.2.0, Implementation Coach · checked on 2026-11-04
- 26
Restart guide ↑Product · iFlowTailor product documentation, Changelog 1.1.0, Restart guide · checked on 2026-11-04
Questions about who it’s for.
- Is iFlowTailor worth it for a small tenant?
- Yes. The Community edition is free and covers the single iFlow and day-to-day operations: Quick Review, Error analysis, Test Studio, XML Workshop, deployments and certificates. The tenant-wide views pay off once you have a few dozen iFlows.
- Can consultancies use iFlowTailor at their customers?
- Yes. The extension works with the session you already have at the customer and stores tenant data only locally, kept separate per tenant. For teams that look after many customer tenants, we are happy to work out the licence together with you.
- Does iFlowTailor help people getting started with SAP Cloud Integration?
- That is what the Implementation Coach is for, available since version 1.2.0: a build plan per scenario, a check against the open iFlow, a learning path and a versioning advisor. In the app it is part of Pro; we propose it as a separate, lower-priced Coach edition; training and trainee programmes get group terms.
- Does iFlowTailor help with migrating from SAP PI/PO?
- iFlowTailor checks and runs iFlows in SAP Integration Suite. The migration analysis (Pro) shows outdated adapters and script APIs, the ISA-M classification and the data lineage of a target field. It is not a migration tool for PI/PO objects.
Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Demo on your tenant