Subject: | Business rules when managing invoices and payments using LinkWEB and LinkPOS | Summary: | PART A - Incomplete transactions in LinkWEB The following business rules apply when using LinkWEB in combination with LinkPOS: - If an invoice is created in LinkWEB and payment is taken in LinkWEB, we do not allow you to load this transition in LinkPOS and complete this sale. You must complete this transition in LinkWEB
- If an invoice is created in LinkWEB and NO payments are taken in LinkWEB, we allow you to load this transition in LinkPOS and complete this sale.
- If a payment for an invoice is taken in LinkWEB and the transaction is not completed, we do not allow the shift to be closed with the "Payment Method" in question, however, you can do a "Partial Close" of any payment method that does not have incomplete transactions in LinkWEB
We recognize that the above issue only happens when the LinkWEB user has an OPEN shift in LinkPOS which is an unusual circumstance. PART B - POS Transaction Date and Time We also found some issues relating to the Transaction Date. Issue: When the user is NOT allowed to change the transaction date, the transaction date is refreshed every second and all is good. When the user is allowed to change the "transaction date", the "transaction date" does NOT Refresh and the transaction is saved with an incorrect Date Time. Proposed Change: - We define the "transaction date" as the Date/Time when the transaction is Saved.
- If the user has changed the Date for the current transaction, we use the changed date. Otherwise, we use the date the "Save " button is pressed.
- When a sale is completed, the Transaction date is refreshed and the time keeps incrementing
- Allow the user to set a Date and Time instead of just the date.
Known issues/Workarounds with this method: - We recognize that if an item is scanned today, and left on the screen until tomorrow, the transaction date will be recognized as today's date.
- If the user has access to change the transaction date, the user must scan an item, then change the transaction date.
in both cases above, we recognize that these are exceptional circumstances and the workaround allows us to maintain the old functionality yet resolves the current date-time issue.
| Audit Notes: | Edited by sanjay on 11/02/21 14:10. Edited by sanjay on 10/02/21 17:01. Edited by sanjay on 10/02/21 16:04. Edited by alvis on 10/02/21 15:37. Edited by sanjay on 10/02/21 15:17. Edited by sanjay on 10/02/21 15:06. | 10 Feb 2021 | 03:27PM Comment 1 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 11-02-2021 03:17 PM Time Taken: 24.00 Notes: Edited by sanjay on 10/02/21 16:58. Edited by sanjay on 10/02/21 16:55. | | PART A - Development work for this case has been completed. 1. The change will be available in version: 12.30.0210 2. The following changes were made(Include Database object names, Program classes, and any other relevant information): - PART A items completed
- If an invoice is created in LinkWEB and payment is taken in LinkWEB, we do not allow you to load this transition in LinkPOS and complete this sale. You must complete this transition in LinkWEB
- If an invoice is created in LinkWEB and NO payments are taken in LinkWEB, we allow you to load this transition in LinkPOS and complete this sale
- If a payment for an invoice is taken in LinkWEB and the transaction is not completed, we do not allow the shift to be closed with the "Payment Method" in question, however, you can do a "Partial Close" of any payment method that does not have incomplete transactions in LinkWEB
- PART B Items completed
- If a user changes the Transaction Date, this date is used. Once the current transaction is saved, the time reverts to automatic
- "Transaction Date" is recorded when the current transaction is Saved
- Added Date and Time portion to the "Transaction date"
3. Affected Areas: - LinkWEB and LinkPOS - Transaction Date Definitions
4. The issue was caused by: - New Feature
5. Notes: 6. Next Step: System Test and UAT ---------------------- PART B - Development Reference: 1. Changes implemented was according to the approved design (Y/N): Y 2. Variations to the approved design: |
| 10 Feb 2021 | 05:01PM Comment 2 by Sanjay (Link Technologies) ETC was changed from 12/02/2021 to 12/02/2021 | 12 Feb 2021 | 01:24PM Comment 3 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 16-02-2021 01:23 PM Time Taken: 1.00 | | Hi Rashna, proceed with UAT |
| 12 Feb 2021 | 03:08PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 16-02-2021 02:59 PM Time Taken: 1.00 | | QA Results Tests carried out according to requirements specified on the case header Test Results Summary Table 1 - Summarised list of issues No | Test Description | Pass/Fail | 1 | If an invoice is created in LinkWEB and payment is taken in LinkWEB, we do not allow you to load this transition in LinkPOS and complete this sale. You must complete this transition in LinkWEB. - Create a cash sales for customer 0003.
- Sale Amount - 10
- Payment Amount - 10
- Load transaction in LinkPOS, this should not be loaded
| Pass | 2 | If an invoice is created in LinkWEB and NO payments are taken in LinkWEB, we allow you to load this transition in LinkPOS and complete this sale - Create a credit sales for customer 0003.
- Sale Amount - 10
- Payment Amount - 0
- Load transaction in LinkPOS, the transaction should be loaded. Process payment of $5.00
- Add another payment of $5.00 from the web.
- Load transaction in LinkPOS,no further payment should be allowed
| Pass | 3 | If a payment for an invoice is taken in LinkWEB and the transaction is not completed, we do not allow the shift to be closed with the "Payment Method" in question, however, you can do a "Partial Close" of any payment method that does not have incomplete transactions in LinkWEB - Create a credit sales for customer 0003.
- Sale Amount - 10
- Payment Amount - 5
- Close shift. This should not be allowed.
- Submit and Print transaction in 1 above.
- The close shift should be closed
| Pass | 4 | If a user changes the Transaction Date, this date is used. Once the current transaction is saved, the time reverts to automatic - Change the transaction date from 12/02/2021 to 15/02/2021.
- Transaction date should be 15/02/2021.
| Pass | 5 | "Transaction Date" is recorded when the current transaction is Saved
| Pass | 6 | Added Date and Time portion to the "Transaction date" Save a transaction validate that the time is updated with the server time | Pass |
Environment Details - OS version: Windows Server 2012
- Application version: 12.30.0211 GA
- Setup: Demo
- Server : 10.0.0.14
- Database: LINKSOFT-DEMO-123
Next Step: - For Closure
|
| 12 Feb 2021 | 04:23PM Comment 5 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 16-02-2021 04:23 PM Time Taken: 1.00 Notes: Created from the WEB using email sent to: sanjay@linktechnologies.com.au | | Thanks Rashna |
|
|