[Event Follow-Up] Building the Content Supply Chain with Workfront, Creative Cloud, and AEM

[NicholeVargas]

First and foremost, thank you Heather Adkins @hkadkins and Yaswanth Vanukuri @yvanukuri03 for taking time this afternoon to share the City National Bank story! And for everyone who joined, I hope you left feeling inspired to integrate and automate some of your processes moving forward.

As promised, I’ve included a link to the recording and a PDF of the slide deck below along with some highlights and resources from Experience League: 

• Recording 
• Slide Deck 

Additional Resources/Highlights 

• Key objectives focused on reducing manual work, minimizing duplication, increasing asset reuse, and improving efficiency. 
• Challenges included modifying requirements during implementation, connector integration issues, and underestimating planning, resources and change management needs. 
• Be sure you have a team of people committed for a dedicated amount of time! Look for a team champion to help with supporting these efforts.
• Benefits included saving over 1,500 hours annually, reducing audit time from weeks to hours, and improving time to market. 
• Learn more - Adobe Workfront plugin for Creative Cloud applications 
• Overview of Adobe Experience Manager Assets integrations 

Be sure to check out and register for future Customer Success events. There’s a handful coming up later this month and into July, so we hope to see you there! 

[Stacey_Robertson]

@hkadkins and @yvanukuri03 can you give some examples of how you used your tasks for naming convention you mentioned on the calls and also your typical folder setup?

[hkadkins]

Yes, in our Workfront project templates we have a parent task for each asset needed. The task name uses the asset file name format: "Project ID - Asset # -Title - Type". Then that task has related child tasks for each step to create the asset. This also helps the designer manage their tasks when they're using the Workfront/Creative Cloud connector.  

For our Workfront folder structure, under the project folder, there are 5 sub-folders: Reference, Design & Copy Only, Studio Only, Creative Proof, and Final Assets. These sync to a WIP section of AEM Assets upon project activation. The files in the Studio Only file are only viewable to our Creative Team. Upon project completion, final assets are upload to Workfront, then sync'd to the production section of our DAM. We then have a process for archiving design files for reference and removing unnecessary WIP files from AEM Assets.

[ChrisYahnke]

Hi @hkadkins - do you use fusion to drive naming conventions for the parent tasks?

[hkadkins]

Hi - Yes, we do.  We automated using several of the data fields entered on a project form to populate the parent task names.  If needed, a creative producer can make updates to the names within the project and those changes will  be updated in the child tasks. 

[JamesMa4]

Hello @hkadkins @yvanukuri03 I'd like to know more about how you apply metadata to assets, specifically: who does this (creative team, or project lead, etc.)? And where this takes place (CC application or WF)?

Thank you!

[hkadkins]

We have two methods: 1) assets sync'd from Workfront to AEM  Assets automatically have Workfront metadata and 2) our DAM coordinator reviews and adds any additional metadata and tags in AEM Assets. 

[JamesMa4]

Thank you Heather! This answer and the answer to Stacey's question are very helpful.

Best regards, James