[Opensource] proper way to accept data entry across multiple pages into one DBObject?

[Eddie Lewis]

Mike
 
We had to head down the path of storing the dbobject as a
persistentAttribute in the session and then populate the dbobject in each
state. The validation had to be customised to only check the fields from the
current page so some customisation had to be performed for the validation. I
can send through some more info on how we do this, however, this can become
a little confusing as we have built up this code over many months. Maybe the
workflow techniques incorporated in the latest expresso release can help. If
not email me - elewis at copyright.com.au <mailto:elewis at copyright.com.au>  and
i can send through some code to get you going.

-----Original Message-----
From: Mike Traum [mailto:mtraum at cirnetwork.org]
Sent: Thursday, 24 October 2002 3:14 AM
To: Expresso Mailing List (E-mail)
Subject: [Opensource] proper way to accept data entry across multiple pages
into one DBObject?


I haven't quite figured out a good way to take in data across multiple pages
into one DBObject.
 
Right now, I do data collection on a single page by generating inputs based
on all of the fields in the DBObject and looping through those to fill the
DBObject using the DBObject validation to check the fields. If I have
multiple pages for one DBObject, then DBObject validation does not work
because the not null fields which are entered on later pages won't pass the
validation.
 
Is there a better way to do this than designing a custom validation class?
 
And, this also brings up temporary storage of the data (storing the DBObject
data before the user gets through all of the screens). Should I be putting
the DBObject into the session?
 
Thanks,
Mike
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.jcorporate.com/pipermail/opensource/attachments/20021024/90fe839c/attachment-0002.htm