Within Deck Views, app creators have the option to select a layer of data to display as a secondary view. This 'nested view' provides a way to visualize lists of related data created by building references between tables.
The nested views can be other tables, decks, galleries or charts - for example, a quick snapshot of the live product inventory for each company displayed in a deck view:
(This Inventory Management Sample App can be viewed & copied here)
To enable a nested view, app creators can simply look for the 'Nested Table Column' field within the deck view to choose a 'related' list of items. Customize the UX of that related list by finding the corresponding 'inline' ref view that was automatically created when the relationship was created.
'Reset on Edit' is a column setting that automatically clears the value of a particular field, any time that record is edited by a user, reducing the need to build separate workflows designed to change values.
For example, a table in an app may contain 'Last Edited By' and 'Last Edited Date' columns, designed to track who was the last person to edit and when the edit occurred. In order to force those fields to be updated each time the record is updated, simply enable 'Reset on Edit' in each column definition. As an extra layer of automation, set the initial values of each column to 'USEREMAIL()' and 'TODAY()' in order to automatically pref-ill those fields with the user login email and today's date.
Requiring recent comments from the app user is another useful scenario for 'Resent on Edit' - by making the column 'required' and also enabling 'Reset on Edit', the comments field will require an update from the user explaining the reason for a change.