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  |   Cloud ERP  |   Home  |

  •     QAD Glossary

  • Release Notes for Release 4.2.3
    QAD CSS Version: 4.2.3
    Release Date: April, 2009
    QAD Product Suite Compatibility: eB2.1 SP2 through SP4, QAD 2007, QAD 2007.1, QAD 2008 Standard, QAD 2008.1 Standard
    Note: During the product life cycle, QAD changed the name of the former MFG/PRO eB2.1 product to QAD 2008 Standard. Individual releases of QAD 2008 Standard are identified by a decimal number; for example, QAD 2008.1 Standard. (The Service Pack 5 and 6 releases were branded as QAD 2007 and QAD 2007.1, respectively.) The Enterprise Financials version of the product is called QAD 2008 Enterprise and follows the same convention of identifying individual releases with a decimal number.
    These release notes describe the most significant changes and fixes introduced with this version of QAD CSS:
    QAD CSS now commits sales orders to the QAD ERP database through an API instead of CIM loading. Also, sales order field mapping has changed in this release.
    The PUK column name in Data Translation Report is changed to Primary Unique Key to be more intuitive.
    Credit Card Security Code (CSC) can now be provided during credit card payment in QAD CSS. This code is a three or four-digit number that appears on the credit card and provides a cryptographic check of the information embossed on the card.
    Invoice Date From/To and Order Date From/To fields are added as additional search criteria in Internal Invoice History Report.
    The showDeliveryIcon system registry has been modified to determine whether the Delivery icon for calculating the promise or due date is displayed in the Shopping Cart summary page.
    This release of QAD CSS includes a new context-sensitive help system; as a result, the Help Maintenance module is now obsolete.
    The Add and Delivery buttons are now displayed in their respective columns in the item list.
    The defaultCustomerProfile has been modified to support multiple values delimited by comma, each representing a default B2C user in a particular domain. This way, you can have a single B2C site support multiple domains by passing different default B2C user IDs to the CSS through the B2CURLParameter parameter.
    When multiple-domain support is enabled in CSS, the defaultSite, defaultShipVia, and defaultTimeZone registry settings are not used. Instead, the defaultCustomerProfile value is used to create the B2C customer data when an order is submitted.