Documentation for your product/version is here:
https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls

Note that Caché 2018.1 supports .NET up to 4.5, it seems you are using 4.8, I'm not sure it works with 4.8.

In Caché Management Portal, go to System Administration -> Security -> Users, in the _SYSTEM user row click the "Profile" link (last column), after the .NET error, what's the content of "Last Reason for Failing to Login"?

Almost impossible to help without details on the .NET code you are using to connect and call Caché.

I think examples use very old version of Visual Studio

You are using an old version/product too, Caché 2018.1.

I think the product IS fully released since more than a week now:

InterSystems announces General Availability of InterSystems IRIS 2024.1

Or I'm missing something?

You even posted in the announce!

found no documentation on how to set a VECTOR Datetype on pure object level

Maybe you can have a look to the documentation of $vector, $vectorop, $vectordefined and $isvector intrinsic functions.

Congratulation Robert! 🏆🎖

Definitely deserved recognition.

The prerequisites for the InterSystems HL7 Interface Specialist certification include the training course and "At least 6 months - 1 year designing, building, and performing basic troubleshooting of HL7 interfaces with InterSystems products version 2019.1 or higher."

Actual/real experience will definitely help in passing the certification, theoretical study and some exercise may not be enough to gain the knowledge required.

In the exam description page you can find a list of "Exam Topics and Content". All questions in the exam belong to those topics.

Last but not least, everything is contained in the documentation.

Where/when do you want to know it?

Usually you get this information looking at the trace of the session/message.

Or you need to know the sender from within your BO code/method?

Parameter runtime computation works fine, you can test it from terminal:

w ##class(ECUH.BPL.ClassMethods.X509CredentialAlias).#VALUELIST

Long story short, you cannot use runtime computed VALUELIST in this context.

I suggest using the proper, officially documented way to implement your requirement, see my first answer above.

Using the Curly Braces a parameter is evaluated at compile time:

Parameter VALUELIST = {..GetValueList()};

You need to evaluate it at run time, in that case use COSEXPRESSION:

Parameter VALUELIST As COSEXPRESSION = "..GetValueList()";

The the relevant documentation is:

Defining and Referring to Class Parameters

I just realized that with IRIS for Health (and I maybe also HelthShare connect) ZAUTHENTICATE is mapped to HSLIB and you should use/modify HS.Local.ZAUTHENTICATE class in HSCUSTOM namespace.

If you are using HealthShare, and I do believe so, please read the following documentation (login required):

Custom Authentication Processing using the Local ZAUTHENTICATE

There you will find:

Important:

The ZAUTHENTICATE provided with HealthShare includes callbacks that allow you to add custom processing at specific entry points. Do not modify the supplied ZAUTHENTICATE. Instead, add your callback processing as class methods in the class HS.Local.ZAUTHENTICATE

If it was mapped to HSLIB, then I think you are using HealthShare, if so, you are not supposed to change that mapping, instead you should use/modify HS.Local.ZAUTHENTICATE class in HSCUSTOM namespace.

I believe the mapping will be recreated when updating/upgrading the system.

I don't think there is a callback method available.

One option could be to subclass %CSP.REST and use your subclass instead of %CSP.REST.

You subclass can be something like:

Class MyCustomCSP.REST Extends %CSP.REST
{

ClassMethod DispatchRequest(url As %String, method As %String, forwarded As %Boolean = 0, args...) As %Status
{
	Set sc=##super(url,method,forwarded,.args)
	
	; your "onPostDispatch" code here 
	Quit sc
}

}

"...the write() function seems to be overlaying the whole stream..."

Of course, that's the way a stream  works as designed. The resulting (target) stream will contains what the Write() method writes to the stream. And only that.

If this is not what you expect, then please provide more details on your goal.

Just in case, try adding a "code" action BEFORE your actions with:

  Do source.Stream.Rewind()
  Do target.Stream.Clear()

How big (Size) is the stream? If it's larger then the maximum string supported string length (~3.5MB), then you have a problem with your code.

When it does not work, do you get an error?

In the DTL, how do you set the "Create" option/parameter? (copy or new?)

Is there any other reference/set referencing the Stream in the DTL?

What product? If it's HealthShare then you should use the class HS.Local.ZAUTHENTICATE in HSCUSTOM namespace.