apologies - I don't have a fully working sample available (or time to put one together I am afraid), but maybe else could put one together for you. You might get further if you share the code you have so far which is using these two components and explain the specific issues you are seeing (your original post wasn't clear that you already had the appropriate components in-hand but were having issues using them correctly)
To show the image you can use: https://docs.intersystems.com/iris20231/csp/documatic/%25CSP.Documatic…
This gives you the ability to bind to a stream via OID
Here is the documentation on the file upload control: https://docs.intersystems.com/iris20231/csp/documatic/%25CSP.Documatic…
HTH!
You don't need to use REST APIs. One of the strengths of Zen was that it allowed you to directly access data within the DB for easy display
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 :)
well played :)
Most welcome - good luck with the final conclusion of your work!
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.
Thank you @Gertjan Klein - that did it! (note, I fixed the missing ) in my example ... obviously I wrote that in my browser and not my IDE ;) )
Thank you @Jeffrey Drumm !!!
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 :)
thanks for the input Robert ... %All is powerful but won't work for me in this scenario.
300 unique packages makes this approach unwieldy
Thanks Clark - this is one of the approaches I hadn't thought of previously
We are using %ALL for some other things but unfortunately it won't apply in this case. Specifically, this is for a HS instance where we need to move auto-created classes into a new routine DB. So I can't add a mapping for each and every package (300 packages).
thanks Tim - this is along the lines of what I was thinking about. Much appreciated!
Thanks Chad - I think that this would be the lowest impact overhead approach if I don't copy the definitions directly via a clone or the globals
Thanks Vik ... that sounds like a good approach to play with!
Thanks Matt, I am trying to avoid using the OS as the middle-man in this case as we have 300+ namespaces to do this on and so should be scripted. I can create a %Method that would do this but was hoping for a quick command that could just do the transfer
seriously! it's amazing how much knowledge there is to be gleaned within this community :)
Bravo gentlemen!! thank you for your continued investment in our community :)
Another very cool aspect of the feature :) So it looks like this is just a built-in alias which ships with InterSystems IRIS.
nice intro - thank you!
@Dmitry Maslennikov - thank you! Docs reference? Do you know what the ":" syntax is?