Start conditions are incredibly useful when developing Workflows in Nintex. They allow the developer to simply and eloquently decide which conditions are necessary for a Workflow to automatically be triggered. For example we might only want our Vacation Request workflow to trigger when an item is saved to our list with a status of Submitted. No point in notifying the boss that you’re just thinking about taking a vacation, eh?
What you didn’t want to know:
Start conditions change the way Nintex Forms trigger the workflow. Workflows with start conditions are started synchronously once the form is submitted. Under normal circumstances, this will not cause any tangible issues, however if you have large workflows being triggered, your user will watch a spinning circle until the workflow finishes its first batch of operations, which can come across to users as a slow system.
Continue reading “The Problem with Start Conditions – Nintex Workflow”
Folders in Lists/Libraries are a common tool used for creating hierarchy and structure in SharePoint. They allow us to organize documents and items in a manner that the end user is both familiar and comfortable with.
The question comes up then, when having to work with the documents in Nintex Workflow when dealing with Folders, how do we search an entire library for a specific document (or whatever other filter may apply)?
Continue reading “Querying Lists with Folders on Alternative Site – Nintex Workflow”
If you’ve got a Flexi Task that has non-standard outcomes (or more than 2) and you want to replace the Decision Control with buttons that submit the form and sets an outcome, you can do so with just a little bit of configuration and JQuery. The following describes how this can be easily accomplished.
Continue reading “Nintex – Replacing a Decision Control with Save and Submit Buttons on a Flexi Task”