New and changed in version 11.0.0
SDL Tridion Docs is compatible with Content Delivery 11.0.0.
- Enhanced user condition
-
Before SDL Tridion Docs 13 SP2, the only way to pass conditions provided by the website visitor from the web application to the Content Service was by using the ISH Cartridge (ish_ambient_cartridge.xml) to add the taf:ish:userconditions Claim to the Claim Store. As of SDL Tridion Docs 13 SP2, you can trigger the client API, passing these visitor-provided condition values. The client retrieves these values, merged with Publication conditions, from the Ambient Data Framework, and passes those merged conditions in the
contextDataparameter in itskeyword()andcategories()calls. The queries return Taxonomies filtered using all of the conditions. - UGC threaded commenting
-
Previously, comments were necessarily a flat list: one comment could not be a response to another comment.
Now, the
UgcCommentApiinterface has a method calledretrieveThreadedComments()(and a counterpart,retrieveFlatComments()) to make this functionality possible. This method does not support filtering by status; how you handle comment threads containing comments with differing statuses is up to you.The
Commentinterface also has two new methods,getParent()andgetChildren(), for navigating a comment thread.For more information, refer to the Content Delivery API reference documentation.
- Enhanced comment filtering capabilities in the Java Content Interaction Library (CIL) for UGC
-
The
SimpleCommentFilterclass now contains a number of new ways to paginate, traverse and filter comments and comment threads. - New Content Service API controller to get a public link to a binary resource
-
You can now create a Content Service URL that returns the public URL of a (specific variant of a) binary resource.
- Public Content API
-
The product now has a new API called Public Content API, consisting of new GraphQL endpoints for the Content Service and the Session-enabled Content Service, based on the GraphQL API query language, and using the same RESTful endpoints as before for the Content Deployer and IQ Indexing and Querying services . You can explore the GraphQL part of the new API interactively using an in-browser IDE such as GraphiQL. The new API uses an inheritance-based domain model, offers support for multiple namespaces and strongly typed models, requires fewer roundtrips and minimizes the overfetching or underfetching of data in each request.
Note that Footprint functionality is not supported in this new API. If you are using (and want to continue using) Footprints, continue using the (now deprecated) SDL Web RESTful API for the Session-enabled Content Service.
The existing SDL Web RESTful API has become a legacy API; it is deprecated.
- Content Delivery configuration files are now validated against their XSD schemas when their microservice starts
-
Previously Content Delivery configuration files (such as cd_storage_conf.xml) shipped with XSD schemas, but the product didn't actually validate the files against their schemas. From now on, when a microservice starts, a check is performed to see if each configuration file is valid against its schema file. If, for whatever reason, one of your configuration files is not valid, the product raises an error and fails to start the microservice.