Ben Spead · Mar 1, 2024 go to post

@Paul DeSantis - By default, all InterSystems Login users can only see the last released version of a product as well as any available preview releases.  Users that are Supported Customers (meaning they have been given access to our Support system as part of a Supported Organization) can access older builds, either through Evaluation or directly through the WRC Direct application.  Do you have a 2nd account which is tied to a Supported Org?  Or do you have a colleague who does?

Ben Spead · Feb 29, 2024 go to post

Absolutely!  In fact, I'm planning a project for my team so that our CICD pipeline will throw a failure if someone checks in a method, property, parameter in a class without Documatic (///) content.  Of course, just because comments exist doesn't mean it is good, but that's at least a place to start!   

Ben Spead · Feb 28, 2024 go to post

Got it - that would be a really great enhancement request though!  I would love to see that in action in VSCode :)

Ben Spead · Feb 28, 2024 go to post

An example would be helpful .... typically I will put argument documentation in my /// comment for the method, and use the <var>arg</var> tags to change the styling of the argument names in the method documentation to make it clear that it's referring to the argument.   

Ben Spead · Feb 26, 2024 go to post

wow - this looks like a very significant leap forward.  Great work and thank you for the continued improvement!!

Ben Spead · Feb 20, 2024 go to post

thank you @Tani Frankel!  We have made sure that download.InterSystems.com redirects to evaluation.InterSystems.com so hopefully those trying to follow this article can still find it even though the workflow will look differently.

@Azezur Rahman  - would you be willing to update your Article since the Download app has been replaced by the Evaluation application?  

Ben Spead · Feb 13, 2024 go to post

Issues found during the Preview are fixed on future Preview releases, so by staying current with the Preview releases you will hopefully avoid running into issues with your testing.

Ben Spead · Jan 31, 2024 go to post

@Chris Stewart - this is awesome!  thank you for the time you spent putting this together and sharing it ... it's a great example of power through simplicity :)

Ben Spead · Jan 19, 2024 go to post

Congratulations and thank you very much to everyone who invests so much into the InterSystems Developer Community!!

Ben Spead · Jan 17, 2024 go to post

@Nimisha Joseph  - I always use the Windows uninstall GUI ... if that doesn't work for you I recommend that you contact InterSystems Support.

Ben Spead · Jan 12, 2024 go to post

for the right column on the top two tables, is that number of downloads or number of distict people who downloaded?

Ben Spead · Jan 11, 2024 go to post

@Sreevani Goli - I am not sure about the DTL syntax, but looking at the error it looks like the "," is being dropped from the 2nd argument.  Maybe you need to try using "","" to escape the double quotes around the comma?

Ben Spead · Jan 11, 2024 go to post

@Sreevani Goli - if you know it is comma delimited and you want to strip off the last comma, you could use $piece() as follows:

USER>s Str="Addr1,Addr2,"
 
USER>write $piece(Str,",",1,*-1)
Addr1,Addr2

This will basically grab the entire string except for the last comma (and anything that comes after it).  

Ben Spead · Jan 10, 2024 go to post

@Alan Watts - there is no client-side Git plugin for Studio.  Studio works exclusively with server-side source-control hooks.  This is what the git-source-control package on OEX is ... it is server-side source control hooks to allow multiple developers to properly interact with a git repo from a single Namespace within InterSystems IRIS.  So once this is properly installed and configured for a given Namespace, once you connect via Studio you should see new top level Menu items in Studio and all changes will be governed by the source control hooks.  Nothing else is needed to be installed on the developers' Studio instances in terms of plug-ins, etc.