Developer tools contest

Initial Release

Now able to use Test Coverage Tool to generate and display coverage of your tests.

Invideo added

fix default content output

Minor update to docs

Initial Release

• support multiple filters on widgets (#461)

Initial Release

Initial Release

Initial Release

• now tuples limited for only ones that defined in data properties even for drilldown (#458)

Initial Release

remove dsw dependency to prevent warnings on install - see https://github.com/intersystems-community/DeepSeeWeb/issues/443. Users who wish to use DeepSeeWeb should install that module separately

try IPM once more

Initial Release

• The previous version was broken by internal changes to JSON processing
• This is now fixed and works in Caché and IRIS
• and is expected to be release resistant

still not in ZPM

use generated module.xml for IPM

• fix changes of JSON Types in IRIS
• By some new release of IRIS JSON DataType codes were changed and broke the package.
• Now JSON Data Type codes are different from the original from Caché anymore.
• This is now fixed checking the environment

Initial Release

Initial Release

Fixed 3.2.44

[2.12.2] - 2025-07-08

Fixed

• Fixed importing Lookup Tables that do not already exist (#791)
• Fix initial import of settings file that has yet to be imported (#794)
• Fixed syncing IRIS with files after pull to diff in the intended direction (#802)

FIX: fixed issue when series were processed even they filtered out

Added simple implementation of rate limits. Now, you can set up the maximum number of requests per minute for your APIs. Just set the value by the route key in the lookup table RESTRateLimits, similar RESTRoutes table. Also, you can use a wildcard (*) as a method name: Sample.API:*

Tip: If you need a more flexible and enterprise solution, I advise you to look at API Manager

Added System name ObjectScript Docker Template via merge.cpf
Thanks to Dmitry Maslennikov

Added system name IRIS Dev Template to the Management Portal via merge.CPF settings

Thanks to Dmitry Maslennikov https://community.intersystems.com/post/rename-iris-instances-docker-or-distinguishing-them-easily-other-ways#comment-281824

property LastUser added

Added performance sensors and failed/successful request counts. All metrics are provided in OpenMetrics format. So, you can grab it with Prometheus and visualize it in Grafana. Details about setting up monitoring in the IRIS can be found here. Don't forget to check the roles of api/monitor application and to enable custom sensors in the IRIS terminal:

zn "%SYS"
d ##class(SYS.Monitor.SAM.Config).AddApplicationClass("REST.Core.Monitor", "YOUR_NAMESPACE")