This document is a test case document for specific understanding

The Wh questions for Team calendar

The Whats? The team calendar is an application which provides managers and employees with a quick overview of the absences of employees in the team. The term team may have different meanings with respect to the person trying to access the calendar. It will be covered in the forthcoming Wh questions. The team calendar along with providing overview can also give access to process the absence request.

The above screen shot illustrates a team calendar view for an employee (can be or cannot be a manager). The view is for a month of 30 days with absence. The cursor when on a particular record shows the absence detail in the tooltip. Legends are provided to make the coloured information comprehensible. The Hows? The team calendar feature can be accessed by an employee in two modes or roles. Either the employee may view the team calendar as a requestor or he/she may access the team calendar as an approver. 1. Access from Leave Request

When the access is done as illustrated above, the employee dons the role of a requestor.

2. Access from Task List

The other mode of access to the team calendar is when the employee can take the role of an approver. He/she can access the team calendar from the task list here as illustrated below.

On selection of a leave request to be processed, a new page is opened with the cumulated list of all the requests which he can approve. It also has a link to the team calendar.

The Whos? The whos part deals with the people accessing the team calendar and the team concept that is the employees displayed as a part of the team. Broadly as we have already seen there are two modes of access to the team calendar as a requestor and as an approver. These modes of access also determine the views and the actions possible on the team calendar requests. We will breeze through these sections in the forthcoming parts with respects to the roles of the logged in user. For the first scenario let us consider the logged in user to be a requestor.

The requestor mode The requestor mode view is available to all the employees as any employee can logically request an absence. We have already gone through the mode of access for the requestor view through the leave request.

The requestor view gives the display as below.

The Team Let us drill down a bit into the details of the team concept. In the requestor view, a team comprises of all the direct reportees to the logged in user and his/her own entry. Here we are looking at the requestor view of Employee Manoj Kumar (Personnel no: 11404, Designation: HOD) who has direct reportees as Manmeet Singh (Personnel no: 11311, Designation: Project Manager) and Kangana Kochar (Personnel no: 11405, Designation: Sr. Procurement Manager). Actions possible As the requestor mode is a mode for all employees, no action on a leave request by any other employee is possible through this view.

If in the requestor clicks on his own request he can change/delete it.

The approver mode The approver mode view as the name suggests can be only made available to the employees approve/reject a absence request. We have already gone through the mode of access for the approver mode view through the task list.

In the approver mode two different views are available for the user to access.

1. Direct reportees 2. All Employees These views define the team concept for the approver mode. The Team Let us drill down a bit into the details of the team concept to anaylse the direct reportees and All employees views. Direct reportees view shows the direct reportees to the logged in user. It provides a team same as the team shown in the aforementioned request mode. Here we are looking at the requestor view of Employee Manoj Kumar (Personnel no: 11404, Designation: HOD) who has direct reportees as Manmeet Singh (Personnel no: 11311, Designation: Project Manager) and Kangana Kochar (Personnel no: 11405, Designation: Sr. Procurement Manager).

All employees view shows the all the employees in the same department as to the logged in user in the team calendar. It will be provided only if the employee is assigned as a HOD in the organization structure. For all the other employees the view will not provide any output.

Here we are looking at the all employee view of Employee Manoj Kumar (Personnel no: 11404, Designation: HOD) who has co-workers in his department Procurement-Head as Chander Chaubey (Personnel no: 11406, Designation: Procurement Manager) and Kangana Kochar (Personnel no: 11405, Designation: Sr. Procurement Manager). The department also has a vacant position for Procurement In-Charge which is not displayed. Let us just have a look what will happen if a user not a HOD tries the All employee view.

Employee Chander Chaubey (Personnel no: 11406, Designation: Procurement Manager) is approving the leave request of Rita Prasad (Personnel no: 11412, Designation: Jr. Officer Procurement ). First he will go the task list (from where he can access the team calendar as an approver)

He can view the direct reportee view from the team calendar

Rita Prasad can be seen as one of her reportees. But when he tries the All employee view, he gets the following display.

No data is shown as he is not an HOD to access the All employee view. Thus we must understand that for all employees who can approve a request, the direct reportees can be accessed, but to access all the employees absences in his/her department, one needs to be the HOD of the relevant department. Actions on views The approver mode is only available for employees who can process (approve or reject) absence requests. Hence logically, it permits the logged in user to process the requests relevant to him/her. Leave requests can be approved or rejected by clicking on a corresponding and relevant leave request entry. Consider the forthcoming screen shot for actions on leave requests.

Here it can be seen that the view is that of all employee, the logged in person being Employee Manoj Kumar (Personnel no: 11404, Designation: HOD) who has co-workers in his department Procurement-Head as Chander Chaubey (Personnel no: 11406, Designation: Procurement Manager) and Kangana Kochar (Personnel no: 11405, Designation: Sr. Procurement Manager).

Points to note Points for remembrance Role of employee who accesses Mode of access Team defined by Actions possible Access possible to Requestor Mode As a requestor From Leave request Direct reportees Only view All employees Approver Mode As an approver From Task list View Dependant 1. Direct reportees view 2. All Employees view View, Process View dependant 1. Direct reportees view accessible to all employees 2. All employees view accessible only to HODs.