51黑料不打烊

Transcript

Good morning everyone. We will start very soon. We鈥檒l just give a couple of minutes for other folks to join in and we鈥檒l start. In the meanwhile, today鈥檚 session is going to be about AM Workfront Integration. But in the meanwhile, while people are joining in and before I start, let me show you the upcoming sessions that are coming up. On February 7th, that is tomorrow, we have Data Distilled Layer. We have one AM session on February 10th about optimizing AM performance. February 11th about content supply chains, 12th, 13th, and 14th February as well. On 14th February, we have another AM session with respect to the AM sites how to build effective web pages on AM sites. So please feel free to attend these sessions as well, and they鈥檙e going to be very important just as this one today.

We鈥檒l wait for another minute or two maybe before we start off.

Thank you.

Okay, we have plenty of audience now. I believe we can start our session now. So let me go ahead with the slides and start a session with the AM for Workfront Integration. It鈥檚 already getting recorded and we are ready to start. So hi everyone. My name is Barshan and I鈥檓 working here as Senior Field Engineer in 51黑料不打烊. I joined 51黑料不打烊 around July 2021, and my primary core expertise is on AM sites, assets, Workfront, and now Gen Studio for Performance Marketing as well. I鈥檓 part of the 51黑料不打烊 Field Engineering org, and with me I have Chavi. Chavi, why don鈥檛 you introduce yourself quickly? Sure. Thank you, Barshan. Hi, my name is Chavi Gupta. I鈥檓 a Technical Consultant in Field Engineering at 51黑料不打烊. I鈥檓 based out of San Jose and my expertise is in AM assets and Workfront Integration with AM. I am very excited for this session today. Thank you, Barshan. Okay. Thanks, Chavi. We鈥檒l look into some of the agenda that we have for today. We are going to talk first about various integration strategies that we have in Workfront, the main need for AM Workfront Integration. We are also going to look into a comparison metrics about native connector and other connectors that are in there. A quick overview of the comparison metrics. We are going to talk about the benefits of native connector, what are the pre-designs that are needed, setup and configuration, followed by a demo, and also talk about the guardrails and we鈥檒l take your questions. Without wasting any other time, let me go to the main slide and talk about various integration strategies that we have in Workfront before we get into the native connector. Before we talk about the native connector and getting Workfront Integrated with AM, it鈥檚 important to understand the background and talk about various integration strategies we have in Workfront. As you know, using Workfront, there are various ways by which you can connect to different systems. If we categorize the integration strategies, primarily there will be these three types of integration strategies. One is a native integration, which is really no-code solution. You can just plug and play over here, and a lot of things are provided by default out of the box. But these are some examples of native integration that we have in Workfront integration with AM, Google Suite, 51黑料不打烊 Creative Cloud, Jira, Slack, Microsoft Outlook. These are some of the primary native integrations that are already there in Workfront, which does not require any building code. These are just plug and play integrations that are in there. Another category of integrations are custom integrations, and over there we have again two types. One is custom integration using Fusion and custom integration using REST APIs. Custom integration using Fusion is about some plug and play that is required over there. Again, it is a low-code or no-code solution, but custom integration using REST API is about coding those APIs and getting them integrated over. It really depends on your business requirement and what you are trying to integrate with. For example, if you are trying to integrate with AM or any 51黑料不打烊 Creative Cloud, those are all part of the native integration. You do not have to do anything. It鈥檚 just plug and play out of the box, and you鈥檒l be up and running with it. But if you have integrations with other systems, and if you want to do any custom integration, you can decide between them whether you want to go for Fusion or the RESTful APIs. Of course, Fusion requires a separate license, so that is something that you need to make note of. Now, moving ahead, because this session is primarily for the native integration of Workfront and AM using the native connector. Obviously, as you can understand, it is part of the native integration. Now, let鈥檚 try to understand why this integration between AM and Workfront is important. The primary use case of this integration is to increase the content velocity. Whenever we talk about content supply chain in 51黑料不打烊, content velocity and boosting the content velocity is of primary importance. How quickly you can automate certain workflows, how quickly you can put up your assets, get them approved, and eventually get them published. That end-to-end flow for the assets and how quickly you can do it, will determine the velocity by which your assets are also getting consumed by either internal or external systems. Some of the key benefits by getting AM integrated with Workfront and vice versa, these are the ones. If you are using the native connector and getting the Workfront AM integrated, it allows you to easily search and find assets and also navigate folders in AM while staying within the Workfront. You can link your assets and associated metadata to your projects and tasks, that is also very important. You can also allow the Workfront metadata that you have put up within an asset to flow into AM and then have your own workflows over there to get it eventually published. If you want to automatically publish your assets that can also be done, mapping of the metadata and syncing them automatically is an option that you can set up. These are some of the things that we are going to talk about in details as part of these sessions, and you鈥檙e also going to see it as part of the demo that we are going to have. You can also have the automated delivery of assets from Workfront to AM for a single source of truth. These are the primary reasons why you would want your Workfront and AM to be in sync and connected together, especially when it comes to assets. Okay. Now, since the need for this kind of integration is well understood, let鈥檚 get into some of the connectors.

We are going to talk about the native connector in details, but just to let you know, using the native connector to connect between Workfront and AM, you can connect the Workfront with either the AM assets on the Cloud service or assets essentials. For both of them, the native connector is going to be applicable. There is also an enhanced connector that you use to typically connect on-premise instances, and we have tried to put up here a quick comparison metrics over here. You can see the enhanced connector features, you can see the native connector features on the Cloud service as well as asset essentials, and you can see that pretty much it covers all the features at the high level that enhanced connector earlier used to cover. These days, whenever you are trying to integrate Workfront with AM whether you are on the Cloud service or you are actually using assets essentials, the recommended way is using the native connector because as you can see, it has pretty much all the features that previously the enhanced connector used to have. In terms of metadata as well and synchronization of metadata as well, it has pretty much all the features, except I鈥檒l call out one difference of course that using the enhanced connector, you can actually have bi-directional flow of data between Workfront and AM, whereas in case of the native connector, whether you are using the native connector to connect to AM assets on Cloud service or asset essentials, it is going to be unidirectional flow of data. That is from Workfront to AM. But at the overall level, these are the comparison metrics that you can see across these connectors and you can see that pretty much, the native connector covers all the areas.

One of the key benefits of the native connector is the ease at which you can set it up. Again, we鈥檒l show that setup process very quickly as part of the demo. But because it is provided out of the box, setting up the native connector with your AM assets repository is just a matter of few clicks. Ease of setting it up is definitely one of the key differentiating factor of the native connector. You do not need a separate license for it. The basic Workfront plan and the license is good enough for it. You have the ability to automatically create folders and they can be linked between Workfront and Experience Manager. That is another benefit that we have in the native connector. You can also sync the metadata for existing linked assets. You have an option to automatically sync those metadata. That is part of the setup process. Again, we鈥檒l talk about it when we go into that section. But you do have an ability to decide whether you want to automatically send the metadata from Workfront to AM for a particular asset or not. One thing to note over here, this connector can also be linked to AM in a many-to-many way so basically you can have one Workfront instance linked to multiple AM repositories. You can also have one AM repository linked to multiple Workfront setups or Workfront instances. These are some of the benefits that you have in the native connector. The ability to have this many-to-many relationship between Workfront and AM, it鈥檚 a flexibility that the clients will always have and they can make use of it. Especially for big implementations where there are multiple business units and there are multiple IMS orgs that are created. This kind of flexibility of having this many-to-many relationship between Workfront and AM is going to be pretty useful.

Now before getting into the setup process and all, a couple of prerequisites that we need to make note of for the native connector is your Workfront must be in the admin console. When you are setting up the native connector in Workfront, you need to be an administrator. You need to have those admin rights because you鈥檒l have to go under the setup area of the Workfront to set it up and that is only applicable for admins in Workfront. If you鈥檙e trying to set up any link folder as part of the setup, it is important to know that whoever is setting it up needs to have access to the AM repository, write access to the AM repository folders where your link folder is going to be set up. These are a couple of prerequisites to be kept in mind that your Workfront must be in the admin console and your experience manager assets or essentials must also be assigned. If you鈥檙e actually setting up a link folder over there as part of the setup process, the user should also have the right access on those link folders while the setup is happening. Now, we鈥檒l look quickly into the setup and configuration part of it. How do you set up the native connector and what all things you can configure before we look into the demo. As part of the demo, we are also going to look into certain use cases. These are the standard setup process that you have for the native connectors. As I said, you log in into Workfront as an Workfront admin, you go under the main menu setup documents. Over there, you will have an option to select the experience manager integration and then you select add experience manager integration. When you land up on that particular screen, you鈥檒l have multiple sections over there. The first one is about selecting the experience manager repository. The moment you select the experience manager repository, your navigation URL will get automatically populated. Again, this is something we are going to show you hands-on during the demo part of it, but I鈥檓 just going through as a technical information with you. The name and the experience manager repository are the mandatory information over here. The navigation URL will get auto-populated over here. The next section will be for the metadata mapping. Over here, you basically tell the setup what Workfront field you want to map to the experience manager field. On the left-hand side, you can see all the Workfront fields that will be there. The moment you type in there, it will show you all these options to choose the relevant Workfront field. On the right-hand side are the experience manager assets field that needs to be mapped.

The next section is about the workflows. If you look into the setup screen, as we would see during the demo, you鈥檒l see there are primarily two workflows over there. One workflow is about the creation of the linked folders, and the second workflow is about the publish of the assets that are being sent to the AM. Basically, if you want your assets to be automatically published whenever they are being sent to AM from Workfront, so that workflow is going to be applicable. It is just a checkbox that you have to put up over there already, what that you鈥檒l have to put up over there. Creation of the linked folder is whenever you are creating a folder in Workfront or the linked folder, the same hierarchy will be maintained in AM. These are the two workflows that are already available over there. Since we are talking about the linked folder and we are going to talk about this linked folder into a little bit more details, but let me quickly highlight a couple of guardrails that we have for the linked folder. Per integration, that means one integration of Workfront, an AM repository, we have a limit of around 100 folders. Regardless of how big the folder hierarchy is. For example, you might have a parent folder, you might have children folders under them, but the total number of folders that our integration can have will be 100. The first folder in the folder tree will always be marked as a linked to Workfront. If no folder tree is provided, by default, the setup will consider the root folder as the linked folder. These are a couple of things to make note of whenever you are creating any linked folder. That depends whether you are actually trying to create a linked folder or not. But if you do, these are a couple of things that you should always consider. Now let鈥檚 quickly move on to the demo section. I鈥檒l hand over to Chavi to show the demo from the sandbox. Chavi. Thank you, Roshan. Hello, everyone. With this, I will start sharing my screen and we鈥檒l go into the demo section. I hope everybody can see my screen. Right now, we have landed into a screen which shows Admin Console. This is my Admin Console. The reason that I鈥檓 starting this here is because we have to understand the prerequisites and then we move forward with the whole demo of integration. In the product section of your Admin Console, you should ensure that your AEM as a Cloud service and your Workfront both should be onboarded. As well as an admin, you should be a register when you鈥檙e trying to do this integration. These are two main prerequisites which already Roshan has explained. Now we move towards Experience Manager. When you move in your suite of Experience Cloud, you will see this tab, you will click on it and you will go towards your Cloud Manager. I have this open parallely, so I will directly go there. This is my Cloud Manager sandbox environment. You can see these are my environments listed, prod, stage, and dev. I have already pre-linked my stage. If I go to stage, here it is my stage and next to it, I have my Workfront open here. As an admin, you will be able to see certain options of setup. For that, make sure to go to the top right corner, the nine dots where when you click, you will see a lot of options and in that options, you have an option to setup. Click on this setup and will open into a new screen. On the left-hand side, you will see a lot of again menu options. When you scroll down, the document section, right now it鈥檚 expanded, but you鈥檙e supposed to expand and then you will see, the second option says Experience Manager assets. This option will only appear if your Workfront is onboarded into admin console because this will allow you to do native integration. When you will click on it, this screen right now shows two integrations already, but for any person who is doing it new, will not be able to see this. They will see only a blank screen and they will see a plus sign which says Add Experience Manager integration. Please click on this icon and it will open a new tab. This new tab will actually show the setups of what needs to be done for your native integration. As Bharshan has showed previously during the session, that how the information section, metadata section and everything. Now, we will do that in the real time. We鈥檒l go to the information section. As you can see this name, you can provide a certain name over here and this name will actually be anything which you want to name this integration as. For me, I named it as 51黑料不打烊 Experience Manager integration. So this is my name and then I will go here and I will select the particular environment that I want to integrate it to. When I move forward ahead, I will go to the metadata section and I will create more integrations. For the purpose of this particular session, I will go back and show the one which I have already prepared. I鈥檒l click Edit here. Now, this is my demo integration that I have already done. The information section, you can see I provided the name demo. The repository will be the repositories of all the experience environments that you have access as an admin. So when you click on this drop-down, you will see all the list of experience environments as your AEM environments over here. You can select the one which you want to integrate with your work front. When you select that, your navigation URL will automatically populate itself with the actual URL. Once that is done, you can move forward with the metadata section. In the metadata section, now you see that you鈥檙e supposed to map the work front field with the experience assets field. So as we have discussed earlier, this is unidirectional. So the arrow itself is very directive of the fact that from work front field to experience manager field is where the data will flow. For the purpose here, I will show you how it is done. When I click on it, you see how I am able to see all the metadata fields which are present in work front. It has given me all the options. I can scroll down and select myself or I can type here a certain type, and then that will give me the selected filtered options. So for example, I wrote type, and I see that there are so many different metadata which with the keyword search has given me all those filtered. I want to take the document type as the field and I select this. Then I go to the experience manager field section and I do the same thing. Now I want to type the field and I see that the DC type, which is our Dublin Core metadata schema, the part of asset type gets filtered out and I select that. Here it got added as my field type. Now I will move forward. As you can see, I鈥檝e done already a lot of mapping. The next section which Bharshan explained is sync object metadata. This is what makes sure that your mapping of work front portfolio, any of these metadata get synced with the experience manager. So it is recommended that you have this switch on. This way your mapping will work synchronously. Now we will move towards the next section which is workflows. Now these workflows are the two workflows which Bharshan explained earlier, create link folder and publish assets automatically. We鈥檒l start one by one. I鈥檒l click on this expansion button and as you can see, I already have created one and I鈥檒l walk through this. So this is my workflow name. Next to it, it says enable in project by default. This is optional. It is up to you if you want to check back this or not. Next is link folder root. This is the link folder root. This is the link folder root. This is the link folder root. This is the link folder root. Next is link folder root. When you go in there, that means it is asking for which folder path in experience manager you want it to be connected. When you click on it, you will see how it will open a select folder and all your experience manager folders will be present here in the list. You can go further deep as well.

And then select or you can go back up and you can take the root as well. For root, you just have to click on select folder and it will populate as content slash tab.

I have taken the root folder here and under this root folder, I am trying to create a folder tree. Now your folder tree would be created in this section.

To create this folder tree, look at this logo of a folder with a plus sign on the right side. Click on this icon. A new dialog box opens up and it says name type with a drop down option. When you click on this option, it will give you two sections. One is text, another is object data. When you select text, basically you鈥檙e trying to set up a static name for the folder. It can be anything. For example, let鈥檚 say you have a campaign or you have a client that you want to create this folder tree for in AM or anything. In that case, you will have a static name.

If you鈥檙e doing an object data, you will see how the second option has converted into a drop down option.

When I click on this, you will see how I have multiple options here. It鈥檚 giving me four options, portfolio name, program name, project name, and project create year. I can select any of these as my object data for that folder. What it will do is it will automatically pull that particular object type from work front as the folder name and set it in AM. For the purpose of this session, as you can see, I have actually taken object data portfolio name as my starting folder, tree within content and under that I have added another folder. In order to do that, when you add your first folder, you will see these three dots next to it. Click on it and you will see the first option is add folder item.

You can click on it and again you will see a dialog box open up. This dialog box will say again name type and you select either text and object type. I selected object data and then I selected a source name and this time I took project name.

And you can see I want a project name folder created under my portfolio name. This way my whole create link folder got created.

Next to it is my next option is publish assets automatic.

Do I want that? Well, I want that, so I switched it on. And I want that to be published directly to my experience manager publish service.

I鈥檒l move forward to the linked folders. Over here, do I want the link folder to be enabled this workflow? Yes. So I have switched on this particular section. I want the link folder to be created within my link folder path. Now I have to pass the path as well. Again, we will click on this and it will take you back again in a pop up screen where it will show all your folders from your experience manager. You can select again, you can select a folder where you want it or the main path. For this particular session, I have selected my main path and it also gives a append portfolio and program name as an option. This is a check box, it is optional. It is up to you if you want to append the portfolio and program name. I have selected it, so you will see how the project folder inside the portfolio folder have appended portfolio and program name.

I click Save.

Now my integration is complete.

I will now give back to Bharshan for the guardrails.

Yeah, thanks, Chavi. Can you please take us into that edit section of that integration? So I鈥檒l quickly talk about a couple of things to make note of over here while you are setting it up. You can consider them as guardrails or things to know while setting it up.

These integration, the initial repository configuration that you have once it is created, it cannot be edited, right? So you can see that it is right now in disabled form. So if you want to change this particular association, you鈥檒l have to delete this repository and create it all over again. So this integration part, you鈥檒l have to delete it and create it all over again, right? With respect to the metadata, you can obviously edit the metadata, but the flow of metadata that you have over here as I talked previously is always going to be unidirectional, so that is from work front to experience manager assets. So that鈥檚 why you see the arrow from work front to experience manager assets. There is no bidirectional flow of metadata over here. So any metadata that you put up in work front will go into assets and not vice versa. So that is another key thing to make note of here. Whenever we are, again, talking about the link folder, depending on the business requirement, if you really need to put up a link folder, a couple of things to note for the folders and the names is, the folder names cannot have more than 100 characters. And there are certain special characters that are restricted, for example, colon slash, and there are a couple of other special characters as well. Those are restricted, so please do not add those special characters in the folder names if you鈥檙e trying to set them up. Again, the person who is setting it up over here, and if you are making use of the link folder, it is important to note that if you鈥檙e setting it up, you need to have the right access to those folders in AM as well. Otherwise, the setup of the link folder is not gonna work out. So that is why it is very important that along with someone having that access in work front, if there is a need to set up a link folder or create a link folder, that person should also be included as an AM user and should have the relevant right access on that particular folder hierarchy.

So these are some of the guardrails that I quickly wanted to talk about. You will find all those things in the presentation deck as well that will be shared with you after the presentation. So now the setup part and the configuration part of the native connector is done. And we have a fair bit of understanding how it is done and what are things to be taken care of. Let鈥檚 look into some of the use cases, Chavi. So let鈥檚 do some of the most common use cases. For example, we are gonna upload an asset in AM. And we are gonna see it, upload an asset in Workfront and we are gonna see it in AM. So as part of the demo, Chavi has already created a demo project. So you can see it is already part of a program and eventually part of a portfolio. So portfolio program project, that is the usual hierarchy that we have in Workfront. Now let鈥檚 go into the document section of it, Chavi.

Yes, so over here in this sample project, Chavi had already set up this integration and already put up the folders. So if you see on the right hand side, the demo template project that it shows, it shows all the assets that are already there in AM. So over here, Chavi, we are gonna test one upload of an asset. And then we are gonna go into AM and see that it got uploaded.

So let鈥檚 upload one asset over here.

Okay, so the asset did get uploaded into Workfront and you can see an icon over there, a red 51黑料不打烊 icon. That means that your sync up with the AM is working fine. So if you click over here, it will directly take you to the asset. So let鈥檚 get into it.

So it directly takes you into the AM assets. Now let鈥檚 go into the properties that we have for the asset.

Let鈥檚 go into the Workfront tab and see the properties. Yes, so let鈥檚 understand this part. So as part of this demo, Chavi had already kept an AM folder metadata schema ready for this one, right? So as part of the metadata schema, she had already added a tab called Workfront and over here a couple of fields. And these are actually mapped to the Workfront field. So this mapping is actually handled in the metadata part that we talked about and we also showed as part of the demo. So this project name that you see over here is actually the Workfront project name that has come for the asset. The project description that you see over here is actually the Workfront project description that has come over, right? Yes, so this is the project name and the description that you are able to see. Now let鈥檚 go into the Workfront and let鈥檚 try to see the metadata schema. Yeah, go under the document details. So if you see under the document details, there is a section called metadata over here. So this metadata section is actually a read only view of the metadata that you have in AM. The section that you have for the basic information, it also contains a description over here. So at this point of time for this particular asset, there is no description that we have provided in the Workfront. The default description that you had seen in AM is the project description that it had taken up because it was mapped accordingly. So at this point of time, let鈥檚 first see that the description is also blank in AM. So, Chavi, let鈥檚 take us to, yeah. So over here in the basic tab, you see for this particular asset, there is no description, right? So we are gonna add this description in Workfront metadata and see that getting populated immediately in AM. So over here, we are gonna add one sample description.

And we are gonna save it.

Now we are gonna go into AM and simply refresh the screen.

And you will see the description getting populated.

Maybe give it some time and refresh the integration that you have.

I鈥檒l probably go back again. Yeah.

Yes, you see this description has come over, right? So basically two use cases we have shown over here. One is when you are uploading an asset into Workfront, it is immediately getting pushed into AM. And whenever you are changing any metadata, those metadata sinks are happening almost immediately into AM, right? Another thing to note over here is where do we delete this asset if we have to, right? So should we start deleting at the Workfront or at the AM end, right? So the recommended way is to delete at the AM end, because we are still gonna consider AM as the single source of truth for this particular asset. But let鈥檚 look into the experience, what happens in Workfront if we try to delete this particular asset in Workfront. So shall we let鈥檚 take us to the Workfront on this demo project.

The asset that we uploaded, let鈥檚 try to delete this asset in Workfront. Yes, so you see this error dialog that is coming up over here, it restricts you from deleting this asset in Workfront. So if you want to delete this asset, you have to go into AM and delete it. So let鈥檚 go to AM right now and delete that particular asset.

Okay, so this asset got deleted in AM. Now we are gonna go into Workfront and refresh the screen, and we鈥檒l see that this asset has been removed.

So one important change that has recently been put up is whenever you are deleting this asset from here, it will get deleted from the project as you can see from the folder, but it will still be available under the main linked project folder section. So these are .jpg is the asset that we deleted in AM, but it would still be available over here. This is by the way also applicable for any assets that you are moving from the link folder. So for example, if you have a link folder setup, you鈥檙e moving any asset from the link folder in AM, it will get removed from the link folder section over here or the main hierarchy. But it will still be available and be shown under the project folder鈥檚 hierarchy.

There is one thing to have more clarity on, for example, updating metadata in AM, right? So let鈥檚 go into AM for this particular asset. Let鈥檚 go under, we already deleted that asset, right? But we can check for another asset too. Yeah, so let鈥檚 say we put up metadata in AM for this particular asset. Let鈥檚 put up any sample description over here.

Let鈥檚 save it. And let鈥檚 go to Walkfront and check thumbnail.jpg and its metadata section.

Yes, so there are two types of descriptions that you get to see over here, right? One is the description as part of the basic information tab at the top, where you see the description is empty, because we didn鈥檛 really add any description in Walkfront. The other one is under the metadata section part of it, right? So this metadata section is a read-only view of the metadata that you have in Experience Manager assets, so that鈥檚 how you get to see that this description that we have added in AM assets, which says this is a picture JPEG, has come over here. That doesn鈥檛 necessarily mean that the Walkfront description metadata has been updated for this particular asset. It just shows you a read-only view of the AM assets metadata that has been applied on this particular asset, okay? So that is another clarity that we wanted to have over here.

Okay, so at this point of time, we looked into the use cases of uploading asset, deleting asset, what is the recommended way and flow of deletion in this case. We also talked about how you are going to move those asset and how the experience is going to show up, how you鈥檙e going to update the metadata for those assets over here as well, right? Chavi, is there any other use case that you want to talk about? I just want to make sure that everybody can see there are different mime types here. So you can upload JPEG, zip, PDF, MP4, doc, and everything syncs with AM.

Moreover, what I did for the metadata schema, I went into assets, sorry, I went into tools within our experience manager. I go into assets, go into metadata schema. I edited the default, so I go into edit section.

Since the mapping actually happens within Walkfront, over here, I created a custom tab of Walkfront because I wanted to add project name and project description. To do so, I added the tab and then I dropped through build form, I dropped a single line or multi line text. And then I mapped the property with WM project name.

If out of the box are there, you will see that already those box are existing and all I did was map DC title within with the document title or document name within Walkfront. But for certain metadata which do not exist in AM, you can create your tab or add those fields within the existing form.

Yes, so shall we just stay there for some time? Let鈥檚 go to the next thing. Yes, just for everyone鈥檚 clarity, go to the Walkfront tab.

Yeah, click on the project name or description, any one of them. Yeah, so these particular metadata that you see, WM colon project name, this is actually a Walkfront metadata, right? And this metadata will be available in AM only if a particular Walkfront instance has been hooked up with this particular instance of AM. If it is not hooked up, it won鈥檛 be available. Because we have set it up this way that this particular Walkfront instance has been hooked up with this AM access instance, we get to make use of any Walkfront metadata that are available and render those fields accordingly. Similar for the project description as well.

So we can show the project description one.

Yes, so this is also another Walkfront metadata. So all these Walkfront metadata are available to you as part of the metadata schema only when the Walkfront is actually in sync or the repository has been set up with the AM assets. So one key thing to also make note of over here is before setting it up is that you have a clear understanding of what all metadata you want to show in AM. So that is all part of understanding your internal business process, as in how you want the sourcing of that asset to happen, how you want that asset to flow from one system to another, how you want the approval process to happen. Based on that, your internal processes will be set up. And during that time, you will have that clarity, as in what all metadata to be shown at the Walkfront level, what all metadata you want to show at the AM level and for what folder. So because this was a metadata schema that was set up, typically for a project you will have your own metadata schema. Here as part of the demo, Chavi has actually modified one of the default metadata schema that was already there. But typically in a big assets implementation project, you will create your own metadata schema, give it by the project name on the application name and then apply that metadata schema to one on multiple folders. So it鈥檚 very important to have that clarity, as in what all metadata are required, what all custom metadata are required, where you want them to be shown and whom you want them to be shown to. And what kind of metadata flow or mapping is required. For example, what kind of metadata information you want to flow from Walkfront to AM. So these are the some of the things and the clarities that are needed over here. And as part of today鈥檚 sessions, we showed some of the most common use cases of Walkfront and AM assets integration.

Okay, we are reaching almost on time. So at this point of time, let me take the control back to the presentation deck.

So this presentation deck will be shared with you. We have also put up a couple of reference material over here. And we are gonna open up the questions and I鈥檓 also gonna put up a poll here. So feel free to answer those questions that are there in the poll.

Let me launch the poll, give me a minute.

Yes, I think you should be able to see the poll.

And please answer a couple of questions if you find this session to be helpful. And we鈥檒l pause here for a moment and take any questions that you have.

Let me also go through the list of questions.

So first question was from Sean. Hi, Sean. Your question was, how did you open the document from Walkfront directly into AM? Was it the AM logo? Yes, so it was linked to the asset that was in there. If you鈥檙e linking or synchronization with AM has worked properly, you will get to see the small adobe icon in red color over there. So that tells you that your synchronization with AM has worked properly. And clicking on that asset will take you directly to the AM asset link. The next question that we have is about versions, which says, can you create versions of assets in Walkfront in link folder? And will that create versions in AM assets? Very good questions. So yes, of course you can create version in Walkfront. So Walkfront does allow you to create version. However, in the native connector synchronizations of version is not supported yet, right? So that is one piece that is not supported yet. In terms of creating versions in Walkfront or in AM for that matter, you do have the ability to create them separately. But if you want to synchronize those version, for example, a version that is created in Walkfront will get synced into AM asset. That support is not there yet.

Is the mapping of custom fields on the roadmap for native connector? It is already there. It is already there. So you can definitely put up a custom field and get it mapped through the native connector. You just have to ensure that you are selecting the right custom field in the metadata mapping section of the setup that is there. And you will also have to see that your metadata schema in AM assets is configured properly so that you are able to render that particular custom field. But in terms of support, that support is already there. You should be able to map custom fields as well using the native connector.

The next question is, will previews of file types other than JPEG be available? Currently, TIFF and PSD only download the files. Yeah, that is true. We don鈥檛 know when it is gonna be supported yet, but we can always check the roadmap from the product team and get back to you.

I know that it is there in the pipeline, but when it will be available, we cannot commit, at least not on this call. So we can go back to the product team and let you know about the roadmap on that particular one. The next question is about content fragments in AM via walk front or is currently only images zip. So the native connector that we showed today, you will have multiple Miami types, right, images, zip folders, zip files can also go. When it comes to content fragment, it is there in the pipeline. I don鈥檛 know how much it is there in terms of availability. We can get back to you on this later on. So there is also some of the beta ones going on with respect to AM鈥檚 walk front and AM sites integration and that is where this content fragment thing is coming into the picture. We can give confirmation on the roadmap once we sync up with the product team. But in terms of GA, it is not GA yet.

There are works going on that sector, but it is not GA yet.

Is what you are demoing specific to AM cloud or is all of this the same for AM version 6.5? No, so this is specific to AM cloud. So native integration is specific to AM cloud and walk front, both on booted on admin console. For AM 6.5, you have enhanced connector and that integration is done via package manager.

And then furthermore, there are more steps in AM as a cloud service option within AM tools, but this is only specific to AM cloud.

Yeah, and it is applicable for both the AM assets or the assets essentials, right? So both for AM assets or asset essentials, you can make use of the native connector. But yes, only on the cloud, right? And your work front has to be on the cloud as well.

Does asset metadata sync if the asset was uploaded in AM? Right, so that is something that we tried to show over here.

When we upload an asset in AM, you will find that asset in work front too. But in terms of syncing the metadata, as I talked about earlier, it is unidirectional from work front to AM. You will be able to see a read only view of the metadata that is there in the AM assets. If you remember the work front metadata section, if you click on the document details at the bottom by default, you will get to see the metadata section. So that is the default view that shows you a read only view of the metadata of that particular asset based on certain default fields. But in terms of truly knowing whether it is bi-directional flow of metadata or not, it is unidirectional from work front to AM.

We were informed that the project folder location AM could be based on custom fields.

What is the status in that feature? That is true. You can actually create project folder names with custom field, just like we showed with the selection of object type, which was portfolio name or project name or those four options. If you create your folder workflow using a template, in that you will see an option of custom field as well. So this is native integration, proper workflow, and then there is another workflow that you can define when you create your project via template. So yes, that is a feature and yes, you can actually use that. So it鈥檚 ongoing, it鈥檚 live and ongoing.

Confirming that updates to metadata on a project folder in work front will sync to AM.

Yes, so if you have any metadata on the project folder, if you go on the metadata section, you will find two tabs over here. One is assets, another is the folder. So even for the folder, if you are able to map it correctly, you should see it getting synced into AM as well. If you remember the metadata section that we talked, let me see if I have it in the slide over here quickly. Do I have a screenshot? I don鈥檛 think so, yeah. So just below, no, not just below it, hold on.

So if you鈥檙e looking into the deck that I鈥檓 sharing, so this is a metadata section that you are going to have, just above it, you will have two tabs. One, it says assets, another it says folders. So if you click on the folders and then you will have an ability to map the metadata from work front to AM, so that way you can sync.

The next question is how do taxonomy namespaces stored within AM play a role in the metadata transfer from work front to AM? It really depends on how you鈥檙e trying to set it up.

So if you want them to be relevant or not, the taxonomy that we have in AM are totally different from the way taxonomies can be set up in work front. The way work front deals with tags are totally different than how we have in AM. So it depends on what you are trying to set it up in terms of, if you鈥檙e asking, if there is a direct correlation or synchronization between these two tags in AM or work front, no. There is no such direct synchronization and correlation between them.

How different is it if your instance is an on-prem six five service pack 21? Like we mentioned earlier, this particular native integration is only for AM cloud or asset as a cloud service and work front on admin console.

This is native integration versus when it鈥檚 six five, whether any service pack, I would say there is a certain, you should be on later service pack, assuming that you are on service pack 21. You should be using enhanced connector to connect with your work front.

Okay, next. The next question is about, it鈥檚 an interesting question, which says, AM assets is powerful to manage assets and metadata within AM, so why work front? Well, there are plenty of reasons why you work front can also be needed. It is typically seen that clients having huge assets implementation make use of work front because you can actually manage a lot of workflows within it. Plus there are certain default integration that a work front provides that I talked about in this presentation, right? So there are certain native integrations, then there are certain custom integrations that you can do either through fusion or through rest APIs in work front. So there are plenty of reasons why even after having AM assets, clients would still like to go for work front, right? And one of the primary reason being managing the internal business processes instead of leveraging the AM workflows, you manage the interworkflow in AM and besides certain default integration capabilities that work front can have. Plenty of reasons, but I鈥檓 just providing one or two reason over here. The next question is, can you clarify if I have exceeded 100 projects in work front then I hit the limit for native connector? Yes, that is a known limit. You can get into some technical nuances once 100 projects, once it is beyond 100 project folders. That is at a part integration level, right? So no matter how you have set up the link folder or how your hierarchies are, for one work front and AM integration that has been put up and you can have multiple of them, but for one integration, the limit is 100. So first you will start having some performance issues and then there would be other technical nuances that might come up. It is in works as I know, so that aspect is also being looked into how that limit can be enhanced, but as of now, that is the limit.

Okay, so I think we have answered all of the questions. Is there any other question that we missed? I think we have answered all of the questions and we are almost at time.

If you do not have any other question, I think we can stop the recording and thanks everyone for joining in for putting up all good questions and for your participation. I see a hand raised, but sorry. Yeah, has someone raised a hand? No, is it? Any other questions? No. Okay, there is one last question that has come from Lynn, Amber Lynn, I believe.

How would the workflow look like if we have an already established folder structure in AM and do not want to create new folders via Workfront? You do not have to necessarily create new folder via Workfront. If you already have an established folder structure, you can link up to that particular structure as well.

I鈥檓 not quite sure what you exactly meant over here, but you can link up to the established folder structure as well. You do not necessarily have to create a new folder. Create link folder is an option. So if you don鈥檛, by doing your integration, if you don鈥檛, let鈥檚 say switch on that particular option or create that workflow, you don鈥檛 need to create a new folder structure. You can create a project under project. When you click on plus sign on the top, it will give you an option to select the particular integration. From that integration, it will open up the folder structure of your AM and you can select what folder hierarchy you want to link with your project. So an existing folder hierarchy from your AM can be linked without creating a new workflow for Holder.

That鈥檚 right.

Okay, we are at time. So thanks everyone for your participation and some of the great questions and staying with us during this demo. You all have a great day. Bye. Thank you. Bye.