
Buildout
243
for a more simple architecture, but in my experience, it is easier to keep these entities separate.
Administration of list data is easier when site requests and created sites are stored in different
places, and there may be many more site requests (including historical, rejected requests) than cre-
ated sites, such that keeping them in the same list will make queries for created site data less ef-
cient. Finally, although the data they store is very similar, the entities represented by these lists are
distinct, such that keeping them in separate lists produces less confusion among users interacting
with the solution. As with the preceding example, this is a matter of style and you should feel free
to alter the implementation as you see t.
Workflows
Finally, the workow logic needed for this solution involves two pieces: managing state transitions
and notifying users. These capabilities could be implemented using Workow Foundation or simply
by having the custom form perform the duties of both state transitions and sending email alerts to
various parties. I chose to use custom form logic to manage state transitions and SharePoint Designer
workows to notify users because I believe it provides a good mix of simplicity and congurability.
State transitions are unlikely to change as much as the messages sent to users, for example, and having
messages dened within a Sha ...