I'm currently in the process of defining how workflow development should look like in my company and how the different environments (development, integration, qa and productive) are being updated.
- SP Designer 2013 has become a really powerful tool. However we do not just yet see it as a tool we want to put into the hands of non-IT departments. Also using SPD means you either have to work with the live system directly or work on a qa environment where you save your workflow as a template ( -> wsp) which you then have to deploy on the live system. Is this feasible? Does anyone have any experiences with that approach?
- Visual Studio 201x workflows are declarative too now. The advantage here is source control integration and debugging capabilities. The tool set is way more complex to use though. And at the end of the day you have .wsp files as well. But of course these files could also bring along columns, content types, list templates and instances, ... things the SPD doesn't offer.
I can see opportunities where SPD might be the right choice. Low business impact, trivial workflow scenario... for anything else I'd go with VS based workflows.
What is your take on the subject?