As part of the new Interoperability UI wave (see what was new in 2025.1, and 2025.3 by @Aya Heshmat), v2026.1 which is available already as a Developer Preview, and this could be a reason for you to give it a ride - will be shipping the new UI for the BPL editor (and other UI goodies).

He's a quick teaser:

Hi community,

I've been working on a side project that I'd love to get some eyes on: a ground-up rebuild of the classic IRIS Production Monitor using a modern web stack. The existing ZEN/CSP-based portal does the job, but I wanted to explore what a contemporary, real-time version of it could look like.

What it is

A standalone Angular web application that connects to any Interoperability-enabled IRIS namespace and gives you a live view of your production — services, processes, operations, queues, event log, and message traffic — all in one screen.

I may have mentioned this before: I believe the Visual Traces, these sequence diagrams with full content of each step, are a fantastic feature of the IRIS Data platform! Detailed information about how the API works internally, as a visual trace, can be very useful for projects on the IRIS platform. Of course, this applies when we are not developing a high-load solution, in which case we simply don't have time for saving/reading messages. For all other cases, welcome to this tutorial!

Hello all,

I have a EnsLib.HTTP.GenericMessage inbound from a webhook with a GC stream.

My router is defined as the following:

Dear Developer Community member,

We’re excited to share a new free, interactive tutorial designed to introduce developers to one of the core strengths of InterSystems IRIS — its unified multi-model architecture.

🧑‍🏫 Data Models of InterSystems IRIS 🧑‍💻

In just 5–10 minutes, this short lab walks you through creating a persisting class, querying it with SQL, and inspecting how the data is stored at the global level — giving you a practical understanding of how IRIS connects object, relational, and hierarchical models on a single data engine.

Happy learning!

If you have ever dug through a large IRIS namespace looking for where a particular string, method call, or pattern was used, you know the pain: there was no built-in way to do a grep-style search across your server-side ObjectScript code from VS Code — at least not without jumping through some hoops.

That is what ObjectScript Search fixes.

Try it today with a simple install from the VS Code Marketplace. If you don't like it, uninstalling is just as easy. But I think you will like it — it is a huge quality-of-life improvement for anyone doing ObjectScript development in VS Code.

Already included in SystemPerformance

There are nfs disk commands (including nfsiostat) included with SystemPerformance, but disabled by default. Enable them by running:

$$Enablenfs^SystemPerformance()

Doing so will add the following nfs commands, for example, on Linux:

1. /usr/sbin/nfsstat -cn
2. /usr/sbin/nfsiostat [interval] [count]

Ensure the commands are installed and runnable from the OS :)

This can be subsequently disabled via $$Disablenfs^SystemPerformance()

Adding a generic command to SystemPerformance

Adding an arbitrary OS tool creates a "user" command under ^IRIS.SystemPerformance("cmds","user")

Hi, Community!

🤔Did you know that InterSystems has a full catalog free online learning resources to help you get up to speed with our products and features?

🎓 Check out this quick introduction, then head over to the online learning site to explore resources like interactive exercises, learning paths, and online courses!

Welcome to InterSystems Online Learning 

Hi Community!

Welcome to Issue #27 of the InterSystems Ideas newsletter! Let's look at the latest news from the Ideas Portal, such as:

✓ General Statistics
✓ New sweepstakes!
✓ Recently implemented ideas by InterSystems

We are trying to track down significant growth within our Namespaces, one big culprit is Ens.AppData (EnsLib.SQL.Snapshot). 

Within many of our BPL's we use EnsLib.SQL.Snapshot to return Results from External SQL Stored Procedures or Query's. The same EnsLib.SQL.Snapshot context variable is used for many of these calls within a BPL. 

Is there something we should be doing at the end of the BPL to ensure that EnsLib.SQL.Snapshot gets cleaned up and purged from Ens.AppData?