See the related docs of the FHIR Configuration Management API:

https://docs.intersystems.com/irisforhealthlatest/csp/docbook/fhir-config-rest-api/index.html

FHIR Server QuickStart Tutorial

See the Native SDK for Java - here are the specific Docs for manipulating Globals as you asked (but the API provides other access types).

There are some related Open Exchange apps - native-api-command-line-java by @Robert Cemper and native-api-contest-template by @Bob Kuszewski you can also use as samples.

I was able to do it with Okta's auth0.

See some info in this post.

For IRIS, since 2025.3, there is a new option for FIFO handling (even with pool size > 1).

See related Docs - Maintaining First-In First-Out (FIFO) Processing and related video Multi-threading an HL7 Interface and scaling beyond FIFO constraints by @James MacKeith 

Regarding your comment @Evgeny Shvarov: "there were no compilation errors, no console messages - no evidence of what is wrong.", in these HTTP (CSP/Web) kind of situations/problems it is recommended to use "CSP Logging" (aka ISCLOG).

If you turn on the %ISCLOG you should be able to see the error you are getting.

For example if I changed my REST dispatch class from the correct: 'Demo.Debug.REST' to a non-existent: 'Demo.Debug.REST11', and try and call my service, I can see from the ISCLOG-based table -

%SYS>>SELECT ID, Category, LogLevel, Message FROM %Library.SysLogTable WHERE Message [ 'ERROR'

| ID | Category 	| LogLevel  | Message 					|
| -- | -- 		| -- 	    | -- 						|
| 39 | CSPServer 	| 2         | [HandleError]: ERROR #5002: ObjectScript error: <CLASS DOES NOT EXIST>CSPDispatch+147^%SYS.cspServer *Demo.Debug.REST11 |

So you can see you would be able to observe you are getting a <CLASS DOES NOT EXIST> error, and the name of the class it is trying to access.

(Of course there are other entries in the log, before, and after this entry, that can also help you relate this error to the URL you are trying to access)

Looks like a great event!

(Especially the Lego part 😉)

Kudos to the Iberia team and all international support!

AlertGroups are defined in the context of using the Managed Alerts framework.

See related docs. And specifically the section about defining them.

If you want an example of doing this in a wider scope, for a whole package, you can see this example (part of the DeleteHelper sample).

Are you instantiating the 'target' variable?...

It doesn't look like it, hence your Invalid Oref when trying to access the MRN property (unless you're sending it in ByRef, but in that case it seems not be an object either).

So it looks like you were focused on the right side of your SET command, though the problem might be on the left side.

Happy Birthday! 🎂

The InterSystems community wouldn't have been the same without... well... The Community!!

Special congratulations to all the Community management team! You do such a great job for the benefit of all of us.

And of course to all the members out there who contribute and take a part in this great place.

Looking forward to the next 10 years!

Wow! RESTFORMS was one of my all-time favorites!

Great contributions all around!

Well deserved recognition!

Thanks @Ariel Glikman, great article, and samples on the OE app/GitHub repo.

I believe anyone deploying IAM in a production-grade environment must consider and would greatly benefit from, using one of these options, and this would be an excellent jump board.

A true pillar of innovation, and commitment to the community.

In general (and messages and streams are just one example) there is a trade-off between more traceability and visibility vs. storage/space (and performance).

QuickStream is indeed a mechanism used internally to address the performance and storage concerns, but, to complete this with a traceability option, there is also a dedicated Business Operation that can add the desired data - see Enhanced Debugging and the introduction of HS.Util.Trace.Operations. This simply adds more calls in the session, to this Operation which (could) include the stream data. The advantage of this is that you can turn it on or off, and you can control also the "level" of tracing. Take into account of course that this needs to be done ahead of what you want to trace/visualize, you can't "apply" this retroactively.