PM Selectable Workspace when Saving

[FrankRec]

After reviewing the blog posts, I now understand the process for creating a
new default Project Workspace in PS2007 and applying it in "Project Workspace
Provisioning Settings". Is there any way for a Project Manager to be able to
select from the list of available Workspaces when saving a project to server
for the first time? If not, would I have to do the following:

1) delete the "default" page of the newly created project
2) navigate to "Project Workspace Provisioning Settings" and change the
default page to another selection on the list
3) go to "Project Workspaces" and create a site for the new project?

Thanks for your help with this.

 

[Jim Erwin]

After reviewing the blog posts, I now understand the process for creating a
new default Project Workspace in PS2007 and applying it in "Project Workspace
Provisioning Settings".  Is there any way for a Project Manager to be able to
select from the list of available Workspaces when saving a project to server
for the first time?  If not, would I have to do the following:

1) delete the "default" page of the newly created project
2) navigate to "Project Workspace Provisioning Settings" and change the
default page to another selection on the list
3) go to "Project Workspaces" and create a site for the new project?

Thanks for your help with this.

I'm pretty sure there is not a way to do that out of the box, but we
did some customization at one client that you may like. Basically,
you need to create some site templates, create a custom field called
"Workspace template" (make it a required field) or something, then
setup an EventHandler for Project-Publish. With that trigger, run
some code to read the custom field value and select a template to
use. Our deployment was slightly more complicated, but very handy.
We created a Site collection to host several sites and each value in
the custom field mapped to one of the sites, so when the project was
published, it would copy the referenced site and create a new site (at
some other location) using this site as a "template". This was nice
because then all you had to do to make changes to the "template" would
be to just modify the site - when a new site was created referencing
that site, the new workspace would look exactly like the referenced
site did at that point in time. This was nice, because then each
division of the company could have and manage their own workspace
template without Admin intervention/assistance. Note that you're
basically stuck forcing all published projects to have a workspace and
you take away the ability for the PM to specify a location for the
site, but IMO it is worth the sacrifice.

If someone has tried other methods of meeting this same need, I'd love
to hear them...

 

[FrankRec]

Jim,

Thanks for the info. This is a good and workable solution.