Form control

Always used with forms. Goerp application handles all pages with one dynamic handler and pages may have multiple forms. When the page is processed by the handler, then all forms and related input models are involved. We need to know the exact model to be sure that after submitting the form POST request, the right model gets processed. This model name should be passed with the postActionEntity input name.

All form control fields:

• postAction - what action should be applied to the entity, currently there is only one option - delete, if passed then form control should also have postActionIds input included. If postAction is not specified, then by default applied save/update action.
• postActionIds - entity ID’s separated by comma (,). Those are input parameters for performing changes under specific entities (in most cases deleting them)
• postActionEntity - defines the model name which is related to the form. Needed only for the save, update and delete options (not needed in query type forms). Supports multiple entities, each of them should be defined in separate input with the same name, check Multi-entity form topic in this section.
• postActionRedirect - defines the link where to redirect after successful post action (not applied to delete action and to forms with GET method)

• Simple actions with form
• Multi-entity form
• Bulk-entity form
  • Sales document sample