ÃÛ¶¹ÊÓƵ

Transcript

Good morning everyone. We will start very soon. We’ll just give a couple of minutes for other folks to join in, and we’ll start.

And in the meanwhile. So today’s session is going to be about a work front 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 distill here. We have 1 a.m. session on February 10th about optimizing game performance, February 11th about content supply chains. Well, 13th and 14th February as well. On 14th February, we have another M session with respect to the science, how to build effective web pages on insights. So please feel free to attend these sessions as well. And they are gonna be really important. Just as this one today.

Will wait for another minute or two, maybe before we start off.

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 the session with the agenda for work front integration.

But it’s already getting recorded, and we are ready to start. So. Hi, everyone. My name is Beacham and I’m working here as senior field engineer in ÃÛ¶¹ÊÓƵ. I joined the ÃÛ¶¹ÊÓƵ around July 2021, and my primary core of expert primary core expertise is on M sites, assets work front and now the Institute for Performance Marketing as well. I am part of the ÃÛ¶¹ÊÓƵ Phil engineering org and with me I have chubby chubby. Why don’t you introduce yourself quickly? Sure. Thank you. Hi, my name is Chubby Gupta. I. I’m a technical consultant in field engineering at ÃÛ¶¹ÊÓƵ. I’m based out of San Jose and my expertise is in M assets and, but mapping integration with M and, I am very excited for this session today. Thank you. Brian. Okay. Thanks. Chubby. So we’ll look into some of the agenda that we have for today. We are going to talk about, first about various integration strategies that we have in work front. The need, the main need for m work front integration. We are also going to look into a comparison matrix, about native connector and other connectors that have been there. A quick overview of the comparison matrix. We are going to talk about the benefits of native connector. What are the prerequisites that are needed. Setup and configuration followed by demo. And also talk about the guardrails. And we will take your questions.

So without wasting any other time let me go to the main slide and talk about the various integration strategies that we have will walk through. And before we get into the native connector. Okay. So before we talk about the native connector and getting work front integrated with IAM, it’s important to understand the background and talk about various integration strategies we have in work front. So as you know, using work front, 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 the native integration which is really no cost solution. Right. So you can just plug and play over here. And a lot of things are provided by default out of the box. So these are some examples of native integration that we have in workflow integration with ABM, Google Suit ÃÛ¶¹ÊÓƵ Creative Cloud, Adidas, slack, Microsoft Outlook. So these are some of the primary, native integrations that are already there in work front, which does not require any kind of, building code. These are just plug and play kind of integrations that are with you. So another category of integrations are custom integrations. And what they are we have again two types. One is custom integration using fusion and custom integration using Rest APIs. So 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. So it really depends on your business requirement and what you are trying to integrate with. For example, if you are trying to integrate with AME or you need ÃÛ¶¹ÊÓƵ Creative Cloud, those are all part of the native integration. You do not have to do anything. It’s just plug and play out-of-the-box and you’ll 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 and 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 work, front end, even using the native connectors. So obviously, as you can understand, it is part of the native integration. Now let’s try to understand why this integration between A and work front, is important. So the primary use case of this integration is to increase the content velocity. So whenever we talk about content supply chain in ÃÛ¶¹ÊÓƵ, content velocity and boosting the content velocity of is of primary importance, right. So how quickly you can automate certain workflows, how quickly you can put up your assets, get them approved and eventually get them published. So 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. So some of the key benefits by getting em integrated with work from and vice versa. These are the ones. Right? So if you are using the native connector and getting the work from the engine integrated you, it allows you to easily search and find assets and also navigate folders in Em while staying within the work front. Right. You can link your assets and associated metadata to your projects and tasks. That is also very important. You can also allow the work front meta data that you have put up within an asset to flow into Em, 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 linking them automatically is an option that you can set up. And these are some of the things that we are going to talk about in details as part of these sessions. And you are 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 work from 2 a.m. for a single source of truth. So these are the primary reasons why you would want to your work front and m to be in sync and connected together, especially when it comes to assets.

Okay. So now since the need for this kind of integration is well understood, let’s 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 work and then M you can connect the work front with either the M assets on the cloud service or assets Essentiels for both of them, the native connector is going to be applicable. There is also an enhanced connector that you used to typically connect on on premise instances. And we have tried to put up here a quick comparison matrix. 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 this to cover. Right. So these days whenever you are trying to, integrate work front with you, whether you, your, 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 connector used to have.

In terms of metadata as well. And synchronization of metadata is well, it has pretty much all the features except I’ll call up one difference, of course, that the using the enhanced connector, you can actually have bi directional flow of data between work front and engine. Whereas in case of the native connector, whether you are using the native connector to connect to M, it’s on cloud service or asset, essentially it is going to be you. You need directional flow of data. So that is from work front to M. But at the overall level these these are the companies and metrics that you can see across these connectors. And you can see that pretty much the native connector covers all the areas.

So one of the key benefits of the native connector is the ease at which you can set it up. Again, we’ll 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 EMR sets repository is just a matter of few clicks. So ease of setting it up is definitely one of the key differentiating factor of the native connector, and you do not need a separate license for it. Of the basic work front plan, and the license is good enough for it.

You have the ability to automatically create folders and they can be linked between work front an experienced manager. That is another benefit that we have in the native connector. You can also sync the metadata for the existing linked assets. You have an option to automatically sync those metadata. So that is part of the setup process. Again we will 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 work front to a again for a particular asset or not. One thing to note over here, this connector can also be linked to a m in in a many to many way. So basically you can have one work for instance, link to multiple M repositories. And you can also have one repository linked to multiple, walk front setups or work for the instances. So these are some of the benefits that you have in the native connector. The ability to have this many to many relationship between work from 10 a.m… It’s a flexibility, that the clients will always have and they can make use of it, even especially for big implementations where there are multiple business units and there are multiple with orgs that are created. This kind of flexibility of having this many to many a relationship between work. 10 a.m. 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 workflow must be in the admin console. When you are setting up the native connector in work front, you need to be an administrator. You need to have those admin rights because you will have to go under the setup idea of the work friend to set it up. And that is only applicable for admins in workflow. And if you’re trying to set up any linked folder, as part of the setup, it is important to know that whoever is setting it up needs to have access to the M repository, right? Access to the M repository folders where you are linked folder is going to be set up. So yeah, these are a couple of prerequisites to be kept in mind that your workflow must be in the admin console and your expense manage your assets. All essentials must be also be assigned. And if you are, actually setting up a linked folder over there as part of the setup process, the user should also have the right access on those linked folders while the setup is happening.

Now we will look quickly into the setup and configuration. Part of it. How do you setup the native connector and what are all things you can configure? Before we look into the demo and as part of the demo, we are also going to look into certain use cases.

Okay. So these are the standard setup setup process that you have for the native connector. So as I said you login into work frontends and work from the 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 and Experience Manager Integration. When you land up on that particular screen, you will 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 am just going through as a technical information with you, the name and the experience manager repository, all the mandatory information over here. The navigation URL will get auto populated over here.

The next section will be for the metadata mapping. So over here you will basically, tell the setup what walk from fields you want to map to the experience manager field. Right. So on the left hand side you can see all the work from fields that are that will be there. So the moment you type in there, it will show you all these options to choose the relevant work from field and on the right hand side of the expense, manage your assets field that needs to be mapped.

The next section is about the workflows. So if you look into the setup screen, as we would see during the demo, you will see there are primarily two workflows with you. Right? So one workflow is about the creation of the linked folders. And the second workflow is about the publisher of the assets that are being sent, to the ATM. So basically, if you want your assets to be automatically published whenever they are being sent to a uniform workflow, and so that workflow is going to be applicable, and it is just a checkbox that you have to put up over there already within that will have to put up with the creation of the linked folder is whenever you are creating a folder in Walk point or the link folder, the same hierarchy will be maintained in AGU. So these are the two workflows that are already, available with you. And 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 link folder. Support integration. So that means, one integration of work front end in repository. You we have a limit of around 100 folders. So regardless of how big the folder have of keys. So for example you might have a parent folder. You might have what which children folders under them. But the total number of folders that integration can have will be 100.

The first folder in the folder tree will already all will always be marked as a linked walk front. And if no folder tree is provided by default, the setup will consider the root folder as the linked folder. So 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 the link folder or not. But if you do, these are a couple of things that you should always consider.

So now let’s quickly move on to the demo section and I’ll hand over to cherry to show the demo from the sandbox. Cherry thank you version. Hello everyone. With this I will start sharing my screen and we’ll go into the demo section.

I hope everybody can see my screen. So right now we have landed into a screen which shows admin console. So this is my admin console. And the reason that I’m starting this here is because we have to understand the prerequisites and then we move forward with the whole demo of integration. So in the product section of your admin console, you should ensure that your IAM as a cloud service and your worker and both should be onboarded and as well as as an admin, you should be registered when you are trying to do this integration. So these are the main prerequisites which already version has explained. Now we move towards Experience Manager. So 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 by so I will directly go there. This is my cloud manager sandbox environment. And you can see these are my environments listed. Prod stage and dev. I have already pre linked my stage. So if I go to stage here it is my stage. And on next to it I have my work front open here as an admin, you will be able to see certain options of setup. So 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. And when you scroll down the document section right now, it’s expanded, but you are supposed to expand. And then you will see the second option says Experience Manager Assets. This option will only appear if your or your work front 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, blank screen and they will see a plus sign which says at 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 version 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 will 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 ÃÛ¶¹ÊÓƵ 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 and I’ll click edit here. Now this is my demo integration that I have already done. And 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 at as an admin. So when you click on this dropdown you will see all the list of experience, environments as your ATM environments over here. And you can select the one which you want to integrate with your work friend. 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 your suppose to map the work front field with the experience assets field. So as as we have discussed earlier this is uni directional. So the arrow itself is very, directive of the fact that from work, from 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. Friend, 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 those 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, the DC type which is our document Dublin code metadata schema, the part of as a 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 have done already a lot of mapping. And the next section which version explained is think object metadata. This is, this is what makes sure that your mapping of work from portfolio or any, any of these metadata get sync with the experience manager. So it is recommended that you have this, to, 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 Marshall explained earlier. Create Link folder and publish assets automatically will start one by one.

I’ll click on this expansion button. And as you can see, I already have created one. And I’ll walk to this. It says linked folder name. So here it’s basically asking that you provide a name, any name, which is basically the folder, link folder, creation that you are going to do here. It’s, it’s that link folder workflow name. So this is my workflow next to it. It says Enable and Project. By default. This is optional. It is up to you if you want to checkbox this or not. Next is linked 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. What root. You just have to click on select folder and it will populate as contents.

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 the plus sign on the right side. Click on this icon. New dialog box open up and it says name type with the 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 are trying to set up a static name for the folder. It can be anything. For example, let’s say you have a campaign or you have a client that you want to create this folder tree for any or anything. In that case, you will have a static name. If you are 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’s giving me four options portfolio name, Program name, Project Name, and Project. Create. Here 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 linked folder got created.

Next to it is. My next option is Public Assets automatic.

Do I want that one I want that so I switched it on and I want that to be published directly to my experience budget publish service.

I’ll move forward to the linked folders over here. Do I want the link folder to be enabled this workflow. Yes. So I have switch 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 popup screen where it will show all your folders from your experience manager, you can select again, you can select the folder where you want it or the mean path for the for I. For this particular section, I have selected my main path and it also gives the band portfolio and program name as an option. This is a checkbox. It is optional. It is up to you if you want to append the portfolio in program name. I have selected it so you will see how the project folder inside the portfolio folder have appended portfolio and programed.

I click save.

Now my integration is complete.

I will now get back to version for the guardrails.

Yeah, thanks to, can you please take us into that edit section of the integration? So I will 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 or 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 will have to delete this repository and create it all over again. So this intuition part you will have to delete it and create it all over 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 you need directional. So that is from walk front to experience manage your assets. So that’s why you see the arrow from front. We expense manage your assets. There is no bi directional flow of metadata over here. So any method that you put up in walk 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 linked folder, depending on the business requirement, if you really need to put up a linked 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 are trying to set them up. Again, the person who is setting it up over here, and if you are making use of the linked folder, it is important to note that if you are setting it up, you need to have the right access to those folders in Em as well. Otherwise, the setup of the linked folder is not going to work out. So that is why it is very important that along with someone having the admin 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 Aim 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 the things to be taken care of. This look into some of the use cases. Cherry. So let’s do some of the most common use cases. For example, we are gonna upload an asset in Am and we are going to upload an asset in work front. And we are going to see it in a. So as part of the demo, Travis 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 work front. Now let’s go into the documents section of it. So we yes. So over here in this sample project, we 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 AUM. So over here should be we are going to test one upload of an asset, and then we are gonna go into AUM and see that it got uploaded.

So let’s upload one asset over here.

Okay. So the asset did get uploaded into work friend. And you can see an icon over there, red ÃÛ¶¹ÊÓƵ icon. That means that your sync sync up with the M is working fine. So if you click over here, it will directly take you to the asset. So let’s get into it.

So it directly takes you into the M assets. Now let’s go into the properties that we have for the asset. Let’s go into the walk for tab and see the properties. Yes. So let’s understand this part. So as part of this demo. So we had already kept a m main folder meta data schema ready for this one. Right. So as part of the metadata schema she had already added a tab called Work Front. And over here, couple of fields. And these are actually mapped to the walk form field. So this mapping is actually handled in the metadata part that we talked about. And we also structured as part of the demo. So this project name that you see over here is actually the work from project name that has come for the asset. The project description that you see over here is actually the walk from project description. That has got more work. Right.

Yes. So this is the project name and the description that you are able to see. Now let’s go into the work front.

And let’s 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 name, 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 wolf. And the default description that you had seen in M is the project description that it had taken up, because it was mapped accordingly. So at this point of time, let’s first see that the description is also blank in M. So let’s 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 walk front metadata and see that getting populated immediately in M. So over here we are gonna add one sample description. And we are going to save it. Now we are going to go into M and simply refresh the screen. And you will see the description getting populated. Maybe give it some time and refresh. Refresh the refresh the integration that you have.

Probably go back again. Yeah.

Yes. You see this description has come over. Right. So basically to use cases we have shown over here, one is when you are uploading an asset into work front, it is immediately getting pushed into M. And whenever you are changing any metadata, those metadata things are happening almost immediately into M, right. Another thing to note over here is where do we delete this asset if we have to, right. So should we start deleting in the work front or at the minute. Right. So the recommended way is to delete and the element because we are still going to consider M as the single source of truth for this particular asset. But let’s look into the experience. What happens in work front if we try to delete this particular asset in work front? So let’s take us to the work front on this demo project, the asset that we uploaded. Let’s try to delete this asset in work front.

Yes. So you see this error dialog that is coming up over here. It restricts you from deleting this asset in walk front. So if you want to delete this asset you have to go into M and delete it. So let’s go to M right now and delete that particular asset.

Okay. So this asset got deleted in M. Now we are going to go into walk front and refresh the screen. And we will 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 not Jpeg is the, asset that we deleted in M, but it will still be available over here. This is, by the way, also applicable for any assets that you are moving from the linked folder. So for example, if you have a linked folder setup you are moving any asset from the link folder in M, it will get removed from the link folder section over here on the main hierarchy, but it will still still be available and be shown under the project folder hierarchy.

There is one, thing to be to have more clarity on for for example, updating meta data in M right. So let’s go into a m for this particular asset. Let’s go under. We already deleted that asset. Right. But we can check for another asset too. Yeah. So let’s say we put up, meta data in M for this particular asset. Let’s put up any sample description over here.

Let’s save it. And let’s go to work front and check thumbnail Jpeg and its meta data 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’t really add any description in walk front. The another one is under the meta data section part of it. Right. So these meta data section is a read only view of the meta data that you have in experience manager assets. So that’s how you get to see that these description that we have added in M assets which says this is a picture Jpeg has come over here. That doesn’t necessarily mean that the work front, description meta data has been updated for this particular asset. It just shows you a read only view of the M assets, meta data 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, 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 looked, talked about how you are going to move those asset and what how the experience is going to show up, how you are going to update the meta data for those assets over here as well. Right. Charlie, 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, you can upload Jpeg, zip, pdf, mp4, doc, and everything syncs with m, and moreover, what I did for the, metadata schema, the I went into assets. Sorry, I went into tools within our experience manager. Going to assets, going to metadata schema. I, I did it the default. So I go into edit section, since the mapping actually happens within work friend over here, I created a custom double version because I wanted to add project name and project description. To do so, I added the tab and then I dropped, to build form, I dropped a single line of multiline text, and then I mapped the property with the project name. If out of the box are there, you will see that already those works are existing. And all I did was map DC title within with the document title or document, name within work front. But for, for, for certain metadata which do not exist anymore, you can create your tab or add those fields within the existing form. Yes. So we just stayed there for some time. Let’s go to the next thing. Yes. Just for everyone’s clarity go to the work tab.

Yeah. Click on the project name or description. Any one of them. Yeah. So this particular metadata that you see w m colon project name, this is actually a work front metadata. Right. And this metadata will be available in a m only if a particular work front instance has been hooked up with this particular instance of M. If it is not there, we won’t be available because we have set it up this way, that this particular workflow instance has been hooked up. With this M access instance, we get to make use of, any work for meta data 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 work for metadata. So all these work from meta data are available to you as part of the metadata schema. Only when the work front is actually, in sync. Or the repository has been set up with the M assets. So one one key thing to also make note of over here is before setting it up, is that you have a clear understanding of what old metadata you want to show in EU. 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 will be shown at the front level. What what will metadata you want to store, at the M level and for what folders. So because this was the metadata schema that was set up, typically for a project you will have your own metadata schema. Here as part of the demo, Chevy has, actually modified one of the default metadata schema that was already there. But typically in a, in 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’s 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, and what kind of metadata flow or mapping is required, for example, what kind of metadata information you want to, flow from walk front to end. So these are the some of the things on the clarity, that are needed over here. And as part of today’s sessions, we showed some of the most common use cases of walk front and iMessage 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’m also gonna put up a poll here. So feel free to answer this 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’ll pause here for the moment and take any questions that you have.

Let me also go to the list of questions.

So first question was from Sean. Hi, Sean. Your question was how did you open the document from work front directly into M? Was it the M logo? Yes. So it was linked to the asset that that that was in there. If you’re linking or synchronization with M as I walked properly, you will get to see the small ab icon in red color over there. So that tells you that your synchronization with the M has worked properly. And clicking on that asset will take you directly, to the M asset link.

The next question that we have is about versions, which says, can you create versions of assets in work front in link folder, and will that create versions in your assets? Very good questions. So yes, of course you can create version in the in work front. So work work front does allow you to create version. However in the native connector synchronization of version is not supported yet. Right. So that is one piece that is not supported yet in terms of creating versions in front of name 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 work front will will get sync into AMS. That support is not there yet.

Is the mapping of cluster fields on the roadmap for native connector. It is already there. It is already there. It is already supported. 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 of the setup that is there. And you will also have to see that your metadata schema in AMS sense 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 different used you only download the files? Yeah, that is true. We don’t 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. It is 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 M via walk front. All is currently only images. See. So the native connector that we showed today you will have multiple my my types right images as folders. As the files can also go when it comes to content fragment, it is there in the pipeline. I don’t know how much, it is there in terms of availability. We can get back to you on this later on. So there there is also some of the beta one is going on with respect to aims, work front and Aim 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 yet the other ones going on, on, on that sector, but it is contingent.

Is what type demoing specific to GM cloud or is all of this the same for Amber version six five? I no, so this is specific to am cloud. So native integration is specific to E and cloud and work front both onboarded on admin console. For Am 65 you have enhanced connector and that integration is done via package manager. And then furthermore there are more steps in a as a cloud cloud service option within a Am tools. But this is only specific to a cloud. Yeah. And it is applicable for both the aim assets or the assets essentials. Right. So both for Am assets or assets. So you can make use of the native connector. But yes. It only on the, on only on the cloud. Right. And your work one has to be on the cloud as well.

And as I said metadata syncope as it was uploaded in M. Right. So that is something that we tried to show over here. When we upload an asset in ATM, you will find that asset in work front. But in terms of syncing the metadata, as I talked about earlier, it is you need it external from work front to M, you will be able to see, a read-only view of the meta data that is there in the 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 bidirectional flow of metadata or not, it is not. It is. You need directional from work for team.

We would weave. It. Yeah. Sorry. Okay. We were informed that the project folder location ATM could be based on custom fields.

What is the status in that feature? Oh that is that is yes, that is true. You can actually create project folder names with custom wheel 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 that this is native integration, proper workflow. And then there is another workflow that you can define when you create your project by a template. So yes, that is that is a feature. And yes, you can actually use that. So it’s it’s it’s ongoing. It’s it’s live and ongoing confirming the data updates to metadata on a project folder and working with sync to M.

Yes. So that so if you have any metadata on the on project folder, if you go into this section you will find two types of what you are. One is assets, another is the folder. So even for the folder, if you able to map it correctly, you should see it getting synced into a game as well. If you remember the metadata section that we talked, let me see if I have it in the slide over here quickly. We have a screenshot. I don’t think so. Yeah. So just below, no, not just below. We told them. So if you are looking into the thing that I’m 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 and it says folders. So if you click on the folders and then you will have an ability to map the metadata, from walk front to game. 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? Simply, it really depends on how you are trying to set it up. All right. So if you want them to be relevant or not, the taxonomy that we have in Em are totally different from the we taxonomies can be set up in walk front. The way walk when deals with tags are totally different than how we have name. Right. So it depends on what you are trying to set it up. In terms of even if you are asking if there is a direct coordination or synchronization between these two tags in Aim or work front. No, there is no such direct synchronization or correlation between the time between them.

How different is it if your instance is an on prem six five service bag? 21 like we mentioned earlier, this particular native integration is only for a cloud or asset, as a cloud service. And work front on admin console. This is native integration versus when it’s 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. Thanks. The next question is about it’s interesting question, which says Army assets is powerful to manage assets and metadata within Am. So why walk friend? Well, there are plenty of reasons why you walk front can also be needed. It is typically seen that clients having huge assets implementation make use of walk fund because you can actually manage a lot of workflows within it. Plus there is certain default integration that a walk 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 Walk friends. So there are plenty of reasons why, even after having a Am assets, clients would still like to go for walk front, right? And one of the primary reason being, managing the internal business processes, instead of leveraging the aging workflows, you manage the entire workflow in AEM. And besides, certain default integration capabilities that work front can have plenty of reasons, but I’m just providing 1 or 2 an overview.

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 unknown limit. You can get into some technical nuances once, 100 projects, once it is beyond 100 project folders that is at a per integration level, right? So no matter how many, how you have set up the link folder or how your hierarchy are for one walk front and the 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 walks as I know. So that aspect is also being looked into, how that limit can be enhanced. But as of now that 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 nine.

If yeah, if you do not have any other question, I think we can stop the recording. And thanks everyone for joining in for putting up on all great questions. And for your part, participation. I see your hand brings park. Sorry. Yeah. It’s someone that’s someone we have just. No.

Any other questions? No. Okay. There is one last question that has come from Lynn Amberlynn. I believe. How would the workflow look like if we have an already established folder structure you name and do not want to create new folders via a work front? You do not have to necessarily create a new folder via work front. If you already have an established folder structure, you can link up to that particular structure as well. I’m 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 linked folder is an option. So if you don’t know by doing your integration, if you don’t let’s switch on that particular option or create that workflow. You can you don’t need to create a new folder structure. You can go in your you can create a project under project. When you click on plus sign on the top, there it will give you an option to, select the particular integration from that integration. It will open up the folder structure of your app. And you can select what folder hierarchy you want to link with your project. So an existing folder asking for your from your name can be link without creating a new fork flow for holder.

That’s right. Okay we are at time. So thanks everyone for your participation and some other great questions and staying with us during this demo. You all have a great day. Thank you. Bye.