đź‘‹ 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
Before k2 five, we were able to use Go to Activity smart object without any issue inside workflow. I tried using in k2 five and workflow goes in running mode.
Scenario -
Let's say I have 10 approval steps. Whenever it is rejected by any step, I want workflow to send back to submitter step and when submitter complete rework I need workflow to come back to step where it was rejected.
To achieve this, I need to draw lines from submitter step to each step and each step to submitter step which creates lot of lines.
got to smartobject would give flexibility. When submitter completes rework, it goes to go to activity smartobject and send workflow back to step who rejected. This way workflow would be clean and no need to draw multiple lines.
Go to activity would help in lot of other scenarios, when there is need to move workflow to on the fly
