What would your model look like in this situation?

What would your model look like in this situation?

Old forum URL: forums.lhotka.net/forums/t/4800.aspx


dmo145 posted on Monday, May 05, 2008

Hi All,

Sorry for the general subject, couldn't think of a good way to sum this up. I've found semi similar posts but nothing quite like this and I'm stuck. Can anyone advise me on a good way to handle the following situation?

A user can use my app to create, save, and delete a Form/Application. This Form is essentially owned by the user so it has a fairly limited set of savability rules. They can work on it, save it, and finish it later if they wish. At some pt the user will decide they've filled out the Form sufficiently and "submit" it to the app, giving up ownership. When they do this I need to check they're submission against a much more rigorous set of rules and change the state of the "owned" Form to indicate it can't be edited anymore. If their Form can't be submitted, they need to be informed as to why and retain the ability to edit their Form until its complete.

So far I've figured there's definitly a requirement for at least 2 separate BO's. One for the user controlled Form and one for the Submission each with thier own vali/auth rules. But before I got much further it be great to hear some ideas.

What would your model/collaborations look like?

Seems like this must have come up before and given that this forum has so many experienced professionals I figured I'd ask before reinventing/rebreaking any wheels.

Thanks tons for any help!

Copyright (c) Marimer LLC