Company: Link Technologies
Case No: L08707. Project: 08.20: LinkSOFT Version 8.2
Logged By: Vineet (Link Business Solutions) on 25 Jul 2017 09:40AM
Priority: High
Product: Payroll & HR
Group: Software Defect
Time Taken: 6.00 (Weight: 6.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Rashna, Sanjay, Vineet
Resolve By: Thursday, 27 July 2017 12:00 AM [2467 days since logged date]
Status: Closed
Subject: FPAYE component disappears from Standard Pay Entries Screen as soon as user presses Save
Summary:    
1. Description: 
     The FPAYE pay code disappears from the standard pay edit menu 329-4 as soon as user loads employee and click on the Save icon. This was replicated on:

Application Version: 8150.000.DEV01
Server:                     LINKQA1
DB:                          LINKSOFT

2. Environment Details

Machine Name
 LINKQA1
User name:
 manager
Operating System:
 Win7 Professional
Browser name/Version:
 
Other 
3. Steps to recreate
  1. For employee E0068, set pay rate as 290,000 per annum
  2. Create standard pay for this employee
  3. Load employee E068 on menu 329-2
  4. Click on the save icon
Note: FPAYE component will disappear.

4. Current Behaviour:
     FPAYE disappears when user click on Save icon at Standard Pay Edit Menu.
5. Expected Behaviour:
     FPAYE should give standard PAYE on menu 329-2
-----------------------------------------------------------------------
--- TO BE COMPLETED AFTER THE CASE HAS BEEN RESOLVED ---
Has the problem been solved?:

Steps taken to resolve the issue:

Has the final solution review been done with the customer? (Yes/No)  Notes from discussion with customer:

Audit Notes:
25 Jul 201710:49AM Comment 1 by Alvis (Link Technologies) Case 8707 added to project 8.15
25 Jul 201705:28PM Comment 2 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 25-07-2017 05:28 PM Time Taken: 4.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): Yes
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):|

  1. Changed standard pay screen to show all deductions, allowances, and benefits setup for the employee. These records are read only in the standard pay screen.
  2. If a record is edited in deductions, allowances and benefit screen then when the employee is loaded on standard pay, the system will recalculate the values.
  3. Calculations for super, tax, and banking includes the records in 1.above.



26 Jul 201708:52AM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 26-07-2017 08:52 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.

All pay codes remain on the screen at save and refresh.

  1. Changed standard pay screen to show all deductions, allowances, and benefits setup for the employee. These records are read only in the standard pay screen.- Deduction, Allowance and Benefits are grayed out 
  2. If a record is edited in deductions, allowances and benefit screen then when the employee is loaded on standard pay, the system will recalculate the values. - Pass
  3. Calculations for super, tax, and banking includes the records in 1.above.- Pass
Figure 1: Standard Pay 


WORKFLOW:
  1. Original case assigned to Development
  2. When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
  3. If system test passes, assign case to Consulting Manager for UAT
  4. If UAT Passes, Assign case for Documentation or close cas

    09 Oct 201908:14AM Comment 4 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
    If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L08707 in the subject line of all emails regarding this issue.

    Document size: 8.4 KB
    For call complaints, please contact the Managing Director of the company using this form.