Difference between revisions of "OtfOdxAccessPath"
| (21 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{DISPLAYTITLE:Open Test Framework - Access Path}}[[Category:OTF]] | ||
==Overview== | ==Overview== | ||
| − | + | Access path is a solid connection from OTX to ODX data. It comprises the shortnames of following [[Allgemeine_Elemente#All.C2.ADge.C2.ADmei.C2.ADne_Ele.C2.ADmen.C2.ADte|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"'' | ||
| + | |||
| + | Access path can be determined from the workflow via shortnames of property of term/action like [[Extensions.DiagCom.GetComChannel|GetComChannel]], [[Extensions.DiagCom.CreateDiagServiceByName|CreateDiagServiceByName]] or [[Extensions.DiagCom.ExecuteDiagService|ExecuteDiagService]]. In some cases, access path can just be detected at runtime. Thereby it would be set at the AccessPath property of corresponding actions. | ||
| + | |||
| + | ==Validation== | ||
| + | {| | ||
| + | | style="vertical-align:top; text-align:justify;"| | ||
| + | Both determined and set access path will be validated in OTF. There 3 [[Core.Validation#Checker_rules|check rules]] for access path: | ||
| + | |||
| + | *'''DiagCom_Chk100''' (warning): The access path can not be determined unambiguously. For example: the ODX database is not set yet. | ||
| + | *'''DiagCom_Chk101''' (critical): The access path may be determined, but the target does not exist (in the ODX database). | ||
| + | *'''DiagCom_Chk102''' (warning): The objectives of the access paths exist, but do not have the same structure (attributes). | ||
| + | |||
| + | In validation, the values in AccessPath property are used only when the access path can not be explicitly determined from the workflow. | ||
| + | | style="width:100px;" | | ||
| + | | style="vertical-align:top; text-align:justify;"| {{ImageStyleCenter|accesspath1.png| 270| Access path validation}} | ||
| + | |} | ||
| + | |||
| + | ==Shortname selection== | ||
| + | {| | ||
| + | | style="vertical-align:top; text-align:justify;"| | ||
| + | Access path is also used to find all the possible values of shortname for property of ComChannel, DiagService or Request/Response parameters. When opening the properties, users just has to choose the right value instead of seeking and entering it themselves. | ||
| + | | style="width:100px;" | | ||
| + | | style="vertical-align:top; text-align:justify;"| {{ImageStyleCenter|snselection.png| 350| Shortname selection}} | ||
| + | |} | ||
Latest revision as of 10:51, 1 October 2018
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"
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.
Validation
|
Both determined and set access path will be validated in OTF. There 3 check rules for access path:
In validation, the values in AccessPath property are used only when the access path can not be explicitly determined from the workflow. |
|
Shortname selection
|
Access path is also used to find all the possible values of shortname for property of ComChannel, DiagService or Request/Response parameters. When opening the properties, users just has to choose the right value instead of seeking and entering it themselves. |
|
