Company: Link Technologies
Case No: L08666. Project: 08.20: LinkSOFT Version 8.2
Logged By: Rashna (Edge Business Solutions) on 11 Jul 2017 06:44AM
Priority: Low
Product: Point of Sale
Group: Enhancement
Time Taken: 7.00 (Weight: 7.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna
Resolve By: Wednesday, 12 July 2017 12:00 AM [2475 days since logged date]
Status: Closed
Subject: Disallow system to save blank reference numbers.
Summary:    

Hi Team, 

POS configuration allows users to save  blank reference numbers.

For example , user edits the "Next Number" for Receipts and sets the value to blank.

 When processing transactions, the transactions are not successfully completed.

Below is the error we get.

Improvement disallow saving of blank reference numbers.


Audit Notes:
11 Jul 201710:59AM Comment 1 by Alvis (Link Technologies) Case 8666 added to project 8.14
11 Jul 201711:05AM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 11-07-2017 11:05 AM

Enforce NextNumbers to have a specific format in the global configuration:

  1. Minimum length = 4: 0001 is acceptable
  2. Max length = 16

Regards

Rashna/Alvis/Sanjeet/Sanjay


12 Jul 201711:21AM Comment 3 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 12-07-2017 11:21 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): 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):|

  1. Minimum of 4 and maximum of 16 characters validation has been added to all next number configurations

14 Jul 201702:54PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 14-07-2017 02:54 PM Time Taken: 1.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.

Test Plan 

Item Number 6 Failed.

Step to Replicate

  1. Under Global set Next Quotation Number and Next POSCash Adjustment number as AP01.
  2. Create a Quotation
  3. Process a Cash In - Cash in not completed.
  4. Error 



Table 1 - Summarised list of issues
NoIssue Description Resolved? 
1 Users could save blank reference numbers Yes 
2 Users can save duplicate reference number (tested in 814) 
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 201703:23PM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 14-07-2017 03:23 PM
    Case Reopened for Test 

    14 Jul 201704:18PM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 14-07-2017 04:18 PM Time Taken: 2.00

    Hi ALvis, 

    Case has failed, refer to comment 4 for details.


    14 Jul 201705:35PM Comment 7 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 14-07-2017 05:35 PM Time Taken: 1.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): No
    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. Added validation for reference numbers to check if the value has been assigned to any other configuration. This will prevent users from saving the same value in two different configurations.

    15 Jul 201712:30PM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 15-07-2017 12:30 PM Time Taken: 1.00

    Hi Alvis, 

     I have tested the case , we can still enter duplicate reference number under global.

    Refer to Figure 1 for fields with ZZ001

    Regards
    Rashna 


    15 Jul 201703:35PM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 15-07-2017 03:35 PM

    Hi Rashna

    This is ok because the values are used in different areas. eg next doctor number can be the same as next customer number.

    regards

    Alvis


    17 Jul 201703:10PM Comment 10 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 17-07-2017 03:10 PM Time Taken: 1.00

    Hi Team, 

    As per comment 9, we have verified, next transaction numbers that are in LBS_POS_Order are verified.

    This case is now closed.

    Regards
    Rashna 


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

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