batch transactions

if i have several "change object" activities within a microflow, but i do not want to commit any changes until the last stop in the microflow (as one commit action), would i need to use the community commons module to leverage a batch transaction?
1 answers

You only need batch operations when performance is the issue (when you are committing such a large number of objects that the entire microflow takes minutes/hours to complete).

If your concern is that all the objects or none at all should be committed to the database, this is already automatically handled by Mendix: all the actions in a microflow are part of the same transaction that is only committed if the entire microflow completes successfully, otherwise everything is rolled back. (Note that this is the default behaviour, but this can be overriden by using "set error handling" on parts of your microflow.)