Difference between revisions of "Extensions.DiagCom.DiagComChk103"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
{| {{TableHeader}} | {| {{TableHeader}} | ||
|- {{TableRow1}} | |- {{TableRow1}} | ||
| − | | '''Name''' || ''' | + | | '''Name''' || '''DiagCom_Chk103''' |
|- {{TableRow2}} | |- {{TableRow2}} | ||
| '''Class''' || [[Extensions.DiagCom|DiagCom]] | | '''Class''' || [[Extensions.DiagCom|DiagCom]] | ||
Latest revision as of 10:28, 10 December 2018
Classification
| Name | DiagCom_Chk103 |
| Class | DiagCom |
| Severity | Warning |
| SpecifiedBy | OTF self-defined check rule |
Description
In an ExecuteDiagService action, if an invalid OTX data type is mapped to a request parameter or a response parameter is mapped to an invalid OTX data type via inline mapping. For instance if a String variable gets mapped onto a request parameter that is of type Integer.
