How does the request data get mapped into the response?

Document ID : KB000091948
Last Modified Date : 18/04/2018
Show Technical Document Details
Introduction:
When creating a virtual service from request/response pairs, how does the request get mapped into the response? What are the rules for deciding which fields get mapped in the response? 
 
Question:
How does the request data get mapped into the response?When creating the virtual service from request/response pairs, how does the request get mapped into the response? What are the rules in deciding which fields get mapped in the response? Example: e022 OR {{=request_Section_N276WK_TAX_CD_SRVC_COMMUN_N276WK_TAX_CD_SRVC_INFO_N276WK_REC_ID_N276WK_IDENT_KEY_N276WK_QCN_TCN_N276WK_SEQ;/*002*/}}
Environment:
All supported DevTest environments
Answer:
Request data is mapped to the response as below:
. When the request and response have same data values and the minimum length is 3 then the response data is automatically magic stringed. If the response has same data values multiple times then the response uses the first request argument.
. To change the length requirements for magic string the values "lisa.magic.string.min.length" property can be used to set the desired length in local.properties.
Additional Information:
https://docops.ca.com/devtest-solutions/10-1/en/reference/property-descriptions/devtest-property-file-lisa-properties#DevTestPropertyFile(lisa.properties)-lvseProperties