Redefine HTTP adapter like this:

Class Production.Adapter.HTTPOutboundAdapter Extends EnsLib.HTTP.OutboundAdapter
{

/// Send a POST to the configured Server, Port and URL, sending form data to the named form variables.
Method Post(Output pHttpResponse As %Net.HttpResponse, pFormVarNames As %String, pData...) As %Status
{

    quit ..SendFormDataArray(.pHttpResponse, "POST", ..GetRequest(), .pFormVarNames, .pData)
}

ClassMethod GetRequest() As %Net.HttpRequest
{
    set request = ##class(%Net.HttpRequest).%New()
    set request.ContentType = "application/json"
    quit request
}

}

And use it instead of default adapter.

Please consider posting it here.

Please consider posting it here.

Try this:

1. Write stream to string

2. Use $zcvt on string $zcvt(string,"O","UTF8")

3. Send this stream to XSLT

Can we leverage this application to show globals currently in Global Buffer?

OCR:

S S="*"
S A="123*456"
S B="$P(A,S,2)"
W @B
S C=@B

Cache private web server is configured and available by default.

If System Management Portal opens then private server works.

Here's a good tutorial on developing Angular applications on Caché.

Please check the output:

set result = ##Class(%File).Delete(fileNamewithPath, .status)
zw result
zw status

There are several ways to do that. Let's say you have a persistent property

Property Problem As %String;

That you don't want anyone to see.

1. Make it private:

Property Problem As %String [ Private ];

It would not be displayed altogether

2. Add accessor methods:

Property Problem As %String;

Method ProblemGet() As %String [ ServerOnly = 1 ]
{
    Quit "****"
}

Method ProblemRealGet()
{
    Quit i%Problem2
}

Method ProblemSet(Arg As %String) As %Status [ ServerOnly = 1 ]
{
    Set i%Problem2 = Arg
    Quit $$$OK
}

This way default callers would get **** and only your app code can access the real value.

3. Do not project property to XML

Property Problem As %String(XMLPROJECTION = "none");

As ensemble message viewer is XML-based it would hide property from it.

4. Create a special datatype. For example MyApp.Datatype.Password datatype returns **** as Display and ODBC values:

Class MyApp.Datatype.Password Extends %String
{

ClassMethod LogicalToDisplay(%val As %String) As %String [ Internal ]
{
    q $case(%val,"":"",:"*****")
}

ClassMethod LogicalToOdbc(%val As %String) As %String [ Internal ]
{
    q $case(%val,"":"",:"*****")
}

}

To use it:

Property Problem As MyApp.Datatypes.Password;

5. Extract the property into a separate class and reference the object of that class.

These approaches could be combined.

ICM can do it.

Use DM and AM instances.

Maybe @Luca Ravazzolo would add more info.

Do you want to get a list of possible values at runtime?

If so consider making your property object-valued:

Property PrdType As Demo.Data.PrdType;

If you do want to build a list once at compile time, then it is probably possible using method generators, but I would not recommend this approach.

Not an answer, but you can use LIST function to remove cursors and simplify code.

ClassMethod GetTypeDisplay() As %String
{
    &sql(SELECT LIST(DISTINCT TypeName) INTO :result FROM Demo_Data.PrdType)
    q result
}

ClassMethod GetTypeValue() As %String
{
    &sql(SELECT LIST(DISTINCT TypeId) INTO :result FROM Demo_Data.PrdType)
    q result
}

I use

set var1 = "value1"
set var2 = "value1"
set var3 = "value1"
set var4 = "value2"
set var5 = "value2"
set var6 = "value3"
set var7 = "value3"
set var8 = "value3"

as it's the most readable. Or 

#dim var1 As Type = "value1"

Time spent on local sets is usually a pittance of all CPU time spent.

Please describe your use case.