Search

Clear filter
Announcement
Anastasia Dyubaylo · Apr 3, 2020

New Video: InterSystems API Management and FHIR

Hi Community! Please welcome the new video on InterSystems Developers YouTube, recorded by @Patrick.Jamieson3621: ⏯ InterSystems API Management and FHIR InterSystems Product Manager @Patrick.Jamieson3621 shows how InterSystems API Manager (IAM) can be used to view and test FHIR resources with InterSystems IRIS for Health. More about InterSystems IRIS for Health. More about InterSystems API Management. Stay tuned! 👍🏼
Announcement
Evgeny Shvarov · Apr 3, 2020

InterSystems Developers Community Release, April 2020

Hi Developers! In March 2020 we improved again developers community engine and introduced the following new features: PDF export and print option for every post; more than one accepted answer; filter mentioning for silent members; bug fixes and minor enhancements. See the details below. PDF export and print option for every post With this release you can export in pdf or print every post. You can make it with two buttons in the top right corner of the post, see screenshot: More than one accepted answer Often we have situations when the question has more than one reply and several replies could be considered as an answer. And previously you should choose which one to accept. With this release, you can choose several replies as accepted answers in one question to make people understand which replies answer it. Check your questions with no accepted answers and see maybe you have answers already. Exclude silent members from mentioning This enhancement improves mentioning by excluding members who never posted from the options list. This will helps also with duplicated accounts filtering the list to active members only. Bug fixes and small improvements As always we fixed a lot of minor bugs, such as the bug in a search, improved events management and so on. Check the full kanban of solved issues in March 2020. Here is the planned kanban for April 2020. Submit your ideas, bug fixes, contribute to Developers Community and stay tuned!
Announcement
Anastasia Dyubaylo · Apr 7, 2020

New Video: Diving into InterSystems Cloud Technology

Hi Developers, Enjoy watching the new video on InterSystems Developers YouTube: ⏯ Diving into InterSystems Cloud Technology In this video, we will provide details about some of the nuts and bolts of our cloud capabilities, particularly with regards to infrastructure, deployment, and provisioning. We will discuss recent changes to InterSystems IRIS, InterSystems Cloud Manager (ICM), and give a technical view of planned enhancements. Takeaway: InterSystems IRIS includes tools that can help me deploy applications in the cloud. Presenter: @Mark.Bolinsky, Senior Technology Architect, InterSystems Additional materials to this video you can find in this InterSystems Online Learning Course. If you would like to explore a wider range of topics related to this video, please use this Resource Guide below: Cloud Deployment Resource Guide Enjoy and stay tuned! 👍🏼
Question
Blaise ZARKA · Apr 21, 2020

Insert a panda dataframe into an InterSystems IRIS table?

Hi, Do you have any experience in inserting a panda dataframe into SQL IRIS Table? The dataframe.to_sql method uses sqlalchemy and it seems no dialect is available for IRIS. thanks, Blaise You can use PythonGateway or IRIS Native for Python to do that. PythonGateway can retrieve dataframe (any object really) as a JSON. Here's a corresponding discussion on the SQL side of things. Thank you Eduard. At this time, we use JDBC connection and INSERT sql command from panda but we look for a more integrated way to do that. Both suggested approaches offer a tight in-process way of InterSystems IRIS - Python integration. I will show some live examples of bidirectional InterSystems IRIS - Python integration in Best Practices for in-platform AI/ML Webinar. Offtopic but generic JDBC provider for SQLAlchemy has been discussed for years in Python community but nothing has been done.
Announcement
Bob Kuszewski · Nov 13, 2023

Deprecation of InterSystems System Alerting and Monitoring (SAM)

InterSystems has decided to stop further development of SAM (System Alerting & Monitoring) and label it as deprecated as of today. InterSystems will continue to support existing customers using the technology, but it is no longer recommended for new deployments. We’ve found that most customers who are interested in the type of observability provided by SAM have chosen to connect IRIS’s metrics API & structured logs to their organization’s existing observability platform in order to have a more complete view of their operational platform. Customers with questions on their current or planned use of SAM should reach out to their account team or contact me directly. Okay, I've been waiting for this. SAM has shown us what is already possible related to monitoring IRIS and the extension with custom metrics is great but it indeed did not integrate very well in existing monitoring solutions. I would like to see a growing community around enhancing IRIS-monitoring. I'm especially interested in getting all the different logs from IRIS into Grafana.Maybe the Grafana-Intersystems-Plugin by Dmitri Maslennikow or an Intersystems-Plugin for Loki might do the trick? Has somebody already achieved this? I don't have any requests for any improvements for the plugin if you wish to try and have some ideas what needs to be added, you are welcome in issues Does this SAM deprecation affect both the server APIs and client appliance (the SAM component shipped as docker containers with grafana-prometheus-iris, etc), or can the SAM Serverside APIs with custom metrics still be used? this is only the SAM container. the APIs it consumes will stay and there are no plans to deprecated those. I hope that the APIs (e.g. /api/monitor/metrics) will still work, so metrics can still be embeded into any monitoring tool that we are using like dataDog. Is this correct to assume? my understanding is that there will be no changes made to those APIs, nor plans to deprecate them. That is what Bob was referring to when he said most orgs use their own monitoring solutions to consume the IRIS data (via those APIs) ... so the APIs will stay, but SAM as an out of the box consumer of the metrics will be deprecated Intersystems REST Api for Metrics For anyone who wants to take a look at the api
Announcement
Anastasia Dyubaylo · Dec 21, 2023

InterSystems FHIR and Digital Health Interoperability Contest

Hi Developers, We have exciting news! The new InterSystems online programming contest dedicated to all things health-related will start very soon! 🏆 InterSystems FHIR and Digital Health Interoperability Contest 🏆 Duration: January 15 - February 4, 2024 Prize pool: $14,000 The topic Develop any interoperability FHIR solution or Healthcare Interoperability solution or a solution that helps to develop or/and maintain interoperability solutions using InterSystems IRIS for Health, Health Connect, or FHIR server. General Requirements: An application or library must be fully functional. It should not be an import or a direct interface for an already existing library in another language (except for C++, there you really need to do a lot of work to create an interface for IRIS). It should not be a copy-paste of an existing application or library. Accepted applications: new to Open Exchange apps or existing ones, but with a significant improvement. Our team will review all applications before approving them for the contest. The application should work either on IRIS Community Edition or IRIS for Health Community Edition. Both could be downloaded as host (Mac, Windows) versions from Evaluation site, or can be used in a form of containers pulled from InterSystems Container Registry or Community Containers: intersystemsdc/iris-community:latest or intersystemsdc/irishealth-community:latest . The application should be Open Source and published on GitHub. The README file to the application should be in English, contain the installation steps, and contain either the video demo or/and a description of how the application works. Only 3 submissions from one developer are allowed. NB. Our experts will have the final say in whether the application is approved for the contest or not based on the criteria of complexity and usefulness. Their decision is final and not subject to appeal. Prizes 1. Experts Nomination - a specially selected jury will determine winners: 🥇 1st place - $5,000 🥈 2nd place - $3,000 🥉 3rd place - $1,500 🏅 4th place - $750 🏅 5th place - $500 🌟 6-10th places - $100 2. Community winners - applications that will receive the most votes in total: 🥇 1st place - $1,000 🥈 2nd place - $750 🥉 3rd place - $500 🏅 4th place - $300 🏅 5th place - $200 If several participants score the same amount of votes, they all are considered winners, and the money prize is shared among the winners. Who can participate? Any Developer Community member, except for InterSystems employees (ISC contractors allowed). Create an account! Developers can team up to create a collaborative application. 2 to 5 developers are allowed in one team. Do not forget to highlight your team members in the README of your application – DC user profiles. Important Deadlines: 🛠 Application development and registration phase: January 15, 2024 (00:00 EST): Contest begins. January 28, 2024 (23:59 EST): Deadline for submissions. ✅ Voting period: January 29, 2024 (00:00 EST): Voting begins. February 4, 2024 (23:59 EST): Voting ends. Note: Developers can improve their apps throughout the entire registration and voting period. Helpful Resources: ✓ Documentation: InterSystems IRIS for Health FHIR Components documentation InterSystems Cloud FHIR Server documentation InterSystems Interoperability documentation Healthcare Data Transformations documentation ✓ Tools: Clinfhir - FHIR visualization and developer tool. ✓ Example applications: FHIR Server Template iris-healthtoolkit-template interoperability-embedded-python FHIR HL7 SQL Demo FHIR DropBox HL7 and SMS Interoperability Demo IrisHealth Ensdemo UnitTest DTL HL7 Healthcare HL7 XML FHIR Interoperability Examples FHIR-Orga-dt FHIR Peudoanonimisation Proxy FHIR-client-java FHIR-client-.net FHIR-client-python FHIR related apps on Open Exchange HL7 applications on Open Exchange ✓ Online courses: Interactive Digital Health Interoperability Foundation - An intro course into Digital Health Interoperability productions built with InterSystems IRIS for Health FHIR Data Architecture FHIR Integrations HL7 Integrations Learn FHIR for Software Developers Exploring FHIR Resource APIs Using InterSystems IRIS for Health to Reduce Readmissions Connecting Devices to InterSystems IRIS for Health Monitoring Oxygen Saturation in Infants FHIR Integration QuickStart ✓ Videos: 6 Rapid FHIR Questions SMART on FHIR: The Basics Developing with FHIR - REST APIs FHIR in InterSystems IRIS for Health FHIR API Management Searching for FHIR Resources in IRIS for Health ✓ For beginners with IRIS: Build a Server-Side Application with InterSystems IRIS Learning Path for beginners ✓ For beginners with ObjectScript Package Manager (IPM): How to Build, Test and Publish IPM Package with REST Application for InterSystems IRIS Package First Development Approach with InterSystems IRIS and IPM ✓ How to submit your app to the contest: How to publish an application on Open Exchange How to submit an application for the contest Need Help? Join the contest channel on InterSystems' Discord server or talk with us in the comment to this post. We're waiting for YOUR project – join our coding marathon to win! By participating in this contest, you agree to the competition terms laid out here. Please read them carefully before proceeding. UPDATE Recently we introduced a yet another Instruqt interactive foundation course on Digital Health Interoperability with IRIS for Health - please give it a try here! It will help everyone who is new to InterSystems Digital Health Interoperability productions to go through several simple but illustrating scenarios and get a great foundation for building your ones! Enjoy! Dear FHIR developers! Also want to highlight a very handy visualization developer tool for FHIR servers - clinfhir. You can examine listed servers there or add your ones. Here is one screnshot to raise your interest: The author and developer of the tool @David.hay published an article about it! Thank you, David! Hello, we have installed the InterSystems FHIR server on our HealthShare instance. Can we still build applications/ solutions for the contest if we are using HealthShare? Thanks. Hi @Momeena.Ali ! Yes, you can, for sure! Don't forget to publish your application on Open Exchange in a form of GitHub or Gitlab repository as an open source. Hey Devs! The recording of the "Kick-off Webinar for FHIR and Digital Health Interoperability Contest" is on InterSystems Developers YouTube! 🔥 ⏯ Kick-off Webinar for FHIR and Digital Health Interoperability Contest Dear developers, We would like to remind you that the second week of registration for the contest has already begun. We look forward to your applications! Have a good day) 🌸 Thanks Evgeny, I had an additional question - we had 6 developers working collaboratively on the two applications we will submit. The contest allows 2-5 developers per submission. What would be the best approach for us to recognize all the participants? Thanks. Hi @Momeena Ali,It's great to hear that so many people are working on creating apps.So that we can tag all developers, it will be better to divide 3 people per application.I also ask you to tell your colleagues to register on the community website, so we can highlight them in the application description.And please tell us who worked on which application so that we can correctly tag everyone.Thank you. Have a good day! Community! Tomorrow is the last day of registration for the contest! 5 apps have been already added: FHIR-OCR-AI by @xuanyou.du iris-fhirfy by @José.Pereira HL7-FHIR-Cohort-Populat by @Momeena.Ali Patient-PSI-Data by @Chang.Daofhirmessageverification by @珊珊.喻 Upload your application and join the contest!🔥
Announcement
Anastasia Dyubaylo · Feb 8, 2024

InterSystems Developer Ecosystem Annual Survey 2023

Hi Developers, Thank you so much for being a part of the InterSystems Developer Community Ecosystem for yet another year! We love that you participate in the life of the Developer Community, Open Exchange, Global Masters, and Ideas Portal. We'd like to know how useful are our portals for you at this point. Please take a few moments to let us know what you think and what could be improved: 👉 InterSystems Developer Ecosystem Annual Survey 2023 👈 Note: The survey will take less than 10 minutes to complete. Your feedback is also welcome in the comments section of this post. We're looking forward to learning your opinions! 😉 Hey Community, Last call to participate in the survey 😉 We look forward to hearing your feedback: https://www.surveymonkey.com/r/R8YXFVQ
Announcement
Kristina Lauer · Jun 26, 2024

Prepare for InterSystems IRIS SQL Specialist certification

Are you signed up to take the new InterSystems IRIS SQL Specialist certification exam? Get ready with these in-person and self-paced learning resources! Learning path: Using SQL in InterSystems IRIS (3h 45m). Classroom training: Developing with InterSystems Objects and SQL Try the practice questions to see if you're ready. Find even more resources to prepare—and information about signing up for the exam—in this Developer Community post.
Announcement
Anastasia Dyubaylo · Apr 16, 2024

[Video] Unleashing the Power of Machine Learning with InterSystems

Hey Community, Play the new video on InterSystems Developers YouTube: ⏯ Unleashing the Power of Machine Learning with InterSystems @ Global Summit 2023 Explore how to do machine learning using all the latest and greatest InterSystems technologies, including Feature Engineering using SQL and our InterSystems Cloud SQL Service, Training an ML model using our InterSystems IntegratedML Service, Training an ML model using a Jupyter Notebook and Python connected to data in InterSystems IRIS, Incorporating ML models into an application using ObjectScript and Embedded Python. Presenters: 🗣 Marta Manzin, Senior Developer, InterSystems🗣 @Donald.Woodlock, Vice President of Healthcare, InterSystems🗣 @Alex.MacLeod, Director of HealthShare Commercial Initiatives, InterSystems Enjoy watching it and explore for more videos! 👍
Announcement
Anastasia Dyubaylo · Jan 16, 2024

[Video] Working with InterSystems IRIS Cloud SQL

Hey Developers, Watch the latest video on InterSystems Developers YouTube: ⏯ Working with InterSystems IRIS Cloud SQL Watch the video to learn how to quickly get started using InterSystems IRIS Cloud SQL, the cloud service that brings the power of an InterSystems IRIS database to an on-demand cloud environment. @Raj.Singh5479 chats with @Derek.Robinson to demonstrate how to easily connect to your InterSystems IRIS Cloud SQL deployment from your favorite SQL client. Enjoy it and keep an eye on upcoming videos! 👍 Thanks Anastasia, Raj and Derek!
Announcement
Anastasia Dyubaylo · Feb 14, 2023

[Video] InterSystems Startup Accelerator Pitching Sessions

Hi Developers, Enjoy watching the new video on InterSystems Developers YouTube: ⏯ InterSystems Startup Accelerator Pitching Sessions @ Global Summit 2022 Check out the innovative solutions introduced by cutting-edge healthcare startups. Members of InterSystems 2022 FHIR Startup Accelerator - Caelestinus - will present their solutions, all built on InterSystems FHIR Cloud and Health Connect services. Presenters: 🗣 @Evgeny.Shvarov, Startups and Community Manager, InterSystems🗣 @Dean.Andrews2971, Head of Developer Relations, InterSystems🗣 Martin Zubek, Business Development Manager🗣 Tomas Studenik, Caelestinus Incubator cofounder Enjoy watching and stay tuned! 👍
Announcement
Bob Kuszewski · Feb 15, 2023

InterSystems Supported Platforms Update Feb-2023

InterSystems Supported Platforms Update Feb-2023 Welcome to the very first Supported Platforms Update! We often get questions about recent and upcoming changes to the list of platforms and frameworks that are supported by the InterSystems IRIS data platform. This update aims to share recent changes as well as our best current knowledge on upcoming changes, but predicting the future is tricky business and this shouldn’t be considered a committed roadmap. We’re planning to publish this kind of update approximately every 3 months and then re-evaluate in a year. If you find this update useful, let us know! We’d also appreciate suggestions for how to make it better. With that said, on to the update… IRIS Production Operating Systems and CPU Architectures Red Hat Enterprise Linux Recent Changes IRIS 2022.1.2 adds support for RHEL 9.0. 9.0 is a major OS release that updates the Linux Kernel to 5.14, OpenSSL to 3.0, and Python 3.9 IRIS 2022.2.0 removes support for RHEL 7.x. RHEL 7.9 is still supported in earlier versions of IRIS. Upcoming Changes RHEL 9.1 was released in November, 2022. Red Hat is supporting this minor version only until RHEL 9.2 is released, so InterSystems will not be adding 9.1 as a supported platform. RHEL 9.2 is planned to be released in late Q2, 2023 and Red Hat is planning to support 9.2 for 4 years. InterSystems is planning to do additional testing of IRIS on RHEL 9.2 through a new process we’re calling “Minor OS version certification” that is intended to provide additional security that a minor OS update didn’t break anything obvious. RHEL 8.4 extended maintenance ends 5/31/2023, which means that IRIS will stop supporting this minor version at that time as well. Further reading: RHEL Release Page Ubuntu Recent Changes IRIS 2022.1.1 adds support for Ubuntu 22.04. 22.04 is a major OS release that updates the Linux Kernel to 5.15, OpenSSL to 3.0.2, and Python 3.10.6 IRIS 2022.2.0 removes support for Ubuntu 18.04. Ubuntu 18.04 is still supported in earlier versions of IRIS. IRIS 2022.1.1 & up containers are based on Ubuntu 22.04. Upcoming Changes Ubuntu 20.04.05 LTS and 22.04.01 LTS have been recently released. InterSystems is planning to do additional testing of IRIS on 20.04.05 LTS and 22.04.01 LTS through a new process we’re calling “Minor OS version certification”. We’ll have more on these “Minor OS version certifications” in a future newsletter. The next major update of Ubuntu is scheduled for April, 2024 Further Reading: Ubuntu Releases Page SUSE Linux Recent Changes IRIS 2022.3.0 adds support for SUSE Linux Enterprise Server 15 SP4. 15 SP4 is a major OS release that updates the Linux Kernel to 5.14, OpenSSL to 3.0, and Python 3.9 Upcoming Changes Based on their release rhythm, we expect SUSE to release 15 SP5 late Q2 or early Q3 with support added to IRIS after that. Further Reading: SUSE lifecycle Oracle Linux Recent Changes IRIS 2022.3.0 adds support for Oracle Linux 9. Oracle Linux 9 is a major OS release that tracks RHEL 9, so it, too, updates the Linux Kernel to 5.14, OpenSSL to 3.0, and Python 3.9 Upcoming Changes Oracle Linux 9.1 was released in January, 2023. Further Reading: Oracle Linux Support Policy Microsoft Windows Recent Changes We haven’t made any changes to the list of supported Windows versions since Windows Server 2022 was added in IRIS 2022.1 Upcoming Changes Windows Server 2012 will reach its end of extended support in October, 2023. If you’re still running on the platform, now is the time to plan migration. Further Reading: Microsoft Lifecycle AIX Recent Changes We haven’t made any changes to the list of supported AIX versions since AIX 7.3 was added and 7.1 removed in IRIS 2022.1 Upcoming Changes InterSystems is working closely with IBM to add support for OpenSSL 3.0. This will not be included in IRIS 2023.1.0 as IBM will need to target the feature in a further TL release. The good news is that IBM is looking to release OpenSSL 3.0 for both AIX 7.2 & 7.3. IBM released AIX 7.3 TL1 in December and certification is in progress. The next TL releases are expected in April. Further Reading: AIX Lifecycle Containers Recent Changes We are now publishing multi-architecture manifests for IRIS containers. This means that pulling the IRIS container tagged 2022.3.0.606.0 will download the right container for your machine’s CPU architecture (Intel/AMD or ARM). If you need to pull a container for a specific CPU architecture, tags are available for architecture-specific containers. For example, 2022.3.0.606.0-linux-amd64 will pull the Intel/AMD container and 2022.3.0.606.0-linux-arm64v8 will pull the ARM container. Upcoming Changes We will phase out the arm-specific image names, such as iris-arm64 in favor of the multi-architecture manifests in the second-half of the year. We will also start to tag the preview containers with “-preview” so that it’s clear which container is the most recent GA release. IRIS Development Operating Systems and CPU Architectures MacOS Recent Changes We haven’t made any changes to the list of supported MacOS versions since we moved to MacOS 11 in IRIS 2022.1 Upcoming Changes We’re planning to add support for MacOS 13 in 2023, perhaps as early as IRIS 2023.1. CentOS We are considering removing support for CentOS/CentOS Stream. See reasoning below. Red Hat has been running a developer program for a few years now, which gives developers access to free licenses for non-production environments. Developers currently using CentOS are encouraged to switch to RHEL via this program. CentOS Stream is now “upstream” of RHEL, meaning that it has bugs & features not yet included in RHEL. It also updates daily, which can cause problems for developers building on the platform (to say nothing of our own testing staff). We haven’t made any changes to the list of supported CentOS versions since we added support for CentOS 8-Stream and removed support for CentOS 7.9 in IRIS 2022.1 Caché & Ensemble Production Operating Systems and CPU Architectures Recent Changes Cache 2018.1.7 adds support for Windows 11 InterSystems Supported Platforms Documentation The InterSystems Supported Platforms documentation is source for definitive list of supported technologies. IRIS 2020.1 Supported Server Platforms IRIS 2021.1 Supported Server Platforms IRIS 2022.1 Supported Server Platforms IRIS 2022.3 Supported Server Platforms Caché & Ensemble 2018.1.7 Supported Server Platforms … and that’s all folks. Again, if there’s something more that you’d like to know about, please let us know. Nice work on the containers side @Robert.Kuszewski !
Announcement
Anastasia Dyubaylo · Feb 23, 2023

Tech Article Contest: InterSystems IRIS Tutorials

Hello Community, After the last heated programming contest, we're happy to announce the next InterSystems technical article writing competition! ✍️ Tech Article Contest: InterSystems IRIS Tutorials ✍️ Write an article that can be considered a tutorial for InterSystems IRIS programmers of any level: beginner / middle / senior from March 1st to March 31st. 🎁 Prizes for everyone: A special prize pack for each author who takes part in the competition! 🏆 Main Prizes: There are 6 prizes to choose from. Prizes 1. Everyone is a winner in InterSystems Tech Article Contest! Any member who writes an article during the competition period will receive special prizes: 🎁 Branded Organic Canvas Tote Bag 🎁 Moleskine Lined Notebook 2. Expert Awards – articles will be judged by InterSystems experts: 🥇 1st place: Mars Pro Bluetooth speakers / AirPods Max 🥈 2nd place: Apple AirPods Pro with Wireless Charging Case / JBL Pulse 4 Light Show Speaker 🥉 3rd place: Magic Keyboard Folio for iPad / Bose Soundlink Micro Bluetooth Speaker Or as an alternative, any winner can choose a prize from a lower prize tier than his own. 3. Developer Community Award – article with the most likes. The winner will have the option to choose one of the following prizes: 🎁 Magic Keyboard Folio for iPad 🎁 Bose Soundlink Micro Bluetooth Speaker Note: The author can only be awarded once per category (in total the author will win 2 prizes: one for Expert and one for the Community) In the event of a tie, the number of votes of the experts for the tied articles will be considered as a tie-breaking criterion. Who can participate? Any Developer Community member, except for InterSystems employees. Create an account! Contest period 📝 March 1st - March 31st: Publication of articles and voting time. Publish an article(s) throughout this period. DC members can vote for published articles with Likes – votes in the Community award. Note: The sooner you publish the article(s), the more time you will have to collect both Expert & Community votes. What are the requirements? ❗️ Any article written during the contest period and satisfying the requirements below will automatically* enter the competition: The article must be a tutorial** on the InterSystems IRIS topic. It can be either for beginners, middle or senior developers. The article must be in English (incl. inserting code, screenshots, etc.). The article must be 100% new (it can be a continuation of an existing article). The article cannot be a translation of an article already published in other communities. The article should contain only correct and reliable information about InterSystems technology. The article has to contain the Tutorial tag. Article size: 400 words minimum (links and code are not counted towards the word limit). Max 3 entries from the same author are allowed. Articles on the same topic but with dissimilar examples from different authors are allowed. * Articles will be moderated by our experts. Only valid content will be eligible to enter the contest. ** Tutorials provide step-by-step instructions that a developer can follow to complete a specific task or set of tasks. 🎯 EXTRA BONUSES This time we decided to add additional bonuses that will help you to win the prize! Please welcome: Bonus Nominal Details Topic bonus 5 If your article is on the topic from the list of the proposed topics (listed below), you will receive a bonus of 5 Expert votes (vs 1st place selected by an Expert = 3 votes). Video bonus 3 Format of the presentation of the content of the article: besides publishing the article make an explanatory video. Discussion bonus 1 Article with the most useful discussion, as decided by InterSystems experts. Only 1 article will get this bonus. Translation bonus 1 Publish a translation of your article on any of the regional Communities. Learn more. Note: Only 1 vote per article. New member bonus 3 If you haven't participated in the previous contests, your article(s) will get 3 Expert votes. Proposed topics Here's a list of proposed topics that will give your article extra bonuses: ✔️ Working with IRIS from C#✔️ Working with IRIS from Java✔️ Working with IRIS from Python✔️ Using Embedded Python✔️ Using Python API✔️ Using Embedded SQL✔️ Using ODBC/JDBC✔️ Working with %Query/%SQLQuery✔️ Using indexes✔️ Using triggers✔️ Using JSON✔️ Using XML✔️ Using REST✔️ Using containers✔️ Using kubernetes Note: Articles on the same topic from different authors are allowed. ➡️ Join InterSystems Discord to chat about the rules, topics & bonuses. So, It's time to show off your writing skills! Good luck ✨ Important note: Delivery of prizes varies by country and may not be possible for some of them. A list of countries with restrictions can be requested from @Liubka.Zelenskaia Great, I love to write tutorials. The winner will get a badge on GM too? I'm uncovering my keyboard and stretching my fingers Is the article word count a minimum or maximum? Neither; all articles must be exactly 400 words. JK; that needs clarification. 400 words minimum – updated the announcement ;) Thanks for the heads up, guys! Hi Devs) What's great news! 🤩 5 news articles have appeared on the Contest page: Tutorial - Streams in Pieces by @Robert.Cemper1003 Quick sample database tutorial by @Heloisa.Paiva Tutorial - Working with %Query #1 by @Robert.Cemper1003 Tutorial - Working with %Query #2 by @Robert.Cemper1003 Tutorial - Working with %Query #3 by @Robert.Cemper1003 Waiting for other interesting articles) 😎 of course! there will be special badges on Global Masters ;) Example: Robert Cemper is so powerful Hey Devs! The 8 new articles have been added to the contest! SQLAlchemy - the easiest way to use Python and SQL with IRIS's databases by @Heloisa.Paiva Creating an ODBC connection - Step to Step by @Heloisa.Paiva Tutorial - Develop IRIS using SSH by @wang.zhe Getting Started with InterSystems IRIS: A Beginner's Guide by @A.R.N.H.Hafeel Creating a DataBase, namespace, inserting data and visualizing data in the front end. by @A.R.N.H.Hafeel InterSystems Embedded Python in glance by @Muhammad.Waseem Query as %Query or Query based on ObjectScript by @Iryna.Mykhailova Setting up VS Code to work with InterSystems technologies by @Maria.Gladkova Important note: We do not prohibit authors from using AI when creating content, however, articles must contain only correct and reliable information about InterSystems technology. Before entering the contest, articles are moderated by our experts. In this regard, we have updated the contest requirements. Hi, Community! Seven more tutorials have been added to the contest! Tutorial: Improving code quality with the visual debug tool's color-coded logs by @Yone.Moreno Kinds of properties in IRIS by @Iryna.Mykhailova Backup and rebuilding procedure for the IRIS server by @Akio.Hashimoto1419 Stored Procedures the Swiss army knife of SQL by @Daniel.Aguilar Tutorial how to analyze requests and responses received and processed in webgateway pods by @Oliver.Wilms InterSystems's Embedded Python with Pandas by @Rizmaan.Marikar2583 Check them out! Hey, Developers! Two more articles have been added to the contest! Tutorial - Creating a HL7 TCP Operation for Granular Error Handling by @Julian.Matthews7786 Tutorial for Middle/Senior Level Developer: General Query Solution by @姚.鑫 There are already 19 tutorials that have been uploaded!Almost one week left to the end of the contest, and we are waiting forward to more articles! Developers! A lot of tutorials have been added to the contest!🤩 And only four days left to the end of publication and voting! Hurry up and upload your articles!🚀 Community! Three more articles have been added to the contest! Perceived gaps to GPT assisted COS development automatons by @Zhong.Li7025 SQL IRIS Editor and IRIS JAVA CONNECTION by @Jude.Mukkadayil Set up an IRIS docker image on a Raspberry Pi 4 by @Roger.Merchberger Devs, only one day left to the end of the contest! Upload your tutorials and join the contest! Our Tech Article contest is over! Thank you all for participating in this writing competition :) As a result, 🔥 24 AMAZING ARTICLES 🔥 Now, let's add an element of intrigue... The winners will be announced on Monday! Stay tuned for the updates.
Announcement
Raj Singh · May 10, 2023

InterSystems Studio is deprecated, starting with 2023.2

InterSystems is committed to providing a high quality developer experience including a great IDE (Integrated Developer Experience). For the past several years we have been evolving Visual Studio Code's ObjectScript tooling in parallel with our long-standing IDE, InterSystems Studio. There have been over 46,000 downloads of the VSCode-ObjectScript plugin, and the feedback from developers is that this is a great developer experience, and now superior to InterSystems Studio. With our 2023.2 release we are deprecating InterSystems Studio (deprecated designates a feature or technology that InterSystems no longer actively develops, and for which better options exist). We will continue to maintain, release, and support InterSystems Studio for quite some time, and we appreciate that it is still an important tool for some customers. However, customers should be advised that we are not investing in it. Our focus is on VSCode. I've appreciated all the customer input as we've grown our ecosystem of VS Code extensions, keeping them open source while offering full support, and maintaining regular and rapid release cycles.As we continue this journey, I look forward to continuing to hear your feedback, ideas, and code. Feel free to comment below or direct message me. As always, your voice plays a major role in this important process. For development VS Code is great. Indent is a lot better and also the syntax checking. One small functionality I'm missing is to open classes fast with a shortcut. We're using HealthConnect and at an item the Class Name is shown in the management portal: I can copy the class name, go to studio press Ctrl-O and paste the class name: In VS code I can open also with Ctrl-O but then I need to fill in /HS/FHIRServer/Interop.HTTPOperation.cls Could be a small improvement? I still can't see my csp files or .bas routines in VS Code. What do I have wrong? @David.Hockenbroch We just improved the UI for creating a new server-side editing workspace folder. If you have no workspace open, you can follow the steps here to create a new one. If you do, you can add a new folder to you workspace by right-clicking in the file explorer and selecting "Add Server Namespace to Workspace..". That command will follow steps 4 and on. To see CSP files, select "Web Application Files" in the menu from step 8. To see basic files, select "code files in <NS>", then select "Filter", then make sure your custom filter contains the "*.bas" pattern. It can include other file types as well. @Menno.Voerman Unfortunately I don't think this is possible. That command is for opening files, and technically the name of the file is "HS/FHIRServer/Interop.HTTPOperation.cls", not "HS.FHIRServer.Interop.HTTPOperation.cls". VS Code is great for development, while InterSystems extensions behavior is disappointing sometimes. E.g., since some update was installed, <Ctrl/Mouse pointer> stopped referencing the methods of another class. <Right button menu -> Goto Definition> stopped working as well. Is it a bug or a feature? @Alexey.Maslov That sounds like a bug to me. Can you file a GitHub issue with steps to reproduce? It would also help to know the versions of the extensions you have installed, the version of IRIS you're connected to, and the text of the file that you see the bug in. Done, expecting that InterSystems ObjectScript was the right choice for the kind of issue. The export capabilities in VSCode are very poor compared to Studio. There should be a possibility to export multiple classes/routines in xml format. VSCode also lacks the different Wizards (SOAP/XML) and the guided way (File/New...) to create classes, processes, DTLs, BPLs and so on. You can't edit BPLs and DTLs with VSCode. Why would you need XML? Hi @Mikko.Taittonen! Why would you need XML export for classes/routines? Why not UDL? UDL is much more readable? @Mikko.Taittonen The vscode-objectscript extension does provide New File commands for Interoperability classes. You can read the documentation here. The SOAP wizard can be accessed from the Server Actions menu. BPL and DTL classes can be edited textually. Support for the graphical editors will be added when they are rewritten using Angular. For a preview of how that would work, you can try out the new Angular Rule Editor in VS Code. For what it is worth: I don't agree.Studio is a Objectscript dedicated IDE (Editor), rather clean and unobtrusive.It could be enhanced quite simple.The only problem is Windows only (which is still 57.37% of all desktops) Fully support this!It's a sense less attack to the traditional installed base ! With our 2023.2 release we are deprecating InterSystems Studio (deprecateddesignates a feature or technology that InterSystems no longer actively develops, and for which better options exist). We will continue to maintain, release, and support InterSystems Studio for quite some time, and we appreciate that it is still an important tool for some customers. However, customers should be advised that we are not investing in it. Our focus is on VSCode. In what sense is this an "attack"? C'mon! we heard this to often: WebLink, Caché, ...- We will continue to maintain, release, and support ....- and every IRIS Version needs a new Studio version Hi: This is possible . How to quickly open class in VS Code | InterSystems Developer Community |. The answer to this is here: if you are using the server-side editing paradigm, which matches what you're used to with Studio, make sure you follow the instructions in the "Enable Proposed APIs" section of the extension's README (also available here). you can then use Crtl+P to find the item you need. my setup instructions The additional features (and the APIs used) are: Server-side searching across files being accessed using isfs (TextSearchProvider) Quick Open of isfs files (FileSearchProvider). Download and install a beta version from GitHub. This is necessary because Marketplace does not allow publication of extensions that use proposed APIs. Go to https://github.com/intersystems-community/vscode-objectscript/releases Locate the beta immediately above the release you installed from Marketplace. For instance, if you installed 2.4.3, look for 2.4.4-beta.1. This will be functionally identical to the Marketplace version apart from being able to use proposed APIs. Download the VSIX file (for example vscode-objectscript-2.4.4-beta.1.vsix) and install it. One way to install a VSIX is to drag it from your download folder and drop it onto the list of extensions in the Extensions view of VS Code. From Command Palette choose Preferences: Configure Runtime Arguments. In the argv.json file that opens, add this line (required for both Stable and Insiders versions of VS Code): "enable-proposed-api": ["intersystems-community.vscode-objectscript"] Exit VS Code and relaunch it. Verify that the ObjectScript channel of the Output panel reports this: intersystems-community.vscode-objectscript version X.Y.Z-beta.1 activating with proposed APIs available. After a subsequent update of the extension from Marketplace you will only have to download and install the new vscode-objectscript-X.Y.Z-beta.1 VSIX. None of the other steps above are needed again. To see CSP files with server side editing if you hold shift before clicking the pencil icon it will load up a web files view Is there a recent and detailed article comparing VSCode plugin and the latest Studio? Something like this is what Studio still does better and this is what plugin does better. Hi @jaroslav.rapp. Attack may be a strong word, but I understand the feeling when beloved tools get less attention than others. We'd love to never leave a technology behind, but the reality is that with limited resources we sometimes have to devote more effort to technologies that will have bigger benefits for our users going forward. It's not always an easy decision, but I believe the short-term pain is well worth the long-term benefits. Hi @Anna.Golitsyna. This recent discussion, First Community Roundtable: VSCode vs Studio, may be useful. I've never used VS Code, and I don't know anything about it. I am wondering whether there are equivalents for a couple things we often do in InterSystems Studio: Export (to XML) and import classes. Find in Files. Also, is there an equivalent to the Namespace Workspace that is available in Studio? That's the arrangement we use the most. Yeah,moving code between Studio instances to other namespaces on same or different serversimply by drag & drop Yes, you can do this in VS Code. Even better, when using the server-side editing paradigm a single VS Code instance can connect simultaneously to multiple namespaces on one or more servers, and you can drag/drop and copy/paste between them. We use the TrackWare SCCS, for both our Cache/IRIS and Delphi application development. TrackWare has the unique distinction of being written in both Delphi and Cache. It integrates well with Studio SCCS. We now own the TrackWare package and I have had to make updates to the Cache/IRIS side to keep it current. (It was formerly owned by Jorma Sinnoma (sp?) who is now a member of the InterSystems team.) It works for us and we would want to stay with it for as long as Studio functionality and SCCS integration stays intact. A real bugaboo for us, besides the ease with which we can check out and check in our Cache/IRIS code elements, is that we would have to come up with another product to maintain source control on the Delphi side. So, please do not stray from what Studio offers us now both as an IDE and its SCCS integration. Thank you Rich Filoramo InTempo Software I feel that I have not explained clearly enough the Studio features that we use. We often export classes to XML files. Similarly, we import XML files, compiling them as classes during import. I didn't mean to imply that this was done simply to transfer classes to other namespaces or servers. Rather, it's a way to archive classes as XML files. (We don't use a source control system.) We use the Find in Files utility to determine the classes and other files in which a given string exists. I mentioned the Namespace variation of the Studio Workspace pane because that is the arrangement of files (classes, lookup tables, message schemas, etc.) that we most often use. @Richard.Filoramo The server-side editing paradigm in VS Code is conceptually similar to Studio in that the files you edit are "virtual" and do not need to be exported to the file system. This mode supports Studio source control classes, so you can continue using them if you want. We have a documentation page that describes some useful features for migrating from Studio that describes where the Studio source control integration can be found in the VS Code UI. @Anna.Golitsyna We have a documentation page that describes some useful features for migrating from Studio that you may find useful. @Larry.Overkamp VS Code does not support exporting or importing source code as XML files. There are existing tools in the terminal and SMP for that. The server-side editing paradigm that John mentioned above is conceptually similar to Studio in that the files you edit are "virtual" and do not need to be exported to the file system to be edited. It supports viewing all files in a namespace like in Studio, and it also supports importing local .cls, .mac, .int and .inc files into that namespace. Searching for text across those virtual files is supported and the UI is much better than Studio since you can click on the match and jump right to that location in the file. Enabling that feature requires some extra steps due to a VS Code core limitation, but this is something that we anticipate will be resolved in the future. @Larry.Overkamp my reply was focused on what @jaroslav.rapp had posted. You also wrote: (We don't use a source control system.) Have you considered changing this situation? If so please take a look at Deltanji from George James Software (my employer). Some videos are available at https://www.youtube.com/playlist?list=PLGnA3ZIngG4oOUCEmplIYgSknQpNOtF08 Thanks, @Brett.Saviano . I'd like to assess what are plusses and minuses of migrating first. I'll watch it, thanks, Raj. I have to say though that I really prefer searchable text that can be visually scanned diagonally in 5 minutes as opposed to watching a 45-minute video. Oh well... What is the benefit of exporting to XML vs exporting to CLS? A thought about moving from *.xml source controlled files to *.CLS (UDL) file content with VSCode. The exported source content is different from existing in source control The export name is different and may be seen as an unrelated resource A while back I had shared community application ompare I mention as this utility allows the comparison of what is installed in a namespace, regardless if the external format was XML or UDL. Some may find useful to see the real differences between their own historic product releases and a current release. At least until have a few releases / baseline in their new source repository. Have notice other community apps like xml-to-udl that might be appropriate for need. I'll add to this, we use the same "embedded" source control behavior across Studio and VSCode for my team within InterSystems, and haven't had issues. @Richard.Filoramo , one question re: TrackWare - do you know offhand which "Actions" and "Other Studio actions" it uses in the UserAction method from %Studio.Extension.Base (see class reference)? There are some limitations/differences between VSCode and Studio but they're on things we see as either less common or undesirable to support from VSCode. One such case we've previously deemed "undesirable" is Action = 3, "Run an EXE on the client. The Target is the name of an executable file on the client machine. It is the responsibility of the customer to ensure this EXE is installed in a suitable location." Your statement that your source control system is written in ObjectScript and Delphi makes me think this might matter to you. More generally, @Brett.Saviano , there may be other aspects of complete support for the interface defined in %Studio.Extension.Base to consider. @Alex.Woodhead Just to clarify for everyone, Studio source control classes that import/export XML files will continue to work and be supported. There just won't be a menu option in VS Code to export files as XML. @Anna.Golitsyna The big plus is that VS Code is in active development, while Studio hasn't seen enhancements in years and now is deprecated. Other than that, here are some benefits of VS Code: Supports Mac, Linux and Alpine Linux in addition to Windows. Much faster release cycles so you get new features and fixes faster. Always forward compatible without needing to install a new version. Much better intellisense support. (a large list of features can be found here) Modern UI with fully customizable themes. Can be connected to multiple server-namespaces in the same window. Debugging supports expanding OREF's to see their properties. Thanks Brett! I will add the support of: Docker Git source control Github/Gitlub interactive plugins Embedded Python Co-pilot (when VScode writes ObjectScript for you instead of you) Full-functional IRIS Terminal And options to use 3rd-party plugins, e.g. from George James, @John.Murray mentioned earlier. Find in Files works with the Enable proposed APIs and valid version working. Was not aware of drag/drop for export/import. I find even though a lot of the discussions around source control are great and easier using vs code I still don't feel there is an easy jumping in point to really get started to use a control system. With the discussion of Intersystem IRIS Studio or VS Code, I understand the initial reaction to think you are losing something using VS Code. Will you miss some things, I'm sure you will, but measured on the whole I feel like VS Code is a much better environment even if all you ever do is objectscript work. I feel like that's the critical thing to remember, there may be some differences but measured on the whole it is better, give it a try and give it a chance, especially learning the full capabilities. I agree. Adopting source control is like committing to a workout regimen. It's hard to get started and feels like a big hassle, but eventually you can't imagine living any other way, and you love the way your body of code looks ;) @Brett.Saviano @Evgeny.Shvarov You listed VSCode plusses, thanks. How about what Studio does that VSCode plus free plugins still do not? One of our programmers complained about debugging as of July 2022. Is it on par now? @Anna.Golitsyna I think the debugging experience in VS Code is actually better than Studio since you can view the properties of OREF's in the variables view in VS Code but not Studio. You can have that developer file an issue report on GitHub, or contact the WRC if you have a support contract. As for features in Studio but not VS Code, the biggest one is the Inspector. It is very unlikely that it will ever be implemented in VS Code. VS Code also does not support integration with the legacy Zen BPL and DTL editors. VS Code will support integration with the new Angular versions of those editors when they are implemented. VS Code also doesn't support syntax coloring for Cache Basic or MultiValue Basic, but you can still edit those files. Will you miss some things?Now working 20 years with Studio I'm kind of "married" knowing all good and bad features.I dislike the idea to face a "forced divorce". Dictated from outside. It smells like very bad times in past. The opposite of freedom of decision. some context about me.. I've been working with InterSystems technologies since 1991 so I've been thru all of the changes for the past 32 years. Unless you give it a chance you won't have an opportunity to see what are the good features in VS code. There is no doubt that working with VSCode is more productive than working with ISC Studio. I've been working with ISC Cache since 1997 and thank God ISC finally has a normal development IDE. But there are small things that need to be fine-tuned:1. When overriding, be able to include the original implementation as well2. The terminal cannot process Home End keys, etc., and it throws lines.3. Close automatically opened routines/classes when debugging is finished4. In the debug console, the zwrite option5. Option to switch from read only file to edit file on GIT disk6. Debugging INT source codes does not work well7. jump to label+offset and a lot of little things will certainly appear. Maybe the problem is that I'm still working on Ensemble 2018 Josef Hi @Josef.Zvonicek, I'm glad that VS Code is making you more productive, and thanks for the feedback. I have some comments about your fine-tuning list: The "override class members" functionality is implemented by the Language Server extension. If you file an issue on its GitHub repository I would be happy to consider this enhancement request. The VS Code integrated terminal is part of the core product, and not our extensions, so I'm not sure we can do anything about this. Can you provide more details about how you started the terminal and the expected vs actual behavior? Newer versions of the vscode-objectscript extension should avoid opening that extra copy of the file when debugging. If you're using recent version like 2.8.0 or 2.8.1 and this isn't working, please file a GitHub issue in that extension's repository and I will take a look at it. The debug console can only evaluate expressions. It's not a full terminal and cannot execute commands, so this isn't possible unfortunately. I'm not sure what a GIT disk is. Are you editing files on your local file system? Can you describe what doesn't work well, and what we could do to make things better? There is a command called "Open Error Location..." that you can execute from the command palette. It prompts you to enter a "label+offset^routine" string and then opens that location. It only works for INT routines though. and just today spotted https://blog.postman.com/introducing-the-postman-vs-code-extension/ . This isn't full formed as they report We will continuously ship features and improvements—such as support for Postman Collections and environments—so be on the lookout. We value your input, so if you have any feedback on this beta version, please feel free to leave it in the comments. but just one more example why measured on the whole VS Code really is a better environment IMHO. For me it's a horrible news 😭 I really prefer to use Studio when explaining how to create properties (particularly relationships) and queries (particularly Class Queries based on COS) to students who see IRIS for the first and the last time during my classes. And when something goes wrong (and it does a lot of the time) it's usually easier to ask them to delete the code that produces error and rewrite it while I'm looking than to figure out what's wrong with it. And if it something more complicated than simple properties it can take a lot of time. Besides, not all students know (and want/need to learn) how to use VS Code and look for proper plug-ins, extensions etc. It will really make my life that much harder. one of my (former) customers suggested this approach: Train COS not on IRIS but on some Caché/ENS 2018 instances with Studio or on some older IRIS version As they run pure COS they have Studio for Training. An no need of new features once all the logic works they may move the result to some final IRIS (if ever they migrated) With #2 (at least for me anyway), the issue seems to be related to running iris session when using the Windows version of ssh.exe (called from VS Code, configured in settings under node terminal.integrated.profiles.windows). Home and End work normally at the Linux shell prompt, but when running iris session the effect is that either key produces the same result as pressing the Enter key. The current command is executed and a new IRIS prompt is generated. It doesn't seem to be a VS Code problem so much as an ISC problem, at least on Windows. Please, give VSCode a try. Regarding of extensions, you can give students a repository with .vscode/extensions.json, that will already contain examples. E.g. here is how my extensions.json looks like: { "recommendations": [ "eamodio.gitlens", "georgejames.gjlocate", "github.copilot", "intersystems-community.servermanager", "intersystems-community.sqltools-intersystems-driver", "intersystems-community.vscode-objectscript", "intersystems.language-server", "mohsen1.prettify-json", "ms-azuretools.vscode-docker", "ms-python.python", "ms-python.vscode-pylance", "ms-vscode-remote.remote-containers" ] } This will not install extensions automatically, but they will be shown as recommended for the workspace, like that: Here is the template they can start from and here is an example extensions.json file. @Iryna.Mykhailova please also look at VS Code's recently-introduced Profiles feature. I imagine this could be useful in learning contexts. Maybe my VS Code setup isn't correct, but if I need to explore % class files to learn more about behavior of some methods (let's face it, the documentation isn't always revealing), I use Studio. A recent example was learning what methods of %CSP.Page I could override and which order the override-ed methods were called in the code. I know in the past I've referenced other things. It's not often but it's helpful when we can. I haven't found a way to view % classes in VS Code. Maybe someone can help me if that's something I've missed! Hi @Michael.Davidovich, I can show you how to configure VS Code to see system classes. Are you using client-side or server-side editing? @Michael.Davidovich you might find this extension useful for exploring inherited methods etc: https://marketplace.visualstudio.com/items?itemName=georgejames.objectscript-class-view One quick/dirty(?) way is to do a "View Code in Namespace" for "%SYS". Under the %SYS namespace the percent classes are not filtered out. In the interest of accuracy, Studio does allow looking at OREFS to see their properties (View As > Object, or Dump object). I've also used Studio for 20+ years. I can still remember how much better it was than what we had before. We can all still use Studio if we want; it's not a forced divorce. But we hope that VS Code -- ObjectScript's features will make you comfortable enough to decide to do a conscious uncoupling. And as Frank Sinatra sang: "Love's much lovelier, the second time around." And he could have sung that at the Diplomat Hotel in Fort Lauderdale in 1974, where coincidentally InterSystems is hosting our Global Summit this year! We sometimes export classes from one environment and import them to another. I don't see .cls as a supported file type for those activities. Hi @Larry.Overkamp ! You can use $system.OBJ.ExportUDL() to export in CLS or MAC or INC. and $System.OBJ.Load or $system.OBJ.LoadDir() to import CLS or XML or MAC. As for transferring code between systems I'd recommend to maintain code in repositories (e.g. git) and deploy code via InterSystems Package Manager. The format doesn't matter as long as you can easily package multiple classes/routines in a single file. By easily I that mean that you should be able to choose the exported classes/routines eg. from a class tree. If I can guess you need export several classes/routines/macro in one file e.g. to deploy to another server. I'd recommend to use InterSystems Package Manager for it @Brett.Saviano Sorry I didn't see this until just now. We are editing on client-side. Is there documentation for this? I searched "package manager" in the documentation and didn't get anything in the results.... Package Manager is going to be a part of a product in near future, but right now it is not a part and can be installed with the following command: s r=##class(%Net.HttpRequest).%New(),r.Server="pm.community.intersystems.com",r.SSLConfiguration="ISC.FeatureTracker.SSL.Config" d r.Get("/packages/zpm/latest/installer"),$system.OBJ.LoadStream(r.HttpResponse.Data,"c") Caution! This is for IRIS only. The package manager. It has documentation, a bunch of videos, and there is a tag here. If for Interoperability productions it may also be appropriate to weigh up existing capabilities available for Production deployment. See: https://docs.intersystems.com/irisforhealth20232/csp/docbook/DocBook.UI.Page.cls?KEY=EGDV_deploying It provides functionality for detecting implementation used by a production. Have created idea for Production exports to generate IPM modules as well as the usual XML export deployment. https://ideas.intersystems.com/ideas/DPI-I-382 Readers of this thread may be interested in this discussion I just started about the export/import topic: https://community.intersystems.com/post/studio-vs-code-migration-addressing-exportimport-pain-point
Announcement
Anastasia Dyubaylo · Jun 16, 2023

InterSystems Developer Ecosystem Spring News 2023

Hello and welcome to the Developer Ecosystem Spring News! This spring we've had a lot of online and offline activities in the InterSystems Developer Ecosystem. In case you missed something, we've prepared for you a selection of the hottest news and topics to catch up on! News 💡 InterSystems Ideas News #5, #6 🔥 Global Masters: get points for your ideas on Ideas Portal 📝 InterSystems Studio is deprecated, starting with 2023.2 📝 Documentation for InterSystems Caché and InterSystems Ensemble versions prior to 2017.1 will only be available in PDF format 📝 Early Access Programs (EAPs) 📝 Take part in the FHIR R5 Quality Review! ✅ HealthShare Unified Care Record Earns National Committee for Quality Assurance Certification 👋 Caelestinus 2023 Kickoff Event ♨ April 4, 2023 - Alert: Incorrect Query Results ♨ April 10, 2023 - Alert: ECP Client Instability ♨ April 27, 2023 - Alert: Database and Journal Corruption when Using Encryption ♨ Get Alerts, Advisories and other Product News directly from InterSystems Contests & Events InterSystems IRIS Cloud SQL and IntegratedML Contest Contest Announcement Kick-off Webinar Technology Bonuses Time to Vote Technical Bonuses Results Winners Announcement Meetup with Winners Tech Article Contest: InterSystems IRIS Tutorials Announcement Bonuses Winners 📄 [DC Contest] 2nd InterSystems Tech Article Contest in Portuguese ⏯️ [Webinar] Webinar in Spanish: "EMPI: Set up and use case" ☕️ [Meetup] In-person Developer Meetup in Boston: Making Sense of Healthcare Data with SQL and Python Pandas ☕️ [Meetup] Benelux Caché User Group Meetup Latest Releases ⬇️ Developer Community Release, Spring 2023 Edition ⬇️ Improving your posting experience ⬇️ Caché and Ensemble Maintenance Releases ⬇️ InterSystems announces availability of InterSystems IRIS, IRIS for Health, & HealthShare Health Connect 2022.1.3 ⬇️ InterSystems announces General Availability of InterSystems IRIS, IRIS for Health, HealthShare Health Connect, & InterSystems IRIS Studio 2023.1 ⬇️ InterSystems IRIS, IRIS for Health, & HealthShare Health Connect 2023.1 developer previews Preview 3 Preview 4 Preview 5 ⬇️ InterSystems IRIS, IRIS for Health, & HealthShare Health Connect 2023.2 developer previews Preview 1 Preview 2 ⬇️ Zen Reports to be removed from InterSystems IRIS and IRIS for Health beginning with version 2025.1 ⬇️ Caché, Ensemble, and HSAP 2018.1.8 released ⬇️ IAM 3.2 Release Announcement ⬇️ IKO (InterSystems Kubernetes Operator) 3.5 Release Announcement Best Practices & Key Questions 🔥 Best Practices of Spring 2023 ZPM Simple Implementation Cookbook Welcome irissqlcli - advanced terminal for IRIS SQL Query as %Query or Query based on ObjectScript Machine Learning in IRIS using the HuggingFace API and/or ml models in local ( using Python ) Debugging Trick with SQL Data anonymization, introducing iris-Disguise Enterprise Monitor and HealthShare CI/CD with IRIS SQL Using Docker with your InterSystems IRIS development repository Debugging Web Debug the ObjectScript code using VSCode ❓ Key Questions of Spring 2023: March, April, May People and Companies to Know About 🌟 Global Masters of Spring 2023: March, April, May Job Opportunities 💼 IRIS system administrators - Stanford Healthcare 💼 InterSystems IRIS Technology Role Remote 💼 IRIS Developer - Health Data Management Engineer, Lead 💼 Job Opportunity for IRIS Senior Developer in SA So... Here is our take on the most interesting and important things! What were your highlights from this past season? Share them in the comments section and let's remember the fun we've had!