Summary release notes for 2.2.85
released on 1/13/2021
Bug 20368: Bug 20368 - MMI/Purchase Orders: When a Purchase order is created/deleted for a Warehouse, we are not adding the Stock letter to the PO causing discrepancies in qty_to_order and onorder values
Bug 21410: Bug 21410 - QBDI : Importing labor operations attached to an invoice causes error when invalid values are in the description
Bug 21428: Bug 21428 - PIP: When importing a Decisiv order that is created directly from the site, an error occurs
Product Backlog Item 21445: Product Backlog Item 21445: PhaseZero - Add support for default branch tax and forcing branch tax rates
Bug 21496: Bug 21496 - PhaseZero - Increase the Vendor ROID field to fit the PhaseZero Id
Product Backlog Item 21530: Product Backlog Item 21492 - PIP Setup: Add a configuration option for skipping Unit Prompts
Product Backlog Item 21705: Product Backlog Item 21705 - PhaseZero: Add a configuration option for showing Notes on an Invoice
Bug 21706: Bug 21706 - PhaseZero: Orders with a null Transaction Id are coming in as New Orders instead of Sales Orders
Bug 21911: Bug 21911 - Year End: Bringing Unreconciled Deposits/Adjustments forward after Year End leaves Transactions Out of Balance
Product Backlog Item 21916: Product Backlog Item 21916: PhaseZero - When importing a PIP RO Record lookup Customer Name with the Customer Id if no name is provided
Detailed release notes for 2.2.85
_______________________________________________________________
DESCRIPTION:
Bug 20368 - MMI/Purchase Orders: When a Purchase order is created/deleted for a Warehouse, we are not adding the Stock letter to the PO causing discrepancies in qty_to_order and onorder values
APPLICATION: PTM Vision/Purchase orders and Managed Mobile Inventory Application
PROBLEM SUMMARY: When a Purchase order is created/deleted for a Warehouse, we are not adding the Stock letter to the PO causing discrepancies in qty_to_order and onorder values
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
***Testing required only if using the Managed Mobile Inventory Application with PTM Vision; Otherwise, no testing is required***
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access Pluss Mobile Inventory
-
Select the Tools Icon
-
Select Settings
-
In the Branch field, enter a Branch Number
-
In the Warehouse field, enter a Store number that exists in the Branch
-
Select the Tools Icon
-
Select Sign In
-
Enter Username
-
Enter Password
-
Select Sign In
-
Select the Inventory Lookup Tab
-
In the Enter or Scan Inventory Item field, enter a Linepart/UPC/Linecode to Search
-
Select a Linepart from the list, Or, verify the Linepart details are shown
-
Verify the Count button is available
-
-
Select the Count button
-
Verify the Count Item Detail screen is shown
-
-
In the Enter Cycle Count Quantity, enter a value that would Decrease the In Stock Quantity
-
Verify the Update button is not available until a valid value is entered
-
-
Select Ok to the dialog popup that states "Quantity Update Successful: XXXXXX Quantity updated to XX. Continue to PO request"
-
Edit the Quantity to order and select Order
-
Verify a dialog popup is shown that states "Purchase Order Request Successful. XXXXX Requested Quantity to Order : XX. Return to Lookup Item Detail
-
-
Select Ok to exit the Purchase Order Request screen
-
Select the Exit button
-
Access PTM Vision
-
Select P. Purchase Orders
-
Locate the Purchase order created from the Mobile Inventory application
-
Verify the correct Order qty is on the Purchase order
-
-
Select F5. Delete
-
Select Yes to Delete the selected Purchase Order
-
Access the Inventory Item in the Inventory file
-
Verify the correct amount has been removed from the Quantity on Order for the correct Inventory item
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
-
Managed Mobile Inventory Application: Please Contact Pluss Software Sales Department for more information
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=23_1_mmi_setup
DESCRIPTION:
Bug 21410 - QBDI : Importing labor operations attached to an invoice causes error when invalid values are in the description
APPLICATION: PTM Vision/Open Orders
PROBLEM SUMMARY: Importing labor operations attached to an invoice causes error when invalid values are in the description
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
***Testing only required if using the Quickbooks Desktop Integration with PTM Vision; Otherwise, no testing is required***
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select O. Open Orders
-
Select the Work Orders tab
-
Select F2. New Order
-
Enter Customer Account Number
-
In the Input field, enter a Labor operation
-
Select Alt+F7. Print Bill and Close
-
Access the Quickbooks Desktop Integration Overview Application
-
Start the Application
-
Verify the Invoice is successfully sent through the QBDI application without error
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
-
Quickbooks Desktop Application Integration: Please Contact Pluss Software Sales Department for more information
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
DESCRIPTION:
Bug 21428 - PIP: When importing a Decisiv order that is created directly from the site, an error occurs
APPLICATION: PTM Vision/PIP
PROBLEM SUMMARY: When importing a Decisiv order that is created directly from the site, an error occurs
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
***NOTE: Testing required only if using the Decisiv or Aurora FleetPerform Integrations with PTM Vision; Otherwise, no testing is required***
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select the External Actions button
-
Select Orders
-
Line up on the PIP order and select F6. Process
-
Verify no error occurs and the order is successfully generated
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
-
5,58: Pip - Decisiv Partner Integration
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=21_0_integrations
DESCRIPTION:
Product Backlog Item 21445: PhaseZero - Add support for default branch tax and forcing branch tax rates
APPLICATION: PTM Vision
PROBLEM SUMMARY: PhaseZero - Add support for default branch tax and forcing branch tax rates
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
***No testing is required as this is functionality for a future integration with PTM Vision***
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
N/A
DESCRIPTION:
Bug 21496 - PhaseZero - Increase the Vendor ROID field to fit the PhaseZero Id
APPLICATION: PTM Vision
PROBLEM SUMMARY: Increase the Vendor ROID field to fit the PhaseZero Id
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
***No testing is required as this is functionality for a future integration with PTM Vision***
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
N/A
DESCRIPTION:
Product Backlog Item 21492 - PIP Setup: Add a configuration option for skipping Unit Prompts
APPLICATION: PTM Vision/PIP Setup
PROBLEM SUMMARY: Add a configuration option for skipping Unit Prompts
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
***NOTE: Testing required only if using the Decisiv Integration with PTM Vision; Otherwise, no testing is required***
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select Services/Integrations/Partner Integrations/Setup/Orders
-
Line up on the Decisiv setup and select F4. Edit
-
Verify new selections have been added to skip the Unit prompts and skip the Add Unit prompts
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
-
5,58: Pip - Decisiv Partner Integration
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=21_0_integrations
DESCRIPTION:
Product Backlog Item 21705 - PhaseZero: Add a configuration option for showing Notes on an Invoice
APPLICATION: PTM Vision
PROBLEM SUMMARY: PhaseZero: Add a configuration option for showing Notes on an Invoice
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
***No testing is required as this is functionality for a future integration with PTM Vision***
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
N/A
DESCRIPTION:
Bug 21706 - PhaseZero: Orders with a null Transaction Id are coming in as New Orders instead of Sales Orders
APPLICATION: PTM Vision
PROBLEM SUMMARY: PhaseZero: Orders with a null Transaction Id are coming in as New Orders instead of Sales Orders
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
***No testing is required as this is functionality for a future integration with PTM Vision***
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
N/A
DESCRIPTION:
Bug 21911 - Year End: Bringing Unreconciled Deposits/Adjustments forward after Year End leaves Transactions Out of Balance
APPLICATION: PTM Vision/Accounting/Check Register
PROBLEM SUMMARY: Bringing Unreconciled Deposits/Adjustments forward after Year End leaves Transactions Out of Balance
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
NOTE: This only affects PTM Vision after the Year End utility has been ran; for assistance, please contact Pluss Software Support Team***
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
-
Access PTM Vision
-
Select A. Accounting System
-
Select C. Check Register
-
Select the Checking account needed
-
Select Yes to bring forward Beginning balance, if prompted
-
Select F6. Options/A. Import Unreconcile Previous Year
-
Select Yes to the prompt that states "Check for unreconciled checks in previous year?: XXXX"
-
Verify any Adjustments/Deposits brought forward are in balance
-
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
http://help.pluss.co/help/PTM%20Vision%20Help/default.aspx?pageid=Welcome#pageid=reconciling_checks_
DESCRIPTION:
Product Backlog Item 21916: PhaseZero - When importing a PIP RO Record lookup Customer Name with the Customer Id if no name is provided
APPLICATION: PTM Vision
PROBLEM SUMMARY: PhaseZero - When importing a PIP RO Record lookup Customer Name with the Customer Id if no name is provided
<<-------------------------------------*SETUP INSTRUCTIONS*------------------------------------>>
N/A
<<--------------------*HOW TO VERIFY THAT PROBLEM IS FIXED*----------------------->>
***No testing is required as this is functionality for a future integration with PTM Vision***
<<------------*SYSTEM FEATURES UTILIZED BY THIS MODIFICATION*-------------->>
N/A
<<----------------------------*SPECIFIC DOCUMENTATION*------------------------------------->>
N/A