This funciton wraps the form manager processing. Ifprocessing is successful, (that is, only 'save'). If editing was successful, the form is frozen in case you want to display it again (usually you want to redirect to the view target).

There are several possible return values:

• save and the variants next and previous (for wizard usage) suggest successful form processing. The form has already been validated, synchronized with and saved to the data source.
• cancel the user cancelled the form processing, no I/O has been done.
• edit, previous, next indicates that the form is not yet successfully completed. This can mean many things, including validation errors, which the renderer already outlines in the Form output. No I/O processing has been done.

The form will be automatically validated for 'save' and 'next', but not for 'previous'. If you want to have save the data for example even during 'next', you need to call datamanager->save after this function returned the according return code.

Normally, all validation should be done during the Form processing, but sometimes this is not possible. These are the cases where type validation rules fail instead of form validation ones. At this time, the integration of type validation is rudimentary and will transparently return edit instead of validation.

• return: One of 'save', 'cancel', 'next', 'previous', 'edit', depending on the schema configuration.
• todo: Integrate type validation checks cleanly.

---

midcom_helper_datamanager2_controller::process_form()

This function should process the form data sent to the server. Its behavoir is dependant on the controller used, see the individual class documentations for details.