OtfOdxAccessPath
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. |
|