otris Documents
The query against otris Documents occurs via the otris Documents SOAP proxy web service.
Key | Description |
|---|---|
Provider* | Value |
Url* | HTTP(S) base address of otris Documents SOAP proxy web service When specifying the base address, include the port number but not the sub-paths. |
ProxyAddress ProxyUser ProxyPassword | Proxy server for communication to the web service (optional) Syntax: see Proxy Server Connection |
User* Password* Principal* Locale | User name, password, tenant ID and language (default: |
AsUser | Second user name, used if the login is performed via "trusted login" in the context of another user |
MaxConnectionsPerUser | Maximum number of simultaneous logins (sessions) for the same user on the SOAP proxy Default value: |
RequestTimeout | Timeout value in seconds, determining how long to wait for a response from the web service before throwing an error Default value: |
The structure of the query command is based on that of query commands in SQL-SELECT syntax:
SELECT {fieldname 1} [AS {alias 1}], …, {fieldname n} [AS {alias n}]
FROM {search source 1}, …, {search source n}
[WHERE {search expression}]
[ORDER BY {fieldname} [ASC|DESC]]The search source can be an otris Documents folder type or an archive, for EAS (Enterprise Archive Solution) (e.g., in the syntax {folder type}@{archive server}). The search expression has to be defined in the native otris Documents syntax (see SOAP proxy documentation) (i.e., generally {field name}{comparison operator}{value}, e.g., company='xSuite Group').
The result values are always returned by otris Documents as strings. xSuite Interface tries to convert these strings into typed values using the data types from the folder type description. However, unlike the otris Documents input system, no explicit formats for parsing the strings can be configured at this point. Therefore, the conversion only works if otris Documents returns the values in a common syntax, especially for dates.