Changelog

Latest updates and improvements.

2026-10-2423:59

Show Details

FixSecurity patch round. Next.js 16.4.3 and DOMPurify 3.4.17 close two critical advisories, and every other library is on its latest compatible version. On the server side, the Go libraries are updated (x/net, x/crypto, x/image and the rest) and the platform builds with Go 1.27.3, which closes the certificate (crypto/x509) and HTTP/2 advisories in the standard library. A vulnerability scan of every module now finds nothing. The charts, icons, animations and diagrams moved to their new major versions (mermaid 12, lucide 1, framer-motion 14) without visible change.
FixThe API reference loads again: one description in the migration equivalence route broke the whole openapi.yaml for the Spectre API subset.

2026-10-2323:59

Show Details

FeatureEverything an AI does with a tool is now traceable. A tool called while answering a chat message is part of that conversation's trace, with whether access allowed it, which agent asked and how much came back. Calls from cascades and from external agents over MCP are recorded the same way; MCP calls were not recorded at all before.
FeatureLong AI runs keep their history. The runs that write policy descriptions for a gateway are kept per run and per policy: who started a run, how it ended, and for each policy whether it worked, how long it took and why it failed. See it under Geschiedenis van de beschrijvingsruns on the Layer 7 Capabilities page, or ask chat. A run cut off by a restart now says so.
FixThe audit log records what really happened. A request the role guard refused shows as refused (403) instead of as a success, each row says how long the request took and who acted, and the platform's own calls are recorded under the system identity instead of being left out.
FixThe comparison table in the combined health check centres its figures under the gateway names.

2026-10-2323:59

Show Details

FeatureOne health check over all gateways of a customer. When a customer has more than one gateway, such as CIBG's external EGWO and internal IGWO, Layer 7 Settings offers one Word report over all of them. The gateways are compared side by side, then each gets its own summary. A new chapter shows what connects them: policies that route from one gateway to the other, calls that only the other gateway can resolve, and policies with the same name that have drifted apart. The observations carry each finding under its gateway, and the appendices follow per gateway. Chat and MCP give the same report.

2026-10-2323:59

Show Details

FeatureThe health check can now be read policy by policy. Every policy in Bijlage A has its own relationship map, showing who calls it, what it calls, which services reach it, and calls to building blocks missing from the export. It also has its own routing map, showing where its traffic goes, both its own routes and those of every building block it reaches, with plain HTTP in red. A service whose route sits two includes down no longer reads as routing nowhere. The overall maps in Bijlage B and C stay as they were.

2026-10-2223:59

Show Details

FeatureAdeptia triggers become Boomi schedules. On the migration Triggers page, every scheduled trigger now comes with its Boomi process schedule, and the timing is proven: the Adeptia original and the Boomi schedule are compared minute by minute over two weeks in the trigger's time zone and must fire at exactly the same moments. Each event type gets its Boomi pattern (a scheduled file or database poll, or a listener), and a CSV and ready-to-fill AtomSphere payloads can be downloaded. On the real export, all 100 schedules are proven equal. Chat and agents can read it too.
FixA description run that a platform restart interrupted no longer shows as still running; it says it stopped, so you can start it again.

2026-10-2223:59

Show Details

FeatureBring APIs from MuleSoft and Axway into Layer 7. On the new Convert page in Layer 7, paste or upload a MuleSoft API Manager API with its policies, a Mule 4 application, or an Axway APIM-CLI api-config.json, and every API comes out as a Layer 7 service policy, scored like any imported one. Each source policy is marked as mapped, partial (with the step that still needs a person), or manual. Passwords and keys from the source are never copied. Store the APIs you choose in the workspace in one step; chat and agents can run the conversion but not store it.

2026-10-2223:59

Show Details

FeatureThe Layer 7 health check report is fully Dutch. Findings, advice and control names are written in Dutch, and each policy in Bijlage A is described in Dutch: "Nederlandse beschrijvingen voor het rapport" on the Capabilities page writes those on our own model, next to the English descriptions the policy pages keep. Names of assertions, variables and services stay as the Policy Manager shows them, and the monthly comparison still matches last month's findings.

2026-10-2223:59

Show Details

FixIn the Layer 7 health check report, each policy's description in Bijlage A now shows bold text, code names and lists as real formatting, instead of loose asterisks and backticks.

2026-10-2123:59

Show Details

FeatureCustom roles. An administrator can create a role such as "Enable U consultant", tick the tools it includes (Layer 7, Migration, Tenders, Bastion, MEDDPICC, AI chat), and give it to an account on the Users page. That account then reaches only those tools, plus signing in, its own profile, notifications and the documentation. Everything else is refused by the server, in the AI chat too, not just hidden from the menu. Bastion is opened as a non-admin: the vaults are read through their registered purposes, and administrator actions stay with administrators.
FixThe Role column on the Users page now saves. Viewer and operator roles were being dropped because the account had nowhere to store them, and no account can set its own role.

2026-10-2123:59

Show Details

FeatureThe Layer 7 designer keeps up with Broadcom. The assertion documentation it explains from is read again from Broadcom's techdocs every week, for each documentation version you watch (11.1, 11.2 and others), and Settings lists what changed: assertions added, removed, renamed or moved, and documentation text that changed. It also warns when a rename would cut an assertion the designer can build off from its documentation. Nothing changes until an administrator approves it, and you can switch between approved versions or back to the built-in catalogue. Chat and agents can see the changes and start a read, but not approve one.

Page 1 of 12