
SPD 2010
161
architects is two-way. The second benet is that it provides a way for solutions to be completed if
SPD 2010 cannot successfully fulll the requirements.
For example, if you are a workow author and you have been assigned a workow project, you can
take the requirements however you have received them and begin building a SPD 2010 workow.
Unfortunately, the conditions, actions, and features cannot fulll every possible workow request.
As such, the only option left would be to build the workow in VS 2010. But rather than start a new
VS 2010 project, if the original workow author exported the unnished workow to Visio, the VS
2010 developer could import that same le back into VS 2010 for use.
The same benet mentioned in the preceding example is also available another way. With Reusable
Workows, an author can save the workow as a template. This saves the le as a .WSP. This le
can be opened in VS 2010 and worked on. So not only do the integration points provide an improved
communication mechanism for business and IT users, they also provide an easy way to transfer infor-
mation so that a project can be added on to or continued rather than scrapping and starting a new
project from the beginning.
Oce InfoPath 2010 Forms
Unbeknown to some users, the majority of forms used throughout SharePoint 2010 sites are InfoPath
2010 forms: New Item form, View form, List It ...