go to post Sylvain Guilbaud · Mar 5, 2020 Hi Ron, thanks for this great article. There's a typo which creates a wondering question about the potentiality of Google Cloud : Using the Google Cloud Console (Easiest) https://could.google.com
go to post Sylvain Guilbaud · Aug 12, 2019 I agree ; that's a drawback.BTW, if you're a partner with a Software Update contract, you can download the IRIS for Health containers directly from WRC Containers Distributions web site :
go to post Sylvain Guilbaud · Aug 12, 2019 Hi Duncan,before getting IRIS for Health on Docker Store, you can start with IRIS for Health Community Edition available on AWS, Azure and GCP.Kind Regards,Sylvain
go to post Sylvain Guilbaud · Nov 8, 2016 The alternative installation of Caché on the Mac OS X is much like the installation on any UNIX® platform.To install Caché:Obtain the installation kit from InterSystems and install it on the desktop (tar.gz)Log in as user ID root. It is acceptable to su (superuser) to root while logged in from another account.See Adjustments for Large Number of Concurrent Processes and make adjustments if needed.Follow the instructions in the Run the Installation Script section and subsequent sections of the “Installing Caché on UNIX and Linux” chapter of this guide.
go to post Sylvain Guilbaud · Oct 5, 2016 Hi Evgeny, this code was written while upgrading to an async mirrored a DeepSee remote instance (originally based on a shadow server configuration + ECP access to ^OBJ.DSTIME global from DeepSee instance to production. It was before DSINTERVAL was created). Of course this sample can be modified to add/remove/modify any other parameter by modifying the query on %Dictionary.ParameterDefinition to filter any other parameter you are trying to add/remove/modify.
go to post Sylvain Guilbaud · Mar 10, 2016 To export globals in XML format, use $system.OBJ.Export : d $system.OBJ.Export("DeepSee.TermList.GBL","/data/TermList.xml")
go to post Sylvain Guilbaud · Feb 18, 2016 Thank you Daniel.Actually I've found another way to do it without modifying any % classes !1. using Studio, create a class which inherits from "%DeepSee.UI.MDXExcel" ; ie : "MDX.export.cls"2. overwrite in MDX.export.cls what you need to modify to fit your expected rendering in the appropriate methods : OnPage, %PrintListingResult, or %PrintResults ...3. in your DeepSee dashboard, replace the Export Excel parameter of your widget, corresponding to this line in our .dashboard.DFI definition : <property name="excel">1</property>by a new navigate control which calls your MDX.export class :<control name="" action="navigate" target="*" targetProperty="./MDX.export.zen?MDX=...mdx query..." location="widget" type="auto" controlClass="" label="Export Excel" title="" value="" text="" readOnly="false" valueList="" displayList="" activeWhen=""> <valueRequired>false</valueRequired></control>NB: to retrieve all the parameters of the targetProperty (MDX, FILTERNAMES, FILTERVALUES, TITLE, ... ) , you just have to first run the native Excel Export and then copy the link by using the Downloads view of your browser.WARNING : the targetProperty length is limited to 250 characters
