for a
> > web application. The problem i am facing is both the boundaries
for
> > different parameters is the same.
> >
> > There is some hidden values generated by the system but they are
> > using the same hidden name. Following is the syntax:
> >
> > \r\n"
> > \r\n"
> >
> > As you can see both left boundaries and right are the same. So
how do
> > i do this. Even if i use different variable name it will still
goes
> > to 18822. How can i do this???
> >
> > Thank you for you clarification
> >
Ans :
The solution of your problem is explained below:
>
> You need to do manual correlation. For that:
>
> 1. Record the script again.
> 2. Go to Runtime Settings --->Log-->Check the enable logging-->
Select
> Extended log and select all the option under Extended Log.
> 3. Run the script once. (Even if script is giving errors)
>
> You know the values, which you want to correlate. In your case the
> values are:
>
> \r\n"
> \r\n"
>
> For first value
> 1. Copy the LB as much as you can.
> 2. Find that LB in Generation Log. If you do not find LB in
generation
> log, just reduce the character length of LB and again try to find.
> 3. Once you get the 1st occurrence of LB, look at the dynamic value
> (i.e. 18822). If it is not there than again try to find LB for that
> dynamic value. Say, you find that dynamic value after three
occurrence
> of LB than value for ORD will be 3 (This is the most important step
to
> find the value of ORD).
>
> Now, you have value for ORD and you need to put the
web_reg_save_ param
> function on its right place in the script. For that, find the same
LB
> in replay log. In third occurrence of the same LB in replay log,
look
> at the number written in the beginning of that line like Action.c
> (
> That number is the line number in the script where you need to put
> web_reg_save_ parm function.
>
> Go to that line and write following code:
>
> web_reg_save_ parm("
> "LB=
> "RB=
> "ORD=3",
> LAST);
>
> Replace all the occurrence of 18822 with {
>
> Repeat all the steps for other values.
>
> It may resolve your problem.
No comments:
Post a Comment