Extensions.Job.AddBranchByName

From emotive
Jump to navigation Jump to search

Classification

Name AddBranchByName
Short Description Adds a set of response parameters with short name
Class Action
Extension OTX Job extension
Group Job related actions
Exceptions TypeMismatchException
InvalidParameterizationException
Checker Rules -
Standard Compliant Yes

OTL Syntax

Job.AddBranchByName(ParameterContainerTerm parameterContainer, ParameterContainerTerm content, StringTerm shortName);

Description

The AddBranchByName is used to add a set of response parameters to the response structure according to a multiplexer database definitioxn given by its short name.

Properties

Name Data Type Class Default Cardinality Description
ParameterContainer ParameterContainer Term - [1] The parameters in which new element (s) to be added.
Content ParameterContainer Term - [0..1] The element(s) to be placed in the newly created multiplexer branch.
ShortName String Term - [1] The name of the multiplexer branch to be added.

OTL Examples

/// Local Declarations

DiagCom.ComChannel ComChannel1;
DiagCom.DiagService DiagService1;
DiagCom.Result Result1;
DiagCom.Response Response1;
DiagCom.Parameter Parameter1;

/// Flow

ComChannel1 = DiagCom.GetComChannel("LL_GatewUDS", "EV_GatewLear_006", false);
DiagService1 = DiagCom.CreateDiagServiceByName(ComChannel1, "DiagnServi_ReadDataByIdentECUIdent");
[#MetaData(RequestPdu), <#Data>22 04 07</#Data>]
DiagCom.ExecuteDiagService(DiagService1, {Param_RecorDataIdent = "VW Logical Software Block Counter Of Programming Attempts"}, {}, Result1, NULL, false, false);
Response1 = DiagCom.GetFirstResponse(Result1);
Parameter1 = DiagCom.GetParameterByPath(Response1, {"Param_DataRecor"});
Job.AddBranchByName(Response1, Parameter1, "Read Data By Identifier / Actuator Test Status");

See also

SendFinalResult
SendIntermediateResult
SetJobInfo
SetProgressInfo
AddElement
AddBranchByIndex
AddBranchByValue
AddEnvDataByDtc
GetComChannel
CreateDiagServiceByName
ExecuteDiagService
GetFirstResponse
GetRequest