Registry Settings

Much of the way buyers interact with QAD CSS is managed through registry settings defined in System Registry Maintenance.

The tables in this appendix list the various registry fields and associated information. Field information is organized based on the area (module) within QAD CSS that the field affects. These areas are:

•	B2C, Business-to-Customer

•	CC, Credit Card

•	Customer Contacts

•	Clearance, License Registration

•	OP, Order Processing

•	Paths, Directory settings

•	Sys, General system settings

Each table displays the following data:

Key: This is the name of the registry field.

Default: This is the default value supplied at installation. Some defaults are blank. Each installation can modify defaults as needed.

Override: This is the default setting of the Override field associated with the registry field. When Override is Yes, the system will continue to look for other instances of this field value that are set up for various groups such as marketing groups or security groups.

Usage: This is a brief description of how the field affects the operation of the system. In some cases, fields may apply differently in a B2C or B2B implementation.

The following conventions are used when specifying registry values:

•	Use the caret (^) symbol to separate multiple items that apply to one field (see orderHeaderInfoLayout).

•	Use the pipe symbol (|) to separate a code from its value (see paymentOptions).

 

Table A.1 Business-to-Customer (B2C) Registry Fields (Page 1 of 3)

Key	Default	Over	Usage
autoExtendNewCustomer	False	No	This setting determines when the customer account is created in QAD EA. True: A customer record is created in QAD EA when the order is submitted. False: At order submission, temporary records are created in QAD CSS. These can be reviewed by an administrator who then submits them to QAD EA. Set this field to False during initial implementation to monitor orders and customers before they are created in QAD EA.
B2CSecurityGroup	B2C	No	This setting defines the default security group for B2C users. You create this group during implementation and associate it menus and menu buttons do determine which areas of your site B2C users can access. By default, this is set to B2C.
createB2CProcess		No	This setting determines when the customer account is created in QAD EA. Auto: A customer record is created in QAD EA when the order is submitted. Blank: At order submission, temporary records are created in QAD CSS. These can be reviewed by an administrator who then submits them to QAD EA. This setting is referenced in the lg/lg_newloginstart.html page, which is an alternate way for letting B2C users register.
defaultCustomerProfile	B2C	No	This setting determines the QAD EA customer that B2C shoppers are associated with before they have logged in or registered. This customer is used for creating sales quotes during the order-entry process to establish pricing and taxes. You create this customer record in QAD EA during implementation and then associate it with a default B2C user account in QAD CSS. Values associated with the QAD CSS user associated with the QAD EA B2C customer specified as defaultCustomerProfile also supply values for fields such as marketing group when a new user record is created during registration.
defaultB2CHomePage	../op/op_indexB2C.html	No	The default B2C user’s home page. B2C users are not typically required to log in like B2B users, since they do not necessarily have a defined user account. You can use this field to redirect B2C users to another type of start page.
DefaultLangForB2CCust	English	No	This setting sets the customer default language code.
defaultShipVia		No	This setting determines the ship via code associated with new customer records (cm_shipvia) created in QAD EA as part of extending customers in a B2C scenario. Make sure that this value is defined in Generalized Codes Maintenance (36.2.13) in QAD EA to avoid validation errors in Customer Maintenance (2.1.1).
defaultTimeZone	PST	No	This setting defines the default time zone code associated with temporary address records created in QAD CSS.
getFedTin	False	No	This setting is used when creating temporary addresses during the order quote process to indicate that the state taxpayer identification number should be used. Set this to True when QAD EA tax calculations are performed through the Sales and Use Tax Interface to Vertex’s Quantum system.
getStateTin	False	No	This setting is used when creating temporary addresses during the order quote process to indicate that the state taxpayer identification number should be used. Set this to True when QAD EA tax calculations are performed through the Sales and Use Tax Interface to Vertex’s Quantum system
implemented	True	No	Indicates that the B2C module is active.
notifyCustomer	False	No	This setting controls the display of a check box asking B2C shoppers if they would like to receive information about updates and specials. Currently, no functionality is associated with this field, but it could be added with custom programming.

 

Table A.2 Credit Card Registry Fields

Key	Default	Over	Usage
confirmedOrders	Yes	No	This setting determines if orders are entered as confirmed.
creditCardHoldStat	HD	No	Specify the two-character hold code status indicating that an order is on hold because the customer has exceeded their credit limit. If this registry setting is not defined, CC is used by default. When an order is on credit hold, QAD CSS sets the hold status in the order header to this value. When the order is created in QAD EA, the QAD EA default hold status is used. In QAD EA, any non-blank value in the Action Status field indicates that the order is on credit hold
creditCardVendorCode	VendorCodeProvidedbyCreditCardProcessor	No	This setting determines which record created in Credit Card Vendor Maintenance that the system should use when implementing the API for creating credit card transactions. Since you can set up more than one record in this maintenance program, the system uses the registry setting to determine which record is active. This field is used only when credit cards are implemented. Its value depends on the way your company is identified with your credit card service provider.

 

Table A.3 Clearance Registry Fields

Key	Default	Over	Usage
notificationDate		No	Stores the date that the site was cleared. Not currently implemented.

 

Table A.4 Customer Contact Registry Fields

Key	Default	Over	Usage
default Contact Info	<A HREF="http://www.yoururl.com"> My Company Support </a> URL redirecting it to Contact page or Can enter plain text with Name and phone number 1-999-9999-9999	No	This field stores the default contact information displayed when a buyer clicks the Contact Us button.

 

Table A.5 Order Processing Registry Fields (Page 1 of 16)

Key	Default	Over	Usage
addAll	No	No	This setting determines whether to display the All All Selected Items button on the Order Entry page so that the user can add multiple items to the shopping cart all at once.
addItemOnce	No	No	This setting determines if buyers can add the same item number only once to their cart. Setting this to No minimizes errors and is recommended unless there is a good business reason to prevent the addition of the same item more than once. Note that this setting does not apply for configurable items defined in QAD Configurator.
addNonAvailItem	No	No	This setting determines whether buyers can add items to the cart that are not defined in QAD CSS (wpro_cust_item table). This setting affects heads-down order entry and the Express Order cart. Setting this field to Yes is a way of letting users order memo items. However, this can create problems later in order processing. To implement a complete process that supports memo items may require additional customizations. If you set this field to Yes, you should set deleteUnavailableItem to No.
deleteUnavailableItem	Yes	No	This setting is currently not implemented. This setting determines whether items that do not exist in QAD CSS are deleted from the shopping cart. This setting is required in addition to addNonAvailItem to manage memo items since QAD CSS lets items be added to a cart indirectly such as through copying an old order or using an order template. When this field is Yes, any items that do not exist are immediately removed from the cart.
configReviewRequired	Yes	No	This setting determines how customers interact with the system when they place configured items in their carts. When this is Yes, an icon displays next to a configured item when it is put in the cart. Buyers can click on the icon to validate the features and options. They then click Update Shopping Cart when they are satisfied with the configuration.
custDldTimeExceed	1000		This setting determines the maximum time, in milliseconds, allowed for the customer records to be downloaded to a csv file.
deleteOrder	Yes	No	This setting determines whether submitted orders are deleted by the system. In normal order processing, an order is submitted by the buyer. The system validates the order and creates a file that is used to update QAD EA. When the order is successfully saved in QAD EA, the status of the order is changed to submitted. If Archive Orders is Yes in Order Control Maintenance, the order is copied to the archive table and then deleted from QAD CSS. Otherwise, it is deleted without archiving. You can use this registry setting to prevent the system from deleting submitted orders for a particular user. This might be needed to troubleshoot a problem a user is having.
finditOE	OE2	No	This setting determines which page displays when the buyer searches from the main QAD CSS home page. OE1: The system loads op/op_item_lookup.html. OE2: The system loads op/op_index.html.
getPriceOfConfigParts	Yes	No	This setting determines if the price of configured items is calculated and displayed in the catalog.
getPriceOfConfigPartsinCart	Yes	No	This setting determines if the price of configured items is calculated and displayed in the shopping cart.
getPriceOnAdd	Yes	No	Not currently implemented. Instructs the system to recalculate the price of an item when it is added to the cart.
hideOrderEntry	No	No	When Yes, order entry does not display on the menu for customers on credit hold.
indexOrderHome	CAT2	No	This setting determines what displays on the main OE2 page. CAT1 and CAT2 determine the level of catalog entries that display in the left pane; these settings are mutually exclusive. MESSAGE, STATUS, and MOTD affect the content of the center pane. These can be used in any combination and determine the order in which the content displays. • CAT1 displays all distinct product categories in the product catalog. • CAT2 display only category 2 level items in the product catalog. • MESSAGE displays any messages created for the logged-in user in User Message Maintenance. • STATUS displays orders previously placed by the buyer and the order status. indexOrderStatusHistory determines how many days of history display. • MOTD displays either any messages of the day defined in Message Maintenance for the current date or a message defined for a marketing group associated with the current user’s customer.
itemDetailPgm	../op/op_itemdetail.html	No	This setting specifies the program to run when a buyer clicks a detail hyperlink in the catalog. • Specify ../op/op_itemimage.html for pop-up (the default). • Specify ../op/op_itemdetail.html for a new HTML page.
itemDetailStyle	inline	No	This setting specifies how the detail page is displayed when a buyer clicks a hyperlink to display detailed information in the catalog. Specify one of the following: • Inline displays a new HTML page. • Popup displays a smaller window.
itemQuantityFormat	->>>>>9.99	No	This setting determines the format and length of the Item Quantity field that display in the three order entry pages and the shopping cart (getCurItems, Item_detail, bcItem_confirm, and bchdo_entry).
itemQuantityShow	8	No	This setting determines how many digits are shown in the Quantity field for OE1, OE2, and HDO.
itemTable.char1	No	No	Not currently used.
itemTypesLabel0-eng	Top Categories	No	This setting determines the label1 in the OE1 index page when the language is English. This and the following related label let implementers adopt the specific terminology required at each site. If you are implementing multiple languages, you must create a corresponding registry entry for that language. For example, if you implement French (frf), create itemTypesLabel0-frf.
itemTypesLabel1-eng	Subcategory 1	No	This setting determines label 2 in the OE1 index page when the language is English.
itemTypesLabel2-eng	Subcategory 2	No	This setting determines label 3in the OE1 index page when the language is English.
itemTypesLabel3-eng	Subcategory 3	No	This setting determines label 4 in the OE1 index page when the language is English.
itemTypesLabel4-eng	Subcategory 4	No	This setting determines label 5 in the OE1 index page when the language is English.
ItemTypesTopLabel	Products	No	This setting is not currently used. It has been replaced by the language-specific version.
itemTypesTopLabel-eng	Products	No	This setting determines the title in the OE1 index page for the top label of item categories when the language is English.
maxOrderLines	0	No	This setting determines the maximum number of lines users can add to the shopping cart. Set this to 0 if the number of lines is unlimited.
OEHome	op/op_itemlookup.html	No	This setting determines which order-entry page to display when the order-entry process is complete or when an order-entry page has not been found some other way. By default, this is OE1. The default is OE1. During user login, QAD CSS determines this value and adds it to the user’s session variables. If the user chooses a different order entry, the session variable is updated and the updated value then applies to the session. The registry value determines the initial default only. A default may be needed when a buyer requests an order-entry page indirectly. For example, the buyer could access the reports menu, copy an order (see reportOrderCopy), view the cart, and then click Continue Shopping. The system then needs to know which order-entry page to display.
orderEntryRightUI	Both	No	This setting determines whether item number, or item description, or both are displayed on the Express Order panel, which is on the right side of the order entry 2 page. Number: Only item number is displayed. Description: Only item description is displayed. Both: Both item number and description are displayed.
orderHeadCommit		No	This setting determines the type value of comments associated with the order header. You can leave this blank or specify a type that identifies the comments as being from QAD CSS. Comment types can be validated using generalized codes in QAD EA, so if you specify a type, make sure it will pass validation.
orderLineCommit		No	This setting determines the type value of comments associated with the order lines. See description of orderHeadCommit.
orderHeaderInfoLayout	3,user_id ^request_date ^due_date ^po ^payment_method ^currency ^shipping_method ^order_comments	No	This setting determines the values that display on the order confirmation page. The first number is the number of rows or columns to display, followed by the fields to display. The confirmation page displays after the buyer commits an order and can be printed if needed. In addition to the fields included as defaults, erp_order_number can be used.
orderHeaderInfoLayoutLabels	Placed By^Request Date^Due Date^PO Number^Payment Method^Currency^ Shipping Method^Header Comments	Yes	This setting determines the labels for the fields displayed on the order confirmation page, as determined by orderHeaderInfoLayout. Specify the same number of labels to correspond to the fields.
orderUIMode	Yes	No	This setting determines if an intermediate page displays during checkout before the order confirmation page. The intermediate page displays a message that the system is processing the order. Set this to Yes if the number of items in the cart is typically large or preparing for confirmation takes a long time. This prevents the buyer from thinking that nothing is happening.
orderWhereAmIGoing	../op/op_bcorderconfirm2.html	No	This is normally set to ../op/op_bcorderconfirm2.html. You can change this to call a different page if you have created a custom page to display before order confirmation.
paymentOptions		No	This setting specifies a list of valid payment methods that can be selected in CSS, separated by the caret (^) symbol. The pipe symbol (|) separates the option to display and its value. Currently, two options with fixed values are currently supported: • Credit Card|1 • Purchase Order|2 You cannot change the fixed values of the options, which means that when both options are specified, Credit Card is always displayed before Purchase Order. If you want to specify Purchase Order as the only option, you still need to set the registry value to Purchase Order|2 instead of Purchase Order|1. Other options can be used, but you must modify the code to change processing based on the option selected.
QADUDomain		No	Specify the domain that QAD CSS should use to log in to QAD EA. This field is used with QADUser. A valid user record with access to this domain must be defined in QAD EA User Maintenance (36.3.1).
QADUPasswd		No	Specify the password that QAD CSS should use to log in to QAD EA. This field is used with QADUser. A valid user record with this password must be defined in QAD EA. If you are using password expiration dates as part of your QAD EA security setup, you must ensure that the system administrator changes the password for this user before the password expires and then updates the QADUPasswd setting appropriately. Otherwise, QAD CSS does not start up or integrate correctly with QAD EA.
QADUser	mfg	No	Specify the ID of the user that QAD CSS should use to log in to QAD EA. This user must be defined in QAD EA.
QCartDescTruncate	12	No	This setting controls how many characters of the item description to display in the Express Order cart. The Express Order cart displays on the right pane with a description and quantity. Since this pane is typically narrow, you can control the number of characters to display with this field.
quoteOrder	True	Yes	This setting determines if a summary of the order total is displayed before the order is submitted. This is done by creating a sales quote in QAD EA and calculating taxes and freight. This information is then returned to QAD CSS and the sales quote is deleted. When the payment type is credit card, the order is always quoted, regardless of this value. This field is typically set to True in a B2C environment, but also might be set to True in a B2B environment depending on the business requirements.
reportOrderCopy	Yes	No	This setting determines if a buyer can copy an order to create a new order. When Yes, a Copy Order link displays in the Order Summary Report generated from the Account Information menu. This lets the buyer take an existing order and copy it into the shopping cart. This feature is typically used in a B2B environment. Reporting is optional in a B2C environment so if you plan to use this feature, you must set up reporting.
runGetAllWhseQty	Yes	No	This setting determines if QAD CSS gets information about the on-hand inventory quantity from QAD EA or from QAD CSS to display with other item details. Note: The system looks at this setting only when runGetWhseQty is set to Qty or Text. When No, the value of totQty specified in QAD CSS Customer Item Maintenance displays in the product catalog. When Yes, inventory quantity is calculated based on the setting of three fields in Sales Order Control (7.1.24): • Qty All Reduce Qty Available (soc_all). When Yes, quantity allocated is subtracted from quantity available. When No, quantity available includes all available inventory, regardless of whether it has been allocated. This field is set to Yes if calculation method 1 or 2 is selected in Sales Order Control. • Required Qty Reduce Qty Avail (soc_req). When Yes, quantity required is subtracted from quantity available. When No, quantity available includes all available inventory, regardless of whether it has been required. This field is set to Yes if calculation method 3 or 4 is selected in Sales Order Control. • Qty Avail Include Qty on Order (soc_on_ord). When Yes, quantity on open purchase or work orders is added to quantity available. When No, quantity available includes only available quantity on hand. This field is set to Yes if calculation method 2 or 4 is selected in Sales Order Control.
runGetBestPrice	Yes	No	This setting determines if QAD CSS runs the best pricing logic in QAD EA to obtain the price for an item when it is displayed in the product catalog. Items in the shopping cart are priced using best pricing regardless of the setting of this field. Use this setting to optimize performance. If the price is not being displayed in the catalog, setting this field to No prevents the unnecessary processing.
runGetBestPriceConfigParts	Yes	No	This setting determines if QAD CSS runs the best pricing logic in QAD EA to obtain the price for a configured item when it is displayed in the product catalog. Items in the shopping cart are priced using best pricing regardless of the setting of this field. Use this setting to optimize performance. If the price is not being displayed in the catalog, setting this field to No prevents unnecessary processing.
runGetDefWhseQty	Yes	No	This setting determines if QAD CSS gets information about the on-hand inventory quantity for the default site from QAD EA or from QAD CSS to display with other item details. Note: The system looks at this setting only when runGetWhseQty is set to Qty or Text. The default site is determined in this order: • A site associated with the customer record in QAD CSS • The site defined in QAD CSS Order Control • The site from cm_mstr record in QAD EA • The site associated with the item in Item Master Maintenance (1.4.1) When this field is Yes, the calculation is similar to that described for runGetAllWhseQty, but only items in the default site are considered. When No, the value of whsQty stored in the QAD CSS Customer Item Master (wpro_cust_item) displays.
runGetMinMaxQty	No	No	This setting determines whether QAD CSS enforces the minimum and maximum order quantity defined in Customer Item Maintenance.
runGetWhseQty	Off	No	The setting of runGetWhseQty has three possible values. Off: Do not perform any availability calculation. If the quantity available has been marked to display in Item Layout Maintenance, no value displays on the screen. Qty: Check the value of the runGetAllWhseQty and runGetDefWhseQty settings and display the quantity available based on those settings. Text: Check the value of runGetAllWhseQty and runGetDefWhseQty and display the text contained in one of two configurable messages, indicating that stock is available or unavailable. • OP000244 displays when zero or less quantity is available in all sites. • OP000245 displays when a quantity greater than zero is available in all sites. Note: This setting has effect only when qtyavaildefault or qtyavail are marked to display in the product catalog in Item Layout Maintenance.
searchList	Master	Yes	This setting determines whether the user's associated customer ID is used in the search for items: • Master (or blank): Search for items not associated with a customer. This is the default value. • Customer: Search for items associated with the currently logged-in customer or items associated with any customer IDs specified in the Master Customer field for the current customer. If no customer IDs are specified for the Master Customer field, only items associated with the current customer are found.
searchMethod	Contains	No	This setting determines if the search type for item search is whole-word search or substring search. • Contains: Item searches are whole-word searches, where the search term is treated as representing the whole word. • Matches: Item searches are substring searches, where the search term is treated as a substring.
searchSortName	Yes	No	Not currently implemented.
setDueDate	No	No	This setting determines the due date on the Shopping Cart page. The options are: • Yes: Use Header/Line requests in CSS to populate the Header/Line Due Date. • No: Always use the default Due Date calculated by ERP.
setReqDate	No	No	This setting determines the default value of the request date the on the Shopping Cart page. The options are: • Yes, and promise dates are being calculated in QAD EA: Order line request date defaults from the calculated order line promise (delivery) date. • Yes, and promise dates are not being calculated: Order line request date defaults from the calculated order line due (ship) date. • No: Order line request dates are blank.
shippingOptions	ERP	No	This field determines the content of the drop-down list associated with the Shipping Method field in the Order Confirmation page. It can have two values: • A list of shipping options to be considered valid during order entry. • ERP, which indicates QAD CSS should use the values defined for the so_shipvia field in Generalized Codes Maintenance in QAD EA. If you choose to create a list, use this format: description1|code1^desc2|code2^desc3|code3... The description displays to the user and the code value is passed to the sales order. If you have set up generalized codes on so_shipvia, all the code values must be valid in QAD EA.
showDeliveryIcon	Yes	No	This setting determines whether the Delivery button is displayed beside the following buttons: • Add button for each item on the product catalog • Add button in the express order cart • Delete button for each line in the shopping cart The setting values are Yes or No.
showDetailImage	Yes	No	This setting determines whether an image is included in the item detail page that displays when buyers click an item in the product catalog.
showDueOrPromDate	PromiseDate	No	This setting determines which dates, if any, display on the order-related reports that can be viewed by customers as well as the order summary page that displays during checkout. PromiseDate: Promise date displays. Both: Both dates display. None: No dates display. (Any other value): Due date displays.
showExtendedPrice	Yes	Yes	This setting determines whether the extended price is displayed in the shopping cart.
showGroupImage	LEFT	No	This setting determines where images associated with item categories in Item Types Maintenance display. Possible values are: • LEFT displays image to the left of the text. • RIGHT displays image to the right of the text. • NO does not display an image.
showHDOfromlookup	Yes	No	This setting determines if a link for heads-down order entry displays in the OE1 page. This order-entry method may be more suitable for a B2B environment than for a B2C environment.
showHeaderComments	Yes	No	This setting determines if a field displays so buyers can enter sales order header comments. This may be more applicable to B2B than B2C.
showIndexSearch	Yes	No	For OE2, determines if the item search box displays at the top of the left pane during order entry. showLookupSearch has the same effect for OE1.
showItemListLabels	Yes	Yes	Not currently implemented.
showItemType	Yes	No	Not currently implemented.
showLegendBar	No	Yes	This setting determines if icons associated with an item in the Icon List field of Customer Item Maintenance display below the item description in the catalog and a legend bar displays at the top of the product catalog. The legend explains the name of the icons associated with the items as defined in Icon Maintenance.
showLineComment	Yes	No	This setting determines if a field displays so buyers can enter sales order line comments in the shopping cart. This may be more applicable to B2B than B2C.
showLinePromDate	Yes	No	This setting determines whether the promise date is shown for each order line item on the shopping cart and the Finish Order pages. The setting values are Yes or No.
showLineReqDate	No	No	This setting determines if a field displays next to each item in the shopping cart so the buyer can specify a request date. Values are: • No: Line item request dates are not entered. showReqDate is typically Yes in this case. • Yes: Line item request dates are entered. The showReqDate field is typically set to No. However, when both showReqDate and showLineReqDate are Yes, an Apply All button displays beside the header Request Date field. This lets users apply the header Request Date to all order lines. • Required: Same as Yes but input of the field is mandatory during order entry.
showLineSerNum	No	No	This setting determines if a field for update of lot or serial numbers displays in the shopping cart and on the order summary page. Values are: No: Do not allow entry of lot/serial numbers and do not display them on the order summary. Yes: Allow entry of lot/serial numbers for each item and display the entered values on the order summary. Byline: Allow entry of lot/serial numbers only for an item when ShowSerial function returns a value of True. Then display the entered value on the order summary. To activate the Byline setting requires implementers to write custom code for the ShowSerial function to return the correct value. As installed, QAD CSS always sets this value to True. Note: The serial numbers entered when this field is Yes are not returned to QAD EA. Implementers must map this value if they want it to be part of the QAD EA order; typically it is mapped as a line comment.
showLookupSearch	Yes	No	For OE1, determines if the item search box displays at the top of the left pane during order entry (op_itemlookup.html page). showSearchIndex has the same effect for OE2.
showOProcStatus	Yes	No	For B2C order maintenance, determines if buyers can search orders by status, as well as criteria such as user ID and customer.
showOrderDetailInCheckOut	Yes	No	This setting determines if the order trailer information is calculated and displays on the order confirmation page. Trailer details include taxes and freight, providing an approximate cost of the total order.
showOrderDetailTotals	Yes	No	This field is used in conjunction with ShowOrderDetailInCheckOut to display the totals associated with the details.
showOrderEntryRight	True	No	This setting determines whether a separate right pane should display in the OE1 screens; the right pane always displays in OE2. To completely disable the display of the right pane in OE1 screens, both this field and showRightPane must be No.
showOrderSummary	No	No	This setting determines if an additional instruction screen should display during order submission when payment method is 2, purchase order. This field should normally be left set to No. Setting it to Yes requires a custom implementation to create a custom orderinstructions.html page to display.
showPartialShipper	Yes	Yes	This setting determines if buyers can indicate acceptance of partial shipments. If Yes, a Partial Shipment check box displays during order confirmation. This feature applies to B2B environments more than B2C.
showPriceinConfigurator	Yes	No	When a configured item is added to the shopping cart, a drill-down icon displays next to the item during checkout. Clicking the icon lets the buyer view the features and options. This field determines whether prices are included with the display of features and options.
showPromDate	Yes	No	This setting determines whether the promise date is shown in the order header on the shopping cart and on the Finish Order pages. When the promise date varies per line, the header promise date shows the latest promise date for all lines on the order. If you want shoppers to see different dates for each line, set showLinePromDate to Yes.
showReqDate	Yes	No	This setting determines whether an updateable Request Date field displays in the order header on the shopping cart and the Finish Order pages. The setting values are Yes or No. When this field is Yes and showLineReqDate is No, the header request date applies to each line on the order and cannot be changed. If you want shoppers to be able to change the date for each line, set showLineReqDate to Yes. When showReqDate and showLineReqDate are Yes, an Apply All button displays beside the header Request Date field. This lets users apply the header Request Date to all order lines.
showShipper	Yes	No	This setting determines if the shipping method can be selected during order confirmation. The effect of this field depends on how the shippingOptions field is set: • If multiple options are defined, a drop-down list displays so the buyer can select a method. • If only one method is defined, it is used by default. • If no shipping options are defined, this field has no effect.
showSortBy	wpro_cust_item. item_number	No	This field controls how items are sorted in the product catalog for both OE1 and OE2. You can specify any value in the QAD CSS item table (wpro_cust_item) such as sort_name, cust_part, item_type. The default is item_number. More than one sort value can be specified using a list separated by carets (^).
showUOM	Yes	Yes	This setting determines if the default item unit of measure displays in the shopping cart.
skipViewCartOnAdd	Yes	No	This setting determines if the cart displays every time an item is added. No: The shopping cart displays each time an item is added. Yes: The shopper can choose to display the cart when they want to.
stockAvailBrowse	111111	No	Not currently implemented. This setting controls the display of quantities columns in Stock Availability Browse.
templateOrder	Yes	Yes	This setting determines if a link to template orders displays on OE1 and OE2 pages. If Yes, the Save Order Template button also displays in the shopping cart.
trailerAddress	No,Yes,Yes	No	This setting controls the display of sold-to, bill-to, and ship-to addresses in the order trailer page. Specify Yes or No for each address; when populated, there should be three comma-separated values in the following order: 1. Sold-to 2. Bill-to 3. Ship-to For a B2C and B2B environment, the two critical address are bill-to for account settlement and ship-to for logistics, taxes, and charges.
useCurrencyUnicode	Yes	No	When this is Yes, the system looks for a hexadecimal unicode associated with the item currency in Currency Unicode Maintenance. If one has been defined, it is displayed before the price amounts. If useCurrencyUnicode is No, nothing displays before the price. However, the system always displays the currency code after the price.
useERPOrderNumber	Yes	No	This setting determines the source of the next order number: No: QAD CSS supplies the next order number. Yes: The next order number is derived from Sales Order Control in QAD EA. The generation of the order number occurs before the order is submitted to QAD EA.
useLangItems	Yes	No	This setting determines how the user’s associated language affects the display of items in the catalog. Yes: Only items with the same language code as the user display. No: All items for the customer display regardless of the item language code. Specific language code: Only items with this code display regardless of the user’s language code. Blank: Only items with a blank language code display. Note: This setting has no effect on the display of items in Customer Item Maintenance.
userCurrency		No	Use this field to override the currency associated with a user in User Maintenance. When a user logs in to QAD CSS, the system checks for a currency in this order: • First, a currency defined with the userCurrency setting • If blank, the value assigned to the CSS user • If blank, the value from the customer bill-to in QAD EA
userCustomerPartNo	Yes	No	Not currently implemented. This field determines how items are validated during heads-down order entry. In this type of ordering, items are validated only when the buyer clicks submit. If this field is Yes, the item must be associated with the customer.
useTemplateQty	No	No	When Yes, buyers can specify an item quantity before submitting a template. This quantity is used as a multiple for each line in the template. For example, you specify a quantity of 10 when selecting a template. The quantity of each line in the template order is multiplied by 10 and added to the shopping cart.
useUserID	LoginName	No	Use this field to determine the value that populates the Entered By field for sales orders in QAD EA: • LoginName: The ID of the user who is currently logged into QAD CSS updates the Entered By field, letting you trace the order to a specific user. • Blank: The value of QADUser (see here) updates the Entered By field. This is the user associated with the process that updates the sales order table.
vshowItemThumbImage	False	No	This setting determines the default value for the Show Item Image check box displayed in the product catalog for OE1 and OE2. Works in conjunction with vupdateItemThumbImage.
vupdateItemThumbImage	Yes	No	This setting determines if a check box displays in the left pane of the product catalog for OE1 and 2 so buyers can specify if item images should display. Works in conjunction with vshowItemThumbImage.
scripts		Yes	Not currently implemented. Lets you override the location of the QAD CSS scripts specified in System Control Table Maintenance.

 

Table A.6 Directory Paths Registry Fields

Key	Default	Over	Usage
images		Yes	Lets you override the location of the QAD CSS image files specified in System Control Table Maintenance.
styles		Yes	Lets you override the location of the QAD CSS style sheets specified in System Control Table Maintenance.

 

Table A.7 System Registry Fields (Page 1 of 7)

Key	Default	Over	Usage
b2bURL	http://www.EnterYourB2 URLHere.com	No	Not currently implemented. This setting specifies the URL reference to the log‑in page for the B2B site.
b2cOrderStatus	False	No	Not currently implemented. This setting defines the display for B2C order history status. This setting determines if shoppers can run the Order Status Report on the customer profile home page. Set this to Yes only if autoExtendNewCustomer is Yes. Otherwise, shoppers may expect to see information for orders that have not been submitted to QAD EA.
companyTimeZone	-0800 PST	Yes	The value of the company time zone is used during e-mail communication to report the time zone from which the e‑mail originated.
compLogoHref	http://yourcompany logohref.com	Yes	This setting defines the URL that will be associated with the additional company logo located in the header. Works in conjunction with compLogoName, which defines the image.
compLogoName		Yes	This setting defines the full file name (with extension) of an additional image to display next to host_logo.gif in the header. The system always displays an image named host_logo.gif first.
ConfiguratorWSURL	http://cfgWebSpeedServerHostName/cgi-bin/wspd_cgi.ksh/WService=cfgWebSpeedBrokerName	No	This setting provides the Configurator WebSpeed URL to enable QAD CSS for items defined with the QAD Configurator (an add-on product for QAD EA).
custDisplayLimit	25	Yes	This setting determines how users select a customer during login when more than one customer is associated with them in User Maintenance. • If the number of customer records associated with the user is less than the value you specify, a drop-down list appears. • If the number of customer records associated with the user is greater than the value you specify, a screen with lookups appears.
defaultCountry	USA	No	This setting defines the default country to use in address records. These must be valid country codes defined in QAD EA.
defaultCustomerRegistration	userreg	No	The default user for customers set up in User Registration. Values for this user are copied when a new account is set up based on information collected in the online registration form and verified through User Registration.
defaultSite		No	This setting determines the default site for the temporary customer ship-to record created by the system when creating quotes to determine a preliminary order summary in the B2C order process. This value is used only when the customer associated with the defaultCustomerProfile does not have an associated site. The site associated with a customer is always used first.
disableAccount	False	No	This setting determines what happens when the buyer fails to provide a valid user ID and password. When True, the user account is deactivated and e‑mail event EX066 occurs. This field works in conjunction with failLoginRetry. When this field is Yes, a user can supply invalid log‑in data three times before an account is disabled.
failLoginRetry	Yes	No	When Yes, the system checks disableAccount after three failed login attempts and disables the account if required.
exHeaderType	1	Yes	This setting determines the style of the QAD CSS header: 1: Three rows of display: menu buttons, menu, footer 2: Like 1 but has an additional header layer consisting of search, date, user, cart summary, and check out
exHeaderCart	No	No	When exHeaderType is 2, this field controls the display of the shopping cart summary and cart icon in the header.
exHeaderDate	No	No	When exHeaderType is 2, this field controls the display of the system date information in the header.
exHeaderMenu	No	No	When exHeaderType is 2, this field controls the display of an additional Quick Menu bar in the header. If used, you must design the items that display on the Quick Menu.
exHeaderSearch	Top	No	When exHeaderType is 2, this field controls where the search object displays in the header. Valid entries are Top and Bottom.
exHeaderWelcome	No	No	When exHeaderType is 2, this field controls the display of message in the header welcoming the user by name, such as Welcome John Smith.
exmenuDefault		No	Not currently implemented.
genMenuHeight	20	No	Tells the index how high the JavaScript menu is. Height is not related to the number of rows, but more to the available menu area. The value should be set based on the resolution of the user’s display device. A value less than 20 may result in improper menu display.
genMenuInLine	True	No	This setting controls how the menu is generated. Menus once finalized can be generated in a JavaScript file and stored. True: Generate the menus in real time each time the buyer accesses the home page. False: Use the generated JavaScript file. This should be set to False once the menus are finalized to improve runtime performance. Use the menuDir registry setting to define where the menu JavaScript file is located.
genMenuWidth	180	No
HDOHeight	215	No	This setting determines the height of the heads-down order-entry frame set.
HDOHeightNS	225	No	This setting determines the height of the heads-down order-entry frame set for Netscape.
hostCopyrightHref	http://www.qad.com	Yes	This setting defines the host copyright URL located in the footer. Change this to a value appropriate for your installation.
hostCopyrightText	<center>A Passion For Manufacturing <br> <a href="http:/ /www.qad.com/resources/copyright.html" class="copyright" target="_blank">© Copyright 1997-2005 QAD Inc.</a> </center>	Yes	This setting defines the host copyright text located in the footer. Change this to a value appropriate for your installation.
hostURL	http://www.EnterYour HostURL.com	No	Not currently implemented. This setting defines the URL of the host’s public Web site. Change this to a value appropriate for your installation.
httpsURL	https://www.EnterYour HTTPSURL.com	No	This setting determines the URL of the host when running in secure mode. The standard host URL is built by the system using information determined during installation in the WebSpeed startup files, and does not need to be defined with a registry setting. This setting is required only under the following conditions: • The entire application is not running under SSL protection. (When the entire application runs under SSL, two URLs are never need.) • Port numbers are included in the host URL, such as: http://host.MySite.com:1234.
indexOrder	SEARCH, MOTD, MESSAGE, STATUS	Yes	Can be set to any of the following or any combination of the following: SEARCH, MOTD, MESSAGE, STATUS. This setting controls the display of the login page for B2B environment. Based on the value of this field: • SEARCH displays a search box for searching through the product catalog. • MESSAGE displays a user-defined message. • STATUS displays all orders previously placed by the buyer and the order status. • MOTD displays a generic message of the day.
indexOrderStatusHistory	30	No	This setting determines how many days of order history are displayed on the Order Status Report. The system looks for orders with an order-entry date up to this many days before today’s date. Set this value based on the transaction volume of the company. Note: indexOrder controls what the user sees on the home page and indexOrderHome controls what the user sees on the Order Entry page. These fields determine if order history can be displayed.
itemDetailLink	Yes,Yes,Yes	No	This setting defines which elements related to items are presented as hyperlinks in the catalog to an additional item detail page. Item Layout Maintenance determines the fields displayed in the Product Catalog. Three fields related to the item can have associated hyperlinks that display a detail page: • Item image • Customer item number • Item number The values in itemDetailLink determine the default values for these three fields in Item Layout Maintenance.
itemLayout	111010000011111	Yes	This setting determines the default values for the display check boxes associated with the 15 fields in Item Layout Maintenance. 1 indicates selection of field as default; 0 indicates non-selection. Users can change these fields in Item Layout Maintenance if needed. The values specified in Item Layout Maintenance determine which item details display in the center pane of the product catalog for OE1 and OE2.
itemLayoutHeader	Description, Item, Additional Info, Available, Price/UM, Quantity	No	This setting defines default values for the Header Label fields in Item Layout Maintenance. These, in turn, determine what displays above the associated column in the product catalog for OE1 and OE2.
itemLayoutHeader-eng	Description, Item, Add'l Info, Avail, Price/UM, Add	No	This setting defines the column labels for the selected item details to be displayed in OE1 and OE2 for the English language.
itemLayoutLabel-eng	,,,,,,,,,Def:,All:,,,qty:,,	No	This setting defines the side labels for each detail for an item in OE1 and OE2 for the English language.
itemLayoutLabel	,,,,,,,,,,,,,qty:,,	No	This setting defines default values for the Side Label fields in Item Layout Maintenance. These, in turn, determine what displays to the left of the item detail in the product catalog for OE1 and OE2.
itemLayoutName	Sort, Desc 1, Desc 2, Customer Number, Part Number, Other 1, Other 2, Other 3, Other 4, Available (Default), Available (All), Price, UoM, Quantity	No	This setting is not currently used. It has been replaced by the language specific registry settings. This setting defines the default descriptions for the elements displayed on Item Layout Maintenance.
jsmsgDir	/qadcss/scripts	No	Specify the full path to the directory where generated error message files are located. QADCSSInstallDir/scripts is recommended. To support multiple languages, QAD CSS places generated error message files in language- specific subdirectories under the directory specified. Messages are read from a generated JavaScript file at runtime.
launchpointHeight	85	Yes	Not currently implemented. This setting determines the height of the frame set that displays when QAD CSS is opened from a link in another page.
lmenustartMenuX	2	Yes	This setting defines the number of pixels for the menu’s horizontal position when genMenuInline is True. If not set, a default value of 7 is used. This accommodates both header types.
lmenustartMenuY	140	Yes	When genMenuInline is True, defines the number of pixels for the menu’s vertical position. If not defined, the default is 112. If exHeaderType is 1, the default value of 112 is adequate. When exHeaderType is 2, a higher value such as 240 is better.
lpMenuWidth	180	No	This setting defines the menu’s width. If not defined, the default is 222.
menuBackGround	#003466	Yes	Sets the background color for the index menu. If not defined, the default is #596D99.
menuBackGroundOver	#000066	Yes	Sets the background color for the highlight bar or the cursor, when the focus is placed on the menu. If not defined, the default is #363ACC.
menuDir	/qad/mfgpro/92/css test/qadcss/scripts	No	When genMenuInline is False, defines the directory location where the menu JavaScript file is stored after generating. Menus are generated in Menu System Maintenance to support multiple languages and improve runtime performance.
menuHeaderBottom		No	This setting defines an additional image to display below the main company logo (always host_logo.gif) in the header.
menuHeaderClass		Yes	This setting defines the style class for the menu header. The default value is the default body class.
menuHeaderSpace	No	No	This setting determines if extra space is needed in the header to accommodate the display of the company logo. If the host_logo.gif cannot be compressed to fit within the upper-left corner, this lets you insert an additional space between the graphic and the menu buttons.
menuWindowOptions	width=700, height=700, scrollbars=1, toolbars=1, statusbar=1	No	Not currently implemented. Determine the properties of the window that opens when QAD CSS is opened from another Web page.
minPasswordLength	6	Yes	This setting defines the minimum password length.
partslookuplogo	parts_look.gif	Yes	This setting determines the name of the image file displayed on OE1 prior to the execution of search.
registrationURL	http://license.qad.com/ scripts/lic.wsc/cl/ cl_checkreg.html	No	The URL of the QAD CSS license server used to obtain a clearance code. Note: Both the key value and usage fields must be set correctly. For usage, specify the following URL: http://license.qad.com/scripts/wsisa.dll/WService= live/cl/cl_checkreg.html
reportFooterLogo	host_logo.gif	No	Not currently implemented. This setting specifies the name of the image file displayed at the bottom of reports. If left blank, the host_logo.gif is used; this image is always used on the header.
runSecurePages	Yes	No	Not currently implemented. Makes pages in the application that use the makeSecure function run under https (SSL). This is required for credit card implementation.
showAddLoginInfo	No	No	Tells the menu bar if additional login information should be shown.
showRightPane	Yes	Yes	This setting determines if the right pane displays throughout the system. The OE2 option always displays the right pane, regardless of the value set in this field.
ShowSTDEXTConfTabs	Yes	No	This setting determines whether the Standard Configurations and Existing Configurations tabs are displayed in the configuration questionnaire. No: Standard Configurations and Existing Configurations tabs are not displayed in the configuration questionnaire. Yes: Standard Configurations and Existing Configurations tabs are displayed in the configuration questionnaire.
userMessageArchive	True	No	This setting determines if user messages are archived or deleted from the main index page. No: Messages are physically removed when the index page redisplays. Yes: Messages are marked for deletion but not physically removed.