Published on Monday, 28th Nov 2016
Previously, users could not change the sequence of the Technical Specifications listed under the technical specification tab for any custom catalog product.
A sequence / Order number has been introduced for each spec head in the Technical Specification Details page. The order number field is a dropdown for each item in the technical specification list. Using the dropdown, the user can change the order of the item as per their choice. Any changes in order will be visible on the Store as well as in Back Office.
Now user has the ability to set Credit limit amount for customers in VARStreet. When Credit Limit exceeds the allowed limit, SO will not be converted to PO.
A new approval rule called ‘Credit limit’ has been introduced in Workflows. This helps in sending the sales orders for approval if the ‘Sales Order amount’ + ‘Outstanding Order Amount’ is greater than the Credit limit set for the customer.
Previously, status of bundle in SEWP Contract catalog would not change from ‘Approved’ to ‘Awaiting for Approval’ if its item Description was changed.
The status of bundle will now be changed from ‘Approved’ to ‘Awaiting for Approval’ if it’s SEWP Item Description is changed.
Previously when a Contract Quote CLIN Checker file was generated, it would contain the Bundle Header as well as the bundle components in it.
Now the CLIN Checker file would contain only the Bundle Header and not its components.
Previously an administrator from the parent company could only run the Spend reports
Now a new column called ‘Customer Name’ has been added in both ‘By Transaction’ and ‘By Transactional Details’ Spend Report. The ‘Customer Name’ lists the name of the parent company as well as its child company
Use Case - The new ‘Customer Name’ column will enable the parent company contact to know the transactions details of the child company including the cart status (created, confirmed, and closed) and price, as well as details of the products in the cart.
A new field called ‘Address Line 3’ has been introduced in Credit Card billing address section for payment methods ‘Credit Card’ and ‘Govt. Issued Credit and Purchase card.
Use Case - The new field is introduced to capture the address line 3 of billing address for a Credit card.
Previously when the stock for a product was not available from any vendor, the system would choose the vendor as per the ‘Cost Source’ defined in the price rule.
A new flag called ‘Use maximum cost when no stock available with any vendor’ has been introduced in Price rule. This will ensure that whenever the product is out-of-stock from any vendor, the system will pick the vendor with maximum cost to calculate the price of the product.
Note - ‘Use maximum cost when no stock available with any vendor’ flag will be available only when ‘Stock Available at Cost Source’ flag is checked.
Previously, the Customer/Contact details had to be manually entered/Uploaded from CW into VARStreet (VS).
The process is now automated. A new link called ‘Customer and Contact’ has been added in User Details Page. Clicking on this link will allow the VARStreet admin to synchronize the Customer/ Contact records from ConnectWise (CW) to VARStreet (VS) in bulk.
To access the link go to BO>>Admin>>Users>>User Name>>External System Link>>Synchronize>>Customer and Contact
Use Case - Instead of manually entering or uploading the Customer /Contacts from CW to VS, it can be synchronized from ConnectWise. This will also prevent duplicate records being created from VS to CW.
Previously, the shipping address was being populated as the billing address of the credit card for guest user in the shopping cart.
Now for guest user carts with payment method ‘Credit Card’ or ‘Govt. Issued Credit Card’, the system will not auto-populate the shipping address as the credit card billing address, instead it will allow the user to enter the billing address of the Credit Card which will then be saved as the billing address of the shopping cart and the same will be displayed in the cart confirmation preview page.
The MSRP of configuration product was appearing as zero in the Search Result page.
The issue has now been fixed, the sum of MSRP of the components of the configuration is being shown as the MSRP of the configuration in the Search Result page.