So my understanding of this is that there is a request for publically exposing an API that would allow the current page flow stack to be blown away so that the next request would generate new instances of the top most page flow and all nesting would be lost.
On 1/12/06, Carlin Rogers <[EMAIL PROTECTED]> wrote: > > Hey Rich, > > Is there a good mechanism for resetting a page flow instance when the page > flow is down in a nested page flow? I.E. a way to get back to the begin > action of the main page flow. Here's the scenario... > > In a portal there may be some state associated to a page flow that they > would manage as well as what we have stuck in the session. When they > reset > state, they'd like to end up back at the begin action of the page flow. > This > works for a non-nested page flow. > > However, for nested flows, I think that with the page flow instance > keeping > a reference to the "current" page flow, in this case the nested flow, and > they try to reset state on the request, they get the begin page of the > nested flow instead of the original page flow begin. > > Do we have something in our API to "reset" a page flow instance itself or > even just blow away the instance that gets stored in the > session? Something > to call so there's no stale state. If not, do you have a suggestion as to > what might be implemented? > > Thanks, > Carlin > >
