Keep up with latest product news



Initial Release
This is my entry to the ongoing programming contest.
This is an IRIS API Explorer. The API Is sorted into different categories and submit types. You can test out the API safely under different privileges. There is a rollback feature for any data changes or deletes.
Thanks!

Initial prototype for local InterSystems IRIS 2026.2. Six live management views, reviewed task/web/role/wallet operations, bounded audit and journal metadata searches, Docker Compose installation instructions and demonstration fixtures. Includes three public English-captioned walkthroughs. AI-assisted development; administrative test instance only. See README and DEMO.md for validation and limitations.
Listing update: adds the public interactive walkthrough at https://rafaorlando3.github.io/iris-relay/. The walkthrough uses fictional data only and needs no credentials. Source remains release 0.2.0, commit fe585681ed05719c202856d4dbf422a1685e5679, with 42 JavaScript and 6 Python tests passed and reversible live checks on IRIS 2026.2 ARM64.






Platform-independent Docker demo.

First public release.
iris-bi-cube-cache-warmer; install with zpm "install iris-bi-cube-cache-warmer"
A docs-only patch resolving two setup blockers reported during the Open Exchange review. No code or public-API changes; existing installations do not need to be recompiled or reconfigured beyond the SSL step below.
%Embedding.Config.VectorDataType reference removed from setup examples. The property is not exposed on every IRIS 2026 build, and the previous INSERT INTO %Embedding.Config (β¦, VectorDataType, β¦) example failed at runtime on affected builds (Field '%EMBEDDING.CONFIG.VECTORDATATYPE' not found, or <PROPERTY DOES NOT EXIST> in ObjectScript). The example now uses only the portable minimum columns (Name, Configuration, EmbeddingClass, VectorLength, Description); VectorDataType is documented as build-dependent and set via property assignment when your build exposes it.sslConfig now correctly documented as required for every HTTPS provider. Prior examples omitted the key, causing %Embedding.OpenAI.IsValidConfig to reject the config at %Save() time with "Invalid Configuration: 'sslConfig' not set". Every JSON example in the README β Installation, Configuration Reference, and Demo β now includes "sslConfig":"OmniHTTPS" at both the top level (for the embedding provider) and inside the rerank sub-block (for the reranker). The Configuration Reference table upgrades sslConfig from optional to required for every HTTPS provider (Cohere, Voyage, Jina); not used by Ollama.Security.SSLConfigs entry (OmniHTTPS) in %SYS before wiring configs. Only skippable when Ollama is the sole provider.Engine.Rerank remains registered as [SqlProc], but this IRIS build's SQL result-set marshaller does not surface custom %SQL.CustomResultSet columns to callers of CALL dc_omniReRank.Engine_Rerank(...) from the SQL runner. The recommended path is the ObjectScript classmethod call followed by %Display() or %Next() iteration. Fully SQL-native surfacing is tracked as a follow-up.Search invocation instead of the SQL CALL (which returned SQLCODE=0 with zero rows displayed in SMP).v1.0.x: No code migration needed. If you followed a previous README to wire your %Embedding.Config, verify your Configuration JSON contains "sslConfig":"<your-ssl-config-name>" at both levels. If your IRIS build did not require sslConfig before, your row still needs it for the reranker to work β this is enforced by %Embedding.OpenAI and every SaaS reranker path.CALL dc_omniReRank.Engine_Rerank(...) from the SMP SQL runner or another %SQL.Statement returns SQLCODE=0 but does not display rows. Use the ObjectScript classmethod call. Fix scheduled for a subsequent release.LEN on %Vector columns β documented in the demo Catalog.cls (pinned at 1536 dims for OpenAI). Adjust LEN or drop the index if using an embedding model with a different dimensionality.







