Company: Link Technologies
Case No: L08408. Project: 08.20: LinkSOFT Version 8.2
Logged By: Vineshwar Prasad (Edge Business Solutions) on 15 Mar 2017 10:20AM
Priority: High
Product: Point of Sale
Group: Change Request
Time Taken: 10.00 (Weight: 10.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: AwaitingApproval, Development, Rashna, Vineet, Vineshwar Prasad
Resolve By: Thursday, 16 March 2017 12:00 AM [2592 days since logged date]
Status: Closed
Subject: Cashier's Shift to open based on Header Location
Summary:    
Bula Vinaka Team,

Currently the configuration is set at menu 222 where the default location of cashier's are set. If the Cashier log's in at a different location, she will still log in at the specified location set at menu 222.

Therefore, if a cashier log's in at any location, the shift should open based on the Header Location.

Regards
Vineshwar Prasad
Application Consultant


Audit Notes:
15 Mar 201711:04AM Comment 1 by Alvis (Link Technologies) Case 8408 added to project 8.10.001
20 Mar 201703:40PM Comment 2 by Sanjay (Link Technologies) Assigned To: Vineshwar Prasad (Edge Business Solutions) Followup Date: 20-03-2017 03:40 PM Time Taken: 2.00

Hi Vineet, what is the justification for this change?

Can you answer the following questions:

  1. How does the user know which shift the location was created in? Do we show this next to the shift number?
  2. Which reports are the users having a problem with?
  3. What happens if a shift is created in a location and the default location is changed?
  4. What happens if default location is not setup? The shift is still created for payments and other administrative transactions.

Regards
Sanjay/Alvis


20 Mar 201704:09PM Comment 3 by Alvis (Link Technologies) Case 8408 removed from project 8.10.001
09 May 201709:32AM Comment 4 by Rashna (Edge Business Solutions) Assigned To: AwaitingApproval Followup Date: 10-05-2017 12:00 AM Time Taken: 2.00
Hi Team ,

Below are the analysis for comment 2

  1. How does the user know which shift the location was created in? Do we show this next to the shift number?
    • Currently users do not know, they only know the location that they are based at. 
    • No, shift number remains the same.
  2. Which reports are the users having a problem with?
    • We have identified the below. Can we verify the other reports that use default location from 222 via SQL.
      • Shift Report (80mm width)
      • Cashier Reconciliation 
  3. What happens if a shift is created in a location and the default location is changed?
    • We tested  that changing the default location does not have any effect. Tested in  version 811. This is because shift is already open. Lbs_pos_shift only updates the "branch field" every time a new shift is open. Changes to location during shift  is not saved in the database.
  4. What happens if default location is not setup? The shift is still created for payments and other administrative transactions.
    • We tested the scenario in 811. if user does not have default location set on 222. The mentioned report in 2 do not populate data for any locations from  512.
Regards
Vineet/Vinesh and Rashna

09 May 201711:01AM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 09-05-2017 11:01 AM Time Taken: 1.00

Development meeting. Agreed to change the following:

  1. When a new shift is opened, the location and number sequence should pick from the logged in the default location.

09 May 201711:01AM Comment 6 by Alvis (Link Technologies) Case 8408 added to project 8.13
14 Jun 201703:22PM Comment 7 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 14-06-2017 03:22 PM Time Taken: 2.00
Development work for this case has been completed.
The change will be available in version: 8.13
Documentation update required(Yes/No. Add change details below)
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 shift open process to pick location from the POS default location configuration. This location is then used to get the next sequence number of shift.

Documentation details:
  

03 Jul 201703:22PM Comment 8 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 03-07-2017 03:22 PM Time Taken: 1.00
System test completed, please proceed with UAT. 

05 Jul 201710:22AM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 05-07-2017 10:22 AM Time Taken: 2.00
1. Was this test completed using Demo / New / Other database? Demo with 813 Beta 1 in QA1.
2. Did the test pass or fail? Pass
3. Tab order, spelling, alignment, font size consistency, screen size etc checked? N/A
4. Data verified, saved, edit, delete/void? N/A
5. Documentation update required? No
Additional Details (Risks, issues, special conditions required for this test to pass etc):

The following test was done

Test Case 1

  • Created Cashier 1, did not set any location on 222.
  • Default location on POS was BRANCH1.
  • Process Sales
  • Successfully generated following reports
    • shift Report 80*80
    • Cashier Reconciliation
    • Transaction report
    • Sales by product
    • Sales Summary


Test Case 2
  • Created Cashier 1, set location on 222 as BRANCH2
  • Default location on POS was BRANCH1.
  • Process Sales
  • Successfully generated following reports
    • shift Report 80*80
    • Cashier Reconciliation
    • Transaction report
    • Sales by product
    • Sales Summary



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

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