InterSystems has always provided -- with each maintenance release -- a document that describes all the changes in that maintenance release. This document is known informally as the relnotes or (now) the MRNotes*. Here’s a link to one of them, just to make sure we’re on the same page: https://docs.intersystems.com/iris20211/csp/docbook/relnotes/index.html
Could you please comment here and tell us if you use this document and how you use it and what you use it for?
For IRIS 2019.1 and later, the documentation has a new look and feel. Check it out:
https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls
The underlying changes include a new style sheet and a complete rewrite of the code we use to generate HTML. (There is now an underlying API for retrieving content as JSON, as well as a large set of unit tests -- for those of you who like that kind of thing!)
Recently there was an internal email thread on which SMTP server to use in demos. I thought I'd share the comments from that thread:
The newer dynamic SQL classes (%SQL.Statement and %StatementResult) perform better than %ResultSet, but I did not adopt them for some time because I had learned how to use %ResultSet. Finally, I made a cheat sheet, which I find useful when writing new code or rewriting old code. I thought other people might find it useful.
First, here is a somewhat more verbose adaptation of my cheat sheet:
I needed to use the OnGetNodeInfo callback of a Zen <dynaTree>, because this seems to be the only way to control the style separately for different levels of the tree. This post describes two discoveries I made.
When you use a dynaTree with the OnGetNodeInfo callback, the dynaTree creates a series of nodes and displays them top to bottom in the order they were created.
We heard from a customer who wanted to display a version number as a read-only production setting. During the build on the build server, this version number is added to the Production class. This works fine, and the Version is displayed in the Portal, but the customer wanted to write protect it, so the enduser can’t change it. The customer had defined the setting like this:
Property Version As %String;
Parameter SETTINGS = "Version:Info";
We advised the customer to define SETTINGS like this instead:
Parameter SETTINGS = "Version:Alerting:label"