I have widget within an inline frame. On the click event of that widget I set a global variable and then open a new page within the same inline frame (i.e. open newpage in Current Window). When attempting to access the global variable value in the OnPageLoad event of the newpage, it appears the global variable is not set. Any workarounds?
Would you mind uploading the prototype? I don’t have too much experience with inline frames but know that cross site requests (which are inherent in inline frames) can be tricky
There is a bit more to it than I originally posted after doing a some more testing. This may or may not be a bug.
Essentially when opening a new page in the current frame is executed on a page constructed by formula, the global variable does not seem to be passed (pages 1 & 2).
However, when opening a new page in the current frame is executed on a page constructed by calling out the page by name, the global variable value DOES seem to be passed just fine (pages 4 & 5).
I’m not sure it this is the cause, but I noticed your On Click behaviors for the rectangles are different between Page 2 and Page 4 for the Open event.
Page 2= Open [[item.page]] in Current Window
Page 4 = Open Pge 5 in Current Window
HI tallgal - that’s actually the point. When the Open command is used on an explicitly defined page (pages 4 & 5) the passing of the global variable works fine. Yet, when the page to be opened is defined by a formula (drawing the page text from a repeater)(pages 1 & 2), the global variable is not passed. Not sure why the behavior would be different.
It looks like you’re running into a bug where changes to global variables have trouble passing through inline frames. Our QA team currently has this issue on file, so I’ll go ahead and add the details you’ve included here to the bug report–hopefully we’ll be able to see a fix for this in a later release.
In the meantime, we have seen that adding a short wait action (using the “Wait” action in the Case Editor) before the variable change in the “OnPageLoad” event of the inline frame’s page allows the new variable value to be read correctly. This might help as a potential workaround as we investigate this issue.