đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
A column to differientiate dev vs prod tasks and instances need to be incorporated into the platform under Tasks (under My Nintex) and Tasks & Instance (under Automate).
Default should not include these like instances has for deleted workflows.
Same concept, box would say "Include instances of development workflows". Tasks would show "Include tasks of development workflows".
Not all customers use sandbox or dev tenant. We use one to avoid managing multiple tenants. Because of this, when we go live, we need a way for these to not be visible as actually tasks for users to complete. We do our best with terminating any dev instances but would be easier to identify these quickly in instances section so we can actually terminate them if we see they are lingering out there.
Hi @Guest ,
Thanks for reaching out, and apologies for the incredibly late response. I'll open this feature up for voting.
In the mean time, there is a shortcut to find related instances to a particular workflow (see image below); You will need to adjust the Start date range, then Select to terminate to bulk terminate all returned instances. If you're keen to remove any test data too, you can then Select to delete to clean up.
Regards,
Kate Huynh