375
Summary release notes for 2.2.132
released on 11/17/2021
Bug 17420: Bug 17420 - Purchase Orders: Able to remove Vendor code from Purchase Order after a PO# is assigned
Bug 23388: Bug 23388 - Purchase Orders/Deleted PO Log: When a part is back ordered, we are logging a deletion in the PO deletion log
Product Backlog Item 23552: Bug 23552 - PTM Vision : Ensure that all instances of Plusspay TransactionIDs are updated to handle long integers
Detailed release notes for 2.2.132
_______________________________________________________________
DESCRIPTION:
Bug 17420 - Purchase Orders: Able to remove Vendor code from Purchase Order after a PO# is assigned
APPLICATION: PTM Vision/Purchase Orders
PROBLEM SUMMARY: Able to remove Vendor code from Purchase Order after a PO# is assigned
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select P. Purchase Orders
-
Select F2. New
-
Enter a Linecode, qty, and a valid supplier
-
Select Ok to create the PO
-
Select O to order the part and assign a PO#
-
Select F4. Edit on the PO
-
Tab down to the Vendor field
-
Use backspace to delete the text from the Vendor field
-
Verify the Vendor code has not been removed from the Purchase Order
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=purchase_orders
DESCRIPTION:
Bug 23388 - Purchase Orders/Deleted PO Log: When a part is back ordered, we are logging a deletion in the PO deletion log
APPLICATION: PTM Vision/Purchase Orders/Deleted PO Log
PROBLEM SUMMARY: When a part is back ordered, we are logging a deletion in the PO deletion log
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select O. Open Orders
-
Select the Work orders tab
-
Select F2. New
-
Enter Customer account info
-
In the Input field, enter a non-inventory part number
-
Select X to access Item details
-
Enter a Desc, Qty, and Cost
-
Select Ok to save
-
Select Yes to back order
-
Enter a valid supplier and select OK
-
Select F11. PO
-
Select Select O to order
-
Select R to receive
-
Select F8. Process
-
Select Yes to add to payables
-
Return to the order
-
Select Alt+F7. Print bill and Close
-
Access PO's again
-
Verify the back ordered part is not shown in the log
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=purchase_orders
DESCRIPTION:
Bug 23552 - PTM Vision : Ensure that all instances of Plusspay TransactionIDs are updated to handle long integers
APPLICATION: PTM Vision
PROBLEM SUMMARY: PTM Vision : Ensure that all instances of Plusspay TransactionIDs are updated to handle long integers
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select O-Open Orders
-
Select a WorkOrder from the list with a Total greater than zero
-
Verify the Terms are Cash
-
Select Alt+F7-Print Bill/Close
-
Select C-Pay by Credit Card
-
Select A-Use Web Pay or B-Use Cloud Terminal. Process Credit Card
-
Upon Approval, the TransactionID data returned does not error due to the length.
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
