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 5.0.1
    QAD CSS Version: 5.0.1
    Release Date: June, 2009
    QAD Product Suite Compatibility: QAD 2008 Enterprise, QAD 2008.1 Enterprise, QAD 2009 Enterprise
    Documentation Updates
    The following documentation has been updated for this release:
    Installation Guide: QAD Customer Self Service (78-0666B)
    New and Changed Features
    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.
    The Add and Delivery buttons are now displayed in their respective columns in the item list.
    The defaultCustomerProfile registry 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 CSS through the B2CURLParameter value.
    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.
    The Verisign credit card API has been replaced by the Paypal credit card API.
    CSS now supports QDoc version ERP3_2 instead of 2008_2.
    QDoc name and QDoc version are now configurable so that CSS can work with the most current QXtend version.
    The following issues have been fixed in this release of CSS:
    Entering over eight lines of comments during the order entry process causes system performance issues.
    No error message appears when the user types a wrong user ID/password combination in the Login Register page.
    The shopping cart sometimes shows a blank page with only header and footer.
    The empty feature is not displayed in the configuration page.
    Setting Up Default B2C Users for Multiple Domains
    QAD CSS now lets you set up a site to support multiple domains. The steps for setting up the default B2C user have changed.
    Set up a customer in QAD ERP that represents the generic B2C customer. Any B2C user that logs in to the CSS site will default to this customer.
    If you are implementing a B2C site that supports multiple QAD ERP domains, you must create the default B2C customer for each domain in QAD ERP.
    For detailed information about setting up customers in QAD ERP, see User Guide: Financials A.
    In Customer Create (, create the default B2C customer record and related financial data.
    Use the guidelines in the following table in addition to the information provided in User Guide: Financials A when creating the customer.
    Customer Code
    You should create a new ID in that will not be used for any other purpose.
    Business Relation
    Business relation information is required even though the information for real customers will vary. These values are required for the tax calculation during the quote process. You should specify values that represent typical values associated with your B2C customers.
    Credit Terms
    These are typically related to credit card payment.
    Fixed Credit Limit
    Set this to a value high enough to support the kinds of items your customers buy.
    Taxable Customer
    Set this to Yes to ensure that tax calculations are performed.
    In Customer Data Maintenance (2.1.1), complete required fields for the customer you created to make customer data complete.
    This is required for the customer record to be loaded into and used by QAD CSS.
    Use the guidelines in the following table in addition to the information provided in User Guide: Financials A when completing the customer data in Customer Data Maintenance.
    PO Required
    Ensure this is set to No. When this is set to Yes for the customer record in QAD ERP, entry of a PO number is required during order entry in QAD CSS.
    In Auto Number Customer - Modify in QAD ERP, select the Active field to enable autonumbering for the B2C customer.
    After setting up the customer record in QAD ERP, test it by creating a quote for this new customer in Sales Quote Maintenance (7.12.1). You need to ensure you can proceed through the entire sales quote frame sequence accepting default values without filling anything in, using only the Next and Back buttons. This is required for the quote from QAD CSS to load successfully.
    Create the default B2C customer in QAD CSS.
    Load the default B2C customer record you previously created in QAD ERP into QAD CSS using Customer Load. If you created more than one default B2C customer for multi-domain site implementation, load them all into QAD CSS.
    Create the default B2C user in QAD CSS and associate this user with the default B2C customer record.
    Use the following steps to set up the default B2C user in QAD CSS. Additional steps for setting up default B2C users for multiple domains are also included.
    Create a security group specifically for B2C customers in Security Group Maintenance.
    Specify this security group for the B2CSecurityGroup registry setting in System Registry.
    In User Maintenance, create a generic user as the default B2C account and associate the default B2C customer with this user.
    Click Add/Edit Associations in User Maintenance and then click Add in User Detail Maintenance. Enter the following in User Detail Editor.
    In the Company ID field, specify the default B2C customer.
    Assign the user to the B2C security group as previously defined in the B2CSecurityGroup registry.
    Set ID type to Customer.
    Set the start page to op/op_indexB2C.html.
    Specify a unique marketing group with this customer/user association, such as B2C_Mktg_Group. This lets you tailor promotions for your B2C customers.
    For multiple domains, perform this step for each domain.
    In System Registry, set the key value of defaultCustomerProfile to the default B2C user ID. For multiple default B2C user IDs in support of multiple domains, separate them using commas; for example, if you created CNCust for domain CN and USCust for domain US, enter CNCust, USCust as the key value.
    Set up security in Menu Button Maintenance and Menu Maintenance using the B2C security group.
    You can customize which buttons display on the menu bar.
    You may want to use a different page for the My Account button such as lg/my_account.html. This is the page illustrated in the order examples in this chapter, which provides access to updating personal and address information, as well as viewing orders.
    Update settings in System Module Maintenance for the home page that B2C customers display.
    You can determine which pages you want to let customers bookmark; you do not want them to bookmark pages that they cannot return to later.
    Set the Login Required field to Customer and Session Required to No for op/op_indexB2C.html.
    Specify op/op_indexB2C.html as the value for the defaultB2CHomePage registry setting.
    The default B2C user is set up.
    To provide access to a B2C site that supports multiple domains, specify the default B2C user ID as the value of B2CURLParameter in the URL to differentiate among different domains. For example, for B2C shoppers to access the CN domain site, provide the following link on the portal site: