All features.

Build, review and test – in the context of the iFlow that is open in the editor right now.

• Community

  Quick Review

  Health score 0–100 for the open iFlow, 40 rules in six categories. Each finding comes with a reason, location and fix; a click jumps to the step. Accept risks with a justification, export the report as Markdown.¹⁸

• Community

  Payload tools and Groovy Lint

  Format, XPath, JSONPath, XSLT, diff, Base64 and GZip. Groovy Lint checks pasted scripts against the rules of the review rule set.¹⁹

• Community

  XML Workshop

  XSD editor as a node tree, XSLT mapping as a diagram with an expected-vs-actual test, XPath editor with click-to-build paths, XML → XSD and sample payloads from XSD, WSDL, OpenAPI and EDMX.²⁰

• Community

  Test Studio

  REST, OData and SOAP with environments, variables and assertions, import from cURL and Postman. On-premise targets via a relay iFlow through the Cloud Connector.²¹

• Community

  Adapter advisor

  Sender and receiver adapters checked against a knowledge base: “current vs. recommended” for each property, with a reason. The Ask Tailor recommendation is part of Pro.²²

• Community

  Naming Studio

  Generate and check names against a standard, tenant audit with a compliance rate per package. You build the standard in the graphical editor.²³

• Community

  Groovy snippets

  Commented scripts to copy – headers, attachments, size-capped logging, exception handling – with search.¹⁹

• Pro

  Groovy Runner

  Run the script open in the editor against a sample payload – on the real CPI runtime, via a runner iFlow in your own tenant, without deploying the actual iFlow.²⁴

• Pro

  Test suites

  Saved tests per iFlow with assertions, to run before and after deployment.²¹

• Pro

  Migration analysis, ISA-M, data lineage

  Deprecated adapters and script APIs, classification into ISA-M patterns, the origin of a target field traced through mapping, XSLT and script.²⁵

• Pro

  Documentation generator

  Interface documentation per iFlow or package as Markdown, PDF or straight into Confluence – generated from the tenant, so it is up to date.²⁶

• Coach

  Restart guide

  Can the iFlow safely run again after an error – and who triggers the retry? A verdict with a score, a numbered build plan that jumps into the editor, a flow diagram and a tenant-wide overview.¹⁰

Errors by cause, deployments, certificates, messages and load – without paging through the monitor.

• Community

  Error analysis

  Failed messages grouped by cause instead of one by one, with a suggested fix from a knowledge base of known CPI errors.²⁷

• Community

  Deployments with drift

  Design time against runtime: changed since deployment, failed deployments, drafts in the runtime.²⁸

• Community

  Certificates

  Expiry traffic light with calendar export and usage down to the step.²⁸

• Community

  Message Monitor and runtime data

  Messages with filters and counters, Data Stores, variables, Number Ranges, JMS and log files – read-only.²⁸

• CommunityBeta

  Data Store and Message Store per iFlow

  The iFlow’s stores with steps, expiry and retention; entries and content on click, held in memory only. Content is read through an interface of the web UI.²⁹

• Pro

  Trace Explorer and Message Journey

  Payload and headers step by step, diff between steps, messages followed across ProcessDirect, JMS and correlation ID.³⁰

• Pro

  Runtime heatmap and performance

  Runtime per step in the diagram, percentiles per iFlow, the slowest steps.³⁰

• Pro

  Not deployed

  Everything that has been changed but not deployed – with a notice right in the editor.²⁸

• Pro

  Message forecast

  Volume for 7 or 30 days and per hour, with range, peaks, the quietest window and measured forecast accuracy.³¹

• Pro

  Correlation graph

  The messages of one correlation as a graph and timeline: hand-overs, branches, missing follow-up iFlows and the critical path – linked by correlation ID, application ID or a custom header. Plus all correlations of the last hour or 24 hours.⁶

• Community

  Endpoint catalog

  All callable endpoints of deployed artifacts in one place: URL, protocol, status and protection. Flags missing role protection and duplicate paths, export as Markdown, CSV or Postman collection.⁴

• TeamBeta

  Message Usage

  Billable and exempt messages per day and month, projection to the end of the month, quota with a warning threshold.³²

• TeamBeta

  Access Policies and Number Ranges

  Which roles protect which packages, gaps in sensitive packages; Number Range usage and when a range is likely to run out.³³

• Team

  Downtime optimizer

  The best window for planned downtime of a system, a Cloud Connector or the whole tenant: the five best windows with expected messages, affected iFlows and timer runs, plus a runbook and a calendar entry.⁸

• CommunityIn the works

  Stack trace decoder

  Instead of 80 lines of Java: the actual cause, script file and line, the affected step and the typical fix per exception class. Offline, without AI.¹⁶

• ProIn the works

  Root cause search with a checked fix

  Error, deployment time, version diff, the same error in other iFlows and the keystore as weighted candidates with evidence. Ask Tailor suggests a fix; iFlowTailor checks it on a copy before you see it.¹⁵

• ProIn the works

  Incident report

  Timeline, impact, severity and probable cause from the message processing logs of a period – ready as Markdown or Jira text.¹⁵

• ProIn the works

  Ask the monitor

  “Failures from yesterday to customer 4711 over 5 s” becomes an editable filter that you see before the query runs. German and English; Ask Tailor only as a fallback.¹⁵

• TeamIn the works

  Morning briefing

  What was unusual since last night: error spikes, iFlows failing for the first time, new error patterns, missing timer runs – measured against the same hours on previous days.¹⁵

Security material, logs, dependencies and the security posture of the tenant.

• Community

  Security Material

  Credentials, OAuth clients, keystore and PGP – metadata only, with usage down to the step.³⁸

• Pro

  Log analysis

  HTTP access and error logs: status classes over time, latency percentiles, 401/403 series, load peaks – in memory only.³⁹

• Pro

  Vulnerability check

  Local inventory of JARs and script imports; checked against OSV.dev only when you explicitly ask, with a preview before anything is sent.⁴⁰

• Team

  Security Risk Radar

  Security posture of tenant and iFlow in eight dimensions, with history and drill-down to the exact location in the editor.¹²

• CommunityIn the works

  Privacy guard

  Finds email addresses, IBANs, card and phone numbers, dates of birth and tax IDs before they end up in an export or with Ask Tailor, and masks them.¹⁷

The AI assistant that uses your own model – only after opt-in, with masking before anything is sent.

• Pro

  Ask Tailor

  18 tasks in four groups: explain errors, find the cause of a run, predict a message, suggest Groovy and mappings, interface specification, operations manual, test cases – with your own model.⁴¹

• Pro

  Advisor in the views

  Ask Tailor where the question comes up: in the monitor, in error analysis, in the review, in the runner, on the adapter and on the changelog.⁴¹

• ProBeta

  iFlow from requirements

  Describe the integration in your own words, Ask Tailor drafts it, iFlowTailor builds and checks the iFlow and, once you confirm, creates it in the package – not deployed.⁴²

• ProIn the works

  Why is field X empty?

  Follows a field, header or property through Content Modifiers, scripts, mappings and ProcessDirect – optionally with the trace of a run – to the link where the value gets lost.¹⁵