Workfront to AEM Assets Main Menu Link

[LanaLa]

Hi there, 

We currently have a link in Workfront through the main menu that takes users to AEM Assets. This is currently set up to the old UI, but we would like to start using the new UI, and so I'm wondering how I can change this link. I have read the Documentation page called "Configure the Experience Manager Assets as a Cloud Service integration", but the way I'm reading it I think this relates to the integration within 'Documents' areas of 'Projects' where we can add linked folders? 

Does anyone know if this is the place I can update the main menu link to direct users to the new UI?

Setup > Documents > Experience Manager Assets

If this is the place, then on the back of this I had a question on metadata mapping. We have just completed a project with a third party who have helped us to define our Metadata schema (in the new UI), and so I'm concerned that this mapping will need to be redone should I add the URL for the new UI?

Thanks in advance, 

Lana

[Kurt_Jones]

Lana,

I believe you make the change under Setup->Documents->Custom Integration as believe the old connector way of creating the AEM Assets link was done there.  It looks like the new UI will be using AEM in the Cloud which is where you would use Setup->Documents->Experience Manager Assets.

It is confusing between AEM Assets being in the cloud or not in the cloud as the connections to integrate them are different.

[LanaLa]

Thanks Kurt.

I'd originally raised a ticket for this and the Support Agent actually posted this for me before I could get to it. They had actually given me the below feedback. You're correct that this is where I should be able to amend the URL, but the field where I need to put the new URL is greyed out.

1. Navigation URL Behavior: The Navigation URL is greyed out because we do not allow changes to this URL, even via API. This restriction was implemented to prevent inconsistent behavior across different AEM instances. Workfront constructs and sets the navigation URL based on the AEM instance's repository ID and type. It is stored in the database, making a CAB (Change Advisory Board) request technically possible, however this would lead to inconsistent user experiences.

Thank you,

Lana