Pega Prpc Leave Management System Specification

Leave Management System ABC corp is planning to implement a leave management system. Given below the requirement. Requirement: 1. User should be able to initiate a Leave request from a portal. Given below the information which needs to be shown as part of the initial screen. 1.1. Employee ID Number – Auto complete field (Populate from the Employee Information Table). 1.2. Employee Name – Read only field (should populate as soon as the employee ID is entered). 1.3. Employee Designation- Read only field (should populate as soon as the employee ID is entered). 1.4. Employee Project Name- Read only field (should populate as soon as the employee ID is entered). 1.5. Employee Supervisor - Read only field (should populate as soon as the employee ID is entered). 2. Once the User clicks submit, the next screen should show his leave details. 2.1. Total Number of Leaves available – Read only populate from the Employee Details 2.2. Total Number of Medical Leaves --Read only populate from the Employee Details 2.3. Total Number of Personal leaves - Read only populate from the Employee Details 2.4. From date and to date - editable with proper validation. 2.5. Type of Leave- personal or Medical (Editable). 2.6. Number of days – Read only. (Calculated based on from date and to date). 2.7. Validation- should not increase the total number of leaves. 3. Once Submitted an email needs to be triggered to the supervisor’s email ID and he needs to approve the request. (Supervisor will not be a part of the PRPC system). 4. If the request is rejected, the request is sent back to the user who initiated the request. 5. If the request is approved, then the corresponding leave information is updated to the employee information database. 6. If the leave type is medical, additional approval is required from the HR team after the supervisor has approved the request. If the HR team rejects the request the leave request is resolved rejected. 7. At any point in time the user who works on the case must be able to see all the information that was shown as part of the initial 2 screens.

Requirement to Store the Employee Information: 1. There are three different tables: 1.1. Employee Information – Employee ID (Primary key), First Name, Last Name, Designation, Project ID. 1.2. Project Details- Project ID (Primary Key), Project Name, Supervisor ID, Supervisor Name, Supervisor Email. 1.3. Leave Details – Employee ID, Number of Medical leave, Number of Personal Leave.

Create SOAP/REST services for external system to update/view information. 1. Create a REST service to get the list of employees, with the leave information and project information. 2. Create a SOAP service to update the Leave details of an employee. 2.1. Inputs- Employee ID, Number of Medical leave, Number of Personal Leave.