I use log to history to debug
I had that same concern. One thing that I added at the beginning of each Child Workflow was a status check of the Parent workflow. The workflow would terminate if started manually.
446 votes33 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
We’ve just released the ability to capture comments from via LazyApproval, apart from that you can also easily store and retrieve those comments (including ones made via Nintex Forms or directly via the task) into a new task action variable (Task comments).
For those who are specifically interested in capturing from LazyApproval the way you do is by supplying the outcome separated by a comma and then the comments .e.g. ‘Rejected, Need more detail before can approve’.
Check it out and let me know what you think…
I am perfectly fine with workarounds when functionality does not exist. However, it would be greatly beneficial if those "workarounds" would be added to the official documentation until they become inherent to a feature.
While one can capture the comments by looking up the Task ID, this becomes useless if a response has been provided via "lazy approval".
If Lazy Approval has been enabled, the designer should DISABLE comments, thus alerting developers IMMEDIATELY to the fact that comments cannot be captured.
I appreciate o365; however, Nintex has become so limited in that environment, it is frustrating.
Improve the documentation to better temper expectations. It sure would have saved me a few hours.
359 votes26 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
We recognise the need for this feature and would like to see it in product. However, this is not a quick fix and requires a fair amount of engineering effort. As we are focused on Universal Forms, we are definitely considering how we can ensure we address this feature in the future release.
I will update this feature when we begin development on Task Forms for Universal Forms.