Congratulations! 

you can reach out to your account manager to get an updated key if you need to stay on the same version of the Community Edition

what type of a page are you using?  csp?  zen?  a third party JS Library?

I suggest that you open a Support ticket with the WRC if you don't get a good answer quickly here.  

@Hiroshi Sato - thank you for sharing!

I would recommend that rather than using $zf(-100) you use the %File class to make your directory creation OS-independent.  This will allow it to be used on different OSes.

Check out the CreateDirectoryChain() method of the %File class:

https://docs.intersystems.com/iris20231/csp/documatic/%25CSP.Documatic…

So your line "Set x=$ZF(-100, "/shell", "mkdir", Directory)" could be replaced by:

Set x=##class(%File).CreateDirectoryChain(Directory,.return)
If ('x) {
  Write "Error Creating Directory Chain: "_return
}

Also, make sure that this script runs as the user that is used for all IRIS processes to ensure that the directory has appropriate ownership and permissions

HTH!

ways great to see a well written tutorial - thank you for the time you spent on this :)

nice work!! thank you all for your contribution :)

may I ask why you would want to do this?  What is the downside of the methods all being in the same class?

I don't think there is any way of doing this other than manually.  I think you'll need to create a new class and then copy the method definition into the new class.

Thank you @Matthew Giesmann !!  I know a lot of work went into this effort, and that our beta testers have been using this successfully for many months.  

Everyone - please make sure to provide feedback, especially if you see any issues.  After a period of dual-use we will be retiring the old UI completely so if there are reasons users need to keep using the old UI for some reason we need to hear about the details ASAP.  

Are you exporting it as OBJ-only, or are you okay exporting it for a previous version which they will then load into their instance and compile?  

E.g. if you use Do $System.OBJ.SetQualifiers("/exportversion=2017.2") it will export the code in Caché 2017.2 format.  *However* this will not catch if you use syntax or updated APIs which were not supported in 2017.2.  You should really get a copy of the target version of software from the WRC (kits or containers) and at least do a compilation test there.  

wow - what an incredibly in-depth tutorial!  thank you @Yuri Marx for the time you took putting this together for the Community!

very nice article!  Nice to see this topic addressed to raise awareness with new users on how this works :)