Inactive Resources

[Sue C]

When a resource is inactive in PWA, is there a reason why the resource
still appears as an available resource for the resource manager in
RESOURCES - VIEW RESOURCE ASSIGNMENTS? Is this normal behavior, or is
there something I am missing? In Project I have set WORKGROUP to NONE
and BOOKING TYPE to PROPOSED, and of course INACTIVE is checked as the
user was inactivated in PWA. Do I need to assign the resource a
different generic-type RBS code to remove them from their old RM's
view?

Also, if I open the RBS and INCLUDE INACTIVE RESOURCES, I run across a
problem in which when trying to save the RBS back, if a user has been
removed from AD, the RBS will not save. This is because they are set
to WINDOWS AUTHENTICATION. Should they be set to PROJECT SERVER
AUTHENTICATION when they are inactivated?

Thanks for your help.

 

[Scott m Wagner - EPM Consulting Services]

Sue,

When you are looking at RESOURCES - VIEW RESOURCE ASSIGNMENTS
you will see "RESOURCE ASSIGNMENTS" these are for ALL resources active or
not. So the behavior is correct.

There is also no reason to reset resources after you inactivate them. Simply
inactivating a resource will disallow his login so no need to remove from
Windows Authentication.

Hope that helps

 

[Sue C]

Sue,

When you are looking at RESOURCES - VIEW RESOURCE ASSIGNMENTS
you will see "RESOURCE ASSIGNMENTS" these are for ALL resources active or
not. So the behavior is correct.

There is also no reason to reset resources after you inactivate them. Simply
inactivating a resource will disallow his login so no need to remove from
Windows Authentication.

Hope that helps







- Show quoted text -

Scott,

Your response was very helpful. Thank you for that.

Also, if I don't want the RM's to see these old resources in their
VIEW RESOURCE ASSIGNMENTS (keep it clean), can I set the old resources
to a "dummy" RBS code? Would that affect reporting of historical
information? My initial thought is that it would...and for this
reason the RM's will have to live with seeing "old" resources in their
VIEW RESOURCE ASSIGNMENTS?

And also (sorry), any currently employed resource who has been
inactivated, does not cause RBS resave isses. However, if a resource
has had his Active Directory account deleted by IS (left company, or
whatever), then resaves of the RBS are problematic because the user
no longer has WINDOWS AUTHENTICATION (or any authentication for that
matter). To resolve this resave problem, I set one individual to
PROJECT SERVER AUTHENTICATION, which then allowed a resave. Do you
see any issue arising from this - bad practice, reporting or
otherwise?

Thanks for your support. I greatly appreciate all of you who work to
answer our emails. Your help is invaluable.

Sue

 

[Scott m Wagner - EPM Consulting Services]

Sue,

It is my experience that you would want to view historical data intact. One
item to note is that you will want to ensure that work is "reassigned" for
tasks that have not been completed by resources that are no longer available.

If the Windows Account is no longer available the resource should not be
modified. Sometimes we must as people leave and we cannot reset them to
inactive without changing them to Project Server Authentication. It is "My
Opinion" (we all have one, LOL) that you should do it only when you must and
don’t change the RBS or other data.

We typically create department reports with SQl reporting services and
filter out inactive resources. If you are interested in a packaged reporting
solution for EPM, one is available from Forte Systems (RASPWA RS)
(http://www.fortesys.com).

Have a great day!

 

[Sue C]

Sue,

It is my experience that you would want to view historical data intact. One
item to note is that you will want to ensure that work is "reassigned" for
tasks that have not been completed by resources that are no longer available.

If the Windows Account is no longer available the resource should not be
modified. Sometimes we must as people leave and we cannot reset them to
inactive without changing them to Project Server Authentication. It is "My
Opinion" (we all have one, LOL) that you should do it only when you must and
don't change the RBS or other data.

We typically create department reports with SQl reporting services and
filter out inactive resources. If you are interested in a packaged reporting
solution for EPM, one is available from Forte Systems (RASPWA RS)
(http://www.fortesys.com).

Have a great day!









- Show quoted text -

Thanks Scott...I appreciate your help.