検索

InterSystems公式
· 2023年5月24日

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

#InterSystems IRIS #InterSystems IRIS for Health #InterSystems公式

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
ディスカッション (9)5
続けるにはログインするか新規登録を行ってください
お知らせ
· 2023年5月22日
Open Exchange

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

#テスト #ツール #Caché #InterSystems アイデアポータル #InterSystems IRIS #VSCode

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
ディスカッション (26)7
続けるにはログインするか新規登録を行ってください
ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
質問
· 2023年5月17日

Looping through repetitive HL7 segment groups in business rule

#HealthShare

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
ディスカッション (7)4
続けるにはログインするか新規登録を行ってください
記事
· 2023年5月9日 2m read
Open Exchange

Helper for Objectscript Language Extensions

#ObjectScript #ビデオ #その他

Creating your own commands or shortcut is one of the strongest features of ObjectScript
If you create your own Language Extensions to ObjectScript you mostly have to find the
proper %ZLANGC00 or %ZLANGV00 or %ZLANGF00 and add the extensions manually.

A few utilities do it already automatically (ZPM, ZME, ..)
This utility allows you to add your extensions also programmatically.

  • eg. at first run, or during installation I found this quite useful for my Docker-based demos as it all happens at start time.

This package includes a demo example to visualize the operation of this utility.

How to Use it

 ; typ = "C" ... command extentson
 ;       "F" ... function extension
 ;       "V" ... variable Extensin
 ; ext = name of the extension
 ; code (by ref) numbered array of lines to add
 ;  
 ; do cmd^zLangExtender(typ,ext,.code)   ;>> add extension

How to Test it

Open IRIS terminal or console

USER>ZN "%SYS"   
%SYS>do ^zLangExample  
Compiling routine : %ZLANGF00.mac  
label="ZZDUMMY"   
line=6  
line(1)=" ; "   
line(2)=" ; just a demo dummy"  
line(3)="ZZDUMMY(%a) "    
line(4)=" quit " I got '"_%a_"' for test""   
line(5)=" ; what a nice demo "  
line(6)=" ; "   
sc=1   
typ="F"   
**** try ****  
sc=" I got 'hi folks' for test"    
result:
         ;Generated by %ZPM.PackageManager: Start
ZPM(pArgs...) Quit ##class(%ZPM.PackageManager).Shell(pArgs...)  
         ;Generated by %ZPM.PackageManager: End  
         ;  
         ; just a demo dummy  
ZZDUMMY(%a) 
         quit " I got '"_%a_"' for test"  
         ; what a nice demo
         ;
%SYS>

And if you run it a second time ?
It returns a standard error %Status.

%SYS>do ^zLangExample
%objlasterror="0 ...ZZDUMMY^%ZLANGF00 already defined.........
label="ZZDUMMY"
line=6
line(1)=" ; "
line(2)=" ; just a demo dummy"
line(3)="ZZDUMMY(%a) "
line(4)=" quit " I got '"_%a_"' for test""
line(5)=" ; what a nice demo "
line(6)=" ; "
sc=""0 ...ZZDUMMY^%ZLANGF00 already defined.........
typ="F"
ERROR #5001: ZZDUMMY^%ZLANGF00 already defined
%SYS>

Warning

It is meant mainly for COS experts !

GitHub

Video

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください