Expand my Community achievements bar.

SOLVED

Brand Portal assets published to DAM and tying in a WF project

Avatar

Adobe Champion

Hello - I am trying to understand how we can link assets uploaded from external vendors into Brand Portal back to Workfront (WF) projects without having to download the assets from AEM and reupload assets into WF.

 

Example: If a vendor uploads assets to Brand Portal and we publish assets to AEM Assets then we add the associated metadata, is there anyway to connect the assets with a Workfront project using the connector without having to add the assets in the WF project itself? (Assets would only live in the DAM, not WF.)

  • Can there be multiple assets tied to one object in WF?
  • If so, will one connection allow for updates across multiple assets (sometimes in the hundreds).
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 3

Yes you can do this by following the instructions in this documentation to create a linked folder or asset inside the documents section in workfront. https://experienceleague.adobe.com/en/docs/workfront/using/documents/wf-aem-integrations/wf-aem-esse...  Link it either to the contribution folder used or better yet link it to the final location where that asset is going to live since it can't live in the contribution folder forever due to the automatic cleanup.

 

There can be multiple assets or folders tied to one object in Workfront.  The metadata you setup in the integration between AEM and workfront needs to be setup at the individual object level if you want to have metadata flow from workfront to AEM.

 

One connection will allow for updates across multiple updates.  One thing to be worried about though is that if you link an asset to multiple projects and then update the data in one project it could overwrite the metadata on the asset.  It will always prioritize the most recent update to the metadata as you can't say which project is the "parent project" for an asset if that makes sense.  Once you link an asset to a project and if you have metadata setup in the integration any updates will update the data on the asset side of AEM.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 3

Yes you can do this by following the instructions in this documentation to create a linked folder or asset inside the documents section in workfront. https://experienceleague.adobe.com/en/docs/workfront/using/documents/wf-aem-integrations/wf-aem-esse...  Link it either to the contribution folder used or better yet link it to the final location where that asset is going to live since it can't live in the contribution folder forever due to the automatic cleanup.

 

There can be multiple assets or folders tied to one object in Workfront.  The metadata you setup in the integration between AEM and workfront needs to be setup at the individual object level if you want to have metadata flow from workfront to AEM.

 

One connection will allow for updates across multiple updates.  One thing to be worried about though is that if you link an asset to multiple projects and then update the data in one project it could overwrite the metadata on the asset.  It will always prioritize the most recent update to the metadata as you can't say which project is the "parent project" for an asset if that makes sense.  Once you link an asset to a project and if you have metadata setup in the integration any updates will update the data on the asset side of AEM.