When JSON code is used inside the Test Step it gets understood as macro code

When JSON code is used inside the Test Step it gets understood as macro code.

Example:
A manual test case is designed with following description/text in a step:
{

"requestId": "b05f3588-ea2e-4e19-7c9b-daddda6205c1",

"deviceId":

{ "obeEquipmentId": "170BF363", "manufacturerId": 3 }
,

"globalVehicleParam":
{ "licensePlateNumber": "K 911", "countryCode": "AT", "euroValue": 1 }
,

"requestValidity": "2018-06-10T09:33:30.822Z",

"displayTextObu": "LPN Changed"

}

This will be represented correct in the test case as long I´m in Edit-Mode.

In View-Mode and also during test case execution it will be represented in this way:

{ "requestId": "b05f3588-ea2e-4e19-7c9b-daddda6205c1",

"deviceId": Unknown macro:
{ "obeEquipmentId"}

,
"globalVehicleParam":
Unknown macro:

{ "licensePlateNumber"}

,
"requestValidity": "2018-06-10T09:33:30.822Z",
"displayTextObu": "LPN Changed"
}