| Subject: | Incorrect TNA processing with odd sign in and signout |
| Summary: | Hi Team, The TNA time is not correctly processed when a time has been modified. This has been replicated in QA1 with 813 Beta 1. This has been identified as the current step up with IGA. Setup is as below - At the device level, the processing mode is "Import and Submit".
- No rules are enabled under "Timesheet Rules".
Steps - Import time for employee E001 as below.
- At 1 pm the supervisor edited the time for employee E001. The "In" time was modified to 8.00am for 04/07/2017. The Status, for the entry, is now "Modified". Refer to Figure 1. The time for 03/07/2017 is a valid entry.
- Employee E001 now signed out at 5.21pm on 04/07/2017. This out time was added to the "Valid" time under 03/07/2017.
Figure 1: Modified time for 04/07/2017. 
Figure 2. Out time for 04/07/2017, created under the valid entry for 03/07/2017. 
|
| Audit Notes: | |
| 05 Jul 2017 | 10:56AM Comment 1 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 05-07-2017 10:56 AM Time Taken: 2.00 |
| Scenario 1 - Employee has only a sign OUT for a day. Employee does not have any IN
- Example 03/07/2017 , Out at 5.21pm.
Expected Result - Create an Timesheet with the OUT time and status ad INVALID. Scenario 2 - Employee signed IN on the 04/07/2017. There is not sign out for 04/07/2017. Employee directly signs out on the 05/07/2017.
- Example
- IN - 04/07/207 at 8.00am
- OUT - 05/07/2017 at 5.30pm
Expected Result - Using the config "TimesheetImport.MaximumHours", split the time entry.
If duration is less than the value set at "TimesheetImport.MaximumHours" , than entry will be one complete entry.
If duration is more than the value set at TimesheetImport.MaximumHours", than split the entry into different time entries.
Scenario 3 Scenario 5 - Employee signed IN and OUT on the 04/07/2017.
- On 05/07/2017, there is a sign IN. Time is Modified.
- Employee signs OUT after time has been modified.
- Example
- IN - 04/07/207 at 8.00am
- OUT - 04/07/2017 at 5.30pm
- IN - 05/07/2017 at 7.15am, Modified to 8.00am
- OUT- 05/07/2017 at 5.30pm
Expected Result - Create an Timesheet with the OUT time and status ad INVALID for 05/07/2017.
|
|
| 11 Jul 2017 | 10:49AM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 11-07-2017 10:49 AM |
| Hi Rashna/Alvis, please come up with a design for the development team to approve. Regards
Sanjay |
|
| 11 Jul 2017 | 10:49AM Comment 3 by Alvis (Link Technologies) Case 8644 added to project 8.14 |
| 11 Jul 2017 | 01:36PM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 11-07-2017 01:36 PM |
| Design change from the discussion between Rashna, Vineshwar, and Alvis: - Create a new timesheet entry when there is only 1 out
- Create a new timesheet entry for consecutive out entry
|
|
| 11 Jul 2017 | 04:18PM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 11-07-2017 04:18 PM Time Taken: 2.00 |
| Development work for this case has been completed. The change will be available in version: 8.14 Documentation update required(Yes/No. Add change details below): Yes QA required(Yes/No.Include areas that require testing): Yes
The following changes were made(Include Database object names, Program classes and any other relevant information):| - Changed the time computation process to create a separate time entry when there are consecutive "out" entries or just 1 "out" entry for the day.
Documentation details: - Create a new timesheet entry when there is only 1 out
- Create a new timesheet entry for consecutive out entry
Note: Please test scenarios using actual and buffer setup |
|
| 15 Jul 2017 | 02:39PM Comment 6 by Vineshwar Prasad (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 15-07-2017 12:00 AM Time Taken: 2.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 3 - Sanjay to release patch only after steps 1 and 2 are completed successfully. STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | Scenario 2 Failed. System does not calculate time based on the maximum hour configuration of 19 hours. | | | 2 | Employee ID : E071 | | | 3 | Setup QA3. Database : LINKSOFT & TNA | | | 4 | | | | 5 | | | | 6 | | | | 7 | | | | 8 | | | | 9 | | | | 10 | | | | 11 | | | | 12 | | |
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 to MD to release patch
|
|
| 17 Jul 2017 | 09:32AM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 17-07-2017 09:32 AM Time Taken: 2.00 |
| Development work for this case has been completed. The change will be available in version: 8.14 beta 2 Documentation update required(Yes/No. Add change details below): QA required(Yes/No.Include areas that require testing): Yes
1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Corrected time computations for normal hours when a shift uses a specified time setting to compute normal, time half and double.
|
|
| 17 Jul 2017 | 05:51PM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 17-07-2017 05:51 PM Time Taken: 2.00 |
| Hi Alvis, We have tested the case with 814 Beta 2 in QA3. We enabled the rule - 'Mark entries exceeding maximum hours configuration as invalid'.
The TimesheetImport.MaximumHours was to 19.
The Normal Hours was correctly calculated as 8 hours. 2 hours was under time and a half and 22 hours was in double time. This time entry was marked as "Invalid" which is correct.
All the scenarios mentioned on the case has passed.
Regards
Vineshwar and Rashna |
|