Difference between revisions of "OtfOdxAccessPath"
| Line 5: | Line 5: | ||
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"'' | ||
| − | 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 [[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== | ==Validation== | ||
{| | {| | ||
| style="vertical-align:top; text-align:justify;"| | | style="vertical-align:top; text-align:justify;"| | ||
| − | Both determined and set access path will be validated in OTF. There 3 [[ | + | 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_Chk100''' (warning): The access path can not be determined unambiguously. For example: the ODX database is not set yet. | ||
Revision as of 04:00, 17 February 2016
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:
When validating 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 property, user just has to choose the right value instead of seeking and entering it himself. |
|
