post timestamp in web_submit_data itemdata in loadrunner

Question

In our hyperion application, we have a explore button. Here is its post:

web_submit_data("explorer", //FIXME: id vlaue parameter
    "Action=https://{host_url}/raframework/browse/explorer", 
    "Method=POST", 
    "TargetFrame=", 
    "RecContentType=application/x-json", 
    "Referer=https://{host_url}/workspace/index.jsp?framed=true", 
    "Snapshot=t19.inf", 
    "Mode=HTML",
    ITEMDATA, 
    "Name=class", "Value=com.hyperion.tools.cds.explorer.ExplorerView", ENDITEM, 
    "Name=id", "Value=EV1390418511260", ENDITEM, //"Name=id", "Value=EV1389926310921", ENDITEM, 

    LAST);

This EV1390418511260 is from

this._rstExplorerViewId = "EV" + (new Date()).getTime(); 

from the loaded module.js file I guess, which is Unix time stamp

I tried lr_save_timestamp("timestamp", LAST ); to correlate value of id with Unix time stamp. like Value=EV{timestamp}. The request is being posted but the response body has

Content-Length: 0 
X-ORACLE-BPMUI-CSRF: false

I want to try

typedef long time_t;
time_t t;

and correlate something like Value=EV{time(&t)} but here it converts to url encode and takes ascii values of those special chars.

What should I do?

Answer 1

Why are you using C code to replace the functionality of built in capability to LoadRunner?

See web_save_timestamp_param() for the number of milliseconds since Jan 1, 1970.

web_save_timestamp_param("tStamp", LAST );

web_submit_data("explorer", 
...
ITEMDATA, 
"Name=class", "Value=com.hyperion.tools.cds.explorer.ExplorerView", ENDITEM, 
"Name=id", "Value=EV{tStamp}", ENDITEM, 
LAST);

if this is your first trip into the Hyperion universe I would heartily suggest you find the most experienced LoadRunner professional available anywhere in the nation to support your efforts. You do not need to be struggling with tool use while at the same time working in one of the more difficult environments for any performance testing tool. Assuming you get someone who has been succesful with Hyperion recently, no matter what your organization spends (even as high as $300 per hour or more) it will be money well spent versus struggling with both tool mechanics and testing of the environment