Company: Link Technologies
Case No: L08759. Project: 08.20: LinkSOFT Version 8.2
Logged By: Rashna (Edge Business Solutions) on 16 Aug 2017 02:07PM
Priority: High
Product: Point of Sale
Group: Software Defect
Time Taken: 2.00 (Weight: 2.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Rashna, Sanjay
Resolve By: Thursday, 17 August 2017 12:00 AM [2439 days since logged date]
Status: Closed
Subject: "Label No" is not generated with "Non Prescription Labels"
Summary:    

I have tested the case in 816 in QA1 with database LINKSOFT.

Steps to Replicate

  1. Open "Non Prescription Label" in POS.
  2. Enter the Medication Names, Instruction, Expiry Date, Price and Save the record. Label No is generated here.
  3. Search and load the label again.
  4. Click on New.
  5. Enter the Medication Names, Instruction, Expiry Date, Price and Save the record.. Label No is "NOT" generated 
Audit Notes:
17 Aug 201709:25AM Comment 1 by Alvis (Link Technologies) Case 8759 added to project 8.17
17 Aug 201710:42AM Comment 2 by Alvis (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 17-08-2017 10:42 AM

Hi Sanjay

  1. When a non-prescription label is loaded, then NEW is clicked, the system saves the new record to the loaded label.
  2. When a non-prescription is loaded, the system logs an error message as shown below:

    exec LT_SYS_Log_INSERT @sUser=N'Alvis',@sModule=N'mscorlib',@sMsg=N'Message: Value cannot be null.
    Parameter name: path BaseException: System.ArgumentNullException: Value cannot be null.
    Parameter name: path
       at System.IO.Path.GetFullPathInternal(String path)
       at System.IO.Path.GetFullPath(String path)
       at System.Drawing.IntSecurity.UnsafeGetFullPath(String fileName)
       at System.Drawing.IntSecurity.DemandReadFileIO(String fileName)
       at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
       at System.Drawing.Image.FromFile(String filename)
       at LBS.LINKPOS.UI.TransactionFind.TransactionFind_Load(Object sender, EventArgs e)',@sStatus=N'Error',@Log_Data=NULL,@sMachine=N'LINKSQL',@T1=N'Alvis',@T2=NULL,@T3=NULL,@N1=NULL,@N2=NULL,@N3=NULL,@CFD=N'T1:UserName'



17 Aug 201702:52PM Comment 3 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 17-08-2017 02:52 PM Time Taken: 1.00
Sanjay has resolved this issue in 8.17

21 Aug 201701:36PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 21-08-2017 01:36 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 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below.

Case tested in QA1 with 817 Beta 1.

Table 1 - Summarised list of issues
NoIssue Description Resolved? 
1 Users should be able to create and save "Non Prescription label". This should generate a label number Pass
2 Users should be able to enter details and print labels. This should generate a label number Pass
3 Users should be label to search and load a label, and new a new label over it.This should generate a label number  Pass
4 At print, the "Print Count" is the number of the labels to print  Pass
5Entering data and clicking on "New or Close" should clear entry. No label number should be generated.  Pass

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 case

    09 Oct 201908:14AM Comment 5 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: L08759 in the subject line of all emails regarding this issue.

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