Skip to main content
Nintex Community Menu Bar
Question

Is there an action that that can move to a previous step in the workflow?

  • August 7, 2026
  • 1 reply
  • 31 views

Forum|alt.badge.img+6

We created a workflow with a start form that includes Text – Long controls populated by rules. This creates an issue when users select “Copy form data” to reuse information from a completed form in a new submission. Because those text controls were populated by rules in the original submission, their values do not carry over to the new form. I have two questions:

  1. Do you have any suggestions for resolving this issue?
  2. Is there an action that allows a user to select a specific point to restart the workflow? In other words, is there an action that can move or jump to a defined step in the workflow?

1 reply

Simon Muntz
Nintex Partner
Forum|alt.badge.img+23
  • Nintex Partner
  • August 10, 2026

Hi ​@AdrianGaribdass01,
 

  1. Do you have any suggestions for resolving this issue?
  2. Is there an action that allows a user to select a specific point to restart the workflow? In other words, is there an action that can move or jump to a defined step in the workflow?
  1. For the rule trigger, you can resolve this in multiple ways. If the rule triggers “if the field is empty”, then one way to resolve this is to use the js-insert plugin from the Nintex Gallery that clears the field on form load, focuses it and then blurs it, which will trigger the rule.
    Code would look like this:
    const wrapper = document.querySelector('.myFieldClass');
    if (wrapper) {
    const el = wrapper.querySelector('textarea, input, [contenteditable="true"]');
    if (el) {
    if (el.isContentEditable) {
    el.textContent = '';
    el.dispatchEvent(new InputEvent('input', { bubbles: true }));
    } else {
    const proto = el.tagName === 'TEXTAREA'
    ? window.HTMLTextAreaElement.prototype
    : window.HTMLInputElement.prototype;
    const setter = Object.getOwnPropertyDescriptor(proto, 'value').set;
    setter.call(el, '');
    el.dispatchEvent(new Event('input', { bubbles: true }));
    el.dispatchEvent(new Event('change', { bubbles: true }));
    }

    el.focus();
    el.blur();
    }
    }
    1. Apart from that, you could trigger rules to do the same thing but only trigger once on form load.

      There is no action to jump to parts of the workflow, but you could configure the submit form to increment a variable when the form data is copied. The workflow you don’t want to run on resubmission could be put into a run if action or on a separate branch by value branch, etc which checks this incremented value, and only where you want the workflow to continue from is run.

Definiti is a Nintex Partner. If you need consulting on this, please contact us via our website or message me.