It's possible we're talking about two different things. Something that
comes up a lot is the idea of a frame of reference longer than a request
but shorter than a session, since there are many tasks which cannot be
resolved in a single request, and are also interdependant.
* Form Wizards
* "Are you sure?" confirmations
* Logging-in from a page and returning to that page
* Starting to add a record, going off and looking up a related record,
and being automatically returned to the add-form when the related record
is selected. (Disconnected picklist.)
I was thinking this part was covered by the "(including flow control and
iteration support)" part, but maybe you are thinking of something else.
Of course, an event queue (or stack) may also help with this.
Craig Tataryn wrote:
> Ted, as for "enforcing" the workflow, I hadn't even considered it. The goal of
> the TODO is just to make a graphical tool that allows you to define a workflow
> and automate the process of setting up your config files to support the
> workflow. Atleast that's how I read it.
>
> <tataryn:craig/>
