Configuring Excelerator Settings

Specify whether allow QXtend to process the raw value of a mnemonic field or the mnemonic itself. For example, the EMT Type field in Customer Maintenance is stored as a mnemonic. The raw value is 01; however, the mnemonic displayed on the screen is NON‑EMT.

Specify whether you want to encode your password for accessing the target QAD Enterprise Applications. Encode Passwords is used if the QXtend application is running with <encodedPasswords> set to true. (This value is set in the qxtendconfig.xml configuration file in QXtend Inbound.)

Provide the host and port information for the QXI server.

Specify the Webapp name, which is the name of the Web service used to connect to QXtend Inbound.

Select this option if using Secure Socket Protocol https encryption. Enabling this is only applicable if QXtend has been configured to run under SSL.

Enter, in seconds, the maximum wait time for responses from QXtend Inbound.

Specify the QXtend Inbound receiver to use to load data into the target QAD application.

Displays the name of the QDoc API the worksheet relates to. The field defaults from the schema imported into the worksheet.

Displays the version of the QDoc API the worksheet relates to. The field defaults from the schema imported into the worksheet.

The menu program the QDoc API is mapped to. (Optional: this information is used when retrieving menu-specific column labels and authenticating Query requests.)

Specify the QAD release the worksheet is interacting with.

Select the default Excelerator worksheet template type to use when creating worksheet templates.

There are two Excelerator worksheet template types:

When you use this template type, the Process Response QDoc option is cleared by default since no message processing is required for QXtend responses.

Use this template type when you want to create from Excelerator new business transaction records (for example, sales orders) in QAD Enterprise Applications that require the target system to generate key field values or business document numbers (for example, sales order numbers).

This feature is realized by using the key prefix. When processing the updates to QAD, the temporary key prefix is removed and replaced with the system-generated key (e.g. the sales order number).

Specify a key prefix (for example, tmp#) to identify key fields or business document numbers of business transaction records (for example, sales order numbers of sales orders) in the worksheet that you want the target QAD application to supply values for. You can then use the key prefix to create temporary key field values (for example, tmp#1, tmp#2, tmp#3 ...) for new records in the worksheet. When the data is sent for processing through the Update QAD function, QXtend replaces the temporary key field values from the requests with values generated by the target QAD application. When Excelerator receives responses containing the system-generated key field values, it updates the worksheet with the new key field values.

The prefix must and can only be defined when the worksheet template type is Business Transaction Template.

The value you enter here defaults to the Key Prefix field in the Design Template dialog box when you design worksheet templates.

Specify the debug level for financial QDocs only. Refer to Debug Levels for the available level options.


Level	Description
1	Logs the start and end of all entry-level business methods. Entry-level methods are called from outside the business logic.
2	Logs the start and end of all methods and procedures, internal and external.
4	Logs parameter values of business methods. This level is only available when level 1 or level 2 is active.
8	Logs all read or update database queries.
16	Logs details of all database update (create, modify, or delete).
32	Analyzes performance and logs possible memory leaks in the business code.

Select this option if you want each update from Excelerator to be treated as a whole transaction in QAD. If any error is encountered, the entire update will be backed out.

Specify whether you want Excelerator to process response QDocs returned from QXtend and update the worksheet with any new data.

Yes (Selected): Excelerator processes response QDocs containing detailed business data (the suppressResponseDetails attribute is set to false) returned from QXtend. Any new data in the response messages will be updated into the worksheet.

No (Cleared): The Excelerator ignores any response QDocs returned from QXtend. The suppressResponseDetails attribute is set to true in the request sent to QXtend Inbound, which limits the data contained in the response to processing status and exception messages, excluding any business data to enhance the message processing performance of QXtend Inbound. You should set the option to No for data load templates.

You can only specify this option for data load templates. For business transaction templates, the option is always set to Yes and cannot be changed.

Specify the receiver to use to query data from the source QAD application. The receiver must be a receiver listed under the Outbound module receivers defined in QXtend Inbound.

Specify the source application instance name.

Specify the name of the profile in QXtend Outbound that defines the format of the queried data.

Note: The format must be compatible with the request XSD that the worksheet was built from. This is important because the format of the query response data must map to the table and field names defined in the worksheet. The table name and field names are case-sensitive.

Specify the QDoc version.

Enter the default maximum number of records to retrieve into a worksheet during data query. Enter zero (0) to retrieve all matching rows.

Enter a valid Progress query to use as filter criteria to filter records. The filter must be a valid Progress ABL WHERE clause and can only be defined against the top-level table of the QXO business object; for example: