A New Era of Collaboration with AEM and Workfront

Transcript

All right, everyone, thank you for joining us today. I see people still logging on, but I’m going to give us, I’m going to get us started because we have a very full agenda for you today.

All right, everyone, welcome to our first session of the perfect blend this year. Today, our amazing group of presenters will be going through how Adobe Workfront and AEM integrate together to further simplify your workflows. We design our webinars to be interactive, so we encourage you to ask questions in the question box throughout the presentation. Type them in there because we’ve designated the last 10 minutes or so for Q&A. I also want to mention a couple of housekeeping items before we get started. First of all, we’re presenting in Adobe Connect today and we are live, but don’t worry, this session is being recorded and can be viewed on demand or shared with other members of your team at a later time. You’ll also get the recording and an email from us tomorrow afternoon. Also throughout the presentation on the right side of your screen, you’ll see a form to fill out to receive more information on either AEM or Workfront directly from your company’s Solution Account Manager. This is a great way to get in touch with someone who best understands your situation and an opportunity to ask questions on how AEM and Workfront could integrate to improve your company’s particular workflow.

Finally, as we’re closing out the webinar, we have a few survey questions that will be at the bottom of your screen. If you could just take a few minutes or so to answer those, we’d really appreciate it. And with that, I’d like to introduce myself. My name is Jeff Umeguano. I’ve been a digital engagement strategist at Adobe for a little over two years now. I lead the production of our webinar series for all of our Experience Cloud products. Prior to my time at Adobe, I spent two years working in advertising for several global agencies in New York. If you have any questions or comments about today’s event or about your experience with Adobe Connect overall, please feel free to reach out. With that, I’d like to hand it over to Casey to introduce themselves.

Thanks, Jeff. Hi, everyone. Casey Witter here. I’ve been working with AEM for nearly seven years now. I started over in the implementation consulting space and then moved over to the post-implementation advisory space a few years ago. And I’m excited to talk to you all today.

And Rajen, could you introduce yourself? Hey, hi, everyone. My name is Rajen Kumar. I’m a senior technical advisor at Adobe. I have more than 10 years experience working on AEM products. And then I have been certified into the work front and AEM and currently I’m managing more than 200 solution-led customers.

Perfect. Thank you.

So let’s go ahead and jump into the content we have for you guys today.

Great. Thanks, Jeff. And welcome, everyone. Today we want to take you through what the integration between AEM and Workfront looks like. We’ll touch on the capabilities of both of the tools as well as some common challenges that we see from our customers. We’ll also walk you through the strategic approach of this integration and how you can understand the ROI. We’ll then touch on what the content supply chain between AEM and Workfront can be before getting into a demo of the integration. And finally, we’ll cover who’s a good candidate for this and ways to optimize the integration once it is complete.

So chances are if you are on this webinar, you are familiar with either AEM assets, Workfront or both. I want to point out some of the key capabilities of both systems so that we’re all up to speed. First here, we have AEM. We’re focused on assets because that’s the main use case for this integration between AEM and Workfront. However, some customers have brought up an AEM sites use case. And if you have one, please feel free to discuss your requirements with your account manager because it’s definitely possible and we would love to initiate that. But for the purpose of this webinar, we’re focused on AEM assets, which is really a centralized repository of all of your digital assets. AEM centralizes the responsibility of applying metadata to your assets in order to improve the consistency and accountability. It has reporting capabilities that show assets uploaded and downloaded each month and a bunch of other reports as well. It allows users to distribute assets and do other key features like search, upload, download, share, etc. AEM has automated experiences that optimize rich media at scale and AEM allows customers to bulk import from cloud storage in a safe and efficient matter.

Now, AEM does much more than this, but that’s all for a different webinar. Now let’s talk about Workfront. Workfront is our project management software. I don’t know if anyone used to use AEM projects. That’s a big deep cut there, but it was our clunky solution to project management in AEM, which we were thrilled to replace with Workfront.

Workfront focuses on strategic alignment that connects business strategy to work delivery. It also emphasizes planning and prioritization to iteratively plan and prioritize your enterprise work. Workfront streamlines execution to personalize and automate your work processes, and it also allows for collaboration and approvals by simplifying these review processes and tracking audit approvals. Finally, Workfront also measures and optimizes performance and gives you the data to drive those decisions within your org.

Again, Workfront does so much more than this, but for the sake of this presentation, we’ll be happy to answer any questions you have. Awesome, thanks Jeff. That gives us a good understanding of some of the key capabilities.

Yeah, but some of the challenges we hear from our AEM and Workfront customers, and also just from surveying our Adobe colleagues as well, is that we found a few trends. Firstly, that many customers that own both AEM and Workfront do not have the tools integrated. We’ve also discovered that this may be from a lack of use cases between the two tools, or just two separate teams using the tools whose processes are siloed. We’ve also seen trends and challenges that the integration is simple, and just so we’re all aware, our product team has been dedicated to simplifying it as much as possible, but there is a lack of understanding what to do once the integration is in place or how the flow should work.

We’ve also seen that once professional services team completes the integration, customers may struggle a bit. Today we want to show you the main picture of how these two tools work together.

Let’s take a step back and consider the end-to-end content lifecycle as a whole. Today we encourage you to expand your mindset to not just one aspect of your content lifecycle, but the entirety of it. For many of us, we only interact with one phase of the content lifecycle, but it’s important to remember that assets are being managed in our organizations from the minute they are formed as an idea, and this idea is not complete until the realized asset reaches its end users or even is archived. So each organization is a bit different, but ultimately we can organize the end-to-end content lifecycle into the phases you see on the screen. Creation and ideation, planning and strategy, delivery and distribution, asset management, which I forgot, and reporting and insights. If you work in Workfront, you might be primarily concerned with planning and strategy, and if you work in AEM, you may be focused on asset management. But how can we make sure our content strategy is streamlined through each phase? It’s important to note that each and every one of your content lifecycles may look a little bit different. Some may be more linear and some may be more cyclical. It really just depends on your business, and it’s also important to note that each and every one of these phases often represents a team of people, meaning that each personas interact with each of this content. So considering all of the personas and considering each and every phase and touch point is kind of the first step in maximizing and optimizing the products you own. So what does it mean to have content go through maybe five different lifecycle phases and touch many different teams? Rajen and I talk to our customers each and every day, and these are some of the common problems that they face even when we’re not having specific discussions to content lifecycle. So we see trends and teams working inefficiently since they’re not communicating with each other. This leads to multiple teams doing duplicitous work or using the same systems but not instituting a universal strategy within those systems. We also see content spread across multiple systems, which sometimes things get lost and having email and Slack having to come into play where there are gaps in these processes. And often these systems aren’t integrated and these processes are more manual and less streamlined. We also see that within a certain persona or lifecycle these processes are siloed. Content goes into the black hole of one phase and there’s no visibility on the ROI or the content of these tools. So while you’re having these strategic conversations with your leadership team, note that the simple configuration between two Adobe solutions that they’ve likely already invested in can not only have streamlined workflows but also reduce disparate teams, reduce disparate systems, or reduce or eliminate siloed processes.

So how to tackle this integration? We’ve broken it down into three steps that you see above. Identify, integrate, and optimize. First determine if this is right for your team and your content supply chain. I have a feeling if you’re on this call you are likely a great the next step is to perform the simple configuration to connect the two tools together and we’ll receive a demo of this later in the call. And finally we want to determine a universal dam strategy between your systems and we won’t be able to get into the weeds of this during this call but as everyone’s strategy is a little bit different but we’ll definitely talk about how we can see value between the tools from there. So what are the main ways AAM and Workfront integration will help your processes? Really it looks like being able to access your dam and Workfront. With that your teams can search and find assets directly in Workfront. You can link assets right to a project or task in Workfront. Your metadata will be mapped and synced between two systems and you can automate the delivery of assets from Workfront. You can also you’re able to connect multiple Workfront instances to one AAM or multiple AAM instances to one Workfront instance. That’s huge when we’re considering your content life cycle and supply chain as a whole. Let’s go to the next slide.

In addition to the content velocity features of the integration we also wanted to point out that this out-of-the-box configuration can take minutes and is done via a simple configuration that admins can carry out. Again we’ll see this in a few minutes. Also single sign-on can be used via one Adobe profile to connect AAM and Workfront. Next these are integrated AAM components where the same asset capabilities and Workfront are also found within AAM. And then of course users have the right to access and the right content at the right times via the admin consoling permissioning. So now I want to hand it over to Rajan to give us insight into what these features could look like in the tools.

Rajan maybe go off mute if you’re speaking.

Thanks Keshi for giving the overview how AAM assets and the Workfront can integrate. So looking into the more deeper how integration setup is going to look like right. So as it is a native configuration so it provided native integrations and you don’t have to download or install any package to make these configurations happen for the AAM as a cloud services especially. And these configurations will be done at Workfront side where administrator can set up these configurations. So just to have these configurations done right you have to navigate to the setup documents experience manager assets and then click on the experience manager. So I’ll be showcasing in the demo as well where to navigate and then so and you can also configure the metadata from the AAM assets as well as the Workfront. And then another advantage of these configurations is like you can have a single or the multiple Workfront instance can be integrated with the multiple AAM repo. So let’s say if you have a stage or productions or the dev repo for the AAM side you can connect from the Workfront separately so you can just keep it track. So moving on to the next and a little bit of more deeper side of the integration. So when it comes to the configurations right so metadata configurations where you will do the mapping of the Workfront object to the AAM assets metadata schema and one-to-one mapping and then you have also options to sync those metadata. So any changes done into the Workfront values it will automatically sync to the AAM assets basically you don’t have to manually push asset again so it will get automatically sync. Then there are a few more configurations related to the workflow where you can automate the systems like a workflow like you can link the folder basically so asset will be automatically go into the particular folder and then another capability is publish asset automatically so as soon as asset goes to AAM from the Workfront it will automatically publish or you have configurations also let’s say if you are using a brand portal to distribute your assets you can also enable that configuration. Then another configuration you will have a link folder where you can just link folder let’s say if you are working on multiple brands and that’s where you want to have a parent folder automatically link you can just link those folder. We’re gonna just see in the demo as well but I just wanted to touch base upon the high level of the integrations then okay so moving to the next like it Workfront interface it also does provide the AAM component which is like a searchable things like where you can easily search any assets if you want to link asset from the AAM’s asset side and then this component have a features like a kind of you can search asset with the tagging and all and it all depend upon the permissions basically what permissions you have been given to the AAM side so if you have been given a permissions for the access in all the asset you will see all the required folder over here and you can navigate to those respective folder and then you can select a folder and if you want to select particular folder that also capability give so you don’t have to go to the AAM asset side basically from you will have AAM component searchable interface available and you can just search it then what are the value propositions this brings this both integrations together right so what are the things you can do it so you can send asset from the Workfront to the AAM asset side you can link folder from AAM asset to Workfront or you can create a deep link for the assets then you have options to configure automatically create a link folder then from the AAM asset side right you can from sorry you from AAM from Workfront side you can navigate directly to the AAM asset there is an icons available you don’t have to manually go to the AAM asset side then it does also provide the search capability where you can just find all asset of level into the asset side from the and then syncing the metadata between Workfront and asset side so these are the few value propositions brings on the table when you integrate Workfront and asset together so we’re gonna see a few of them in more details so looking at the send asset from Workfront to AAM asset right so how do you send assets so you will have a one task created basically and the task you will upload an asset from the asset you will just select the AAM integrations and then you can send it while sending the assets right it will just populate the window where you where do you want to save this asset into the AAM and then you can navigate to the these folder and then save it so you can easily assign the asset from Workfront to AAM side and only the considerations it is required like there are some limitations with the storage as well so when you upload a asset to the Workfront storage will be gone to the Workfront and when you push asset to the AAM storage will be gone to the AAM as well and there is some limitations with the asset size so probably you have to consider that limitations while you sending the asset from Workfront to AAM assets then support for the AAM schema property which I talked about right in the configurations basically so you have options to map Workfront object to the AAM schema field and once you set up a configurations basically one-to-one mapping and then you play with the asset upload and all it will automatically get synced to the AAM so we’re gonna see these all in the details in the demo also so you will get some understanding then a deep link I see like a lot of all options were related to the asset linking so deep linking is the one of the also another features which basically you can once you link the asset of to Workfront right so then you have the options to directly navigate to the asset without navigating to the AAM it provide a link and you can just click on the link and it will just take you to the AAM side and then you can see the property so it just quickly you can carry out all the operations and again I’ll say if you have a permissions to see then only you can navigate to the AAM asset side so with that I’m gonna showcase the demo with these all few of the capability and you can realize what can bring in the table how the integrations works together and what are the value capabilities so with that let me share my screen all right I hope my screens are visible so here I am on a Workfront side so before getting into the features of the these integrations I’ll just go and touch base upon the how the integrations and where the integrations is going to reside this native configurations right so oh once you get into the work Workfront homepage so you will have options to navigate setup and as I said that these operations can be done by the administrator so you must have the permissions into the Workfront to do these operations then you will go to the document and then you see the experience manager asset over there then you can click on the add experience manager integrations once you click on the integrations then it will automatically populate your AAM repo AAM instance repo basically so if you have been given access to the multiple instance it will just populate all the repo over here and then you will select it and that is why we need to have both the Workfront as well as AAM asset into the same org id so it can integrate easily so once you select this ones then it will automatically populate the in the URL of your repo and then all the configurations over there so let me open the configurations which I have already created so I’m gonna go to the configurations and edit this so looking at the configurations at that it’s a pretty straightforward you don’t have to do much from in terms of the integrating these two solutions so you have access to the instance you just select that automatically populated the navigations URL you will you’re gonna just provide the name of the integrations whatever as works for you and then you will be moving to the metadata configuration side so this is the place where you will map Workfront object to the AAM assets metadata field so I’ll showcase one demo also with the how it works also so as of now if you can see the task fields are mapped with the custom field of customer schema field and then this is the configurations basically sync object metadata so any changes happen to the Workfront side which has been mapped to the AAM asset right that will automatically updated if you don’t want to get automatically updated you can just on and off the this all configurations based upon your use case then moving to the workflow configuration this is what like the configurations you have create link folder so you can also have options to like a you can link create the link folder and then another options you can have a publish asset automatically see the use case where I come across customer have asked okay once my asset is already approved into the work work front I don’t want to just again publish to the navigate it to the AAM and then publish it is there any way we can just automatically publish as soon as I push asset to the AAM only right so this is what the configurations and along with that if you are using your asset to the brand portal here’s the configuration so in fact you don’t have to go to the AAM again and to publish to the brand portal so from here you can control so if you can select this configuration it will enable it so and this configurations will enable only when you have brand portal enabled so as of now I don’t have in my sandbox enable the brand portal so you don’t see this checkbox to enable it then this is the last configurations which is talk about the linked folder so where you can just link your folder with the parent one so basically you can have parent folder created and then append this one so and it does also provide you the options where do you want to link it right so it just populate the windows and it is all coming from the AEM side all the folder whichever folder you want to map it you can just map accordingly you just select that and then select folder it will just create it so then as part of that folder if you want to append portfolio and the program names and here’s the configurations you can check click on and then you can make the enable so this is at our configurations which looks pretty simple it’s a native configuration it’s not much to do just give provide the few set up the informations and it’s all done so and the best practices is basically you should have asset metadata schema created into the AEM as well and then when you are walking to the configurations at least you have all the field related so let me quickly jump to the AEM side so AEM side where are you gonna create a schema so you will navigate to the armor tool assets and then you will go to the metadata schema and i have already created it weekend holiday so but if you have to create a new you can click on the create button it will just give the option so let me open the already created weekend holiday i did so i have few set of the schema field so basically one is the project name then reference number and sales category descriptions revenue tab and discount so and few of the field i have mapped into the work front side so and this once you create a metadata schema and it’s ready so then whatever and do you can just select that and apply to the parent folder of the your brand where you want to apply this metadata schema and then so in for my case i have applied to the holiday folders and since i have already applied it’s gonna just say okay it’s going to override so i’m going to override so from um verifications perspective whether it’s got applied or not you can navigate to the asset side and then you can go to the files and then click on the folder and go to the property it will just showcase okay metadata schema we can where it is already tagged all right so now i have already created the schema into the aem i want to map those uh filled with the work front object so um so this is the what configuration so let me go through again so what i did basically the task categories is mapped with the holiday product this is the custom so all the uh custom field right you can just whatever the schema you have into aem it will just automatically populate it so you can see uh all the custom uh fill metadata field is populating over there and you want to map it you just select any of them and then i this side you will have a all the work front object so if you want to uh select any of the field uh let’s say for the name just i’m taking one of the example uh so i want the name from the task so you will have all the objects available over here you can just select that it will get mapped so this all the configurations has been mapping done so let’s test it how it’s gonna work with the uh life so right so all right so i have a one um projects has been created already for the holiday season and uh for the new task has been created christmas sales so what i’m gonna do uh for this task if you see if you go back to the task details so i have a name of the task christmas cells and then the descriptions and then i have custom uh forms in the work front as well which have the holiday sales information so like a product category sales category discount and the users rights and now what i’ll do i’ll go to the document side and i will go to the uh add new to just upload one of the assets basically so i’m going to upload uh one of the assets so let’s select these assets once this asset is uploaded now uh now you can see the difference basically so you can see there’s a icon here so once you asset is moved to the aem side then it will generate the icons which means it generated the deep link basically so asset has been already linked but if it is not there it will not so so now how do i send this address asset to the aem site so select that then there is a arrow options over there which you’re going to click that and you will have a integrations name whatever the name you have given while doing the setup you click on that aem integrations and then it will give you the options so where where do you want to uh save this asset right so uh i will go to the folder where i have created so this is my folder and holiday so this is for the christmas related things i will just select that folder and then i will select this one so this is going to uh send asset from uh work front to the amc now you can see the asset has been successfully sent you can see the link over there now um let’s check whether the asset has been pushed to the aem or not so you can directly navigate from the this deep link click on the link it will take you to the aem and you must have the access to the am side so now let’s check whether those metadata asset which was the mapping was done right whether it has been synced or not automatically so you can see the project name so project name was mapped with the work front object which is a task name so this is the christmas cell so you can see the name is already there then reference number which is mapped with the task details the reference number so you can see the two one three five one so which is already available then uh cells category is the christmas so if you see the um value over there right cells category christmas this constant percent so you can see all the things value this content percent and then descriptions and then product category right and there are few additional metadata of will uh which either you can just map it or you want to keep it to only these fields can be updated only from the am side so that is also the option but just wanted to let you know like um all the mapping fields the value has been automatically up updated now um what we’re gonna do uh let’s change the discount value from the 10 to 20 percent and we’ll save it and we’ll see uh whether this value get updated or not so we’ll see in some time before that uh let me uh go through the another use case so this is where you saw where um basically you have to choose the folder so while helping to the customer uh i came across like okay is there any options where i don’t have to choose the options i know uh is for the uh us campaign i’m gonna run and i can pre-link all those folder directly so if i upload it it should automatically work right so what i’m gonna do uh i’m going to create a new task just to be in the and with the name of the task new yourself and then just add the descriptions click off the new here cells and then just create a task and uh let’s go to this task and what i’m going to do i want to add the custom forms as well so i’m going to add the custom forms what we have from the created one so i have added the custom forms let’s choose the categories like uh anything and then sub cut cells category you can just select the new years and then this con 10 percent use this right yes then save it okay now what i want uh this uh task whatever it is created i want all the assets being uploaded to uh this task automatically update to the aem side so how you can do that you can just link your folder so you can click on that add new and then go to the your integration side then go back to your uh folder where you have it so let’s go to the folder then let’s go back inside i want to just link it with the all the new year cell related so i just linked that and before so pressing here let’s see the aem side also if you see the new years right you will see that these folders are already created into the aem side so you can see the digital product health and beauty and this clothing accessories so these all fields will be going to be available over here so you can see automatically when you created a link these all folders has been uh created now if you want to add any uh asset over there you just click on the document or either you can just drag and drop so i’m going to click on the document and then i’m going to select any one of the assets over there as soon as you it get uploaded it will be automatically available to the aem so since the folder has been already linked you can see the icon it has been already linked and let’s check out whether the metadata fields also got updated or not so let’s click on this dip link it’s self-processing so it’s going to take some time you can see that it’s automatically populated the project name new year cells reference number cells category is gone and the product category so by this way you don’t have to uh again uh schema metadata value automatically sync and then asset will be also automatically uh come to the respective folder where you want you don’t have to manually select because is for the each campaign running you know where you want to add all those folder right so you can just uh add here in the respective folder automatically it will go to the aem sites another way also if i go back to the uh task the krishmash one and we wanted to check we have updated the value for the discount value this one’s 20 uh so we will see whether it got sink or not so you can see the value has been all automatically synced so you don’t have to just come to the aem side and then update it whatever the data you are updating a work front side it will get updated over there all right and you can also link uh assets uh from the aem side as well so uh rather than a use case like i want whatever the asset into the aem i want to add to the work front side and i’ll ask someone to approve whether this asset looks good or not right so for in that case also you can just click on the add and then from uh navigations point then you can just go to the respective folder and whatever for the assets you want to link then you can select that it will just get link over there and then you can send this task to the approval manager and ask them to review the whether the asset looks good or not and then if it looks good then yeah complete the task so this is the other ways basically you have all asset into the aem first and you want to get it review from the task created in the work front side then last capability just wanted to touch base upon so one you are in the work front and from the work front side you can directly navigate to the aem and that’s where it comes like assets so when you click on asset you have access to the your aem asset repo it will just automatically redirect to the aem side where you can just play around with them so yep that is what i had to share as part of the demo i’m gonna pass this to casey to talk about more on the best practices great thank you for a fabulous demo rajan so if that all looked great to you i want to take a moment to reiterate who is a good candidate to integrate aem and work front so first of course if you own both products and have an interest in integrating but also if you own one product and are looking into purchasing the other implementing one solution is of course a great time to set up this integration i want to note that this says cloud service customers this integration is also available in other aem versions such as on premise or managed service but the integration is less out of the box and it’s not just a solution it’s just using the native connector and just so we’re all aware all new updates to aem are done for cloud service customers so if you did want to make a significant investment in this integration in your content supply chain it might also be a good time to upgrade to cloud service so if your team is dedicated to enhancing your content supply chain of course or asset management processes you would also be a good candidate and if your team is a good candidate you would also be a good candidate for quick time to value with this out of the box functionality i’m sure your boss would love to hear about how you performed a simple configuration and now your tech stack is more integrated so we also recommend this integration if you have active technical teams or dan librarians to manage and overview the integration as a whole typically with anything aem and work front we recommend yeah technical and business side of things to keep everything afloat so what to do with assets once they reach aem i know we focus mainly on the integration aspect of the strategic approach but the last pillar of how these two tools work together is really through dam strategy so while you’re planning this integration we urge your teams to determine and roll out the universal dam strategy the first step is to understand your current content supply chain and all the touch points in your content life cycle what data can help enhance or automate those processes and then try to determine a scalable dam strategy so implementing a standardized manner of filing and managing assets can result in strategic efficiencies across your organization like increased reuse of assets minimize duplication and reduce time spent searching and sharing assets so investing time and effort to develop this structure can increase adoption for all the business users involved and there are three key features to standardize on an aem assets implementation those being folder structure metadata schemas tag hierarchies and naming conventions so there’s many questions in the chat about schemas and whatnot they’re super flexible in aem once you kind of look through every single aspect of your damn organization go through and make any schemas that need to be done that can be on the folder level on the dazit type level really just whatever makes sense to your business and all of those will be synced between the two tools if you do choose to integrate and then of course you can work with a business advisor if you have questions pertaining to dam strategy and something else to keep in mind is considering a search first experience so how the users in both systems find the content and which fields or tags can be used to make sure that’s streamlined and finally we’ve talked a lot about how this integration can reduce disparate teams systems processes etc with that comes change management so i briefly want to touch on some quick ways to ensure users are adopting these changes before we get into q a so first we recommend treating this integration as a small launch with that you can pilot these new features with targeted groups and ensure that they’re onboarded this is also a great time to gather feedback and tailor training specific to the questions that arise one of the biggest things that we tell our customers is whenever they have questions about these integrations if they’re already being set up a huge aspect of it is just testing making sure once things are set up to say do they work for each and every one of their use cases are they breaking are there things that are slipped through the cracks testing is a huge part of it and i know it takes a lot of work but definitely will help with this change management rollout and next we also recommend a clear identification of the roles and responsibilities of the users of each system so a dam librarian is typically best practice but it really just means anyone that can make sure that the data systems processes etc are running smoothly we’ve also seen customers create a center of excellence committee that is dedicated to improving the processes so essentially i know we threw a lot of information your way we’d love to jump into some q&a with our remaining time yes thank you casey rajan that was awesome all right everyone as promised let’s go over a few questions you submitted to us today so rajan let’s kick it off with with you where should the metadata tagging occur in aem or in workfront yeah sure so basically if you want to map work front object with the custom any of the aem metadata schema obviously you first gonna create a schema into the aem side once it is ready then you’re gonna map with the existing work front object but there could be one use case where you want you have a custom forms as well in work on site and you want to map with those in that scenario you’re gonna create the schema field in the both the side what you have seen into the demo got it perfect and this next one’s for you casey how can we use work front in our website offers yes so we mentioned it a couple times but the main use cases between aem and work front typically fall under the aem assets realm but if you did have a use case for sites we’d love to scope it out it would look somewhat similar to what we’re seeing in assets but instead of those like assets that we’re approving and sharing content with it might be pieces of content so definitely talk to your account manager about your use cases and requirements and we can go from there got it i’ll go back to you rajan for another one how long can we expect the integration to take well so uh native integrations especially with the aem as a cloud services is just like a couple of minutes for the configurations as long as you have the metadata already created from the both side and you know the what mapping has to be done so integrations is a straightforward and just good to go and later on if you have any additional capability in the integrations configuration like publishing linking folder you can always go ahead and update the integrations but from the initial level of the integration this is a pretty straightforward and just a couple of clicks got it uh thank you and staying with you rajan a similar one what are the integration options for on-prem aem versus cloud aem right so what you saw today uh in the demo that was related to the aem as a cloud service integration that’s the native integrations but there are connectors available for the customer who are still on the aem or ams or like on-prem they have the options to install the package in an enhanced connector to the real instance and then do the all required state of the configurations where you have to do a lot of configurations not no i would not say the to the aem as a cloud service integrations but there also you have options to map all the schema and all the required set up the configuration so just to go further you have to install the connector package basically got it all right uh thank you very much and on that note let’s end it with our final question of the day and it’s a really great one casey how can we show the increased roi of the partnership between aem and workfront when proposing the solution to a leadership team yeah so i think the big aspects here and specifically we could talk about increased reuse of assets minimize duplication reduce time spent searching and sharing assets but also as we talked about combining your team so that these processes are less disparate so that your systems are less disparate those are kind of the big pillars that we can talk through with your leadership team perfect thank you both for all of the incredible insight with that everyone i want to quickly wrap us up today on this screen we have a few survey questions for you as well as one more opportunity to let us know if you’d like more info on either aem or workfront and how they can integrate within your workflow if you have any specific question for your account that we weren’t able to address today please reach out to your solution account manager if you’re not sure who’s that is you can reach out to me directly and i’ll put you in touch with the correct person and as a reminder you will receive the recording of today’s event in an email from us in 24 hours so that’s all for us today thank you all again for attending we really appreciate it have a great rest of your day and we look forward to seeing you at one of our upcoming events