go to post Ben Spead · Jan 12, 2023 @Carlos García - could you please try again? I think we have taken care of the issue on the back end for your account.
go to post Ben Spead · Jan 12, 2023 @Marc Mundt I completely agree with you! There is a really awesome reference for InterSystems Studio Hotkeys in the docs: https://docs.intersystems.com/iris20201/csp/docbook/DocBook.UI.Page.cls?... Having a mapping to VSCode would be very useful.
go to post Ben Spead · Jan 11, 2023 @Carlos García - please reach out to InterSystems Support to report this and request assistance in getting it sorted out.
go to post Ben Spead · Jan 5, 2023 I love the subject matter - I was touring Independence Hall in Philadelphia on New Year's Eve with my family (which is where this document was signed). Following up with watching '1776' (the musical), and "National Treasure" in the following couple of days :) So I've been having a lot of focus on the U.S. Declaration of Independence recently ;)
go to post Ben Spead · Jan 5, 2023 Incredibly detailed article (love the screen shots!) Thank you for the time you spent putting this together :)
go to post Ben Spead · Jan 5, 2023 Evgeny - if you can track non-registered users on the side, do they get included in the "View Count" for each article? Or do only logged in readers get counted? Another contributing factor in the underreporting of readers is the participants who read the articles via email. I at least scan every article and question on the D.C. via my Inbox as I prefer an email-centric workflow. However, I am counted as a 'reader' only on those articles and questions which I decide to comment on or answer. I am sure I am not the only one consuming the D.C. content in this way.
go to post Ben Spead · Dec 30, 2022 @Udo Leimberger - thank you so much for being such an active part of the D.C., and I agree this community rocks! Have a very blessed 2023 :)
go to post Ben Spead · Dec 23, 2022 @Antti Suomi - thank you for raising this. it is being worked on, although due to the holiday we are not sure how long it will take (this requires aid from a 3rd party vendor). we apologize for the inconvenience.
go to post Ben Spead · Dec 21, 2022 @Jamshid Dehghanian - You are running a Community Edition of InterSystems IRIS for Health, and the built-in license key will only work for approximately one year and then will expire ... this may lead to the message you're seeing. Options include: - Go to Evaluation.InterSystems.com and download the latest version of InterSystems IRIS for Health Community Edition - Reach out to your account manager and ask for an extended Community Edition key that you can install on your instance Note - your routines and classes will be stored within the Routine DB for your Namespace, so you should be able to look in the SMP and see which iris.dat this is and you can just make a copy of that file on the OS level (stop InterSystems IRIS first). This will ensure that you don't lose anything for that namespace. You can also back up your data database if that is important to you. When you upgrade to a newer kit these should be preserved anyway, but I understand you'd like extra insurance so this is the way to ensure that. Hope that helps
go to post Ben Spead · Dec 19, 2022 If you look at the FAQ you'll see that this is specifically addressed:[quote] What happens if I have a deployment with a PWS and I install a new version? If an existing PWS is present IRIS will continue to use it. [/quote]
go to post Ben Spead · Dec 16, 2022 Nice explanation of how this works - thank you @Fabiano Sanches !!
