Hi Kai,
Unfortunately only MII Illuminator service supports the content-type as text/json and not the Runner service.
Illuminator service is used for calling query template and Runner service is used to call transactions.
So you would not get transaction output as JSON directly.
So the work around is to wrap the transaction in a Xacute query and then call this query from your UI.
Lets see if MII extends this JSON support to the Runner service in future releases.
Answers to your questions:
1. Has the xacute query only Param.XX as parameters or does it contain self named Parameters?
All the queries have Param.XX and only transactions accept named params
2. On the transaction details page I see the numbers (same as SQL Query example with Param.1).
Here you need to map your transaction named params to Param.XX
3. I suspect only Param.1 to Param.32 exist in the query.
Yes.
Regards,
Rohit Negi.