You could put this in your action, since it's more about workflow than
domain object.
In your action, you'll use $this-redirect or forward methods to
redirect/forward user to the ethernet module's newForPc action, passing to
it needed parameters (pc id). newForPc will create a new EthForm, set its
Hi,
My data model has a Pc table with a 1-n relation with an Eth table.
I'd like to configure the backend forms in order to :
1 - Show 'New Pc form' with button 'save and add interface'
2 - When pc is saved (processForm), Pcs new id is put in session
3 - Then, the form for creating a new
Wouldn't it be a lot better if you pass the pc_id to the new form like this
(in the controller):
$eth = new Eth()
$eth-pc_id = sfUser::getAttribute('pc');
$ethForm = new EthForm($eth);
There should be a loose coupling between classes. This way it's a lot
cleaner.
As for the pc id storing in
