Difference between revisions of "OtfOdxAccessPath"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
==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"'' | An example of complete access path: ''"LL_AccesStartInterUDS'''.'''EV_KessyHellaMQBAB_002'''.'''DiagnServi_ReadDataByIdentActuaTestStatu'''.'''Req_ReadDataByIdentActuaTestStatu'''.'''Param_RequeServiId"'' | ||
Revision as of 08:09, 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
|
When validating the values in DiagMetaData element are used only when the access path can not be explicitly determined from the workflow |
|
