We have a SharePoint list that has list items created and updated frequently. However, we only need a workflow started when the value of 1 sharepoint list column is equal to "Needs Review".
Users will create and update the list item many, many times, finally they are ready for the list item to be reviewed with approvals. How would you approach the design?
Sure, it is very easy to have a workflow started with list item created or updated, but 90% of those workflows don't need to be created (unless the column value = "Needs Review"). To me it doesn't make sense to add that overhead to the K2 server and create all those workflows whenever a list item is created/updated, when I really only need a workflow when the list item column has value "Needs Review".
Anyone have any ideas for a design approach on my question above? Using K2 blackpearl, I'm thinking to use K2 Studio to create the workflow, unless you think we need some coding, then I could use the Visual Studio Designer.