Preventing top level tasks to be selected on timesheet

[Larry Christofaro]

I am trying to find a way to prevent users from choosing and adding top level
tasks to the timesheet. I heard that there is a way to to do this (API,
event handler, ??)but if someone can give me a jump start I would be greatly
appreciated. Thanks...

 

[Assaf Leibovich]

Hi Larry,
According to this:
http://www.eggheadcafe.com/software/aspnet/32021499/how-do-we-prefent-top-le.aspx, there is no out-of-the-box solution for this issue.
However, I did notice that there are products out there providing a
prevention of reporting on top level tasks.

Maybe this site can give you a direction on customizing timesheet activities:
http://epmtsst.codeplex.com/

HTH
Assaf

 

[Larry Christofaro]

Thanks Assaf. I know some companies have done this and would love to know
how they did it... I'm still searching

 

[HansH]

One possible solution is using server side events.
On each timesheet save, an event is launched. You can write an event
handler that retrieves additional information for each timesheet line
(like: is this a top level task), and based on your checks, you can
cancel the timesheet save action.

I hope this helps,
Hans

Projectopolis <http://msepm.hsquared.be>

 

[Stephen Sanderlin [MVP]]

Larry,

Hans is correct that server-side events are one possible solution. The
problem with this approach is that there's no simple way to send
feedback to the user outside of email. That being said, if you choose
this approach I'd suggest that you avoid cancelling the timesheet save
event and instead prevent the user from submitting the timesheet --
otherwise, your users will be very annoyed that they have to re-enter
everything. At least if you allow them to save they can later transpose
the information.

Another approach would be to add some JavaScript to the
SelectTaskDlg.aspx page (I'm thinking in the UpdateTaskFullName
function) found in C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\12\TEMPLATE\LAYOUTS\PWA\TIMESHEET\. This approach
isn't really ideal, though, because it involves editing the underlying
page. Unfortunately, since this isn't a web part page, this is the best
we can do. Note that any change to this file will affect all PWA
instances in the farm. If you choose this approach, you should be
careful to not break anything or cause any unintended side effects.
Also, be sure to test thoroughly and to keep a copy of your changes, as
this file could be overwritten by a service pack or other update.
Looking at a few of the available products that offer a solution to this
issue, it appears that they've taken this approach.

When I do deployments, my personal preference is to handle this as a
training issue by teaching users to not use top-level tasks and
instructing timesheet approvers to reject any timesheet that includes a
top-level task.

Steve

--
Stephen Sanderlin, Project MVP
VP of Technology
MSProjectExperts

For Project Server Consulting: http://www.msprojectexperts.com
For Project Server Training: http://www.projectservertraining.com

Read our blog at: http://www.projectserverhelp.com