9

As mentioned for TBBs to be able to make changes to CM items, you need to set allowWriteOperationsInTemplates = true in the Tridion.ContentManager.config on all machines that are rendering for you, so this means all CM servers and all Publisher servers. Please note that as documented, SDL strongly recommends against this practice as it compromises your ...


8

As it was not possible to have a separate application use the SAML Authentication module (see Rick's answer) I had to take a step back and re-think how my custom pages work. Because the custom pages are using the core service, what I really wanted was to make sure that core service calls were done in the context of the authenticated user of the Tridion UI. ...


7

IIRC, the current implementation for SAML 2.0 authentication uses ASP.NET Session State, which requires: Use of Sticky Session on your Load Balancer (to prevent the same ASP.NET Session ending up on multiple CMS servers) Use of a single Web Application So, creating your own separate Web Application may not work. Can you create a Virtual Directory instead ...


6

Update: Please see the correct answer by David Forster in the comments below. You may want to check whether there is Workflow set via the Associated Component Process on the Schema. This may put the Component straight into Workflow (as a Version 0.1) without needing it to be added to a Bundle.


6

If a component is greyed out when it's just created, this usually means it's created, but not yet checked in. There are several causes for this you build the component using custom code, but you save it without checking in when you manually create the component in the CME gui, you save it, but you don't check in the component. some workflow process starts ...


6

SDL Tridion Sites 9 will be the successor of SDL Web 8.5, which is a Web Content Management (WCM) solution, but it is not released yet. SDL Tridion Docs 13, is a DITA-based structured content management solution, which was formerly SDL Knowledge Center. SDL Tridion Sites and Docs are part of the SDL Tridion DX suite. You have tagged your question with sdl-...


6

The View On Site button is only enabled if the current Publication has a Business Process Type associated with it. For the UI to know that, it needs to load the Publication. That is why there is a slight delay the first time -- but the next time you select a Page, the Publication is already loaded and there is no delay.


4

AFAIK it's supported but can't be hosted on the same machine as the CM. You have the choice of running it on a fenced server in the SDL Cloud environment or running it outside of SDL cloud and connecting to the CoreService to generate your reports.


4

Templates are read-only unless you change the CM configuration. Do you have a separate publisher? Have you changed the configuration on that system? Just noticed the "Cloud" part - As Bart mentions, I'm not sure that changing the configuration is supported in that case. For on-premise the relevant documentation under Backwards compatibility and API changes ...


3

AFAIK, there is currently no application-level support for proxies. Note that in case of DXA 2.0, support would be needed in the DXA Framework, but also in the UDP CIL. So, this seems like an Enhancement Request for both DXA and UDP. If you think this adds much value, I would recommend to submit it as an Idea on the SDL Community Site.


3

There's a configuration setting that, by default, sets templates to have read-only access to the TOM.NET API. See allowWriteOperationsInTemplates (and set to true) in the tridion.contentmanager.security element in the Tridion.ContentManager.config As noted in other posts here - this deprecated approach is strongly recommended against.


3

I'd suggest to check if publishing service user has rights to update the Component on that particular Publication. Can you update the question with the logs, if there is any error?


2

You're saying: The value for <extendeddocumentType>9758</extendeddocumentType> definitetly matches the regex [a-z0-9][a-z0-9_]{0,63}$ so the error in description does not make any sense. But that's not true, this regex only allows lowercased strings for field names. So, if you lowercase your field name (extendeddocumentType) in the custom TBB ...


Only top voted, non community-wiki answers of a minimum length are eligible