| Subject: | "CASH" records disappears from "current pay" when editing pay from "Manual Edit" screen |
| Summary: | Hi Sanjay, We have tested the case in 815 DEV003. Setup is in QA1 with Database LINKSOFT. See details for Employee E068. Payrun ID 455. When editing pay details from menu 334-1-2 "CASH" component from Normal Pay is deleted from the system. Steps To Replicate. - Create Normal pay from menu 332-1 for Employee E001. Set "Pay Scheme" as "CASH".
- Open the pay on menu 334-1-2.
- The Cash component is removed from the pay details.
|
| Audit Notes: | |
| 26 Jul 2017 | 10:30AM Comment 1 by Alvis (Link Technologies) Case 8713 added to project 8.15 |
| 26 Jul 2017 | 12:10PM Comment 2 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 26-07-2017 12:10 PM Time Taken: 2.00 |
| Development work for this case has been completed. The change will be available in version: 8.15 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):| - Changed manual pay screen to recompute banking using the same function as used in current pay screen.
- Added disabled color for "read only" fields
- Removed all computations code from manual pay screen and moved it to use SQL procedures.
|
|
| 26 Jul 2017 | 03:12PM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 26-07-2017 03:12 PM 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 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. - Changed manual pay screen to recompute banking using the same function as used in current pay screen - Pass
- Added disabled color for "read only" fields - Every component on manual pay is editable.Manual pay nothing is greyed at the moment, can state example which could be read only field
- Removed all computations code from manual pay screen and moved it to use SQL procedures. Verified calculations were correct
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
|
|
| 27 Jul 2017 | 08:00AM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 27-07-2017 08:00 AM Time Taken: 1.00 |
| Corrected issue with read-only fields to display as grayed out. please test in beta3. |
|
| 27 Jul 2017 | 09:12AM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 27-07-2017 09:12 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 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below. Added disabled color for "read only" fields - All Pay codes with classification as "Banking" is read only on the screen.
Table 1 - Summarised list of issues | No | Issue Description | Resolved? | | 1 | All components from the current pay should be opened on the manual edit screen | Pass | | 2 | Cash and Bank are read only and should recompute when other components paid amount is altered | Pass | | 3 | When users enter an additional pay code, the banking amounts should recompute. | Pass | | 4 | Banking amount should reconcile with banking report | Pass |
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 6 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 |