cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Not applicable

'Commit Pending' action after every update action Or before a dependent read?

Jump to solution

I've seen workflows having a 'Commit Pending' action after every update action. Is that required even if there is not a dependent read action following? What is the best practice - 'Commit Pending' action after every update action Or After an Update action only if it's followed by a dependent read?

TIA!

Labels: (1)
Reply
3 Replies
Highlighted
Automation Master
Automation Master

Re: 'Commit Pending' action after every update action Or before a dependent read?

Jump to solution

The "Commit pending changes" action has to be added only if you need the changes you've done in your workflow to be effective because of the following action. Without "Commit pending" action, the workflow execute the changes you've configured in your workflow when there is a pause, a task or when the workflow ends.

The following article is very interesting :

Designing your Workflow - Commit Pending Changes Action NW2010 & NW2013

This video too :

Video: Batched Actions and Committing Changes in Nintex Workflow

Hope this helps

View solution in original post

Reply
Highlighted
Not applicable

Re: 'Commit Pending' action after every update action Or before a dependent read?

Jump to solution

Thanks Caroline!

0 Kudos
Reply
Highlighted
Automation Master
Automation Master

Re: 'Commit Pending' action after every update action Or before a dependent read?

Jump to solution

No problem

0 Kudos
Reply