+3In the on-prem versions of SharePoint Nintex Workflows the column that is created when a workflow is published indicates the status of the workflow.
However, in the Office 365 version of Nintex Workflow that column gets created, yet remains blank.
Why is that column there?
Am I missing out on something?
Best answer by larry_bolton
Nintex Support is saying the same thing - this is a known issue and it's on the roadmap. They also sent a link where the Nintex community can vote on features: https://nintex.uservoice.com/forums/218291-3-nintex-workflow-for-office-365/suggestions/4509518-workflow-column-status
My suggestion to Nintex would be to add some sort of annotationin the Help documentation to indicate which features are "Coming soon" versus those that are ready to use. This would benefit everyone. The Nintex support staff would benefit by reducing the amount of support requests, the Nintex sales team would benefit by having fewer confused customers and thus more hardy recommendations, and customers would benefit by not wasting precious time trying to figure out how to make a feature work that has no hope of working.
+9There is a workflow action called "Set Workflow Status" which which will set the value of that field as a hyperlink to the workflow history page.
Very limited in use compared to on-premise and if a workflow errors in anyway it remains at the previous status and isn't changed to "error" - which makes managing workflows in Office 365 a nightmare currently.
+7This problem of workflow column remaining blank is a known issue on 365....you didn't miss anything !
+3Nintex Support is saying the same thing - this is a known issue and it's on the roadmap. They also sent a link where the Nintex community can vote on features: https://nintex.uservoice.com/forums/218291-3-nintex-workflow-for-office-365/suggestions/4509518-workflow-column-status
My suggestion to Nintex would be to add some sort of annotationin the Help documentation to indicate which features are "Coming soon" versus those that are ready to use. This would benefit everyone. The Nintex support staff would benefit by reducing the amount of support requests, the Nintex sales team would benefit by having fewer confused customers and thus more hardy recommendations, and customers would benefit by not wasting precious time trying to figure out how to make a feature work that has no hope of working.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.