Known issues
Known issues of Tridion Docs SES Connector
- The implementation was build and tested using version 3.7 of the SmartLogic Semantic Enhancement Server (SES) web services API using http. As long as the API is compatible the connector should work for higher versions as well.
- There is no way to provide a username/password for the web services.
- The default proxy of the system is used to access the web services. No other proxy configuration is supported.
- The
RetrieveTagsmethod only returns terms that are selectable. TheRetrieveTagStructurecan return non-selectable terms, so the user can use them to navigate to a selectable term deeper down in the hierarchy. - Only hierarchical relations are taken into account for the
RetrieveTagsmethod, so you should avoid using other relationship types. Exception: for the conversion relation, you can use other relation types. - Only one fields filter and one dynamic entry points field is supported
- The only condition name you can use at the moment is "CLASS".
- If you use a dynamic entry field (or fieldsfilter in combination with static entry points) in order to limit the results to a certain subtree of the taxonomy structure, you might run into a the following problem with the
RetrieveTags: In order to provide a quick response, we provide the input filter together with the terms the user filled in (for the dynamic entry or filter field) as required ancestors to the SES API, so that SES can already limit the results to the appropriate subtree. However we have no way to "tell" to the SES API that it should take those ancestor terms into account as possible hits as well. This means you might get less hits than expected, as the root terms for a dynamic field or the filter terms will not return as hits. A workaround would be to use "CLASS" conditions, so these terms become non selectable. Note that theRetrieveTagStructuredoes not have this problem as the structure is returned without filtering.