The Time card Management feature enables users track their time for the assigned tasks also helps to capture associated cost along with it. Tasks can be any entity which is extended from task table like project, project task, incident, problem, change request.
Note: I won't cover what is already there in the documentation. This is applicable for releases below London.
In this, I would like to shed light on overview of how approval flow work and what happens beyond that.
Creation Process:
Users can create time cards from Time sheet portal (formerly known as Worker portal). All the time cards created for a week are tied to a time sheet of that week where hours are aggregated for each day. Time cards can also be auto created based on the time spent by user on a particular task. This feature is driven by Time sheet policy. Initially state will be "Pending", once user submits, state will be "Submitted".
Approval Process:
Submitted time cards are visible to approvers. Approval process could be 2 step or 1 step process based on the time sheet policy.
There is special approval flow if the task is of type Project task where Project Manager has to approve the work logged by the user.
Note: If a time card is rejected, state will be "Rejected" and associated time sheet also moves to "Rejected" state.
Post Processing:
Once time card is approved and task type is project task, actual hours are updated on relevant resource plan and resource allocation daily table and also on Project task. An expense line would be created based on labor rate card.
All unprocessed expense lines are processed by a daily schedule job which updates actual amount on respective cost plan and breakdown. This amount would rollup to project, program and portfolio.
Feel free to ask any questions associated to Time card management.
Thanks Best Regards,
Sunil B N
14 Comments
