Hi Nitish,
here some thoughts:
- don't call it form builder package since "form builder" is used to describe the part in the templating system that creates forms for OpenACS
- your whole idea sounds like a little workflow. you can check bug-tracker on how workflow might be useful, though there is no support for field specific permissions but workflow does all the magic of notifications, opening/closing/commenting/...
The only problem with bug-tracker is, that once a ticket is defined (the fields of an object) it cannot be extended. So right now you would have to created several instances for each form (book suggestion, purchase order...).
- see also package assessement/tcl/as-action-proc.tcl for how they extended assessment to allow the definition of actions that take place when an activity has taken place. By the way, assessment is the successor of survey.
Greetings,
Nima
