Subject: | System should not allow Time and Leave to be applied on the same day |
Summary: | Bula Vinaka Team,
Business Scenario: At any point in time, the maximum number of hours for Time Entry or Leave Entry or a combination of both should not exceed the hours set in configurations "Time Entry maximum hours per day".
Justification: Currently the system allows time and leave to be applied and approved of the same date and when payroll is processed, both the entries get pushed in the pay. This way the employee ends up being paid twice for a particular date. Test Plan:
Kindly take a look. Thank you Aarti Gayaneshwar |
Audit Notes: | Edited by sanjay on 05/03/19 10:34. Edited by aarti on 16/10/18 08:12. Edited by aarti on 08/10/18 21:24. Edited by aarti on 08/10/18 21:18. Edited by aarti on 25/09/18 07:22. |
19 Oct 2018 | 02:06PM Comment 1 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 19-10-2018 02:06 PM |
| Development meeting. Assigned to Sanjay for design review. |
|
07 Nov 2018 | 08:48AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 07-11-2018 08:48 AM |
| Thanks Aarti, the requirements are clear and we will include this in the next update. |
|
07 Nov 2018 | 08:48AM Comment 3 by Sanjay (Link Technologies) Case 9593 added to project 10.X |
27 Nov 2018 | 03:02PM Comment 4 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 27-11-2018 03:02 PM Time Taken: 1.00 Notes: Edited by alvis on 27/11/18 16:29. |
| We cannot use the "Time Entry maximum hours per day" configuration for leave entry. Instead, we can add the following configurations: - Allow "Time Entry" to overlap with leave applications when Time entry status is "Submitted"
- Time entry are all entries marked with "Activity Type = Time Entry"
- When submitting these entries, the system will validate the date and time against the leave applications. If an overlap is found, then the time entry will not be submitted.
- Allow "Leave Entry" to overlap with "Time Entry" when "Leave Entry" status is "Applied"
- Time entry are all entries marked with "Activity Type = Time Entry"
- When applying for leave, the system will validate the date and time against the time entries. If an overlap is found, then the leave will not be applied.
The following changes will be made: - The above rules will apply when any process changes the time and leave entry
- Time entry
- Time view by day
- Time view by week
- Time calendar
- Time approval
- Timesheet import -> Submit timesheet
- When editing a submitted time entry, the system will change the status to New
Note: Users will still be able to create a back-office leave entry with status Taken. i.e bypass the above check. |
|
30 Nov 2018 | 02:41PM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 30-11-2018 02:41 PM Time Taken: 4.00 |
| Development work for this case has been completed. The change will be available in version: 10.2 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Added configurations:
- Allow "Time Entry" to overlap with leave applications when Time entry status is "Submitted"
- Time entry are all entries marked with "Activity Type = Time Entry"
- When submitting these entries, the system will validate the date and time against the leave applications. If an overlap is found, then the time entry will not be submitted.
- Allow "Leave Entry" to overlap with "Time Entry" when "Leave Entry" status is "Applied"
- Time entry are all entries marked with "Activity Type = Time Entry"
- When applying for leave, the system will validate the date and time against the time entries. If an overlap is found, then the leave will not be applied.
- Refactored Time Entry procedures to perform a prevalidation check before creating saving the time entry
- The prevalidation checks have been added to the following screens:
- Time Entry
- Time View By Day
- Time View By Week
- Time Approval
- Time Calendar
- Added validation to Leave entry when the status of the leave is changed to "Applied".
Note: The validation is NOT added to the following areas: - Timesheet Import -> Submit Timesheet.
- The process that creates "Public Holiday Entitlements"
- Data uploaded from Excel
- Users will still be able to create a back-office leave entry with status Taken. i.e bypass the above check.
2. The issue was caused by: - Change request
3. Next Step - UAT
|
|
10 Dec 2018 | 08:46AM Comment 6 by Alvis (Link Technologies) Case 9593 removed from project 10.2 |
10 Dec 2018 | 08:46AM Comment 7 by Alvis (Link Technologies) Case 9593 added to project 10.1 |
11 Dec 2018 | 09:00AM Comment 8 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 11-12-2018 09:00 AM Time Taken: 1.00 |
| System test completed. Proceed with UAT. |
|
13 Dec 2018 | 08:53AM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 13-12-2018 08:53 AM Time Taken: 2.00 |
| Hi Sanjay QA Results Tests carried out according to requirements specified on the case header Test Results Summary Summarised list of test areas
Rule: Allow "Leave Entry" to overlap with "Time Entry" when "Leave Entry" status is "Applied" = No |
Time entry status is "Submitted". Time : 8am to 5pm. The user should not be able to apply for leave. Leave Entry, Leave Applications, Leave Calendar (Case 9753) | Pass |
Timesheet is status is "Submitted". Time: 8am to 5pm. The user should not be able to apply for leave. Leave Entry, Leave Applications, Leave Calendar (Case 9753) | Pass |
Create a time entry from 8am to 1pm for 7/12/2018. Submit Time Entry. Create leave entry for 2pm to 5pm. This should be allowed. | Pass |
| |
Rule: Allow "Leave Entry" to overlap with "Time Entry" when "Leave Entry" status is "Applied" = Yes |
Time entry status is "Submitted". Time : 8am to 5pm. The user should be able to apply for leave. Leave Entry, Leave Applications, Leave Calendar (Case 9753) | Pass |
Time entry status is "Submitted". Time : 8am to 5pm. The user should be able to apply for leave. Leave Entry, Leave Applications, Leave Calendar (Case 9753) | Pass |
| |
Rule: Allow "Time Entry" to overlap with leave applications when Time entry status is "Submitted" = No |
Leave entry is "Planned" for a 08/12/2018, the user should be able to "Create" time entry | Pass |
Leave entry is "Planned" for a 08/12/2018, the user should be able to "Submit" time entry | Pass |
Leave entry is "Applied " for a 12/12/2018, the user should be able to "Create" time entry | Pass |
Leave entry is "Applied " for a 12/12/2018, the user should not be able to "Submit" time entry | Pass |
Leave entry is "Approved" for a 12/12/2018, the user should not be able to "Submit" time entry | Pass |
Cancel approval and void leave. The user should be able to submit time entry. | Pass |
| |
Rule: Allow "Time Entry" to overlap with leave applications when Time entry status is "Submitted" = Yes |
Leave is "Applied" and the user should be able to submit time entry | Pass |
Leave is "Approved" and the user should be able to submit time entry | Pass |
Environment Details - OS version: Windows Server 2012
- Application version: 10.1.3.7
- Setup: Demo
- Server : 10.0.0.14
- Database:RASHNA-LINKSOFT-DEMO-10
Steps to reproduce failed scenarios: N/A Next Step: for documentation - The notes are updated under "Time View - Day" in the details of each entry.
- "Entries Submitted Successfully" indicates that the "command" to submit an entry is completed.
|
|
17 Dec 2018 | 09:18AM Comment 11 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 17-12-2018 09:18 AM Time Taken: 1.00 |
| Hi Sanjay, Documentation updated on the case - Company Administration - Configuration - Human Resource Management
Thanks Rashna |
|
19 Dec 2018 | 09:43AM Comment 12 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 19-12-2018 09:43 AM |
| Thanks Rashna |
|
09 Oct 2019 | 08:14AM Comment 13 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 |