What's new in iGlow

iGlow 0.8.48

• Before you approve a deploy, the card lists what the iFlow needs that is not ready on the tenant: a missing credential or key, a placeholder login, or a Script Collection or message mapping that is not deployed. It is a warning only; you can still deploy.
• New SFTP check: iGlow can ask the tenant for an SFTP server's host key and gives you the exact line to add to Known Hosts, also for servers behind the Cloud Connector.
• Clearer explanations for SFTP host key errors ("reject HostKey", "HostKey has been changed"), a Data Store entry that already exists, and receivers that refuse too many headers.
• No new permissions.

iGlow 0.8.47

• If you remove iGlow, a short optional page asks why, so we know what to fix.
• After a change that worked, iGlow may ask once for a store review. It asks at most twice, and never again once you say yes.
• No new permissions.

iGlow 0.8.46

• Simulations of long iFlows now count steps the way SAP does, including the steps inside a called local process. A range that is too long is split into parts before SAP refuses it.
• When a simulation can't run on the tenant, iGlow stops retrying after the second try and asks you whether to deploy without it. The deploy card says that the change was not simulated, and shows the last simulation that failed.
• Test requests can now go to a sub-path or with query parameters, such as ?v=1.
• Router conditions that read the message body are caught before saving, with what to do instead: SAP only accepts headers and properties there, or an XPath condition on an XML body.
• iGlow now sees the credential set on OData receivers, so "where is this credential used" finds them.
• Shorter answers, without repeated reminders.
• No new permissions.

iGlow 0.8.45

• Fewer runs that end with "Lost the connection to the iGlow server" after the answer was already written: the panel now goes on with the finished step.
• Dropdown values whose name has brackets, like "Query (GET)", and empty dropdown values are now set correctly.
• No new permissions.

iGlow 0.8.44

• Ask for a technical design document and iGlow makes it as a Word file: it fills your own Word template, or uses iGlow's layout with a picture of each process, the mapping rules, scripts, checks and the iFlows it depends on. You can add test data: one real test request (needs a service key in the Test tab), a recent message from the monitor, or a simulation.
• Test one message mapping with your own sample input, without deploying it.
• Check from the tenant whether a host is reachable over TLS, so you see unknown hosts, timeouts and certificate problems without testing from your laptop.
• Long iFlows can now be simulated: runs longer than SAP's 10-step limit run in parts.
• Lay out the main path in rows and change a step's size; copy an iFlow and change the copy with one approval.
• Safer mapping changes: iGlow refuses to save a change that would drop mapping rules it did not mean to touch.
• Dates and script lines that only name a key are no longer hidden as phone numbers or secrets; real phone numbers and passwords still are.
• Fewer failed edits: renaming many steps at once, Mail, SFTP, JMS and Kafka on a Send step, schema file paths and Splitter settings are put right for you, and a locked iFlow now says who holds the lock and since when.
• Big XSD and WSDL files are read as a short outline, and scripts can be searched for a word.
• Faster, cheaper chats: iGlow keeps its common tools ready and loads rarely used ones only when needed.
• After you switch iFlows, an "Ask the same for this iFlow" chip repeats your last question there.
• No new permissions.

iGlow 0.8.43

• If an iFlow, script or mapping is saved by someone else while an approval card is open, iGlow now saves nothing and says so, instead of overwriting that work.
• Download an iFlow's externalized parameters as an Excel file.
• The SAP tab is marked while a card there waits for your answer.
• While the model thinks, the chat shows it ("Thinking… 23 s").
• Message mappings: up to 500 changes in one go; long mappings are read as one rule per target field.
• Searching a long message attachment for a word, and reading it in parts.
• Fewer failed iFlow builds and test runs; step names are found even when written with hyphens or underscores.
• Check a long list of iFlow names in one go: iGlow says which exist, where, and which don't.
• Make the same change to many iFlows at once (up to 25), with one approval; iFlows that are locked, not iFlows, or changed meanwhile are left alone and listed.
• An approval you missed while away no longer gets lost: the request pauses, nothing is saved, and you can still approve it later.
• Content Enricher and Poll Enrich steps are now connected to their system the way SAP expects, so deploy no longer fails with "no incoming connector".
• iGlow now reads Timer schedules, polling schedules and Looping Process Call conditions when it explains an iFlow.
• "Fix with iGlow" no longer shows on messages that completed.
• When a failed message comes down to a message mapping, iGlow can now open and fix the mapping in the same chat.
• No new permissions.

iGlow 0.8.41

• AI usage is now a monthly allowance plus a daily one, instead of a week and a 5-hour window. Two small bars under the chat box, Today and Month, show how much is used at a glance (hover for the reset times); past 80% they turn into a sentence with an Upgrade link. Settings shows the same two bars with percentages. A request already running when the day runs out may finish.
• New plan sizes: Free about 200 AI requests a month (still doubled until 31 December 2026), Pro $25/month with 4× Free, Max $100/month with 20× Free.
• Message mappings: iGlow can now use all 74 of SAP's standard mapping functions, with the same dropdown values as SAP's editor, and checks date patterns before saving.
• Reading a message mapping now shows the rows of a FixValues table.

iGlow 0.8.40

• "Explain this iFlow" answers start sooner: a question about the whole iFlow no longer waits for long thinking. Questions about a single step keep the deeper thinking.
• When you ask for exactly your steps, or no logging steps, a new iFlow no longer gets an extra "Set log headers" step.
• When a failure comes from a message mapping, iGlow now reads the mapping itself instead of saying it can't open it.
• The package overview says when a ProcessDirect address is served outside the package, so iGlow no longer guesses which iFlow serves it.
• Ask about your plan or your usage limit and iGlow can now tell you how much of this week's allowance is used and when it resets.
• Shortening a long chat costs less.
• iGlow can now build a message mapping inside an iFlow, copy a package mapping into an iFlow, and change a mapping that already lives inside an iFlow.
• Reading a mapping now shows the code of its custom functions and every constant it uses.
• iGlow can add XML schema (XSD), WSDL and EDMX files to an iFlow, remove or rename files, and remove parameters that nothing uses.
• Dropdown settings such as Proxy Type "On-Premise" or the Content Modifier's "Global Variable" are now saved the way SAP expects, instead of failing with "Invalid value".
• Polling senders such as SFTP can now poll every few minutes or hours, daily at a set time, or on a cron schedule, in your time zone.
• iGlow can create a package, list all your security material, and delete a credential after checking that nothing uses it.
• Attach an OData $metadata file and iGlow reads the field names of each entity from it.
• When a test run needs a message mapping to be deployed first, iGlow now says so.
• No new permissions.

iGlow 0.8.39

• Pressing Stop while iGlow saves an iFlow is safer: your next message waits for the save to finish, and iGlow then knows whether it went through instead of guessing.
• Script fixes change only the lines they are meant to, also in scripts with Windows line endings.
• New on SAP pages: a "Changed since deploy" or "Not deployed" pill on the Artifacts list and in the iFlow editor, and a ProcessDirect pill that lists the addresses an iFlow uses, with a link to see who else uses each one.
• Long chats cost less: out-of-date iFlow details from earlier messages are shortened, and very long runs are trimmed once before they reach the higher price.
• When the main AI model fails in the middle of a run, the backup model now takes over properly.
• No new permissions.

iGlow 0.8.38

• Hovering a package row now shows the right thing: the full package name on the name, and who changed it and when on the date.
• Ask how to set up a JDBC data source and iGlow opens the JDBC Material page and lists the fields to fill in.
• No new permissions.

iGlow 0.8.37

• Building an iFlow fails less often on small mistakes: the HTTP address of a Request Reply step can be made configurable.
• A missing route name now lists the Router's real routes, and a step is no longer mixed up with a route of the same name.
• When the agent sends a list in the wrong form, iGlow reads it when the meaning is clear, or says exactly what to fix.
• A failed step that a later step put right is shown grey instead of red, so red means something still needs attention.
• No new permissions.

iGlow 0.8.36

• Pro and Max plans can now be bought: choose Upgrade in Settings or on the usage-limit message. Payment is
• Settings shows Manage plan once you are on a paid plan, to change card, switch plan or cancel.
• No new permissions.

iGlow 0.8.35

• A credential iGlow created as a placeholder stops showing as a placeholder once you save it with the real user
• The Scripts tab no longer closes the panel after you change an iFlow's Configure values.
• Timers can run every few hours ("every 2 hours").
• Fewer suggested next messages that lead nowhere.
• No new permissions.

iGlow 0.8.34

Covers 0.8.31 to 0.8.34 (0.8.33 was not uploaded).

• Paste a screenshot into the chat, or attach or drop a PNG, JPEG, GIF or WebP picture. Pictures are made smaller
• Package rows show how many iFlows are not deployed, and "changed since deploy" for deployed ones edited later.
• A package you just made in SAP shows up without reopening the panel.
• On an iFlow page, that iFlow is shown first in its package, and its failed messages and health refresh on their own.
• A small puppy walks along the chat box as you type, runs back when you send, and digs while the agent works.
• Fewer failed edits: exception subprocesses get one End, steps added to one route keep the order you asked for, and
• Suggested next messages no longer make up hosts or values.
• Long runs cost less: the chat history is no longer rewritten on every step.
• No new permissions.

iGlow 0.8.33

Covers 0.8.31 to 0.8.33.

• A small puppy walks along the chat box as you type, runs back when you send, and digs while the agent works.
• Fewer failed edits: exception subprocesses get one End, steps added to one route keep the order you asked for, and
• Suggested next messages no longer make up hosts or values.
• Long runs cost less: the chat history is no longer rewritten on every step.
• No new permissions.

iGlow 0.8.30

Covers 0.8.20 to 0.8.29.

• Attach files to the chat, such as a specification or a sample payload. Long files get a table of contents, so the agent reads only the sections it needs. Long chats are shortened automatically so they can go on.
• The agent asks once whether a tenant is for development and test or for production, and it can add Error End Events.
• Adapter variants are named the way SAP's editor shows them, for example "SAP RM" or "Plain SOAP".
• Fewer failed steps while the agent edits: a step name that is almost right is matched or suggested, a simulation that SAP refuses once is retried, and before a deploy the agent names the steps it has not tested.
• The chat box grows with your text and can be dragged taller.
• iGlow finds your tenant from the SAP domain and page address. On any other page, a "Use this tab" button connects it.
• No new permissions.

iGlow 0.8.19

• After an edit, the lines in the iFlow diagram meet their steps again. Before, a line could stop just short of a step it had moved or changed.
• When SAP won't start a simulation, you see all of SAP's reasons.
• The "session expired" warning goes away as soon as SAP answers again.
• No new permissions.

iGlow 0.8.18

• iGlow remembers what you teach it, like naming rules, the package you use or how you like answers, and uses it in your later chats instead of asking again: each note only for the tenant, package or iFlow it is about, and only when it helps. Only you see it. Ask the chat to change or forget a note; see the list, clear it or switch memory off under Settings → Advanced.
• No new permissions.

iGlow 0.8.17

• The agent can connect and disconnect steps, and remove steps where branches meet, empty exception subprocesses and unused local processes, so you no longer have to fix those in the SAP editor.
• Simulations start in the main integration process, not a local one, and accept step names.
• Values like {{Host}} typed into a step become real externalized parameters.
• Scripts kept in a Script Collection can be read, and the agent remembers the package after it opens another page.
• A request that ends without an answer says so.
• No new permissions.

iGlow 0.8.16

• An approval card that waits for you shows how long it has waited, puts a mark on the toolbar icon, and is dropped after 10 minutes with nothing changed. Time spent waiting for your answer no longer counts against a request's 15 minutes.
• Message mappings with several source messages can be changed, and reading a mapping says which fields use functions iGlow cannot write (custom functions, for example).
• A Message Mapping step that SAP reports as "Mapping file not found" comes with the fix.
• A mapping deploy stops waiting when the SAP tab or session is gone, and says so.
• No new permissions.

iGlow 0.8.15

• The side panel shows your AI usage as a share of your plan's weekly and 5-hour allowance, so a quick question uses less of it than building an iFlow. Settings shows both, and the free plan's launch offer (usage doubled until 31 December 2026).
• No new permissions.

iGlow 0.8.14

• The agent tests a change before it deploys it: it runs SAP's simulation with the reply it expects, and deploy refuses changed steps that no passing simulation has covered, unless you agree to deploy them untested.
• Simulations run to the end of the normal route and say why when SAP refuses to start one.
• JSON to XML (and back) with SAP's standard converter, new iFlows that follow SAP's design guidelines from the start, and Message Mapping steps that point at a mapping in the package.
• Search, where-used and iFlow comparisons find every iFlow of a large package, and show the address behind a configurable parameter.
• Rate an answer with thumbs up or down, with reasons and a comment.
• E-mail addresses you type in the chat are passed on as typed, so they can be used in a Mail adapter; ids that look like phone numbers are no longer masked.
• No new permissions.

iGlow 0.8.13

Covers 0.8.12, which was not published to the store.

• New JMS and Mail channels (and other adapters whose newest version the tenant cannot build yet) are written at the version the tenant supports, so they deploy instead of failing with "not supported in Cloud Integration profile".
• Message mappings can use arithmetic and comparison functions (add, greater, less, equalsA, round, substring and more).
• Fewer failed edits: steps placed with stepId, a second exception subprocess, renaming a process, and a parameter in a one-column table now work; clearer errors when a script name is wrong.
• No new permissions.

iGlow 0.8.12

• Package overviews, iFlow documents and tenant comparisons now show the values set in Configure (for example a PROD address), not only the defaults in the iFlow design. Links between iFlows through ProcessDirect and JMS use those values too.
• No new permissions.

iGlow 0.8.11

Covers 0.8.9 and 0.8.10, which were not published to the store.

• Hints right on SAP's pages, with no AI needed: a heat map on the iFlow canvas (where messages fail and how long steps take), a step-by-step walk-through of the path a message took, the Timer schedule in plain words with runs that did not happen, a table of Router conditions, waiting and failed messages in JMS queues, and failure counts on a package's Artifacts tab.
• Hard-coded settings in an iFlow can be turned into configurable parameters in one go.
• Message mappings: create them from XSD files, use mapping functions, and deploy them. XSLT, XSD, WSDL and other text files of an iFlow can be saved too.
• The chat agent can do more: Local Integration Processes and Process Calls, iFlow process settings, adapter variants, copying and deleting iFlows, runtime settings, and blank, Timer and SFTP starter iFlows.
• More reliable saves: when SAP answers a save with a server error, iGlow tries once more the way a page reload would, and otherwise explains what went wrong. Deploy errors show SAP's own reason.
• The side panel opens only on the tab it was opened from.
• No new permissions.

iGlow 0.8.8

• Faster simulations: iGlow reuses the test setup SAP prepared for an unchanged iFlow, like the editor does (a rerun takes about 2 s instead of 9), and simulations of one iFlow prepare side by side.
• The chat agent builds a new iFlow in one go more often: steps and routes can be referred to by name ("after Call HTTP", "on Not Found"), a step "after a Router" goes on its default route, and a route without a condition can become the default one.
• Groovy scripts are also checked for quoted builder element names and for empty catch blocks (which SAP's script check flags).
• No new permissions.

iGlow 0.8.7

• Chat agent tests its changes more reliably: a simulation now follows the route a Router actually sends the message down, instead of stopping at it and reporting success.
• The agent keeps a list of changed steps and routes that no simulation has run yet, and works through it before deploying.
• Groovy scripts are checked when saved for mistakes that fail at runtime (for example a builder element named like a variable).
• When a test call fails, the agent reproduces it in the simulation to find the failing step, instead of waiting for the message log.
• No new permissions.

iGlow 0.8.6

• "Document this iFlow" (Overview tab) replaces "Document this package": one iFlow as a Word file or an HTML file that prints to PDF.
• The document covers the diagram, route, adapters, externalized parameters, scripts, credentials, error handling, deploy state and a "How to test" section with the request, expected outputs and test scenarios.
• Upload a customer's Word template (.docx/.dotx): iGlow fills its matching headings and label fields and puts the rest in an appendix. Templates stay in the browser (IndexedDB).
• Made in the browser, without AI and without sending anything to iGlow's servers. No new permissions.

iGlow 0.3.0

• Test tab starts with a sample request body built from the iFlow (JSON or XML, with the fields the first steps read); "Suggest body" asks the AI for a realistic one (counts as a triage call).
• After a test call, the response shows the message's status; a failed message shows the failing step and error, with "Fix with iGlow" to start the fix flow in Chat.
• No new permissions.