create OUT: otx, diag: otxDiagCom from IN: transformate;

lazy rule Asam3dResponse2ResponseParameters {
    from
    	source: transformate!Asam3dResponse
    to
        -- This target element from DiagCom is not put anywhere in the current rule,
        -- which makes it reside in the DiagCom output file eventually.
        -- There is nothing I can do about that, although I need it in the OTX file
        -- and it should be put there by the next rule 'Asam3dCallServiceTactic2Action'.
    	otxResponseParameters: otxDiagCom!ResponseParameters(
    		name <- otxStringTerm
    	),
    	otxStringTerm: otx!StringLiteral(
    		value <- source.name
    	)
}

lazy rule Asam3dCallServiceTactic2Action {
    from
    	source: transformate!Asam3dCallServiceTactic,
    to
    	otxAction: otx!Action(
    		id <- thisModule -> getId(),
    		realisation <- otxExecuteDiagService
        ),
        -- This output element eventually resides in the OTX output file,
        -- although it is from the DiagCom model. This is how I need it!
        -- I guess it works because it is put into an OTX element right above,
        -- i.e. in the very rule where it is created.
	otxExecuteDiagService: otxDiagCom!ExecuteDiagService(
		diagService <- otxDiagServiceValue,
        -- The DiagCom target element 'otxResponseParameters' from the above rule
        -- 'Asam3dResponse2ResponseParameters' should be put in the current
        -- output element 'otxExecuteDiagService' here, but, as written above,
        -- goes to the DiagCom output file.
		responseParameters <- source.service.responses
			-> collect(response | thisModule -> 
                           Asam3dResponse2ResponseParameters(response))
	),
	otxDiagServiceValue: otxDiagCom!DiagServiceValue(
	        valueOf <- source.service.name
	)
}