Personas 3.0 Viewport Navigation reset when returning to an initial selection screen

[bradyfrey]

Personas 3.0 SP08
RE-FX BDT Application using Viewports

We are using Viewports to simulate tabs in our BDT applications. The application includes a initial record selection screen, the parent flavor screen, and several viewports. The parent and each of the viewport screens provide a standard SAP cancel button from the original application. Pressing the cancel button allows the user to leave the viewport screen and return to the initial selection screen. The user can then switch record ID's and select to display the new record.

The problem is that the display command returns to the viewport that was previously displayed. We would like the display button to start at the parent flavor screen and not one of the viewports.

We could force the cancel button on the viewports to reset to the flavor parent screen using a viewport.reset statement, but this causes unnecessary overhead when returning to the flavor parent screen prior to reaching the initial selection screen.

Is there a simple way to reset the viewport index without having to actually return to the flavor parent screen?
We would want this to happen everytime we navigate into a flavor from the intitial selection screen.

In this example we are finished with the record while viewing the Assignments Viewport (9004)

We cancel from the Assignments Viewport and reach the Initial Selection Screen to change record IDs.

Selecting the Display or Change button returns the user to the Assignments Viewport (9004).
The desired result would be to return the user to the Basic Data tab (Viewport.Reset()).

[tamas_hoznek]

Actually, if you always want to reset the viewport index when you arrive to the second screen after the selection screen, you could do that in an onLoad script for the second screen. The problem of course is that this only works if you are staying in that one screen while processing the object, so if you navigate to another screen then return to this one, then the viewport would be reset, which may not be what you want.

[bradyfrey]

Tamas,

I was able to assign a script to onClick event of the standard buttons. With this I used the simple statement "session.utils.rest();". I had thought I tested this and it launched the onLoad event of the parent viewport screen. I was able to successfully test that it does not. Thanks for the tip. This should work for us.

Thanks,

Brady

[tamas_hoznek]

Hi Brady,

Is the 'Cancel' button the standard one, which returns to the selection screen?

You say, "We could force the cancel button on the viewports to reset to the flavor parent screen using a viewport.reset statement" - actually, this seems to be the way to go, i.e. replace the standard 'Cancel' button with your own script button, that first resets the viewport and then presses the standard 'Cancel' button.

But "this causes unnecessary overhead when returning to the flavor parent screen prior to reaching the initial selection screen" - what extra overhead would this be?

I'm not sure I fully understand the issue you are describing...