Idea Summary
For an Interactive Grid (IG) - Automatic Row Processing (DML) page process, setting the Execution Scope should process every row from the IG.  Currently, it behaves exactly the same as “For Created and Modified Rows”.

Use Case
On our current Inventory project, we have a requirement on a page to let a user perform a “Save As” feature on a parent-child data set on the page.  This pattern occurs multiple times within their app.

For example, they could be looking at an Order with multiple Line Items.  The Order info is displayed in a header region while the Line Items are displayed in an editable IG.  They would like to be able to edit some of the Line Items and then click a “Save As” button which will copy the Order and save the edits *only to the new copy*.  On Save As, the original Order will remain untouched, and all changes will be written to the new Order and its Line Items.  Without the “All Submitted Rows” functionality, we can only process the modified rows - we will lose the unmodified ones.  There are work-arounds for this (like executing some JS to mark all rows as modified) but they are less preferable than something declarative.

Preferred Solution (Optional)
When Execution Scope = “For Created and Modified Rows”, the behavior should remain the same - process only created/modified rows in the IG.

When Execution Scope = “All Submitted Rows”, process every row from the IG.

I believe this is how it worked with Tabular Forms.