Difference between revisions of "Extensions.DiagCom.DiagComChk103"

From emotive
Jump to navigation Jump to search
(Created page with "{{DISPLAYTITLE:Check rule '''DiagCom_Chk103'''}} == Classification == {{ClassificationCheckRule | DiagCom_Chk103 | DiagCom | Warning|OTF self-defined ch...")
 
Line 1: Line 1:
 
{{DISPLAYTITLE:Check rule '''DiagCom_Chk103'''}}
 
{{DISPLAYTITLE:Check rule '''DiagCom_Chk103'''}}
 
== Classification ==
 
== Classification ==
{{ClassificationCheckRule | DiagCom_Chk103 | [[Extensions.DiagCom|DiagCom]] | Warning|OTF self-defined check rule}}
+
<!-- {{ClassificationCheckRule | DiagCom_Chk103 | [[Extensions.DiagCom|DiagCom]] | Warning|OTF self-defined check rule}}-->
 +
{| {{TableHeader}}
 +
|- {{TableRow1}}
 +
| '''Name''' || '''DiagCom_Chk100'''
 +
|- {{TableRow2}}
 +
| '''Class''' || [[Extensions.DiagCom|DiagCom]]
 +
|- {{TableRow1}}
 +
| '''Severity''' || Warning
 +
|- {{TableRow2}}
 +
| '''SpecifiedBy''' || OTF self-defined check rule
 +
|}
  
 
== Description ==
 
== 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.
 
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.

Revision as of 10:27, 10 December 2018

Classification

Name DiagCom_Chk100
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.