New post

Find

InterSystems Official
· May 24, 2023

Zen Reports to be removed from InterSystems IRIS and IRIS for Health beginning with (New Target) of 2025.3

InterSystems is announcing an end of maintenance event for Zen Reports beginning in Intersystems IRIS and IRIS for Health 2025.1.  This follows the deprecation notice made when InterSystems IRIS was introduced in 2018 and subsequent inclusion of InterSystems Reports in 2020 to provide replacement reporting functionality.  An overview of the timeline is:

March 2018.   InterSystems IRIS 2018.1:  Announcement of Zen Reports deprecation, continued shipment to provide continuity for existing applications

April 2020.     InterSystems IRIS 2020.1:  Intersystems Reports incorporated as part of user-based InterSystems IRIS and IRIS for Health and Advanced Server licenses

May 2023.      End of maintenance notification for Zen Reports

2H 2024.        Zen Reports available as an ipm module

2H 2025 (InterSystems IRIS 2025.3)   Zen Reports package removed from InterSystems IRIS and IRIS for Health distributions

InterSystems introduced InterSystems Reports, powered by Logi Reports from insightsoftware (formerly Logi Analytics)  as an embedded reporting solution starting with InterSystems IRIS and IRIS for Health 2020.1. InterSystems Reports provide a modern, drag and drop reporting solution for InterSystems customers and partners.  

We expect to transition Zen Reports to an independent package using IPM (InterSystems Package Manager) and to stop shipping Zen Reports with InterSystems IRIS and IRIS for Health version 2025.3. Zen Reports will continue to be available as an ipm module and may be distributed but will not be maintained by InterSystems.  The WRC will continue to provide support on prior versions of Cache and IRIS that contain Zen Reports but no updates are expected to Zen Reports software.

For more information on getting started with InterSystems Reports:
InterSystems Learning Path

InterSystems documentation

Global Summit session: Intersystems Application Services' move from Zen Reports to InterSystems Reports

insightsoftware's Logi Report documentation and tutorial

 

Please comment below or contact dbpprodmgrs@intersystems.com with any questions about this announcement.  

9 Comments
Discussion (9)5
Log in or sign up to continue
Announcement
· May 22, 2023

InterSystems Testing Manager - a new VS Code extension for the %UnitTest framework

If you have already built unit tests using the %UnitTest framework, or are thinking about doing so, please take a look at InterSystems Testing Manager.

Without leaving VS Code you can now browse your unit tests, run or debug them, and view previous run results.

InterSystems Testing Manager works with both of the source code location paradigms supported by the ObjectScript extension. Your unit test classes can either be mastered in VS Code's local filesystem (the 'client-side editing' paradigm) or in a server namespace ('server-side editing'). In both cases the actual test runs occur in a server namespace.

Feedback welcome.

26 Comments
Discussion (26)7
Log in or sign up to continue
Discussion (0)1
Log in or sign up to continue
Question
· May 17, 2023

Looping through repetitive HL7 segment groups in business rule

Hi,

we get HL7 ORU messages from a laboratory system. Messages that do not contain an observation date should not be forwarded to the business operation. My problem is that the observation date can be in any repetition of the ORCgrp. How can I loop through the ORCgrps in a business rule?

Regards

Robert

7 Comments
Discussion (7)4
Log in or sign up to continue
Article
· May 13, 2023 2m read

a virgin Jupyter-Notebook

Following one package from the last contest I met a strange problem.
There was the requirement to install jupyter-notebook
I work on Windows and there was some old Python installed
No big surprise: Installation of jupyter-notebook failed
Therefore, the latest version of Python was installed fast.

Big disappointment: the installation of jupyter-notebook failed again!
Because the new installation of Python didn't upgrade the old one.
And also the environment variable PATH was not cleaned
This was not obvious immediately and took endless time and effort.

Several cycles of installation and de-installations followed.
After a lot of manual intervention in Windows settings finally 
allowed Jupyter-Notebook to start.
Though it was not willing to operate in the virtual environment (venv).

This was the point when I had just enough.
I said to myself: "What you do here is just nonsense!"
After cleaning my workspace and the traces of all the failing
installations (several GB) I took a different approach.

  • The idea was to use my well-working Docker installation: 
  • Find a simple container with installed Jupyter-Notebook
  • Fill it with all the required Python modules
  • Forget about venv. More virtual than a Docker container is not possible.
  • Link your local directory into the container. So copying into the container is not necessary.
  • Not to forget the mapping for default port 8888 

The Docker container was built and running in no time 
compared to all my previous attempts. 
It was composed of these 2 files:

Dockerfile

ARG IMAGE=jupyter/base-notebook
FROM $IMAGE
USER root
COPY ./requirements.txt /tmp/requirements.txt
RUN pip3 install -r /tmp/requirements.txt

If you don't have requirements just un-comment the last 2 lines.

docker-compose.yaml

version: '3.9'
services:
  notebook:
    build:
      context: .
      dockerfile: Dockerfile
    entrypoint: jupyter notebook
                --allow-root
                --no-browser
                --ip 0.0.0.0
                --port 8888
                --NotebookApp.token=''
                --NotebookApp.password=''
                --notebook-dir=/ext
    ports:
    - 8888:8888
    volumes:
    - ./:/ext
    

And now after starting the container your Jupyter-Notebook is ready for access.

http://localhost:8888/

This was definitely easier than my previous attempts.
I felt it as a personal success, as this was a totally new territory for me.
 

Discussion (0)1
Log in or sign up to continue