Difference between revisions of "NF8.2 Suspend workflow until commit"
(Created page with "= '''Feature:''' Suspend workflow until commit = '''Goal:''' Functional '''Developer:''' Martin Schönbeck '''Feature Ticket:''' [https://idempiere.atlas...") |
CarlosRuiz (talk | contribs) m |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
'''Description:''' | '''Description:''' | ||
| − | This feature allows to suspend a workflow upto the actual transaction is committed. It does not initiate a commit itself. Effectively it works like the normal wait with a time greater than 0 where the workflow processor restarts the workflow later, but here the workflow is restarted immediately after commit. | + | This feature allows to suspend a workflow upto the actual transaction is committed. It does not initiate a commit itself. Effectively it works like the normal wait with a time greater than 0 where the workflow processor restarts the workflow later, but here the workflow is restarted immediately after commit. It is activated by using a value of -1 in the wait action. This also ensures the workflow will be restarted by the workflow processor if it by any reason couldn't be continued after the commit. |
| − | [[image: | + | This is especially useful before a jasperreport is to be started by a workflow to ensure it sees all changes done. Or if you want to send an e-mail you'll probably make sure the e-mail doesn't tell anything which may be rolled back due to later errors. |
| + | |||
| + | [[image:WorkflowWaitCommit.png]] | ||
[[Category:New Features|U]] | [[Category:New Features|U]] | ||
| − | [[Category:New Features v8. | + | [[Category:New Features v8.2|U]] |
[[Category:New Features Functional]] | [[Category:New Features Functional]] | ||
Latest revision as of 16:17, 8 January 2021
Feature: Suspend workflow until commit
Goal: Functional
Developer: Martin Schönbeck
Feature Ticket: IDEMPIERE-4186
Sponsor : Martin Schönbeck Beratungen GmbH
Description:
This feature allows to suspend a workflow upto the actual transaction is committed. It does not initiate a commit itself. Effectively it works like the normal wait with a time greater than 0 where the workflow processor restarts the workflow later, but here the workflow is restarted immediately after commit. It is activated by using a value of -1 in the wait action. This also ensures the workflow will be restarted by the workflow processor if it by any reason couldn't be continued after the commit.
This is especially useful before a jasperreport is to be started by a workflow to ensure it sees all changes done. Or if you want to send an e-mail you'll probably make sure the e-mail doesn't tell anything which may be rolled back due to later errors.
