How could we create a JSON which works on version 2016.1 ‽‽‽

Hello,

We need to send data to an API using form_data as follows:

Using Ensemble 2017 we would use dynamic objects as:

set body={}.%Set("app_id",pRequest.appId).%Set("contents",contents).%Set("include_player_ids",pRequest.idsDispositivos)

However, how could we create a JSON to include into the form-data value??? We would like the following result: {"language1":"message1","language2":"message2"}

First we thought about creating it directly, however it stills being a dynamic object and wouldn't work with Ensemble 2016.2

set body = {
"app_id": "...",
"include_player_ids": ["..."],
"contents": {"en": "NEXT APPOINTMENT", "es": "SIGUIENTE CITA"}
}
 

Then, we thought about creating it a string and then somehow converting it to JSON:

//set tData("contents") = "{"_pRequest.idioma_":"_pRequest.mensaje_"}" //Convert to JSON?

I have read: https://community.intersystems.com/post/introducing-new-json-capabilitie...
 

And tried the following commands into the terminal with Ensemble 2016.2

USER>set object = ##class(%Object).$new()
 
USER>set object.name = "Stefan Wittmann"
 
USER>do object.$toJSON()
{"name":"Stefan Wittmann"}
USER>
 

And applied to our case:

USER>set message = ##class(%Object).%New()
 
USER>set message.en = "english message"
 
USER>set message.es = "mensaje espanol"
 
USER>do message.$toJSON()
{"en":"english message","es":"mensaje espanol"}
USER>
 

So our code would be:

set tFormVarNames = "app_id,contents,include_player_ids"

set tData("app_id") = pRequest.idApp
set object = ##class(%Object).%New()
set object.en = pRequest.mensaje
set object.es = pRequest.mensaje
set tData("contents") = object.%ToJSON()
set tData("include_player_ids") = pRequest.idsDispositivos

set ..Adapter.SSLConfig = "comunicacionMSSSI" set tSC = ..Adapter.SendFormDataArray(.tResponse,"POST",httpRequest,.tFormVarNames,.tData,"https://onesignal.com/api/v1/notifications")

How would you achieve the required behaviour??? To create a JSON which would work on Ensemble 2016, with the structure:

{"language1":"message1","language2":"message2"}