👋 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 are looking for the Nintex roadmap, you can find that on Nintex Community
If you have questions about Nintex Ideas, please contact firstname.lastname@example.org
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact email@example.com
For exemple :
I have a need to create a resource in an external system when submitting a form. In the case of a resubmission we need to retrieve the existing resource and not create a new one.
When building a workflow action history, I would like to identify the resubmission step. Without having to do complex calculations/checks to get the information.
That's why I need to know if this is a resubmission in my workflow, and then I can add a different processing logic.
OK yes that makes more sense so thanks for the additional info.. Could you provide any more detail about what you are looking to do in the workflow if the instance is a resubmission? Be great to understand the scenario you are looking to solve..
I meant to say, having a variable in the Workflow Designer, allowing us to add a logic in the Worklfow implementation in order to know if the current instance is a resubmission.
And this feature is not existing.
This already exists Nicolas, any resubmission of a previous instance will show as part of a hierarchy with an expandable arrow in the instances page.