Company: Link Technologies
Case No: L08662. Project: 08.20: LinkSOFT Version 8.2
Logged By: Fariha Kauser Tafsil (Link Fiji) on 08 Jul 2017 08:32AM
Priority: High
Product: Payroll & HR
Group: Enhancement
Time Taken: 1.50 (Weight: 2.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Fariha Kauser Tafsil, Rashna
Resolve By: Monday, 10 July 2017 12:00 AM [2456 days since logged date]
Status: Closed
Subject: Remove CNB as the "Bank Code" for BSP in new LINKSOFT database.
Summary:    

Hi Sanjay,

In new LINKSOFT database, when users create the bank BSP, the default "bank code" on 311-1 automatically is CNB.

CNB is not a valid bank in FIJI. Hence, when we generate the bank file, the bank files are not generated correctly. This causes support cases.

Can we remove, CNB from the "Bank code" on the system?

Also requesting for other banks such as HFC, Bred Bank to be added to the Bank list so users do not have to enter the banks when they are setting up their current and future organizations.

Please if you could address these enhancements.

Regards,
Fariha

Audit Notes:
11 Jul 201708:31AM Comment 1 by Alvis (Link Technologies) Case 8662 added to project 8.14
14 Jul 201711:40AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-07-2017 11:40 AM Time Taken: 1.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): No
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):|

  1. Changed new database script:
    1. Removed CNB
    2. Changed BSP to use BSP bank instead of CNB
    3. Added HFC bank and pay code
    4. Added BRED Bank and pay code

14 Jul 201704:09PM Comment 3 by Fariha Kauser Tafsil (Link Fiji) Assigned To: Sanjay (Link Technologies) Followup Date: 14-07-2017 04:09 PM Time Taken: 0.50
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
NoIssue Description Resolved? 
1 The default "bank code" in 311-1 for BSP is automatically set to CNB Yes 
2  
3  
4  
5  
6  
7  
8  
9  
10  
11  
12  

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 to MD to release patch

    14 Jul 201704:44PM Comment 4 by Fariha Kauser Tafsil (Link Fiji) Assigned To: Sanjay (Link Technologies) Followup Date: 14-07-2017 04:44 PM
    Case incorrectly assigned, closing case now.

    If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L08662 in the subject line of all emails regarding this issue.

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