Documentation Center

Content Manager core changes (15.1.0)

This release includes several improvements to the Content Manager core.

Added support for plugins in Web service API
Tridion Docs 15 now supports IWrite plugins for Baseline and BaselineItems, and supports IDelete plugins.
Content Manager OpenAPI
Tridion Docs 15.1 introduces OpenAPI as a new public API for use with Content Manager. Tridion Docs OpenAPI is a RESTful web service that is the preferred API for interacting with Content Manager. OpenAPI is used by the Organize Space user interface.
Compared to the existing WCF-based API, the new OpenAPI offers the following advantages:
  • Easy to use
  • Support for HATEOAS links and JSON-based models
  • Support for language-agnostic and platform-independent development
  • Authentication through Tridion Access Management using OpenID Connect
Automatic XML configuration upgrade when upgrading from Tridion Docs 15
When you perform an upgrade from Tridion Docs 15 to Tridion Docs 15.1, the upgrade transforms your XML configuration files to become valid against Tridion Docs 15.1 schemas. If you are upgrading from an earlier version than Tridion Docs 15, you still need to make those modifications yourself.
Resilient response to invalid XML configuration
Before Tridion Docs 15.1, a service would fail on startup if its XML configuration was invalid. As from Tridion Docs 15.1, a service with an invalid XML configuration will instead throw an exception and wait for a valid XML configuration. This is true for the following services:
  • BackgroundTask
  • TranslationBuilder
  • TranslationOrganizer
Additional metadata fields, sourced from a simple, out-of-the-box taxonomy system
Tridion Docs 15.1introduces a new XML configuration file, Admin.XMLTaxonomyConfiguration.xml, which users that have the new Taxonomy Management privilege can configure from Organize Space at Settings > XML Settings > Taxonomies. This file configures a basic taxonomy consisting of the following metadata properties, along with some out-of-the-box sample values:
  • PRODUCTFAMILY
  • PRODUCTRELEASE
  • GOAL
  • AUDIENCE
This configurable taxonomy offers customers who don't use the Semantic AI feature the ability to create and manage a more structured, less "flat-list" collection of metadata properties. Customers who do use Semantic AI can hook up the configuration to their PoolParty instance.
The new fields are also defined in MetadataConfig.xml, as follows:
Name in taxonomy configName in MetadataConfig.xmlContent typeLevel
PRODUCTFAMILYProduct Family Namepublicationlogical
PRODUCTRELEASEProduct Release Namepublicationversion
GOALGoalstopic, map, Library Topiclogical
AUDIENCEAudiencetopic, map, Library Topiclogical
You can replace the flat-list LOVs "Product family name" (FISHPRODUCTFAMILYNAME) and "Product release name" (FISHPRODUCTRELEASENAME) with the PRODUCTFAMILY and PRODUCTRELEASE properties, respectively, by running a migration script called MigrateToIshTaxonomies.ps1.
Applications migrated to .NET Core to support reading configuration from multiple sources
In our journey to configure Tridion Docs from a centralized configuration system, individual Content Manager applications need to support reading their configuration from multiple sources, such as from a configuration file or another configuration system. Converting the applications to .NET Core makes this transition easier, as it already provides support for reading configuration from multiple sources.
The following system components are now migrated: Crawler, Background task, Translation Builder, Translation Organizer, TrisoftSolrLucene
As a result of the migration, the names and locations of configuration files have changed as follows:
ApplicationOld file and locationNew file and location
Background tasks \Infoshare\App\BackgroundTask\Bin\BackgroundTask.exe.config\Infoshare\App\BackgroundTask\Bin\appsettings.json
Translation Builder \Infoshare\App\TranslationBuilder\Bin\translationbuilder.exe.config\InfoShare\App\TranslationBuilder\Bin\appsettings.json
Translation Organizer\Infoshare\App\TranslationOrganizer\Bin\TranslationOrganizer.exe.config\Infoshare\App\TranslationOrganizer\Bin\appsettings.json
TrisoftSolrLucene.App\Applications\TrisoftSolrLucene\Bin\TrisoftSolrLucene.exe.config\InfoShare\App\TrisoftSolrLucene\Bin\appsettings.json
Solr Lucene 9.4.1
The Content Manager search engine is now upgraded to Solr Lucene 9.4.1. Because this new version of Solr implements Server Name Identification (SNI), the keystore should contain all allowed IP addresses. For this reason, the peer name check (expressed through the SOLR_SSL_CHECK_PEER_NAME property) was disabled by default in solr.cmd as from Tridion Docs 15.1. You can enable it, together with a new keystore, yourself.
Delete Publication Version business rule

This release adds a new business rule that triggers the automatic deletion of a publication whenever the last remaining version of a publication is deleted. This rule prevents having an invalid publication that contains no versions.