| Subject: | Leave Application Policy - Prevent employee from applying Leave based on Company Policy |
| Summary: | 1. New Design: - Add Leave code maintenance form in ESS
- Add detail form to allow leave code rules
- Add a table for leave code rules and populate with the rule "Allow leave applications if it is applied before [N] days from "Leave Start Date". The default is N=0. Active=0
- Add validation in leave entry in ESS and Backoffice.
- When the rule is changed, add a notes entry with what has changed
- The rule should only be applicable if leave entry is done via ESS
- Rule only applied if status is "Applied"
- Since there will be no restriction at BO level, the user can handle exceptions including "Sold" flag.
2. TEST PLAN: Place all possible test cases relating to this new feature/Change request (Requester to fill in) | ID | Test Case | Expected Results | Pass/Fail | Reference | | 1 | Leave is allowed if the start date is after 14 days from calendar date
Test1: suppose today's date 31/01/2018, leave start date: 14/02/2018. Capture the system calendar date as leave entry date. This is 14 days. This should be allowed
| Leave should be successfully applied |
|
| | 2 | Test2: leave start date: 01/02/2018. Entry Date 01/02/2018. This is 0 days. This should not be allowed
| Message to indicate of HR Policy
|
|
| | 3 | Test3: leave start date: 13/02/2018. Entry Date 01/02/2018. This is 12 days. This should not be allowed | Message to indicate of HR Policy
|
|
| | 4 | Test4: This rule only applies to status "Applied" from ESS | Message to indicate of HR Policy
|
|
| 5
| Test5: Make leave entry from Back office with status applied.Use same dates as in Test 1, 2 & 3
| Leave should be successfully applied for all three date range
|
|
| 6
| Test6: Plan a leave from 14/02/18 to 14/02/18 on 01/01/2018.Change Leave status to "Applied" on 12/02/18
| Message to indicate of HR Policy
|
|
| 7
| Test7: Plan a leave from 14/02/18 to 14/02/18 on 01/01/2018.Change Leave status to "Applied" on 31/01/18
| Leave should be successfully applied for all three date range
|
|
|
==========OLD DESIGN BELOW THIS LINE======================================================================= 1. Change Details/Justification: (Requester to fill in) Most companies in Fiji have an Annual Leave Policy that employees must apply for Annual Leave 14 Days/7 days prior to going on leave. In order to control this process, they are requesting if we could facilitate this in our future releases of LinkSOFT. Rule: When an employee is applying for leave in ESS, the duration between leave entry date and the leave start date should be more than or equal to the days defined at leave level. This rule should only be applied to leave status "Applied".
Need to Introduce new field at leave level as in Figure 1. Figure 1: Screen Change .JPG)
|
| Audit Notes: | |
| 02 Dec 2015 | 12:16PM Comment 1 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 29-07-2016 12:00 AM Time Taken: 1.00 |
| Move to HR conversion project. Patch 80.006A |
|
| 15 Nov 2016 | 10:57AM Comment 2 by Alvis (Link Technologies) Case 7163 removed from project 9.00 |
| 11 Jan 2018 | 08:32AM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Sanjeet (Link Business Solutions) Followup Date: 11-01-2018 08:32 AM Time Taken: 1.00 |
| Development meeting January 2018 Sanjay, Alvis, Sanjeet and Vineet.
This request needs to be a customization as it does not fit into all company leave application process. For example in urgent situations leave may need to be allowed. Estimated Effort: D8,ST2,UAT2 Design - We will add a set of rules for company policy.
- The leave update procedure can call a apply rule.
- The rule table will have option to enter leave days.
- This change will be implemented in ESS only.
|
|
| 16 Jan 2018 | 09:29AM Comment 4 by Sanjeet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 23-01-2018 12:00 AM Time Taken: 0.50 |
| Bula Team, I have provided an estimate to FBC team. Will wait for clients approval before we proceed with development. Regards
Sanjeet
|
|
| 18 Jan 2018 | 08:22AM Comment 5 by Sanjeet (Link Business Solutions) Assigned To: Development Followup Date: 18-01-2018 08:22 AM Time Taken: 0.50 |
| Bula Team, We have received approval from FBC. +++++++++++++++++++++++++++++++++++++++ Hi Sanjeet We can go ahead with this. Thanks Vimlesh Sagar|Chief Financial Officer| Fiji Broadcasting Corporation | P.O.Box 334, Suva| TEL: (679) 3314333 ext 2914 | FAX: (679) 3220991| CELL: (679) 9992810 Email: vsagar@fbc.com.fj
++++++++++++++++++++++++++++++++++++++++++++++++ Regards
Sanjeet |
|
| 18 Jan 2018 | 08:22AM Comment 6 by Alvis (Link Technologies) Case 7163 added to project 900 |
| 18 Jan 2018 | 08:25AM Comment 7 by Alvis (Link Technologies) Case 7163 removed from project 900 |
| 18 Jan 2018 | 08:25AM Comment 8 by Alvis (Link Technologies) Case 7163 added to project 8.3 |
| 18 Jan 2018 | 09:12AM Comment 9 by Sanjay (Link Technologies) Assigned To: Sanjeet (Link Business Solutions) Followup Date: 18-01-2018 09:12 AM Time Taken: 1.00 |
| Design: Sanjeet, Rashna, Sanjay, and Alvis: 18/01/2018 - Add Leave code maintenance form in ESS
- Add detail form to allow leave code rules
- Add a table for leave code rules and populate with the rule "Allow leave applications if it is applied before [N] days from "Leave Start Date". The default is N=0. Active=0
- Add validation in leave entry in ESS and Backoffice.
- When the rule is changed, add a notes entry with what has changed
Design Questions: - Can you complete the test plan and include what status to check this rule.
- What happens when an employee returns from leave and leave needs to be processed under 14 days. We should not disable the rule as this will allow employees to apply for leave in this window.
- What happens with sold leave.
- Please provide a detail test plan with scenarios
|
|
| 22 Jan 2018 | 01:25PM Comment 10 by Sanjeet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 22-01-2018 01:25 PM Time Taken: 1.00 |
| Hi Alvis, - The rule should only be applicable if leave entry is done via ESS
- Rule only applied if status is "Applied"
- Since there will be no restriction at BO level, user can handle exceptions including "Sold" flag.
- Test Plan updated.
Regards
Sanjeet
|
|
| 05 Feb 2018 | 04:52PM Comment 11 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 05-02-2018 04:52 PM |
| Agreed to build in beta2. |
|
| 06 Feb 2018 | 03:33PM Comment 12 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 06-02-2018 03:33 PM Time Taken: 6.00 |
| We have reviewed the design and decided to add this configuration to the leave maintenance form. Reason being creating a new form in ESS would mean part of leave maintenance is in ESS and the other part is in back office. To keep things consistent, we have added a field on Leave Code maintenance for "Apply Before Days". Changed the validation in ESS and back office to check for "Apply Before Days" and leave status as "Applied". The update will be available in beta 2. regards
Alvis/Sanjay |
|
| 13 Feb 2018 | 01:23PM Comment 13 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 13-02-2018 01:23 PM Time Taken: 0.50 |
| System test completed. Please proceed with UAT. |
|
| 16 Feb 2018 | 12:01PM Comment 14 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 16-02-2018 12:01 PM Time Taken: 2.00 |
| QA Results Step 1 - Developer will perform test based on test cases provided Step 2 - Product expert to complete Product QA based on test cases.
Test cases are provided on the case header before the case is approved for development. Test Results Summary Table 1 - Summarised list of issues  - OS version:windows 7
- Application version:8.3.2.0
- Database (Demo/New/Client): Demo LINKSOFT
- Client on QA1
Documentation completed on the case. Documentation updated under Payroll - Leave Management - Leave Codes. Steps to reproduce failed scenarios:
|
|
| 09 Oct 2019 | 08:14AM Comment 15 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 |