In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com




Release Notes for Release 4.2.2
QAD CSS Version: 4.2.2
Release Date: September, 2007
MFG/PRO Compatibility: MFG/PRO eB2 SP8+ and eB2.1; QAD Enterprise Applications 2007 (QAD 2007)
Note: Effective with Service Pack 5, MFG/PRO eB2.1 has been renamed QAD 2007. Release Notes references to MFG/PRO also apply to QAD 2007.
Related Documentation: Implementation Guide: QAD Customer Self Service (item 78-0627C); Administration Guide: QAD Customer Self Service (item 78-0619C); Installation Guide: QAD Customer Self Service (item 78-0638C)
These release notes describe the most significant changes and fixes introduced with this version of QAD CSS.
New and Changed Features
1
When the confirmedOrders registry setting is No, payment transactions by credit card are no longer processed. Once the sales order is confirmed, the CSR needs to manually process the payment transaction to create a credit card transaction record.
2
B2B or B2C users can now add selected items to the shopping cart all at once on the Order Entry page. Previously, they could only add one item at a time.
3
The CSS report print function now supports Microsoft Internet Explorer 5.0 and above.
Corrections to Existing Features
1
The system no longer displays the Progress message ERROR: Query failed get first when you perform searches in CSS.
2
The system has been modified to display the Credit Card Details page correctly when the credit card type or credit card vendor is not set up.
3
You can now save credit card vendor details in Credit Card Vendor Maintenance without any credit card type defined. Previously, a Progress error would display.
4
During credit card processing, when QAD CSS fails to communicate with the payment processing server, related sales orders are no longer created in MFG/PRO.
5
Submitted orders are no longer displayed in Uncommitted Orders Report.
6
The system has been modified to process configured items correctly. Previously, sales orders containing configured items could not be properly created in MFG/PRO.
7
QAD CSS has been modified to CIM load sales orders to MFG/PRO for customers on credit hold when Hold Orders Over Credit Limit is No in MFG/PRO Sales Order Control (7.1.24) and Verify GL Account is Yes in Domain/Account Control (36.1).
8
A sales order CIM load failure caused by untrimmed spaces in the ship-to address has been fixed.
9
Mail issues related to the UNIX Sendmail e-mail type have been fixed.
10
The system has been modified to display the item feature page correctly when the item is configurable.
11
The system can now delete sales quotations completely without leaving behind orphan records that may cause duplicate key errors.
12
Item configuration issues caused by special characters in mandatory features of configured items maintained in MFG/PRO have been fixed.
13
Customer upload now works correctly for all fields.
14
The system now correctly displays line-item price, extended price, and line total on the Finish Order page when a price list is associated with the ship-to address.
15
The system has been modified to correctly set base currency, calculate prices, and process sales orders properly in a multi-domain, multi-currency environment.
16
The system now displays a warning message when you enter an existing PO number during order entry. Previously, no warning message was shown when a unique PO number was required but duplicate PO numbers existed.
17
Issues relating to the closing of the pop-up windows in Item Import and Customer Import have been fixed.
18
The installation script has been modified to generate a compile list correctly during installation of QAD CSS 4.2.1 on Windows.
19
The extended price calculation difference between QAD CSS and MFG/PRO due to a pricing decimal limit in QAD CSS has been resolved.
20
The system has been modified to correctly calculate configured item prices in sales orders when the ConfirmOrder registry setting is No.