Hello pri,

In these multi-window solutions I think the GTRR step works best with opening
a new window. So perhaps your script should be the opposite of what we have
done so far: (in words not steps) find out if the window is Open and if it
is Close it. Then let the GTRR Open the new window for you.

ahh yes, that would seem to do what i asked. thank you.

but it is a bit awkward, any other solutions?

Hello pri,

Actually I think it is easier -no bias here

Your script only needs two steps: Close Window [Name:WindowA] and GTRR. If
the windows isn't open then an error may be generated but you don't need
to know about and there is no error message to disturb the user.

yes you are right about the simpleness in the scripts but the
awkwardness is that lets say the window is created in the top right,
but the user moves it to the bottom left and resizes the window. Now if
the users clicks on the button int he portal a second time the
moved/resized window will close and a new window in the original
location(top right) will open. The new window will not "replace" the
old window that was resized and moved. So for the user there will be a
slight inconvience of resizing and re-moving the window each time the
script is accesed, and obviously the user will see the windows
closing/opening.

that is why, i found it awkward to do. I was expecting a script that
continues to use the same window but changing the related records based
on the row the button was clicked. sorry for being picky. thanks for
the help.