Hey Richard,
I've never actually looked at the contents of that table, and would never have thought that records could be added to it. Interesting.
The eConnect Programmers Guide explains adding custom transaction requester records to eConnect_Out_Setup. My guess is that the data in that table is then used to create a trigger. I never knew that was possible.
Creating a Transaction Requester document type
The Transaction Requester allows you to create custom Transaction Requester document types. You can use the Transaction Requester to define new document types that support your specific business needs. For example, you can create a document type to retrieve data from tables that the original Transaction Requester document types do not include.
To create a custom Transaction Requester Service, you first identify the tables and other information that the Transaction Requester requires. You need to identify a document type name, the tables to use, the index columns, the key fields used to join tables, and the data fields you want to include in your document.
You must recreate all custom requester services after an installation has completed. The install drops and recreates the eConnect_Out_Setup table. Any custom information in the eConnect_Out_Setup table is lost.
To define your document type, you need to add the information you gathered to the eConnect_Out_Setup table. The Transaction Requester uses the information in this table to retrieve and publish eConnect XML documents.
To use the <eConnectOut> XML node with the Transaction Requester, you need to use the following elements:
You use DOCTYPE to specify the type of Transaction Requester document you are targeting. The DOCTYPE value must match one of the document types in the eConnect_Out_Setup table. Examples include Customer, Employee, and Sales_Transaction.
You use FORLOAD when you want your query to produce documents for the Outgoing Service. If you set FORLOAD to one, your query information is placed in the eConnect_Out table. The Outgoing Service uses your query information to create an eConnect XML document and place that document into a queue.
You use FORLIST when you want the Transaction Requester to return the query result directly. You typically use this with the GetEntity method of the eConnectMethods class to get an XML string that represents the query result.
You use the INDEXFROM and INDEXTO elements to specify the select criteria for your query. The number for each INDEXFROM and INDEXTO correpond to the INDEX columns for the specified document type in the eConnect_Out_Setup table. For example, INDEX1 for the Customer document type in the eConnect_Out_Setup table is CUSTNMBR. To use <eConnectOut> to retrieve cusomer information, you must use customer number values in INDEX1FROM and INDEX1TO.
To request a single record, place the same value in the INDEX1FROM and INDEX1TO field. To get several records, place the first value in the INDEXFROM element and the last element in the INDEXTO element. The Transaction Requester retrieves your first and last values and any records with an index value between them.
The following example shows how to use <eConnectOut> to retrieve a list of customers from the TWO database. Notice how INDEX1FROM specifies a customer number and INDEX1TO specifies a second customer number. The Transaction Requester returns XML that includes the two specified customers and any customers with a customer number between the two specified values.
Share
Report
75,848
All responses (
Answers (
