Differences from Drupal 7 webform_workflow module

Last updated on
29 May 2022

This documentation needs work. See "Help improve this page" in the sidebar.

Key differences

Workflows need to be set up via the Workflows module, rather than per-form. This also means the idea of transitions (which determine what states can be changed to what states) is introduced in this module.

"Set submissions to the first state after editing" option

Due to the introduction of transitions in the new module, this option no longer exists exactly - as it wouldn't always be possible to transition back to the initial state from every other state, unless a transition was set up allowing that. For example, if you have states Submitted and Approved, but only one transition from Submitted to Approved, there would be no transition to set it back to submitted, and it could violate the logic of the workflow to do so.

This means in the webform_workflows_element module what happens on editing is set per transition. In the element edit form each transition has an option called "Run transition on submission edit". You can choose there whether to run the transition when the original submitter edits it, or when anyone edits is. This means when the submission is edited, and that transition is possible based on the current state, the transition will be run. If the transition isn't possible, because the current state is not in the "from" states for the transition, nothing will happen.

Recreating the Drupal 7 functinality

If you need the exact same functionality as "set submissions to the first state after editing", simply create a transition which has every state as "from" and your desired first state as "to" - e.g. 

  • Transition name: 
    • Reset to submitted
  • From: 
    • Submitted
    • Approved
    • Rejected
  • To
    • Submitted

This will ensure every submission state will always be able to reset to Submitted when someone edits the submission.

Help improve this page

Page status: Needs work

You can: