Form rules: Difference between revisions
Removed redirect to Form#Form rules Tag: Removed redirect |
Marek Rodak (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Rules TOC}} {{WIP}} | {{Rules TOC}} {{WIP}} | ||
Form is a screen in the application that contains numerous fields which either hold or await the data. It is a tool that enables system administrators to represent the database data and collect user data in a user-friendly way. Default behavior of an entity form can be changed using form rules, which control form events and provide actions that can take place if one of the events occurs. | |||
==Lifecycle of Entity Form & Entity Form events== | |||
Default behavior of an entity form can be changed using form rules, which control form events and provide actions that can take place if one of the events occurs. Form event is an action of a user or code, which invokes response action from the entity form. The main three events are: | |||
*[[On Load]]: Occurs before the form is displayed on the screen. It occurs immediately after the user chooses to open an entity record from the List view screen. On Load rule connected to a Load event is activated on Load itself. | |||
*[[On Change]]: Occurs after the form has been displayed on the screen and any change on it is recognized. OnChange rule connected to a Change event is activated on Change and Load events as well. | |||
*[[On Save]]: Occurs after the form has been displayed on the screen, user hits the save button and the form is trying to get closed (off the screen). OnSave rule connected to a Save event is activated on Save itself. | |||
[https://www.resco.net/blog/entity-form-its-lifecycle-events-and-best-practices-for-form-rules-with-practical-examples/ blog] | [https://www.resco.net/blog/entity-form-its-lifecycle-events-and-best-practices-for-form-rules-with-practical-examples/ blog] | ||
Revision as of 10:56, 25 November 2022
| Rules and examples |
|---|
|
| Warning | Work in progress! We are in the process of updating the information on this page. Subject to change. |
Form is a screen in the application that contains numerous fields which either hold or await the data. It is a tool that enables system administrators to represent the database data and collect user data in a user-friendly way. Default behavior of an entity form can be changed using form rules, which control form events and provide actions that can take place if one of the events occurs.
Lifecycle of Entity Form & Entity Form events
Default behavior of an entity form can be changed using form rules, which control form events and provide actions that can take place if one of the events occurs. Form event is an action of a user or code, which invokes response action from the entity form. The main three events are:
- On Load: Occurs before the form is displayed on the screen. It occurs immediately after the user chooses to open an entity record from the List view screen. On Load rule connected to a Load event is activated on Load itself.
- On Change: Occurs after the form has been displayed on the screen and any change on it is recognized. OnChange rule connected to a Change event is activated on Change and Load events as well.
- On Save: Occurs after the form has been displayed on the screen, user hits the save button and the form is trying to get closed (off the screen). OnSave rule connected to a Save event is activated on Save itself.