View Events allow you to provide actions to run when certain events occur, such as selecting a row in a table view or saving a form. These actions can replace default navigation behaviors, enabling you to create streamlined custom navigation within your apps. You can learn about different types of actions in the actions section.
Row Selected (Table, Deck, and Gallery Views)
The "Row Selected" Event is triggered when a user taps on an individual record in the Table, Deck or Gallery views. If you specify an Action, it will replace the default behavior of viewing the record details in a detail view (even if the action does not cause its own navigation). Use cases might include navigating directly to the edit form when selecting a row, or quickly changing the value of a status column without the need to open the details view.
Form Saved (Form Views)
The "Form Saved" Event is triggered when a user saves an add or edit form. If an Action is provided that causes navigation, it will replace the default navigation behavior (including Auto-Reopen and Finish View settings). Unlike the Row Selected Event, if a Form Saved Action is provided that doesn't cause navigation (such as an update row Action or a navigation Action whose condition is not met), the default navigation behavior will still occur.
Events can be connected to Actions within the individual view settings of supported view types in the UX / Views section of the editor. For custom behaviors, first create your own Actions in the Behavior / Actions section of the editor. Eligible Actions can then be selected as Event Actions in the view settings. Note that only Actions based on the same source table as the view are eligible to select as Event Actions. System-generated Actions such as "View Map" associated with Address columns or "View Related" associated with Ref columns can also be chosen. The default "auto" option corresponds to the built-in behaviors normally associated with each event.
Additional Notes on View Events
Multiple effects for one Event can be combined by providing a composite Action.
Not all view types currently support Events, but more Event types will likely be added in the future.
To configure Form Saved Events, you may need to create a new form reference view first.
Actions based on different tables than the view will not appear in the dropdown - if you don't see the action Action you want as an option, make sure the data sources match.