Why?

Apr 4, 2009 at 4:20 PM
Edited Apr 5, 2009 at 10:30 PM
If you don't need the full power of Visual Studio workflows then SharePoint Designer can be an attractive option.  SPD generates much of the boiler-plate code required in a workflow (association, initiation and task forms) but falls short in a few areas, one of which is the lack of a well rounded set of workflow activities.  There are several excellent projects that have worked to fill the gaps but I kept finding myself in need of another activity. Enter IPY4SPD.  It allows you to run an IronPython script directly in a workflow step.  In addition to having access to the entire .NET framework, it passes several key variables to the script so you can get at your data quickly: _actprops_ (workflow activation properties),_site_ (the current SPSite),_web_ (the current SPWeb),_list_ (the current SPList) and _item_ (the current SPListItem).  Once you're done manipulating your SharePoint data, IPY4SPD allows you to optionally return a script variable back to the workflow.