Sergey - I also appreciate the point about the "component" approach (as we're using 1.x + Angular Material).  If you have any good references or tutorials on that approach (and/or contrasting with the 'typical' approach to do Angular 1.x), please post them :)

Gaolai,

You need leading whitespace on any line of a routine which is not a line tag.  Try putting a space or Tab on your 2nd and 3rd lines.

Also, "Hello there!" isn't a valid COS command.  Try using:

   Write "Hello There!"

I think this would be a great approach Evgeny!

If we change the unanswered query to only include questions with 'true' answers selected, do we expect everyone to be good enough citizens to go back and select true answers once they are provided?  Would admins be able to mark true answers if the author abandons the thread?

Removed as requested (although I personally think that the screenshot makes people more likely to take a look at your code rather than less likely).

Well played Fabian :)  Merry Christmas to you as well!

For debugging or programmatic purposes?  If debugging / interactive you can just zwrite the variable to see the properties.

Nice sample Fabio - thanks!!

Michael - thanks for the article.  It would be really helpful if you could add a paragraph at the top explaining what the Ensemble scheduler is and what it's main use-cases are so that people can tell quickly whether or not this is something which they would want to learn more about.  Perhaps as an Intro?

%ZNODENAME appears to be a statically linked callout function (see http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...).  This is specific to your code / application / environment and isn't something generic to Caché.

If you are interested in retrieving your server name, try using:

$piece($system,":")

I think that may be a custom routine.  I don't recognize it as a Caché-supplied resource. 

Assuming you are a supported customer, you can download this from the Distributions page in the WRC application.

Sorry - I missed that.

Getting the "When" is easy - there is a timestamp in the header of the generated .INT code showing when the source was last compiled.  E.g:

 ;Sample.Address.1
 ;(C)InterSystems, generated for class Sample.Address. Do NOT edit. 10/27/2016 09:12:38AM
 ;;7A2F686C;Sample.Address
 ;
However the "Who" might prove to be more challenging. You might be able to accomplish this with a Method Generator that records the $Username and timestamp for access via a method or parameter?  See http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...

You can add logic in %OnAfterSave() for your object which will grab the object ID, $Username and the timestamp and tuck them away in an auditing table somewhere.  Alternatively you could add LastChangedBy and LastChangedTimestamp properties to your object and then populate them inside of %OnAddToSaveSet() (this is probably the most straightforward way to do it).

Hope that helps!

I second the motion!