As I’ve been deep in the world of Project Server 2010 configuration this week, I thought I’d share a quick round up of the cool things I have noticed:
- Ability to edit custom fields in PWA without Pro client running.
- Project and Task Custom Fields update when project edited in PWA (Except for the first time usually).
- SharePoint 2010 Workflows have been updated, they are quite nice; for example the approval workflow is now able to do multi-level serial / parallel approvals, etc.
- Saving new Workspace templates is so so easy now! Just save site as a template, then go to your project type and select the new template!
- PDP’s rock – ‘enuf said.
- BI Centre is great, but so much more time will be needed (at least at first) in getting the reports you need. The flip side is that the reason why so much more time is needed is because you can get so much more out of them!
More to come in the coming days / weeks as it looks like client number 2 is going to kick of a 2010 implementation in the next week or so. Exciting times..
Very much appreciate your help.
We created a custom category with generically defined resources. [One important point of clarification/terminology; we created regular work resources that are titled generically (Desktop Support, DB Manager Etc.) BECAUSE we want to specify a default assignment owner (not available with true generic resources) in order to trigger a notification to the default assignment owner that they need to assign the task to one of their employees. In our case the assignment owners are Project managers].
Here is the problem situation.
Project Manager 1 (say, PM1) assigns tasks to specific employees that report to him and to various generic resources from the team that PM1 built for the project. Some of the generic resources report to Project Manager 2 (say, PM2). PM 1 notifies to PM 2.
PM 2 (who is the owner of these generic resource and, therefore), is responsible to assign tasks only to specific employees under his supervision. For this, PM2 identifies his/her specific employees based generically titled resources and re-assigns the tasks to them. But Project Manager 2 is also able to re-assign the tasks to any specific employee on the project team that PM 1 built, including those that report to PM1.
We want Project manager 2 to be able to re-assign only to his direct reports.
How do we set up permissions/filters to achieve this?