| Subject: | Incorrect Leave Notification - Employees Recommending own leave |
| Summary: | There is an issue with the leave notification. - Employee E006
- Leave - AAL
- There are 2 approvers.
- Approver A approves the leave and notification are sent as recommended leave. This is sent to Approver B.
- The email reads that the employee has recommended the leave. This is should be approver A.
|
| Audit Notes: | |
| 28 Jul 2017 | 11:30AM Comment 1 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 28-07-2017 11:30 AM Time Taken: 1.00 |
| Hi Rashna, Please change the alert template. The following tags can be used: | {LT_HRM_Leave_fx.ID} | | {LT_HRM_Leave_fx.CompanyID} | | {LT_HRM_Leave_fx.EmployeeID} | | {LT_HRM_Leave_fx.EmployeeName} | | {LT_HRM_Leave_fx.TransactionID} | | {LT_HRM_Leave_fx.LeaveCategory} | | {LT_HRM_Leave_fx.LeaveType} | | {LT_HRM_Leave_fx.LeaveDescription} | | {LT_HRM_Leave_fx.DateFrom,Datetime} | | {LT_HRM_Leave_fx.TimeFrom,Time} | | {LT_HRM_Leave_fx.DateTo,Datetime} | | {LT_HRM_Leave_fx.TimeTo,Time} | | {LT_HRM_Leave_fx.HoursTaken} | | {LT_HRM_Leave_fx.DaysTaken} | | {LT_HRM_Leave_fx.LeaveStatus} | | {LT_HRM_Leave_fx.LeaveCommentsHTML} | | {LT_HRM_Leave_fx.LeaveComments} | | {LT_HRM_Leave_fx.ApprovalLevel} | | {LT_HRM_Leave_fx.ApprovedByCompanyID} | | {LT_HRM_Leave_fx.ApprovedByEmployeeID} | | {LT_HRM_Leave_fx.ApprovedByEmployeeName} | | {LT_HRM_Leave_fx.MedicalCertificateSubmitted} | | {LT_HRM_Leave_fx.MedicalCertificateDaysSubmitted} | | {LT_HRM_Leave_fx.ESSWebsiteURL} | | {LT_HRM_Leave_fx.ESSWebsitePage} | | {LT_HRM_Leave_fx.EmailNotificationTo} |
|
|
| 01 Aug 2017 | 08:22AM Comment 2 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 01-08-2017 08:22 AM Time Taken: 2.00 |
| Documentation completed on the case. Documentation updated under Administration -- Document Templates -- Leave Approval/Reject Email Template. CC: Alvis, can you change the Leave Approval/Reject Email Template. to be standard as below. 
Regards |
|
| 09 Aug 2017 | 10:39AM Comment 3 by Alvis (Link Technologies) Case 8716 added to project 8.17 |
| 17 Aug 2017 | 02:22PM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 17-08-2017 02:22 PM Time Taken: 1.00 |
| The template layout has been added to the upgrade script. The template will be applied once the database is upgraded to 8.17. New and demo databases will have this layout as default. |
|
| 22 Aug 2017 | 08:15AM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 22-08-2017 08:15 AM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test Step 2 - Product expert allocated by Consulting Manager for Product QA. Consulting Manager to allocate resource Consulting Manager to sign off on UAT and Generic Test
STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below.. Case tested in QA1 with database LINKSOFT. Tested in 817 Beta1. Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | The leave notification to approvers should be as per comment 2 | Failed. "Approved by" is not included in the notification |
Image : 
WORKFLOW: - Original case assigned to Development
- When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
- If system test passes, assign case to Consulting Manager for UAT
- If UAT Passes, Assign case for Documentation or close case
|
|
| 22 Aug 2017 | 09:34AM Comment 6 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 22-08-2017 09:34 AM Time Taken: 1.00 |
| Added approved by to the template. Changes will be available in beta2. |
|
| 22 Aug 2017 | 03:12PM Comment 7 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 22-08-2017 03:12 PM Time Taken: 1.00 |
| QA for product and Patch Releases Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test Step 2 - Product expert allocated by Consulting Manager for Product QA. Consulting Manager to allocate resource Consulting Manager to sign off on UAT and Generic Test
STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Case tested in QA1 with 817 Beta 2 with database LINKSOFT. Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | The leave notification to approvers should be as per comment 2 | Pass |
Image 
WORKFLOW: - Original case assigned to Development
- When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
- If system test passes, assign case to Consulting Manager for UAT
- If UAT Passes, Assign case for Documentation or close case
|
|
| 09 Oct 2019 | 08:14AM Comment 8 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |