Discussions

So, if I create a communication log item and I specify an OutputType, most of the time this is a CommunicationOutputMethodEmailData, for example:

"OutputMethod": {
	"$type": "Asi.Soa.Communications.DataContracts.CommunicationOutputMethodEmailData, Asi.Contracts",
	"From": ...
	"To": ...
	"CopyTo": ...
	"Subject": "Test Email Subject 1"
}

During some additional testing with (read:guessing) different type names, I discovered there is also a CommunicationOutputMethodSmsData, but I can't figure out if there are any properties on it. It seems to take and return an empty object successfully, though - for example, I can create and get this back successfully as part of the OutputSteps collection:

"OutputMethod": {
	"$type": "Asi.Soa.Communications.DataContracts.CommunicationOutputMethodSmsData, Asi.Contracts"
}

Interestingly, in the staff site UI... it behaves exactly like an e-mail. There is no differentiation to tell the user this is an SMS message:

Nor in the actual communication logs themselves either:

So... what is this, can/should we use it, and why doesn't RiSE reflect the communication type correctly?