Hi @Karishma_begumSh ,We’re looking to translate only the dropdown values in DAM metadata forms based on the language node under which the asset resides, rather than the current behavior where i18n follows the AEM user preference (which affects the entire instance UI).Requirement:When editing an ass...

Hi @ManviSharma , We have explored the tags approach, but is there a way to restrict it to single selection? By default, it always allows multiple selections, and we couldn’t find any configuration to make it single-select. The reason we need this is that, based on the selection of one field, we wan...

Hi There, We have a requirement where several custom dropdown fields have been added to the metadata schema of our assets (DITA files). During the translation process, AEM currently picks up the dropdown key value (the stored value) instead of the display label. This key is then sent for translation...

Hi @giuseppebaglio ,No, not the Phrase TMS. By TMS, I mean the generic term Translation Management System, which in our case is an in-house translation engine without an explicit connector for AEM. We are developing a custom connector to integrate it with AEM.Since this TMS requires us to poll for t...

Hi Team, We have a requirement to poll translated content from the TMS. Could you confirm if AEM provides any default polling mechanism for this, or if we need to implement a custom one? In case a custom polling mechanism or scheduler is required, how can we identify the correct Translation Object t...

Hi Everyone,I’ve found a solution to this issue and here’s a quick overview:Reason: By default, rep:cugPolicy nodes are protected and aren’t included in replication.Solution: To enable CUG policies on publishers, we need to configure the Apache Jackrabbit Oak CUG configurations in the Config Manager...

Hi @Aakarsh , It is there for the replication-service.

Hi @daniel-strmecki , It is there for the replication-service.

Hi @arunpatidar , I am using admin credentials only.

 Hi Everyone,I'm facing an issue during the replication of content into AEM. Specifically, I'm encountering the following error:Repository error during node import: rep:cugPolicyI have checked the below points and these are in place:User group is already there on both Author and Publish.Replication ...