How Input Values are Passed to the Service the Browser-Based Client Invokes
Regardless of whether a browser-based client uses a URL that uses HTTP GET or HTTP POST, when Integration Server receives the URL, it creates an IData object from the input information that the browser-based client supplies. Integration Server then passes the IData object to the specified service. This becomes the pipeline upon which the service operates.
To create the IData object, Integration Server creates two key/value pairs for each input value: one of type String and one of type String list. For example, the following URL specifies input values that contain the variable sku with value A1 and quantity with value 1, and the resulting IData object that Integration Server creates:
/invoke/sample.webPageDemo/order?sku=A1&quantity=1
Key | Value | Data Type |
sku | A1 | String |
skuList | A1 | String list |
quantity | 1 | String |
quantityList | 1 | String list |
Note:
Avoid using input variable names that end in “List.” Although Integration Server accepts variable names ending in “List,” the resulting IData might not be structured in the way you need. For example, if you pass in a variable called skuList, the resulting IData contains a String called skuList and a String list called skuListList. Additionally, if you pass in variables named sku and skuList, subsequent sku and skuList variables in the query string might not be placed in the IData fields as expected.
If you must use “List” at the end of your variable name, consider using “list” (lowercase) or appending one or more characters at the end of the name (for example, abcListXX).