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.
433 votes31 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
We have just started the initial work on a couple new features to address both the capturing of comments via lazy approval as well as being able to easily access the comments in the workflow.
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.
328 votes23 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
The ability to see List Form attachments from a Task Form is now under review.