Privilege Needed: Project Manager
To enable Project Manager approval for a project, set the Project Approval in the Time section value to Yes when setting up a project. Any timesheets submitted while this value is Yes will require approval by the project manager for that project, (or by an alternate approver) before that timesheet can be set to Completed. If time is already submitted for the project before the Project Approval value is set to Yes, that time will not require approval by the project manager.
See the note below about Automatic Approvals (e.g. submitters do not have to approve entries they just submitted).
Below is an example of an approval queue for a Project Manager that has several timesheets that have been submitted. The queue is broken down into distinct tables by Project, with any Primary Approvals displayed first, followed by Alternate Approvals.
The project manager can see:
The project manager can now do 1 of 5 things:
).
).
) icon.
)
icon.
) icon. When the project manager views the timesheet,
he/she will not see the entire timesheet, but rather, just time for that project he/she is
the project manager for. Selecting this option, the Project Manager can
then continue to approve each of the user's timesheets for that project
without having to come back to this screen.Check out statuses, for more information on the various statuses within the approval process.
Below is an example of a window that will pop up when the project manager approves or disapproves a timesheet. These comments are captured and stored in the Approval History of that timesheet. The Approval History can always be displayed when viewing any timesheet, located at the bottom of the document. These comments are also sent in the E-mail message if you are running Unanet with the E-mail option enabled.
 |
|
Below is an example of how the timesheet is displayed to the project manager
after the (
)
icon is pressed from the Approve Timesheets window shown at the top. Here,
the project manager can see the owner of the timesheet, the time period, the
hours worked each day but only for a specific Project, and a table
listing the comments entered for each cell (if any were entered). The next
table is the approval history section followed by the current controller and
status of the timesheet.
From this screen, the project manager can Approve or Disapprove the timesheet; which will pop up the approval window shown above. The Appr/Nxt button approves the current timesheet without any comments and display the next timesheet in the Project Manager approval queue (for this project). The Skip button allows you to ignore the current timesheet and move on to the next timesheet in the approval queue.
Note: User's are no longer required to approval their own entries -- at least, that's the basic premise. Actually, to be more specific, the individual that submits a timesheet who also happens to be responsible for the primary approval -- will no longer have to approve the entry they just submitted (it will be automatically approved -- with a corresponding Approval History entry supplied by the system).
Example: when a user is also a manager, project manager or customer, and they submit their own time, these items will not appear on their own corresponding approval queue. If a delegate, however, submits time for another user, and that other user is their own primary approver -- well that other user will still have to approve their own timesheet (since they weren't the one that submitted it).
See Approval History example below:
One exception to this policy is the time import. Automatic approvals are disabled when it comes to time entered into the system via the time import.
Return to Unanet Table of Contents page
Copyright © 1998-2002 Computer
Strategies, Inc., All Rights Reserved.
Last revised: September 13, 2002.
