I'm still fairly new to Nintex. This article was immensely helpful: https://community.nintex.com/docs/DOC-1035
I know that there are SharePoint batches and Nintex batches. I know it is advised that you use the "Commit pending changes" action after updating an item. I also know that changing states in a State Machine "saves" your progress. Are there any other actions or processes that will "save" your progress? I'm not sure if I'm wording this correctly.
I want to build a lean workflow that isn't clogged with unnecessary "Commit pending changes" actions if there are other actions or processes I'm using that will do the same thing. For example, changing states after an item is updated. I don't need to use the "Commit pending changes" action after an "Update item" action if the very next thing my workflow does is change states.
I have been looking for some sort of tutorial or cheat sheet, but I haven't found anything yet. Can anyone point me in the right direction?
Solved! Go to Solution.