https://community.rws.com/product-groups/tridion/tridion-docs/Welcome to the Community group for Tridion Docs, a DITA-based structured content management solution that solves the complexity of creating, managing and distributing in-depth product content and technical documentation at scale.en-USTelligent Community 12 Non-Productionhttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60968/tridion-conditions-in-fluid-topicsMon, 27 Apr 2026 10:52:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:621f3c99-489a-4449-a660-666eea929bb3Jonathan ChandlerHello everyone, Has anyone successfully published content that includes multiple conditions (for example, customer X, customer Y, internal, external, series X, series Y, etc.) from Tridion to Fluid Topics and then had Fluid Topics segment or filter that information effectively? In particular, I’m interested in learning: Whether conditions were resolved in Tridion at publish time or passed through to Fluid Topics and managed on that side. How conditional content was handled to avoid content duplication or condition explosion How Tridion metadata and condition values were mapped to Fluid Topics facets, tags, or profiles If a better long-term approach would be to scrap conditions and move to DITAVALS If you use Tridion conditions and also publish content to Fluid Topics, I'd appreciate hearing how you do it, what works, what doesn't, and any best practices or resources that may help. Thanks in advance for any insights you’re willing to share.Tridion Docs 14fluid topicsishconditionconditionshttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60964/does-tridion-docs-15-only-require-the-installation-of-a-server-certificate-or-is-the-installation-of-a-server-application-process-certificate-also-necessaryMon, 27 Apr 2026 02:42:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6d4fbe3b-311a-412e-9c39-5f8ce54a5bd5Hugo HuangDoes Tridion Docs 15 only require the installation of a "Server Certificate", or is the installation of a "Server Application Process Certificate" also necessary? The previous certificate we purchased include both "Server Certificate" and "Server Application Process Certificate" by default. The new certificate that we will purchase only includes the "Server Certificate". If the "Server Application Process Certificate" is also needed, we will have to purchase it separately.https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60923/require-reports-option-to-list-where-used-at-the-folder-levelMon, 20 Apr 2026 06:14:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6e8ca924-9349-4010-92b5-236f22fb0121Priyanka SinghIt would be helpful to have a Reports option at the Graphics folder level to view Where Used details and determine whether files/objects are used. Currently, this information is available only at the individual file level, requiring manual checks for each file/object. A folder-level report would make it much easier to identify usage of Graphics folder files/objects, including whether they are used or not. Due to procedural constraints, sometimes not all illustrations can be accommodated, and some files may remain unused. With a Reports option, it would be easy to identify whether a graphic file is used or not. This visibility would support better planning and coordination between writers and illustrators and help reduce unnecessary effort by avoiding the creation of unused files in an ongoing release or in the next project.reportswhere usedtridion docs 15Publication Managerhttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60354/deleting-released-objects/192936Wed, 15 Apr 2026 05:23:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:ef55317c-590c-4857-9444-209b867a5a9cRagnar BranæsI am aware of the issues related to released objects. The database is after all designed to keep released objects "safe". In our case, we are going through a large reorganization, and our database has been duplicated into "ours" and "theirs" repository. We need to delete a few publications and bookmaps from "their" repository. In my experience, if you start by deleting the publication (all versions!) you can continue with the next level objects - bookmaps - and so forth. I appreciate all help here, and I am sure that we are not the only Tridion Docs customer with such needs. Mark Novembrino , I saw your input on the use of an API, thanks! I will dig into that, as I do not know how to access the database with an API.https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60354/deleting-released-objects/192934Tue, 14 Apr 2026 17:10:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:086afc2b-0bc8-4972-868a-b218906f1b6aMark NovembrinoIt is possible to revert the publication output status from released back to draft using the PublicationOutput 2.5 SetMetadata web service API. Using this API, you can set Draft . Once all the publication outputs are back in draft state, you can delete the publication. More info about the API here: docs.rws.com/.../publicationoutput-2-5-setmetadata-70082https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60354/deleting-released-objects/192912Tue, 14 Apr 2026 08:16:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:8cbdb8c4-f21f-4f9e-a5c3-dc81e2a0bcbdRagnar BranæsHello everybody! I see from many replies here that as an administrator I am supposed to be able to release objects. What I need to do is to release certain publications and bookmaps, nothing else. I have moved to Tridion Docs 15.2, I am an administrator, but I am still not able to delete released publications. It is imperative that I can do so after a major reorganization in our company. Please advice. regards Ragnarhttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60799/capability-to-log-clientconifig-access-for-troubleshooting-and-auditFri, 03 Apr 2026 02:12:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:2aa5f2fd-f4d1-4fc0-aa74-ca6ef2cebe29Masayuki YamaneI think logging capability is very essential for all network access, and that should be the same with ClientConfig files sync'ed by Publication Manager and Authoring Bridge. However, according to both clients (i.e. Publication Manager and Authoring Bridge) and Tridion Docs servers don't have capability to extend logging level for ClientConfig sync. Is that true? That is actually a problem when I troubleshoot ClientConfig sync issue with RWS Support. RWS hosts six production servers for us, and those are workload balanced. With that condition, unnecessary ClientConfig file sync happens when the timestamp would mismatch than previous file sync. Even worse, each of users seem to be experiencing the unnecessary file sync issue differently, possibly due to workload balancer. So, even though redeployment of ClientConfig files by RWS Support improved the consistency across six production servers for some users, I am hearing from some other users, hey, still experiencing that issue. Although RWS Support have ever tried to make the folder content consistent again and again, that won't be suppressed fully. We can't identify which production server the issue is remaining. I don't know what the challenge is with RWS to implement that logging capability. But, if that logging capability wasn't possible for RWS, can RWS take different approach to identify required ClientConfig file sync?https://community.rws.com/product-groups/tridion/tridion-docs/b/weblog/posts/automating-on-tridion-docs---ishremote-v8-2-1-for-powershell-7-6-and-comes-with-a-built-in-mcp-serverThu, 02 Apr 2026 08:58:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:d07ec701-0cc6-43a6-8f14-0182516f6d82Dave De MeyerWhat happened Full release notes are on https://github.com/RWS/ISHRemote/blob/master/Doc/ReleaseNotes-ISHRemote-8.2.md Before I forget, all people with a Github account, could you spare a moment to STAR this repository - see top-right Star icon on https://github.com/RWS/ISHRemote/ Appreciated! General This release inherits the v0.1 to v0.14 up to v8.1 development branch and features. All cmdlets and business logic are fully compatible even around authentication. In short, we expect it all to work still :) The one that is required to run on PowerShell 7.6 LTS hosted by .NET 10. Several big quality of life security improvements regarding implicit authentication and refresh stability. This stability powered the introduction of ISHRemoteMcpServer - an MCP Server that allow natural language quering of your Tridion Docs system. Furthermore, ISHRemote v8.2 is the recommended version to use for Tridion Docs 15.3.0 ( #207 #235). Remember All C# source code of the ISHRemote library is online at master , including handling of the different Connection protocols in a NET 4.8, NET 6.0 and .NET 10.0+ style. All PowerShell-based Pester integration tests are located per cmdlet complying with the *.tests.ps1 file naming convention. See for example AddIshDocumentObj.Tests.ps1 or TestIshValidXml.Tests.ps1 The below text describes the delta compared to fielded release ISHRemote v8.1. Platform Support for PowerShell 7.6 PowerShell 7.6, a Long Term Service (LTS) release hosted on .NET 10 (LTS), required code changes because of breaking changes between .NET 8 and .NET 10. When using ISHRemote v8.1 or earlier, the most prominent error on a New-IshSession invoke is Could not load type 'System.IdentityModel.Tokens.SecurityKeyType' from assembly 'System.ServiceModel.Security which should trigger you to upgrade to this release. Along the way refactored some warnings X509Certificate2 and ServicePointManager (HTTPS/SSL/TLS) usage. The chosen solution is to have 3 runtimes: Kept Windows-only .NET Framework 4.8 for usage in Windows PowerShell 5.1 with as little code changes as feasible. Kept cross-platform .NET 6.0 for usage in cross-platform PowerShell 7.2 and 7.4 with as little code changes as feasible. Do note that these platforms are out-of-support by Microsoft; in turn ISHRemote considers these deprecated as well. Introduced cross-platform .NET 10.0 for usage in cross-platform PowerShell 7.6. This variation received all possible third-party library updates as well; ranging from Duende.* over System.ServiceModel.* to supporting library like System.Text.Json and more. #235 Stability improved by actively recovering interactive sessions Every usage of a cmdlet will, when almost expired, refresh the security tokens. However, when not using ISHRemote cmdlets or the implicit local or global $ISHRemoteSessionStateIshSession or explicit $ishSession object, the session expires by default after around 57 minutes when using ISHID or similar on other identity providers. In turn resulting in error An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. . In this ISHRemote version, the session will attempt to get a new token automatically on every triggered ISHRemote cmdlet. If you created the IShSession object over an interactive browser, you will see the browser again perhaps with or without a credential challenge in the browser. Change is only for protocols WcfSoapWithOpenIdConnect and OpenApiWithOpenIdConnect ; no change for WcfSoapWithWsTrust . Infamous random annoying error The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state. should now recover within the cmdlet or worst-case when rerunning the same cmdlet. This without applying the earlier workaround of building a New-IshSession . MCP Server for Tridion Docs CMS powered by ISHRemote ISHRemoteMcpServer Introduction Tridion Docs CMS has a very rich API which opens up all the power of Organize Space, Draft Space, Publication Manager, and more. ISHRemote is a PowerShell library that abstracts some authentication and metadata modelling complexity from the Tridion Docs API in an opionated way like default metadata. ISHRemote also comes with a built-in help for every cmdlet - or should I say MCP Tool - as you can see in for example Get-Help New-IshSession -Detailed . It lists purpose, parameters, syntax and examples - this for every cmdlet. #213 #233 Model Concept Protocol ( MCP ) is the language to offer tools to your chosen Large Language Model ( LLM ) to have smart data interactions. Where in the past the LLMs had access to functions to for example find out the weather in some location, now you can offer it a tool box to access a specific domain like Tridion Docs . MCP Tools enable AI models to perform actions. Each tool defines a specific operation with typed inputs and outputs. The model requests tool execution based on context. Combining documented ISHRemote cmdlets with the interaction pattern of MCP Tools to LLMs, we see at least the below purposes... By offering every ISHRemote cmdlet as an MCP Tool to your LLM, it means you can ask your system questions like Create a new ishsession to https://ish.example.com/ISHWS/ . And yes it will create you that $ishSession variable in the background that you can use over the other MCP Tools - or I could say cmdlets. This allows you to use natural language to query your specific instance on How many user roles are there? or which status transitions do you have for a module? . These requests will be executed using your authenticated $ishSession . As ISHRemote cmdlets understand the API and many of its concepts, it can explain system concepts usage questions. This allows you to query How many statusses are there? , Does the system have any privileges? which could be followed by These are labels, any way to use these values in an API? . It can explain existing ISHRemote PowerShell scripts. And because the MCP Tools look a lot like ISHRemote cmdlets, you can reuse your LLM's PowerShell knowledge to draft PowerShell scripts . You could query for Can you write me a powershell script to create a user? or Can you suggest a rewrite using the faster search cmdlet? . Although the LLM will not always offer working code, but it does seem to make sure you don't have a blank sheet in front of you. You now have something that you can debug and get to a working state as you can feed it your runtime errors and it will improve the generated code iteratively. ISHRemoteMcpServer Setup using Visual Studio Code Below animation give you an overview on what you need to do to set it up. Important is that your Visual Studio Code Terminal runs a different PowerShell process then the one behind the ISHRemoteMcpServer which means that any $ishSession is not reused which could lead to initial confusion. Below the steps in some more detail... You need ISHRemote v8.2+ installed in your PowerShell v7 (not Windows PowerShell!). See Installation-ISHRemote-8.0.md for guidance. Make sure that it works by calling the classic New-IshSession -WsBaseUrl https://ish.example.com/ISHWS/ Open your installed Visual Studio Code preferably to a working folder where you have or plan to have your scripts saved. Now you need to create or extend your .vscode/mcp.json with the below code block. Optionally use a different log file path, and use the double backslashes to comply with the json file syntax. Or you can run without client-side logging by removing -LogFilePath \"$env:TEMP\\IshRemoteMcpServer.log\" . Start the IshRemoteMcpServer using the decorator Start Go to your CoPilot, put it in Agent mode. After typing a hash ( # ), you should see the registered MCP Tools which look a lot like cmdlet name pop-up, starting with #Add-IshAnnotation . Now set your LLM to Claude Sonnet 4.5 (or better). In the chat enter Create a new ishsession to https://ish.example.com/ISHWS/ , where the url is an existing url. { "servers" : { "IshRemoteMcpServer" : { "type" : " stdio " , "command" : " pwsh " , "args" : [ " -NoProfile " , " -Command " , " & { Start-IshRemoteMcpServer -CmdletsToRegister (Get-Command -Module ISHRemote -ListImported -CommandType Cmdlet).Name -LogFilePath \" $env:TEMP \\ IshRemoteMcpServer.log \" } " ] } } } ISHRemoteMcpServer Architecture The diagram below explains the deployment architecture, and allows to clarify the lifecycle of the MCP Server, especially regarding any $ishSession lifecycle. Overall ISHRemote as MCP Server does not act differently from any PowerShell 7+ ISHRemote interactive session - the PowerShell session is hidden for you however by Visual Studio Code. When you click the Start decorator in the mcp.json , Visual Studio Code will start a local PowerShell ( pwsh.exe ) process using a local stdio transport MCP server. As ISHRemote was already installed and working up front for interactive usage, this module will be loaded by the first cmdlet called. The first ISHRemote cmdlet call is Start-IshRemoteMcpServer which holds the infinite loop to service the LLM interaction. The first LLM question in the lifecycle of the registered ISHRemoteMcpServer is the initialization and exposing the available tools. The ISHRemoteMcpServer runs on your local machine that pushes the heavy lifting via PowerShell over ISHRemote and in turn HTTPS to a Tridion Docs service. When you ask for Create a new ishsession to https://ish.example.com/ISHWS/ it is the local PowerShell process ( pwsh.exe ) that will trigger your trusted browser to appear for an authentication dance unless you ask the LLM to authenticate with client/secret ;) In turn if you use the Stop or Restart decorator in the mcp.json , you actually have stopped your PowerShell ( pwsh.exe ) process which means you lost your implicit $ishSession . Hat tip to dfinke/PSMCP offering a generic PowerShell library wrapper which is self-contained and tweaked for ISHRemote purposes to make it easier for our user base. ISHRemoteMcpServer Reminders A list of reminders and known issues which we noticed while experimenting... We never got the same answer for Create a session to https://ish.example.com , so in turn you need to monitor this assistant on what it does. If it tells you that it will recursively loop the whole folder structure (so Get-IshFolder -BaseFolder Data -Recurse ) then it will take a long time and in turn there are a lot of results (so tokens, so cost). Very similar to your human assistant. Guidance is offered to the LLM over Register-IshRemoteMcpInstructions.ps1 which also might make sense for a human to read :) As LLMs, and in turn the tweaking of ISHRemote MCP Server over instructions and so on, are a continuously moving target. The subset of IshRemoteMcp cmdlets could still change and are not necessarily an exact compatible API surface like the other original ISHRemote cmdlets. If you do a Stop or Restart of ISHRemoteMcpServer then that process is gone and so is your authentication. Although it might look like your 'Chat' can still continue, we expect most MCP Tools to fail.PowerShellISHRemotehttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60651/content-importer-general-access-for-authors/192237Mon, 23 Mar 2026 16:36:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:0c521a01-edbf-46b6-b8f5-2b2dca9fe8e7Elizabeth GschwindHi Stacey - a couple of things. At FICO, only our administrators perform imports. We always import into an "Import" folder (with subfolders for each project) so the writers can check the imported files before moving them into the main repo. (If you are importing updated versions of topics that are already in the repo, this won't work because the object will be overwritten at its current location.) I hope this helps.https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60651/content-importer-general-access-for-authorsFri, 20 Mar 2026 14:17:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e1e2a551-9fed-4fd0-975c-bedcdb7c521dStacey MeggsOur team is responsible for our company's Tridion Docs instance (v15.2). We've been using TD for 10 years. We find that Content Importer works great for translated content. However, it is more error-prone for English content. In fact, when we outsource conversion to DITA, the vendor always chooses to avoid Content Importer, instead opting for their custom methods instead. Aside from migrations, English imports are rarely requested by our authors. When they are needed, our support team does them for the authors who request them. However, the use cases are growing and there is more of a demand for English content imports. Do you generally allow access to Content Importer for your authors? If so, what risks has that presented? What are your general best practices for authors using Content Importer? Or do you generally limit it only to support roles? Thanks for your perspective.Content Importertridion docs 15Best Practiceshttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/56663/how-to-switch-from-old-dtd-based-xml-to-dita-in-tridion-docs/191841Tue, 10 Mar 2026 10:35:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:da78b8db-ff8d-4ccc-8462-523b7f6d147cFrank RalfMany thanks for all your pointers. And sorry for not replying earlier. The project had been delayed and will only start later this year. Best regards, Frankhttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60494/setting-multiple-values-for-a-metadata-field-using-documentobj25-create-shows-invalid-entries/191746Wed, 04 Mar 2026 17:54:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:f96d3877-4e22-4ba7-b1ad-f648fae3af1fMark NovembrinoHi, Dave. I figured out the problem. My application is dependent on an another application that forwards the metadata to my application already configured as ishfields. There were non-breaking spaces between the commas in the field values and I didn't see them. After running out of ideas, I just guessed that maybe there was something unusual like that. When the non-breaking spaces were replaced with regular spaces, the metadata was set in TD properly. Problem solved.https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60494/setting-multiple-values-for-a-metadata-field-using-documentobj25-create-shows-invalid-entries/191732Wed, 04 Mar 2026 14:17:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:4b6818d6-51d0-4982-8766-b102b222b0dfMark NovembrinoThanks for the quick response, Dave. The msiamtch of "id" and "element" is because I was trying both. Typically I'm using "id" for everything, but I tried using "element" to see if that fixed the problem. It did not.I'll have a look at the logging as you recommended and dig further.https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60494/setting-multiple-values-for-a-metadata-field-using-documentobj25-create-shows-invalid-entries/191711Wed, 04 Mar 2026 07:34:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:3b75d05c-dcbe-41e0-a743-f3e52fbe5eaaDave De MeyerHi Mark, If we have two behaviors something is different. What caught my eyes first is that you pass FCUSTOMFIELD1 using ishvaluetype="id" and that you pass FCUSTOMFIELD2 over ishvaluetype="element". Is that intentional, from a product perspective I would have expected both to be aligned, or is this yours? Furthermore, from a CMS perspective we are just saving the value that came in. It is however your (custom) IMetadataBinding implementation that validated the incoming values in the first place upon save. And your (custom) IMetadataBinding implementation decides why it is not returning labels. So looking at the logging of that implementation on how it acts would be my next step. Best wishes, Davehttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60494/setting-multiple-values-for-a-metadata-field-using-documentobj25-create-shows-invalid-entriesTue, 03 Mar 2026 23:50:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:bb483db5-3870-448a-91f4-5254c829a4fbMark NovembrinoSome weird behavior here that is vexing me... I making a web API call -- DocumentObj25.Create -- to create a topic in a Tridion Docs 14 environment. For one of the metadata fields I am setting, there are multiple taxonomy values. When I look at the created object in Publication Manager, two of the three values are listed as invalid. I performed the same operation manually in Publication Manager and looked at the log to see how Publication Manager was passing the metadata via the same API call. The metadata structure looks exactly like the one I am passing with my API call, but the result is correct. The values are not listed as invalid. Here is what my metadata looks like: Name of my topic 17573177, 17574057 en-US 1 86301381, 86301382, 87394644 FCUSTOMFIELD1 is set correctly from the API call. FCUSTOMFIELD2 is not set correctly. One value is set, but the other two are marked as invalid. When I look at the logs in Publication Manager, when I create an object manually, I see the same exact metdata structure for FCUSTOMFIELD2 as what my API call is passing. But Publication Manager sets it correctly, and my API call does not. Also note that if I limit the FCUSTOMFIELD2 to one value in my API call, it works without a problem.https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/59914/is-there-a-way-to-cancel-translation-jobs-that-use-the-file-export-template-in-tridion/191658Mon, 02 Mar 2026 06:13:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:684044ea-6d03-4af8-aa97-c1fd3715e1bfEva NauerthThank you, Andriy!https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/60466/release-notice-for-td15-2-1/191648Sat, 28 Feb 2026 01:23:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:2164898f-591d-46f8-861e-f30de70f93c4Naoki HiraiHi Andriy Zhidko , I read through the blog post and release notices. I realized that many issues have been solved, so I feel it is worth applying the update as soon as possible. Thanks a lot!! Best regards, Naokihttps://community.rws.com/product-groups/tridion/tridion-docs/f/forum/59914/is-there-a-way-to-cancel-translation-jobs-that-use-the-file-export-template-in-tridion/191643Fri, 27 Feb 2026 19:07:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:220f5b0f-2413-4e9c-add1-dd52a5c42414Andriy ZhidkoHi Eva, The Tridion Docs 15.2.1 release announcement was published on the community today. Please see Tridion Docs February Update is Out! (version 15.2.1) You can find release notes by following the links below: New and changed in version 15.2.1 Fixed issues in version 15.2.1