igor2000

Проблемы возникли на 2 итерации. Не нужно удалять, нужно коррелировать вручную

Все заработало. Нужно просто коррелировать вручную rowid

 

Возможно нашел в чем проблема, но не знаю как ее решить 

 

"Name=SWERowIds", "Value=SWERowId0={CorrelationParameter_1}, SWERowId1={CorrelationParameter_2}", ENDITEM,

 

кусочек скрипта:

web_submit_data("start.swe_62",
		"Action=https://{my_ip}/oa/start.swe",
		"Method=POST",
		"TargetFrame=",
		"RecContentType=text/html",
		"Referer=",
		"Snapshot=t64.inf",
		"Mode=HTML",
		ITEMDATA,
		"Name=SWER", "Value=65535", ENDITEM,
		"Name=SWEVI", "Value=", ENDITEM,
		"Name=SWERowId", "Value=", ENDITEM,
		"Name=SWEMethod", "Value=NewRecord", ENDITEM,
		"Name=SWEC", "Value={Siebel_SWECount}", ENDITEM,
		"Name=SWEReqRowId", "Value=0", ENDITEM,
		"Name=SWERPC", "Value=1", ENDITEM,
		"Name=SWENeedContext", "Value=true", ENDITEM,
		"Name=SWEApplet", "Value=ATC Address List Applet Potreb Cash", ENDITEM,
		"Name=SWEActiveApplet", "Value=ATC Address List Applet Potreb Cash", ENDITEM,
		"Name=SWEView", "Value=ATC Opty Cash Contact Info 2 View", ENDITEM,
		"Name=SWEField", "Value=s_5_1_0_0", ENDITEM,
		"Name=SWECmd", "Value=InvokeMethod", ENDITEM,
		"Name=SWESP", "Value=false", ENDITEM,
		"Name=SWEBID", "Value=-1", ENDITEM,
		"Name=SWETS", "Value={SiebelTimeStamp}", ENDITEM,
		"Name=SWEActiveView", "Value=ATC Opty Cash Contact Info 2 View", ENDITEM,
		"Name=SWEDIC", "Value=false", ENDITEM,
		"Name=SWEP", "Value=", ENDITEM,
		"Name=SWERowIds", "Value=SWERowId0={CorrelationParameter_1}, SWERowId1={CorrelationParameter_2}", ENDITEM,
		LAST);

Судя по логам при воспроизведении vugen посылает это:

 

 

SWERowIds=SWERowId0%3D%7BCorrelationParameter_1%7D%2CSWERowId1%3D%7BCorrelationParameter_2%7D

 

т.е. в запросе не rowid а просто текст CorrelationParameter_1 и CorrelationParameter_2. 

 

При записи было так: 

 

SWERowIds=SWERowId0%3d3-2L7IR7R%2cSWERo"

"wId1%3d3-2L7IR7A"

Вопрос: Как их разделить чтобы vugen посылал правильные rowid's?

 

Нашел решение на http://i1.blogs.msdn...ual-studio.aspx

Советуют ·

 Root cause:

• SWERowId & SWERowIds values not correctly correlated.
• Based on many references we did correlate this value through manual correlation and also by using a custom extraction rule However, we still were not able to see the records being created even after correlation and were still getting some error related to end of file error.

How to fix:

• Delete both SWERowId & SWERowIds data valued from requests.
• This value appears in many requests and it’s recommended to clear the value by going to each request.

После удаления rowid все работает. 

Будут ли из-за удаления проблемы в дальнейшем?

Возможно нашел в чем проблема, но не знаю как ее решить 

"Name=SWERowIds", "Value=SWERowId0={CorrelationParameter_1}, SWERowId1={CorrelationParameter_2}", ENDITEM,

кусочек скрипта:

web_submit_data("start.swe_62",
		"Action=https://{my_ip}/oa/start.swe",
		"Method=POST",
		"TargetFrame=",
		"RecContentType=text/html",
		"Referer=",
		"Snapshot=t64.inf",
		"Mode=HTML",
		ITEMDATA,
		"Name=SWER", "Value=65535", ENDITEM,
		"Name=SWEVI", "Value=", ENDITEM,
		"Name=SWERowId", "Value=", ENDITEM,
		"Name=SWEMethod", "Value=NewRecord", ENDITEM,
		"Name=SWEC", "Value={Siebel_SWECount}", ENDITEM,
		"Name=SWEReqRowId", "Value=0", ENDITEM,
		"Name=SWERPC", "Value=1", ENDITEM,
		"Name=SWENeedContext", "Value=true", ENDITEM,
		"Name=SWEApplet", "Value=ATC Address List Applet Potreb Cash", ENDITEM,
		"Name=SWEActiveApplet", "Value=ATC Address List Applet Potreb Cash", ENDITEM,
		"Name=SWEView", "Value=ATC Opty Cash Contact Info 2 View", ENDITEM,
		"Name=SWEField", "Value=s_5_1_0_0", ENDITEM,
		"Name=SWECmd", "Value=InvokeMethod", ENDITEM,
		"Name=SWESP", "Value=false", ENDITEM,
		"Name=SWEBID", "Value=-1", ENDITEM,
		"Name=SWETS", "Value={SiebelTimeStamp}", ENDITEM,
		"Name=SWEActiveView", "Value=ATC Opty Cash Contact Info 2 View", ENDITEM,
		"Name=SWEDIC", "Value=false", ENDITEM,
		"Name=SWEP", "Value=", ENDITEM,
		"Name=SWERowIds", "Value=SWERowId0={CorrelationParameter_1}, SWERowId1={CorrelationParameter_2}", ENDITEM,
		LAST);

Судя по логам при воспроизведении vugen посылает это:

Mesto_Jizni_Rabota.c(152): Error -26372: ContentCheck Rule "Status_Error1" in Application "Siebel" triggered. Text "`Status`Error`" matched (count=1)  	[MsgId: MERR-26372]
Mesto_Jizni_Rabota.c(152): Error -26377: No match found for the requested parameter "Siebel_Star_Array_Op59". Check whether the requested boundaries exist in the response data. Also, if the data you want to save exceeds 1024 bytes, use web_set_max_html_param_len to increase the parameter size  	[MsgId: MERR-26377]
Mesto_Jizni_Rabota.c(152): Notify: Saving Parameter "Siebel_Star_Array_Op59 = ".
Mesto_Jizni_Rabota.c(152): Error -26377: No match found for the requested parameter "Siebel_Star_Array_Op58". Check whether the requested boundaries exist in the response data. Also, if the data you want to save exceeds 1024 bytes, use web_set_max_html_param_len to increase the parameter size  	[MsgId: MERR-26377]
Mesto_Jizni_Rabota.c(152): Notify: Saving Parameter "Siebel_Star_Array_Op58 = ".
Mesto_Jizni_Rabota.c(152): Error -26377: No match found for the requested parameter "Siebel_Star_Array_Op60". Check whether the requested boundaries exist in the response data. Also, if the data you want to save exceeds 1024 bytes, use web_set_max_html_param_len to increase the parameter size  	[MsgId: MERR-26377]
Mesto_Jizni_Rabota.c(152): Notify: Saving Parameter "Siebel_Star_Array_Op60 = ".
Mesto_Jizni_Rabota.c(152): web_submit_data("start.swe_35") highest severity level was "ERROR", 2929 body bytes, 260 header bytes  	[MsgId: MMSG-26388]
Ending action Mesto_Jizni_Rabota. 

Вот такой ответ от сервера вызвал первую ошибку: @0`0`3`3``0`UC`1`Status`Error`SWEC`39`0`1`Errors`0`2`0`Level0`0`

На что смотреть, чтобы починить?

Из Доки: 

An error message relating to Back or Refresh typically has the following text:

We are unable to process your request. This is most likely because you used the browser back or refresh button to get to this point.

Cause: The possible causes of this problem may be:

Но как это починить не понятно.