Commit changes
Available in scheme types:
Non-pricing
Pricing and Ticketing
If there are actions which by default does not save the changes to the booking and there are no other actions after this action that saves the changes then you might want to use the Commit changes instead of commit the change in the actual action.
Example, in this process/flow there is no action that will save the changes when/after a remark was added, therefore the error is received when checking/activating the scheme:
The solution to the above would be to add a Commit action the process so the remark is saved:
(note: in the Write remark you can choose to commit as well; eg End or End and Retrieve, but sometimes you might not want to commit at that stage)
Any action with this bottom right corner does not save the changes by default:
