Initial Release

JWT-related options, a bunch of fixes

fixed loader in iris.script

• dotenv installation instructions
• fix error "sqlalchemy.orm.exc.FlushError: Instance <Datayour_table_name at 0x288f1d06120> has a NULL identity key"

typo in REDAME fixed

Initial Release

Initial Release

Initial Release

Initial Release

Lots of security patches applied by GitHub dependabot.

Platform-independent Docker demo.

• Demo rebuilt on intersystemsdc/iris-community:latest-em: one container, no Web Gateway, no separate IPM install
• Same docker compose commands on Windows PowerShell, Command Prompt, WSL, macOS, and Linux; no bash scripts
• Demo runs in the USER namespace with Analytics enabled; cubes, pivots, dashboard, and warmed queries are built into the image
• Both test suites run from one command; GitHub Actions builds the image and runs them on every push
• Cache-warmer package unchanged; IPM module iris-bi-cube-cache-warmer 1.0.1
• Verified on InterSystems IRIS 2026.1 Community Edition

First public release.

• Query-frequency-ordered cache warming for IRIS BI cubes after builds and synchronizations
• Cube Manager Post-Build and Post-Synchronize integration with background, coalescing workers
• Dashboard and saved-pivot warming, including dashboard default filters
• Persistent run and per-query statistics, queryable via SQL
• IPM module iris-bi-cube-cache-warmer; install with zpm "install iris-bi-cube-cache-warmer"
• Docker Compose demo with two synchronized cubes, a dashboard, and tests
• Verified on InterSystems IRIS 2025.1 and 2026.1 Community Edition

Release notes — v1.0.4

dc.omniReRank v1.0.4 — Documentation fixes for setup on IRIS 2026

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.

🐛 Fixed

• %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.

✨ Improved

• New Installation step 4 walks the operator through creating a Security.SSLConfigs entry (OmniHTTPS) in %SYS before wiring configs. Only skippable when Ollama is the sole provider.
• Installation step 6 clarifies the consumption path. 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.
• Demo section now uses the ObjectScript Search invocation instead of the SQL CALL (which returned SQLCODE=0 with zero rows displayed in SMP).

🧪 Validated

• 69 unit tests green against IRIS 2026 (no external services required — every provider path is mocked).
• End-to-end demo verified: 20 OpenAI embeddings + real Cohere reranker over three natural-language queries, results reordered as expected.

🔄 Upgrade notes

• From 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.

⚠️ Known limitations

• 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.
• HNSW vector indexes require a fixed 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.

🙏 Thanks

• Dmitrij Vladimirov (Open Exchange review) — for catching the two setup blockers and the excellent bug-report quality that made them a five-minute fix.

Initial Release

Tech release

7 demos left

Initial Release

Added selectable LoginMethod for token requests

• some packages were unbundled
• some lost sources removed
• what's left waits for an obvious reason

Initial Release

Initial Release

Initial Release

Initial Release

1. Dashboard export support — multi-sheet workbook export, per-widget buttons, openpyxl availability detection with graceful degradation
2. Docker support — Dockerfile, docker-compose.yml, iris.script, .dockerignore
3. REST API auth fix + version bump to 1.1.5 — the AutheEnabled bitmask fix for the real blocking bug
4. Docs — README/QUICKSTART updates (Dashboard export usage + Docker quick-start) and the new docs/ architecture writeups

Initial Release

added DSW as suggested
USER>zpm "list"
dsw 4.0.32
mdx2json 3.2.50
samples-bi 1.0.5
vscode-per-namespace-settings 1.0.0

Initial Release

Fixed deployment from scratch issues

Fixed ZPM module

• Added customizable unauthorized error checker (see IsAuthError() method)
• Added RawJWT mode when the server returns only a JWT token as plain text. In this case, the API client extracts the expiration date from the token payload. I consciously did not add signature verification, since it requires additional elements (encryption algorithm, public key) and is not needed to extract the date
• Bug fixes