Hi all,
I want to do a struts based workflow. I need that the information
captured through the steps of this workflow persist in someway that if
the user close the browser next time the user login the info previously
capturated shows up in the same step in which the user left the app before.
Understanding that different companies interpret them in different ways, I
have always thought of webflow and workflow in the following terms:
webflow - the path by which a user travels through a WEB application to
complete a unit of work. An example would be a series of screens used by a
I've worked with similar requirements for a project some times ago. it was
a questionnaire (very long) and the user have the possibility to stop and
resume even in different sessions...
My solution was persistence; I saved data in a file (xml format) to
achieve this goal (a database can do the
Ah, now I see. What you're looking for is a way to persist incomplete
webflows. Well, in a *typical* webflow, you have 1 screen per table, where
each screen is a new record/relationship. Each subsequent screen might use
the previous screen's primary key (or composite, if necessary for the
Thanks for your quick responses.
I agree with you Monkeyden, there are differences between two
definitions webflow and workflow, I'm planing to code a webflow.
Monkeyden your aproach is very close to what I need but... certainly I
need to use save points, but if I use them between tables
As I mentioned, many webflows have a series of screens, each of which builds
on the preceding screens. The example I gave showed that the first couple
screens would select an employee id and department id. This might be a good
save point in the webflow because a relationship was made (EMP -
6 matches
Mail list logo
