Multiple choice technology packaged enterprise solutions

Application Engine does not commit a step containing a Do Select action with the Select/Fetch option enabled until the entire step completes successfully, regardless of the other options you have selected.

  1. True

  2. False
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

When a Do Select action uses the Select/Fetch option, Application Engine defers all commits until the entire step completes successfully. This is because Select/Fetch opens a cursor and processes rows sequentially - committing mid-stream would close the cursor and break the iteration. Other commit options on the step are ignored until the Do Select finishes all rows. This ensures data consistency throughout the fetch loop.

AI explanation

When a Do Select action has the Select/Fetch option enabled, Application Engine holds off committing any database changes for that step until every row fetched has been processed and the step finishes without error. This ensures the whole result set is handled as one all-or-nothing unit of work, so a failure partway through doesn't leave the database in a partially-updated state — regardless of other commit-related settings on the step.

Keep practicing — related questions