Sources.
“AI-powered.” “Enterprise-ready.” “Fully automated.” – Tools for SAP integration promise a lot and prove little. For a tool that gives a reason, a location and a fix for every finding, that would be embarrassing. So every claim on this website has a source: product claims point to our documentation as of version 1.2.0 of 3 November 2026, books and services to a link and a date.
The habit comes from our sister JournalTailor: no booking without a receipt, no receipt without a source. For us it reads: no finding without a reason, a location and a fix1.
Product
Version 1.2.0 of 3 November 2026
Version 1.2.0 adds the Implementation Coach, the endpoint catalog, the header & property finder, externalised parameters as a map and matrix, Message Journey as a correlation graph, the downtime optimizer and message flow analysis, plus a health score that stays the same when you reopen an iFlow. Version 1.1.0 added the System map with outage analysis and the Restart guide. Version 1.0.0 introduced the edition structure with a badge in the header, Message Usage, Access Policies & Number Ranges, Security Risk Radar, Log analysis, Vulnerability check, the XML Workshop, the hourly Message forecast, the graphical version history with changelog generator, the Adapter advisor and “iFlow from requirement”.
iFlowTailor product documentation, Changelog 1.0.0, 1.1.0 and 1.2.0 · checked on 2026-11-04
Browser extension for Chrome, Edge and Firefox
One codebase for Chrome and Edge (Manifest V3) and Firefox (WebExtension). A side panel sits next to the iFlow editor; a content script detects tenant, package and iFlow; a separate workspace shows tenant-wide analyses. User interface in English (default) and German.
iFlowTailor product documentation, README and Security Whitepaper, section 1 · checked on 2026-11-04
No vendor server, no telemetry
There is no CloudDNA server, no analytics tool, no error telemetry and no remote configuration. Updates come only through the browser stores; no remote code is loaded. Data leaves the browser only when you trigger it: Test Studio requests, your AI endpoint, Confluence export, vulnerability lookup – each host with the browser’s permission.
iFlowTailor product documentation, Security Whitepaper and the extension’s privacy policy · checked on 2026-11-04
Existing SAP session, no SAP password
The extension uses the browser’s existing SAML/IAS session, never triggers a login or basic authentication dialog and stores no SAP passwords. It reads only via GET on an allowlist of paths (OData services and read-only endpoints of the web UI). The roles of the signed-in user apply – iFlowTailor can never do more than that user.
iFlowTailor product documentation, Architecture decision 0002 and Security Whitepaper, section 2 · checked on 2026-11-04
Read-only by default, writes only with a preview
Write actions are off by default. Every write action passes a chain of checks: approved endpoint, read-only mode, block by the team policy, then a dialog showing before and after. Every outcome is recorded in the local audit log, including cancellations and blocks. A policy can enforce read-only mode and block each action individually.
iFlowTailor product documentation, Security Whitepaper, section 2 · checked on 2026-11-04
Secrets encrypted locally
API keys, service keys, tokens and secret variables are stored as ciphertext in the extension’s local storage: AES-GCM 256 with a non-exportable WebCrypto key. The tenant index is kept separately per tenant in IndexedDB and can be deleted.
iFlowTailor product documentation, Security Whitepaper, section 3 · checked on 2026-11-04
Licence verified offline
The licence is an Ed25519-signed JWT and is verified in the extension against built-in public keys – without a licence server and without usage tracking. It can be bound to tenant hosts. When it expires, iFlowTailor falls back to Community; settings are kept.
iFlowTailor product documentation, Editions, technical section · checked on 2026-11-04
Beta: all features unlocked
As long as the shipped version contains no public licence key, nothing is locked; the header then shows “Beta · all features”. As of 3 November 2026 the list of keys is empty. With the first key, the edition structure takes effect.
iFlowTailor product documentation, Editions, technical section; licence key configuration · checked on 2026-11-04
Editions and price ideas
Community (free), Coach (this website’s proposal: approx. €9 per user per month, billed annually – Community plus Implementation Coach, learning path, Versioning advisor and Restart guide; part of Pro in the app today), Pro (approx. €19 per user per month, billed annually), Team (from approx. €2,500 per tenant per year), Enterprise (on request). Each edition includes everything in the one below it. The amounts are price ideas for validation; the binding price is the one in the quote. Pro via a payment provider, Team and Enterprise via quote, purchase order and invoice.
iFlowTailor product documentation, Editions; Coach edition proposal · checked on 2026-11-04
“In the works”: built, not yet in any release
Features marked “In the works” are built and automatically tested in the app repository but are not included in any published version. They have been checked with test data only; we confirm the connection to the SAP editor and SAP interfaces on a real tenant. Scope, edition and date may still change before release. We list them because they show where iFlowTailor is heading – not as a commitment.
iFlowTailor product documentation, Changelog, “Unreleased” section, 4 November 2026 · checked on 2026-11-04
Quick Review: Health Score with 40 rules
40 rules in six categories (security, error handling, performance, maintainability, operations, standards), counted at build time. Each rule deducts from the remaining score: the first finding Critical 15%, High 7%, Medium 3%, Info 0%, each further finding of the same rule half as much as the one before. The deductions are multiplicative – the score approaches 0 but never reaches it, and poor iFlows remain distinguishable. Each finding comes with its location, rationale and fix; a click jumps to the step in the editor. You can accept risks with a comment, and the report is exported as Markdown. Rules can be switched off or reweighted via team policy.
iFlowTailor product documentation, Rule catalogue and score formula (packages/rules), status after 1.1.0 · checked on 2026-11-04
Payload tools, Groovy Lint and snippets
Format and minify, XPath, JSONPath, XSLT, structured diff, Base64, GZip. Groovy Lint applies the catalogue’s rules to a pasted script. The snippet library contains commented Groovy scripts, with search.
iFlowTailor product documentation, User guide, Tools · checked on 2026-11-04
XML Workshop
XSD editor as a node tree with synchronised source, XML → XSD from several samples, XSLT mapping diagram with expected-versus-actual diff (XSLT 1.0 in the browser; 2.0/3.0 is detected and named), XPath editor with click-to-path and namespaces, sample payloads from XSD, WSDL, OpenAPI and OData EDMX. Works without a tenant.
iFlowTailor product documentation, Changelog 1.0.0, XML Workshop · checked on 2026-11-04
Test Studio and relay
REST, OData and SOAP with environments, variables, assertions and import from cURL and Postman. On-premise targets via a relay iFlow with proxy type On-Premise through the Cloud Connector; an allowlist limits the target addresses. You import the relay yourself – iFlowTailor never imports or deploys automatically. Test suites (Pro) run before and after deployment.
iFlowTailor product documentation, User guide, Test Studio; helper iFlows · checked on 2026-11-04
Groovy Runner
Runs a script against a sample payload and headers – via a runner iFlow in your own tenant, so on the real CPI runtime. The script open in the editor is picked up. Scripts run on a copy of the message with a time limit; the runner is intended for development and test tenants and needs a service key.
iFlowTailor product documentation, Changelog 1.0.0 and helper iFlows · checked on 2026-11-04
Adapter advisor
Checks sender and receiver adapters (including HTTPS, HTTP, OData, SOAP, SFTP, JMS, AMQP, Mail, IDoc) against a knowledge base: for each property “current vs. recommended” with rationale, source and confidence. Read-only. The Ask Tailor recommendation is part of Pro.
iFlowTailor product documentation, Changelog 1.0.0, Adapter advisor · checked on 2026-11-04
Naming Studio
Naming standard as a rule file with patterns per artefact type, graphical editor, generator, live check and tenant audit with a compliance rate per package. Templates are included; a team policy makes the standard mandatory.
iFlowTailor product documentation, User guide, Naming Studio · checked on 2026-11-04
Migration analysis, ISA-M, data lineage
Migration analysis (deprecated adapters and script APIs), classification against the ISA-M patterns and data lineage of a target field across mapping, XSLT and script. Part of Pro.
iFlowTailor product documentation, Editions, Pro · checked on 2026-11-04
Documentation generator
Interface documentation per iFlow or package from the tenant as Markdown, PDF or Confluence (upload after confirmation, token in the vault).
iFlowTailor product documentation, User guide, Documentation · checked on 2026-11-04
Error analysis by cause
Failed messages are grouped by normalised error signature instead of being listed one by one. A knowledge base of 23 known CPI error patterns (e.g. TLS handshake, 401 from the receiver, certificate chain, timeouts, mapping errors) provides the cause and a suggested fix.
iFlowTailor product documentation, User guide, Error analysis · checked on 2026-11-04
Deployments, certificates, monitor, runtime data
Deployments with drift between design-time and runtime state, certificates with an expiry traffic light and calendar export, message monitor with filters and counter, Data Stores, variables, number ranges, JMS and log files – read-only. “Not deployed” (Pro) shows changed artefacts that have not been deployed, with a notice in the editor.
iFlowTailor product documentation, User guide, Operations · checked on 2026-11-04
Trace Explorer, Message Journey, heatmap
Trace Explorer with payload and headers per step and a diff between steps; Message Journey across ProcessDirect, JMS and correlation ID chains; runtime heatmap in the process diagram and performance with percentiles. Part of Pro.
iFlowTailor product documentation, Changelog 1.0.0 and user guide · checked on 2026-11-04
Message forecast
Volume and load forecast for 7 or 30 days from 14, 30 or 90 days of history, for a tenant, iFlow, package or system. Explainable model based on the weekday pattern and a robust trend, with range, peaks, quietest window, error rate compared with the previous period and measured forecast accuracy; breakdown by hour and heatmap. Read-only, everything in memory.
iFlowTailor product documentation, Changelog 1.0.0, Message forecast · checked on 2026-11-04
Message Usage
Measurement as under Monitor → Message Usage: billable and excluded messages per day and month, projection to the end of the month with a range, comparison with the previous month, quota with a warning threshold, treemap package → iFlow. If the source cannot be read, the view estimates from the message processing logs and says so clearly. Part of Team. Status: beta. The feature uses an interface of the SAP web UI that SAP does not document as a public API; we are confirming it on real tenants together with our first customers.
iFlowTailor product documentation, Changelog 1.0.0, Message Usage · checked on 2026-11-04
Access Policies and Number Ranges
Coverage matrix package × role, warning for sensitive packages without full protection, check of the artifact references; number range utilisation with a forecast of when a range will be exhausted. Read-only, part of Team. Status: beta. The feature uses an interface of the SAP web UI that SAP does not document as a public API; we are confirming it on real tenants together with our first customers.
iFlowTailor product documentation, Changelog 1.0.0, Access Policies & Number Ranges · checked on 2026-11-04
Contents of Data Store and Message Store
Data Stores and persisted messages per iFlow with steps, expiry and retention; entries and contents on click, read-only and in memory only. The contents are fetched via the web UI’s download command, with the public API as fallback. Status: beta. The feature uses an interface of the SAP web UI that SAP does not document as a public API; we are confirming it on real tenants together with our first customers.
iFlowTailor product documentation, Changelog 1.0.0, Data Store & Message Store · checked on 2026-11-04
Dependencies
Graph per iFlow: sender and receiver systems, adapters, ProcessDirect and JMS chains, Data Stores, variables, value mappings, script collections, credentials and keystore aliases.
iFlowTailor product documentation, User guide, Dependencies · checked on 2026-11-04
Tenant index and grep
The index is built incrementally in the background and kept separately per tenant in IndexedDB. Full-text search and grep across iFlows, scripts, XSLTs, mappings, properties and parameters. Part of Pro.
iFlowTailor product documentation, User guide, Tenant index · checked on 2026-11-04
Tenant Compare, version diff, changelog
Tenant Compare puts the versions, parameters and deployments of two tenants side by side. The version history shows all versions with date, author and comment; the diff marks new, changed and removed elements in the process diagram. The changelog is generated without AI; optionally, Ask Tailor phrases it. “Suggest changelog” fills in the comment in the SAP “Save as version” dialog; saving remains up to you. Older versions require optional API access.
iFlowTailor product documentation, Changelog 1.0.0, version history and changelog generator · checked on 2026-11-04
Tenant Health, landscape and cleanup
Tenant metrics with trend (score, naming compliance rate, error rate, expiring certificates, unused artefacts), system map and cleanup candidates with rationale: no messages, never deployed, runtime only, empty package, unused script collection, draft in the runtime. Nothing is ever deleted automatically.
iFlowTailor product documentation, Editions, Team · checked on 2026-11-04
Security material as metadata only
Alias, type, expiry date and name are read. Private keys, passwords and secure parameters are not touched. iFlowTailor shows where each item is used, down to the step.
iFlowTailor product documentation, Security Whitepaper, section 2 · checked on 2026-11-04
Log analysis
HTTP access and error logs from the tenant’s log files or a local file, read-only and in memory only: status classes over time, latency percentiles, load peaks, 401/403 series, 5xx clusters, grouped error patterns.
iFlowTailor product documentation, Changelog 1.0.0, Security · checked on 2026-11-04
Vulnerability check
Local inventory of the bundled JARs and script imports, including those from referenced script collections. Only at your explicit request: a lookup against OSV.dev (Maven coordinates and version only, preview before sending, can be blocked via team policy) and the CISA KEV catalogue.
iFlowTailor product documentation, Changelog 1.0.0, Vulnerability check · checked on 2026-11-04
Security Risk Radar
Eight dimensions – transport/TLS, authentication, secrets, logging of sensitive data, certificates, error handling, script security, dependencies – for the tenant and the open iFlow, deterministic scores, drill-down to the exact location in the editor, daily history (numbers only). Part of Team.
iFlowTailor product documentation, Changelog 1.0.0, Security Risk Radar · checked on 2026-11-04
Ask Tailor with your own model and masking
Opt-in only. You choose the provider: Anthropic, Google Gemini, Mistral, SAP AI Core (Generative AI Hub), Azure OpenAI or an OpenAI-compatible endpoint, including a local model. The request goes directly from the browser to the chosen endpoint, never via a CloudDNA server. Before sending, email addresses, hosts, URLs, IPs, IBANs, tokens, secrets, message IDs and your own terms are replaced by placeholders; the reverse mapping happens locally, and the panel shows the text that was sent. Script code only after your explicit approval. Via team policy: block AI, restrict endpoints, enforce masking. 18 tasks in four groups. Part of Pro.
iFlowTailor product documentation, Security Whitepaper, section 4; AI providers and tasks · checked on 2026-11-04
iFlow from requirement
Ask Tailor drafts a specification from a description; iFlowTailor builds the iFlow from it (BPMN with diagram, parameters, scripts) and checks it with its own parser and the review rules. “Create in package” is a write action with confirmation and audit log, not deployed; addresses and credentials are externalised as parameters. The write path follows the public API but has not yet been confirmed on a tenant – hence beta.
iFlowTailor product documentation, Changelog 1.0.0, iFlow from requirement · checked on 2026-11-04
Team policies and custom rules
A team policy controls read-only mode, blocked actions, rules and severities, naming standard, custom rules, AI (allowed, endpoints, mandatory masking), minimum score and expiry date. Loaded from a file or URL, it applies only with a valid Ed25519 signature. Custom rules run as a safe JSONLogic subset without eval, or as XPath. Policy Studio assembles the policy, tests it and exports it for the browser policy.
iFlowTailor product documentation, Enterprise rollout and Security Whitepaper, section 5 · checked on 2026-11-04
Distribution via browser policy
IT distributes the extension, policy and licence key through managed configuration: Chrome and Edge via GPO/Intune (Windows), configuration profile (macOS) or JSON file (Linux), Firefox via policies.json. Users cannot change a policy distributed this way. Technically this works in every edition; Enterprise covers rollout support, licence scope and support SLA by contract.
iFlowTailor product documentation, Enterprise rollout · checked on 2026-11-04
Development and supply chain
TypeScript in strict mode, more than 270 automated tests, CI with type checking, tests and build on every push, nightly smoke test, few runtime dependencies, lockfile. Tenant data never enters the repository; test data is anonymised. Please report vulnerabilities to security@iflowtailor.com.
iFlowTailor product documentation, Security Whitepaper, section 7 · checked on 2026-11-04
Restart guide
Shows whether an iFlow can safely run again after an error and who triggers the retry (Cloud Integration, the next poll, the sender, the timer or the calling iFlow). Checks include the error path, bounded JMS retry with dead-letter queue, transaction handling, idempotency, store-and-forward, SFTP post-processing, timeouts, XI quality of service and AS2 MDN. Result: a verdict with score, a numbered step-by-step plan with jumps into the editor, a flow diagram, Markdown export, an explanation by Ask Tailor (masked, without payload) and a tenant-wide overview. Strictly read-only. Part of Pro in the app; this website proposes it for the Coach edition.
iFlowTailor product documentation, Changelog 1.1.0, Restart guide · checked on 2026-11-04
System map and outage analysis
The tenant index produces a map of every system the tenant talks to – detected via host, destination or JDBC data source, with chains via ProcessDirect and JMS and the Cloud Connector per location ID. Clicking a system simulates its outage: which iFlows fail, stop polling or no longer receive input, which callers fail with them, where JMS messages back up, which downstream systems stop receiving anything and how many messages are affected. In addition: a ranking of single points of failure, Markdown export for runbooks and an emergency plan with Ask Tailor (names and metrics only). Part of Team.
iFlowTailor product documentation, Changelog 1.1.0, System map & outage analysis · checked on 2026-11-04
Implementation Coach
In the product since version 1.2.0, part of Pro in the app; this website proposes its own Coach edition for it. A guided plan from the inbound side via validation, mapping, routing, receiver, error handling, restart, monitoring, externalisation and tests through to documentation – each step with the reasoning, best practices, typical mistakes and a jump to the matching view. A scenario text adds hints (synchronous, JMS, polling, timer, large volumes, on-premise, B2B, personal data). Comparison with the open iFlow: done, open, problem, with the next step highlighted. The learning path is stored locally only (rule IDs, scores, hash), can be switched off and deleted. Versioning advisor: major for an interface change, minor for a new feature, patch for a fix or configuration, none for a pure layout change, with a suggested comment. Ask Tailor tailors the plan (masked, without payload). Strictly read-only: the Coach changes no iFlow and saves no version.
iFlowTailor product documentation, Changelog 1.2.0, Implementation Coach · checked on 2026-11-04
Endpoint catalog
Since version 1.2.0, part of Community. All callable endpoints of deployed iFlows, APIs and OData services with the full runtime URL, protocol, status, version and who deployed when; from the tenant index, the sender’s protection (user role, client certificate, CSRF). Flags the default role ESBMessaging.send, endpoints without authorisation, CSRF switched off, duplicate paths and artefacts deployed with errors. Export as Markdown, CSV and Postman collection – URLs and methods only, no credentials. Strictly read-only.
iFlowTailor product documentation, Changelog 1.2.0, Endpoint catalog · checked on 2026-11-04
Header & property finder, externalised parameters
Since version 1.2.0, part of Pro. Finder: where headers, exchange properties and custom header properties are set, read and removed across the tenant (Content Modifier, Groovy and JavaScript, expressions in adapters, steps and routers, XSLT parameters, Allowed Headers), passed on via ProcessDirect and JMS, set but never read, and lost along a chain; message search over the last 7 days by the value of a custom header property. Values only for constants that do not look like secrets. Parameters: an inventory of all externalised parameters with unused, empty and conflicting values, as a map (treemap package → iFlow → parameter), a value matrix and by family, optionally with the live configured values. Secrets never appear in plain text in any view.
iFlowTailor product documentation, Changelog 1.2.0, Header & Property Finder and Externalised parameters · checked on 2026-11-04
Message Journey as a correlation graph
Since version 1.2.0, part of Pro. Related messages as a graph: handovers via ProcessDirect and JMS from the tenant index, otherwise followed by time; branches at splitter and multicast, missing follow-on iFlows as ghost nodes, the critical path to the message that ends last. A timeline with one lane per iFlow. Linked via correlation ID, application ID or a custom header; “Correlations in period” lists the groups of the last hour or 24 hours. Read-only, data in memory only.
iFlowTailor product documentation, Changelog 1.2.0, Message Journey as a correlation graph · checked on 2026-11-04
Downtime optimizer
Since version 1.2.0, part of Team. Finds the best window for planned downtime of one or more systems, a Cloud Connector or the whole tenant. Weights the expected messages per iFlow and hour of the week from history by their effect (fails at the sender, timer run is missed, waits in JMS, is picked up afterwards, follow-on iFlow idles), including chains via ProcessDirect and JMS. Result: the five best windows with score, expected messages, affected iFlows, timer runs and catch-up, confidence across previous weeks, a weekday × hour heatmap and blackout times. Export as a runbook and a calendar entry (.ics). Strictly read-only.
iFlowTailor product documentation, Changelog 1.2.0, Downtime optimizer · checked on 2026-11-04
Message flow analysis
Since version 1.2.0, part of Team. The system map with real traffic as a Sankey diagram: sender → iFlows (chains via ProcessDirect and JMS as further stages) → receiver. Width = messages of the last hour, 24 hours or 7 days; failed messages as a red sub-stream, retry and escalated as orange. Strongest flows, the systems with the most traffic, the iFlows with the most errors, growth against the previous period and load peaks. Export as SVG, PNG and Markdown. If an iFlow has several senders or receivers, its messages are split evenly (an approximation). Read-only, data in memory only.
iFlowTailor product documentation, Changelog 1.2.0, Message flow analysis · checked on 2026-11-04
Debugging in the editor (in the works)
In the works, not in any release, planned for Pro. Inline debugger: a run right on the iFlow diagram, steps green, red or grey, the router branch taken, duration per step, body, headers and properties before and after as a diff, time travel and a live bar of the latest runs; strictly read-only, trace data in the tab’s memory only. Run comparison: a failed against a successful run, aligned by step IDs, the first difference with its reason. Watched values: XPath, JSONPath, header and property as a column across all steps. Trace switch: log level set to trace for 10 minutes as a confirmed write action with an audit log entry; until the SAP call is confirmed on a real tenant, the write action stays locked in the extension. Traces stay in the panel’s memory (25 MB at most, never on disk). Variable inspector: values line by line in the Groovy Runner. The connection to the SAP editor is marked VERIFY in the code.
iFlowTailor product documentation, Changelog, “Unreleased” section: inline debugger, run comparison, watched values, trace switch, variable inspector · checked on 2026-11-04
Testing without deploying (in the works)
In the works, not in any release, planned for Pro. iFlow simulator: a payload sent locally through the iFlow without deploying (Content Modifier, router, filter, JSON/XML converters, Base64, splitter, XSLT, process calls), receivers from saved mocks, Groovy optionally via the Groovy Runner, steps that cannot be simulated are marked. Trace as regression test: after a preview and confirmation, sensitive and volatile values removed, local only. Path coverage from the run steps of the message processing logs. Check against OpenAPI, WSDL or EDMX with boundary cases as a collection. Test suite from a mapping specification (Excel, CSV). Test gate on the Deploy button, never blocks, can be set by team policy. DEV against QA: a request or collection sent to two environments. The SAP behaviour of individual steps in the simulator is marked VERIFY in the code.
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
Root cause search, incident report, ask the monitor, morning briefing (in the works)
In the works, not in any release. Root cause search (Pro): collects, read-only, the error text, step, model, changes since the previous version, deployment time, recent runs, the same error in other iFlows and the keystore, and turns them into weighted candidates with evidence. Checked fix (Pro): Ask Tailor suggests a minimal change; iFlowTailor applies it to a copy only and checks it with Groovy syntax, Groovy Lint and review rules; nothing is written into the iFlow. Why is field X empty? (Pro): a field, header or property followed through the iFlow statically and optionally with a trace. Incident report (Pro): timeline, impact, severity, cause, export as Markdown or Jira text. Ask the monitor (Pro): everyday language in German and English becomes an editable filter; Ask Tailor only as a fallback, with iFlow names and the filter schema. Morning briefing (Team): overnight anomalies against the same hours on previous days (median and MAD). Ask Tailor only ever receives masked data or aggregates.
iFlowTailor product documentation, Changelog, “Unreleased” section; editions, cut for debugging, testing and AI · checked on 2026-11-04
Stack trace decoder (in the works)
In the works, not in any release, planned for Community as part of error analysis. The error text is turned into the exception chain and the actual cause (“Caused by”), script file and line, affected steps and HTTP status; for each exception class (NullPointer, MissingProperty, ClassCast, NumberFormat, XPath, SAX …) the typical cause and fix. Your own script frames are separated from hidden framework lines. Offline, without AI.
iFlowTailor product documentation, Changelog, “Unreleased” section, Stack trace decoder · checked on 2026-11-04
Privacy guard (in the works)
In the works, not in any release, planned for Community. Detects personal data: email, IBAN (with checksum), phone, credit card (Luhn), date of birth, name fields and tax and VAT IDs. Shows where they occur and can mask them. Hooks into masking before Ask Tailor and warns before trace export and code export in the Test Studio.
iFlowTailor product documentation, Changelog, “Unreleased” section, Privacy guard · checked on 2026-11-04
Vendor
SAP Cloud Integration Cookbook
“SAP Cloud Integration Cookbook – Advanced Cloud Integration with SAP Integration Suite” by Martin Koch, Thorsten Reisinger and Marc Urschick, SAP PRESS. In iFlowTailor, known error patterns refer to the relevant book by the authors.
Rheinwerk Verlag (SAP PRESS) · checked on 2026-11-04
Books by the authors at SAP PRESS
In addition to the Cookbook: “Cloud Connector für SAP”, “SAP Business Technology Platform – Sicherheit und Berechtigungen”, “SAP Business Technology Platform – Administration” (each also available in English) and “Git und SAP – Versionsverwaltung und Transporte” (German titles).
Rheinwerk Verlag (SAP PRESS) · checked on 2026-11-04
OSV.dev – vulnerability database for open source
Public database of vulnerabilities in open-source packages, including Maven artefacts. iFlowTailor queries it only at your explicit request and sends only Maven coordinates and version.
OSV.dev (Open Source Vulnerabilities) · checked on 2026-11-04
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