Provide new Parent/Child Form input Type - Pick list with automatic row insertion

[WillowMobileSys]

Imagine for a moment an app, where several Child items, 20 or more, need to be inserted.  Maybe they are questions for a template in a Survey app.  Or Products to be ordered from a Supply Vendor.  Adding 20 or more items, one by one, in the current Inline Table form is extremely tedious.  A user must click the Add/New button on the Parent Form to open the Child Form, insert details, click Save to return to Parent Form and then repeat this process for each Child. 

In many cases, these Child rows require only a single item chosen and the other details can be automatically populated.  So this input pattern has been avoided for many apps.

There has been an emerging pattern over the past couple of years to replace the usual Parent/Child input pattern using an Inline table.  This new pattern uses a dedicated EnumList column as a pick list and then a series of actions are attached to the Form Save Behavior that will create the new rows in the Child table.  The whole intent is to provide a better user experience.  

Another variation of this EnumList pattern is to create skeletal child rows again leveraging the Form Save Behavior - e.g. assign Product only.  The time the last action in the group of the Form Save Behavior navigates to a Child table view in QuickEdit so that the rows can all be edited simultaneously.

Proposal...

Because the EnumList column is created solely for facilitating this new Parent/Child input pattern AND the pattern of actions to create the Child rows is always the same,  I propose to wrap this new frequently used input approach into a new Parent/Child input feature. 

It seems to activate this new feature, the parent column of the Child table, where the "Is part of" flag is set, would be the appropriate place to specify the properties for the behavior.  The picklist column would need to be identified and a place to specify assignment of any other child columns would be needed.

Ideally, this new feature would also allow for launching into a table in QuickEdit for efficient editing of the newly created child rows.  However, there is a gap in QuickEdit where we cannot specify additional actions on Table Save.  That would need addressed as well to reach full potential of this new capability

Prior Feature Idea for Table QuickEdit Save:

https://www.googlecloudcommunity.com/gc/Feature-Ideas/New-Event-Action-for-Tables-QuickEdit-Save/idi...