go to post John Murray · Mar 15, 2016 What Caché version are you working with?The use of SCHEMA in this way is documented athttp://docs.intersystems.com/cache201513/csp/docbook/DocBook.UI.Page.cls... but not at http://docs.intersystems.com/cache20141/csp/docbook/DocBook.UI.Page.cls?... so it appears to have been introduced with 2015.1. I didn't find any mention of it in the 2015.1 release notes though.
go to post John Murray · Mar 14, 2016 If your READ from wrappercomp raises an error (e.g. end of file) you don't have anything in place to catch this error, CLOSE wrappercomp and USE olddev once more. I suggest you add some code (for example a TRY/CATCH block) to do this, and also to tell you what the error was. That information might help you find out why the wrappercomp pipe didn't work as you expected.
go to post John Murray · Mar 14, 2016 I think a "GRANT EXECUTE ON SCHEMA xyz TO roleA, roleB" should be sufficient to give users with roleA or roleB the ability to run any stored procedure defined by any class in your xyz package, even classes / procedures that you haven't yet written.
go to post John Murray · Mar 14, 2016 AFAIK only the owner of the class (set using the Owner keyword on the class, defaulting to _SYSTEM) has automatic rights to invoke all of the SQL stored procedures that the class implements (as classmethods with the SqlProc keyword). Anyone else who needs to be able to invoke them will need the right granting to them, either directly or via a role.
go to post John Murray · Mar 11, 2016 That's interesting to know. It means that my experiment can become: USER>s oResult=##class(%Library.File).FileSetFunc("c:\s\","*.txt") USER>while oResult.%Next() {w !,oResult.%Get("Name")} ... And now static code analysis that detects classmethod references can spot the use of the secret FileSetFunc method within the class that implements the query I'm using.
go to post John Murray · Mar 11, 2016 What version of Ensemble / HealthShare is running its webserver at chft-eprtiedev.xthis.nhs.uk:57772 ?
go to post John Murray · Mar 11, 2016 Thanks for putting so much time and effort into this Mike.Would you be willing to offer the examples etc as PDF downloads as an alternative to .docx files?Maybe also worth deleting the "Sample Page" item from your site.
go to post John Murray · Mar 11, 2016 One caveat about transferring globals between namespaces / instances using XML format is that by default when you load the XML into the target namespace the global(s) in your XML file will be pre-killed. In other words, it's a "replace" operation rather than a "merge" one. This may be exactly what you want in many situations, but if you've been used to using other utilities to export and import globals then it's different.To override this behaviour, add the "/mergeglobal=1" qualifier during your import, for example as the second argument (qspec) to $system.OBJ.Load(), which is of course the Load classmethod of %SYSTEM.OBJ.See more qualifier documentation here.
go to post John Murray · Mar 10, 2016 Thanks Dmitry. That worked, upgrading me from 1.0.107 to 1.0.112
go to post John Murray · Mar 10, 2016 Hermain, I think yours predates the point where ISC implemented the ability to update Atelier from within Atelier. I suggest you download the latest kit and install that. Thereafter you ought to be able to update from within. But bear in mind I'm not an ISC person, so my advice might be incorrect.
go to post John Murray · Mar 10, 2016 Thanks for sharing this detailed information Jamie. I noticed that the headers have links to a wiki on GitHub, but they're unreachable to me and presumably to other non-ISC folk.
go to post John Murray · Mar 10, 2016 Was that repository URL pre-populated in your Atelier?Maybe the response Dmitry gave to this post I created in the Atelier community will help you.
go to post John Murray · Mar 9, 2016 Tiago,Do you mean that when you are writing output from the server (e.g. from a source control class) you want to be able to control the colour of that text? I have never discovered a way of doing that, but let's see if anyone at ISC knows of an undocumented feature there.
go to post John Murray · Mar 9, 2016 I can confirm that the 64bit Windows Ensemble download link is working for me.
go to post John Murray · Mar 9, 2016 That worked. I guess the Developer Community application ought to do a better job with content expiration or something in order to make sure we see the correct images.
go to post John Murray · Mar 9, 2016 Nicki, did you paste the wrong thing as your second image? Under the title "studio:" I'm seeing an Atelier "Create a New Project" dialog screenshot.
go to post John Murray · Mar 9, 2016 Existing users of our Deltanji source code management tool, which runs natively inside Caché / Ensemble / HealthShare, may want to start using Atelier without having first to re-engineer their source control. I foresee a need for an Atelier user to be able to interact with a Deltanji dialog and then trigger a server-side action.
go to post John Murray · Mar 8, 2016 While not directly (yet) addressing Jenny's specific Ensemble HL7 interface scenario, discussions on the "Development teams and namespaces" thread may be of interest.
go to post John Murray · Mar 8, 2016 Certainly looks strange that you can browse namespaces on the Server Explorer tab but the new project wizard says it can't find any. I don't see your symptoms on mine, but I'm connecting to a Windows instance of 2016.2. My Atelier "About" box shows version 1.0.107. Is yours that version too?
