Difference between revisions of "OtfOdxAccessPath"
| Line 10: | Line 10: | ||
| style="vertical-align:top; text-align:justify;"| | | style="vertical-align:top; text-align:justify;"| | ||
Access path can be determined from the workflow via shortnames of property of term/action like [[GetComChannel]], [[CreateDiagServiceByName]] or [[ExecuteDiagService]]. In some cases, access path can just be detected at runtime. Thereby it would be set at the AccessPath property of corresponding actions. | Access path can be determined from the workflow via shortnames of property of term/action like [[GetComChannel]], [[CreateDiagServiceByName]] or [[ExecuteDiagService]]. In some cases, access path can just be detected at runtime. Thereby it would be set at the AccessPath property of corresponding actions. | ||
| + | |||
| + | It will be verified in OTF whether the access paths exist. There 3 [[OtxValidation#Checker_rules|check rules]] for access path: | ||
| + | |||
| + | New Checker-Rule: | ||
| + | • Warning: The access path can not be determined unambiguously | ||
| + | • Critical: The access path may be determined, but the target do not exist | ||
| + | • Warning: The objectives of the access paths exist, but do not have the same structure (attributes). The author is the warning only indicated | ||
| + | to treat this in a suitable manner. A detection of the treatment does not occur | ||
When validating the values in AccessPath property are used only when the access path can not be explicitly determined from the workflow | When validating the values in AccessPath property are used only when the access path can not be explicitly determined from the workflow | ||
Revision as of 09:49, 3 December 2014
Overview
Access path is a solid connection from OTX to ODX data. It comprises the shortnames of following ODX element: logical link, ecuvariant (optional), diagservice, request/response and parameter, written in order and separated with ".".
An example of complete access path: "LL_AccesStartInterUDS.EV_KessyHellaMQBAB_002.DiagnServi_ReadDataByIdentActuaTestStatu.Req_ReadDataByIdentActuaTestStatu.Param_RequeServiId"
The access path is used for validation and supporting selection of possible shortnames instead of editing.
Validation
|
Access path can be determined from the workflow via shortnames of property of term/action like GetComChannel, CreateDiagServiceByName or ExecuteDiagService. In some cases, access path can just be detected at runtime. Thereby it would be set at the AccessPath property of corresponding actions. It will be verified in OTF whether the access paths exist. There 3 check rules for access path: New Checker-Rule: • Warning: The access path can not be determined unambiguously • Critical: The access path may be determined, but the target do not exist • Warning: The objectives of the access paths exist, but do not have the same structure (attributes). The author is the warning only indicated to treat this in a suitable manner. A detection of the treatment does not occur When validating the values in AccessPath property are used only when the access path can not be explicitly determined from the workflow |
|
