
238
CHAPTER 9 Building a Site ProviSioning SyStem
In this case, the approver is determined by traversing the corporate hierarchy upward from the sub-
mitter’s position. The rst user found whose job title contains a certain matching string (such as
dir
for director-level resources) is selected as the approver. The
matching string to be searched for is
configurable for each type of site in the taxonomy. This solution requires the correct configuration
of corporate hierarchy within Active Directory (AD), and that user imports from AD have been set
up for your farm within the User Profile Service. Furthermore, users’ titles must be set appropriately
for matches to be found. If no
matching string is provided, the system selects the submitter’s direct
manager. If the system cannot find a match, it defaults to a preset user configurable per site type.
Additional Complexity
Depending on the complexity of your organization, additional roles and approvals (second or even
third level) may be required. You may prefer that support staff have the ability to reassign approv-
ers without creating sites. This functionality can certainly be built by extending this solution, but
for the sake of a clear example, you can implement a system in which a group of Site Creation
Administrators have complete control over requests to x issues with the request process. (The
approver is unavailable, but a ...