Microsoft 365 Community PnP Webcasts, 9 Oct 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: PnP Webcast - Deployment options for SharePoint Framework Solutions

Description

PnP Webcast around deployment options for SharePoint Framework solutions. Concentration on how to get your solutions deployed to SharePoint sites and the impact of tenant-scoped deployment setting for deployment for web part and extensions. Additional details from http://dev.office.com/blogs.

A

Welcome everybody: this is SharePoint patterns and practices. Webcast assistant I wanted to actually, let's say, concentrate on the deployment options for SharePoint framework solution and in this particular case it means explicitly what does it mean that we have, for example, the news tenant scoped deployment option available in the SharePoint framework solutions which was released after GA, but for 41.3 version of SharePoint framework and what are the other implications on when you're deploying a solution or a web part or an extension to paper size to the sharepoint online? So how do you actually deploy them?

A

How do you activate an extension as an example in the site and what are the options for you to manage those things? My name is Fiona I'm, a senior program manager from SharePoint engineering and with me today, as the person asking difficult questions is Waldeck. Mastercards Waldeck will do a quick intro as well of.

B

Course, hi everybody, my name is Olle most Akash I am also developed. An MEP I work at rancour and today we'll be talking about deployment options for SharePoint framework solutions.

A

Indeed, indeed, so, the the title is relatively Chenery, but like mentioned, we really wanted to concentrate on what does it mean when you're doing a tenant scope or non tenant? Curb deployment option in SharePoint framework? And how do you get your customization activated on the sides or not, and we only have a one slide, because we wanted to actually demonstrate this deployment options in practice. But let's talk about this one slightly, so what does it actually mean?

A

So, if you are using the the one point is at one point to version or newer version of SharePoint framework, yeah I think it is one point two: it doesn't matter the latest version of SharePoint framework. It is actually asking that. Are you looking in the deploying this solution as a tenant scope of option or not?

A

And if you this tenants, if you do choose to tenants, go to option what it means is that if you put up a part solution to the application color gallery, your web parts will be automatically available in a web part bigger, but then it might have costs or- and we know that it cost some questions from the community- that what does it actually mean? For extension, so I have a SharePoint framework solution which contains, for example, application customizer. Why isn't the doctor vetted Chris all of my sites and all of my site collections so.

B

Would that be before we go to extensions? Let me just ask one thing right, because we had similar option available with edits right when you will deployed the package and then you would actually install the package in the app catalog side, and that way you would be able to use the Adhan across all sides. Is this the same.

A

Not precisely so, and if we quickly got you back on the under adding model time frame, that was a tenant deployed, adding and what it meant was that you actually created the adding instance that the app catalog site collection and then you said that hey I want to have this adding visible across all of my sites. Even though the terminology in the UI was I. Wanna have this adding deployed across all of my sites, which wasn't actually the case.

A

What what happened there was that we we added a link to that add-in which still remained in the application, catalog site collection to the site contents page of every single site, where you selected that to be the point, for example, based on a site, template or based on a URL pattern, or so on that slightly different scenario, because in this case, what we are doing. If we talk about, let's concentrate first on the web part.

A

So the the web parts and SharePoint framework solutions they actually the way they get deployed is that when you activate an application, that's solution in app catalog. We actually kind of enabled the flag and my and to be that web part to be available to be used across this across the whole tenant and what I mean what I mean with that one is that we store the manifest of the web part in the application, catalog site collection, it's hidden there.

A

You don't need to know that it's there, but that's what actually happens in the background and then, if you do not have the denon, scoped and deployment option enable you will still need to go and explicitly install the solution in a site and to get that webpart visible and an application picker. But if you do have the transcript and option enable, then the web part will be just automatically available within all of the sites and all of the pages within your tenon.

A

As long as the the web part has been a web part solution has been deployed and after them, hopefully that made sense.

B

A

Questions so let's try to climb.

B

Yet so let me try to recap that, and let's see if that that is easier, so with add-ins, there was a link from every single site pointing to the enth instance of off edit right, because back in the days when we installed an add-in that would create an end in sight right. So you had to go to that place all right now with SPF X.

B

That's not the case right, because the only thing that we have is the manifest and, as you said, that's stored within the catalog so and that's not copied around to any side dad. That's just current, just a reference that that is there and it's now turned on yeah and the moment we choose to deploy a tenant wide. That is a checkbox right that it says now it's available everywhere.

B

Every side that that's querying for available webparts will also get that link to that manifest and with that we'll be able to show the web part, and you will be able to add it on your pages correct. Yes, yes,.

A

So cha and now that's the webparts story. So but then the extension story, it's the new fellow, the extension qi8 September 2017, which is a great thing, but the extensions do not get automatically available or in the U is in in your site collections, even though you would actually deploy them using the tenon scope deployment option. But the channel scope, deployment option means for extensions is that you basically enable them to be available.

A

It doesn't mean that they're visible yet and then there's the additional step where you actually activate the extension, for example, application customizer in a site, collection level, but.

B

But I guess that that, in a way it is comparable, it is comparable to webparts right below spider. Even you know you deploy web part tenant wide. It doesn't mean that that web part will show on every single page across the whole agent, correct, correct. It is available there for you to add. So it's extension, it's exactly the same. It is available there for you to add. Well the caveat there is that, whereas users can add webparts through the UI, you cannot do it extensions right.

B

So exercises are meant to be set set up in a different way, correct that.

A

Is absolutely correct, so technically yeah? What you're saying yeah exactly concept is exactly the same and who knows at some point? We might actually have an extension picker for administrators of the site collection, so they can actually see what extensions are available and they can enable them in the site, collection, scope or side console.

B

Right yeah, you know what let me, let me go quickly to user voice. Exactly absolutely.

A

Please do that because we want to get votes on those user voice entries, so we can prioritize and to demand. We understand the demand of the field for their side ears. Now, okay, that hopefully kind of settles. It then maybe we'll absolutely create some additional documentation on this. One graphic graphical clarifications and what does it actually mean and it might sound complicated but I think the easiest way to understand what's happening on the background, and what do we need to do is actually do this life, so we wanted to in this webcast.

A

We really wanted to basically do four different solutions: simple out-of-the-box back part, or what do we need to do to get it deployed and also tenants go to a part? What does it actually mean a simple application, normal application customizer and then then on scope, application, customers and how do I actually get it live on the side? So let's actually do this. Let's start with a wet words, so let me actually get on my machine.

A

So here's my web part setup or the solution set up for this particular webcast, and we cannot talk about the remote probation in patterns. Then, how does that impact during the demo as well? But let's start with a a the normal web part. So let me go to the next next normal and quickly have a look on what we actually have here. So here's my visitors to their code. This is just an out-of-the-box web part which has been already deployed so.

B

Technically yeah you.

A

Wanna grab another.

B

One, the web part, whatever.

A

Wow yeah indeed,.

B

A

Thank you. It's good to have somebody else to watch, but my hands on two.

B

Edges right, yes, exactly.

A

To know that somebody's paying attention here we go so, let's get to the web part now we're in the web part, and what we've done here is that we've done already kind of initial and deployment of this web part, so you can actually see them working in practice. So we kind of a we have already the Java Script files being hosted in this location.

A

So we don't have to deploy stuff, but this is just stayed a normal web part, which is the out-of-the-box clean report just doing the basic set up and there's the text which is saying I'm normally deployed. So let's have a look on what does this mean in practice? So if I start an explorer- and let me actually jump to my app catalog, which is completely empty, how do we get stuff deployed? We go to the SharePoint solution, folder, because I've already done the package solution.

A

Option then I track stuff in here and because the JavaScript files are already in my CDN I, don't need to actually get them explicitly. The point I can show you that in a second as well.

A

Now we can see here that the URLs, where the JavaScript files are being loaded is the public, CDN and SP PNP seed in address and the VP normal, and that's fine for me, because I've actually set this one up within my dinner, so I'm clicking, deploy and essentially what it means is that we already previously created a CDN set up for this tenant and in this case those turbo JavaScript files are being hosted from this folder and because it's an office, 365 CDN there being host access to the CDN, which is much more performant now now.

A

The solution is that webpart is available in my app catalog. So let's actually create a new SharePoint site, so we can actually see quickly create a new site using the modern UI switch. So the site creation is super fast. So let's call this webcast vidcast demo one and getting that one I created. It takes to be a five six, seven seconds which is still like, and it's super amazing how fast this are nowadays, comparing all time when we were creating classic theme sites. So here's my site.

A

So, no because the solution was a normal web part if I go and modify this page, we do not see that webpart available in my record picker or component picker or whatever or whatever. We call this. So the only way I can actually get the wet part to be available within the site. Is that I actually explicitly go to the site contents and add new, an app and then I select that web part, which is not visible in the apps?

A

You can add functionality and there's my web VP normal client solution, and after doing that, then the web part is available to be used within the site. Now, obviously that was when we started the GA of SharePoint framework. That was the initial that was step number one yeah and this isn't optimal, because what, if you need to push one web part to be available in hundreds of thousands of site collections? How would you do it?

A

Because we don't have a native API, at least at the time when this video is getting recorded, to get this solution deployed to the side? So that's not really an optimal thing.

B

That that another scenario that is not not included is what have you on the web part to be available in nearly created sites. Yes,.

A

Yes, immediately on the newly created slides we immediately when the site is going to create it, you want to have that one available. So that's not an optional thing. So, let's actually move back on here and let's get back on the on our let's go: VP and tenon scoped CD, maybe and Allen scope there. We go so I'm going to open that for a solution.

A

So this one has been configured my package solution. There is this: one has been configured with the tenant, scoped option to be enabled, and that's essentially the question in the yeoman template. So let me actually do that as well.

A

So if I go in here, let's create a sample folder and let's clear that one and now, if I, do Microsoft SharePoint when we run to the yeoman template- and we actually ask do you- want this solution to be automatically deployed across your tenna, and that question is only if you choose to sharepoint online only option so that functionality is not available in SharePoint 2016 t-to back to. Can we use that folder, and this is the question: do you want to allow tenant admin?

A

The choice of being able to deploy the solution to all sides immediately without running any future deployment or running had enough sin sites pretty big picture, but it is pretty descriptive there. So this is well, let's go yes or no question.

B

And I get there. There are so many things in it right because well what it actually says is that do you give the admin that choice, meaning it's not going to be always deployed tenant white admin will still have the choice whether they want to do it or not. Correct yes,.

A

That is correct, so let's have a look on that. So, let's, let's actually have a look on that some compost at one I'm gonna jump back on my solution. So this is where the term scoped deployment option was set to true, and we wanted to actually check how this actually works. I'm going to open up the Explorer in my SharePoint solution, folder, we already previously created the solution. A few minutes before the recording and now, if I go to app catalog and I want this solution to get deployed.

A

We can track and drop again the solution. Now the question is slightly different, so the question here is actually saying: there's to see it, there's the URL pointing to the CDN all of that, but make this solution available for all sites in organization. So, even though the developer has designed and made the decision that okay, this is a web part where we wanna push to all of the solutions automatically when it's getting deployed. It's still a tenant admin or the app catalog administrator decision. Is that the case or not?

A

So if you do not check that checkbox, then the solution is not automatically or a web part is not automatically getting a component. No.

B

So there are two things: I'm, not sure. If now is the right time for it, so first of all, you said that developer makes the choice whether they want to allow it or not. Why developers.

A

Well, I didn't say that the developer makes the decision based on this design of the functionality part.

B

A

To be used to cluster the cross site collections or not, and then the admin actually makes the final call. The keychains and key point here is that if the skipped feature deployment egos true as in it is a tenant scoped to the point option, we do not execute any feature xml's, which might be as part of the solution. In this case, in our solution, we do not have an XML files here, but you might have, for example, a dependency of the web part to an existing list or a new list on the site.

A

So, as my installation of the solution, your web part is assuming that there's a new list called let's say my urgent tasks and sure yeah. Theoretically, you can execute JavaScript, which is creating that list. But what? If the user, who is actually adding the functionality or adding the the web part to the page, doesn't have permissions to create lists?

A

That's where the future XML based provisioning, actually wins and because the feature XML, if you include those in your solution based on our tutorial guidance as well, and we executed all of the XML and feature definitions by elavator with elevated permissions. So even though the user wouldn't have the right permissions to create a list, when you add the solution to the slide explicitly, it will actually execute until its creation process.

A

B

Dart again, to do two things: I want to.

A

B

Because this flag is, let's say, related to how the package is built, that's exactly why only developer can say whether it makes sense for their package or not quite.

A

B

So, as you said, the admin makes the final call, but it's only developer, who build the package can tell where the death package is suitable for tenant wide deployment or if it has declarative provisioning elements inside where and which is why it has to be installed for each side, because otherwise the package would be or parts of the package would be skipped, correct, correct. That is absolutely correct.

B

So so, if so, if you think about it, imagine that you didn't want to do any of the XML, because three reasons: what would be the alternative approach to achieve exactly the same right so to be able to allow users or unprivileged users to create all assets that the pack geez so yeah.

A

So, let's talk about that one so just making sure that the web part works properly and now that we created this one web cast and Emma won, and let's put that web part here. If we go to the web part beaker, we can see that our tenant scoped deployment, a web part, is available and that's getting deployed or rendered properly.

A

So, even though I don't have any solutions, instance on a side know if this web part would have a dependency on the list like mention, you can use the feature XML inside of the solution, but then you would have to explicitly install the solution or west of the site and that's not necessarily an optimal thing, even though sooner or later we will have an API to do that now, the alternative option. What you can do is that you, if you have a solution which is owning the site collection provisioning.

A

Essentially, you have a cipher collection, self-service site collection creation story and you have a custom endpoint there, which is, for example, applying some theming and colors, and all of that at this time you could use that to let's say, create those lists available, and that would be the typical way of making that happen right right.

B

So, in other words, you would either need to have an add-in or an ad app that runs on their app only permissions right. So in order to elevate correct and then that component would provision everything your package needs in the site, correct. That is correct, yes, which is significantly more work than adding a few xml bits that.

A

Is absolutely true so and I already him that we're add that we will have sooner or later a ALM api's and that will tackle some of the story as well, because this is not this. This is definitely one of those things where we don't have. What is the best practice? Well, it absolutely depends. It depends what your great part is doing and it depends on on. Do you have a self-service, ID provision in and it depends on?

A

How do you create your sites and who's creating those sites, and all that, so we will have an ALM API is quite soon available, which will kind of fulfill the the final gap on the scenario and then those aren't designed to make it possible for you running code and install applications at insanity, open framework solutions, one by one to the side, so you are still able to have or automate the installation, because right now, there's no API as to make that happen.

A

So if you have a solution which requires to be installed explicitly on a site, there's no supported api's, which would actually make that happen right now. Okay, so that's the web part story and what kind of a already talked about slightly the extensions, but what about the extensions? So, let's actually have a look on extension, some kind of a similar set up with extensions as well.

A

So if you go first, the normal extension story, if we run through our tutorials- and you have a look on the, for example- the application application OOP- where did it go application customizer?

A

We actually used the non tenon scope deployment option in the tutorials, which basically means that are there's no skipped feature equals true in the in the solution package, solution definition and we actually create you as part of 1.3 version forward. We create you to default, feature definitions and all of that to a bracket solution chase and that basically means that to be able to get this extension available for you in the site, this particular extension, which is not tenants code.

A

You will need to install the solution to the side and we can actually, let's walk this through. So as part of the part of the solution default solution structure, we actually create an element's XML file. The elements XML file is automatically churun generated piece of map based on the default values and in this case it's basically saying: hey SharePoint.

A

Whenever distribution is getting instant to the site, please associate this application customizer with this ID to sa user custom action to the site and by the way this is the parameterization for this application customizer so that, whenever it's being used, this is the the instance level configuration for the workstation. Now, let's actually make this one deployed, so we can walk through what happens and what's then, the difference between that and a tenant, scoped extension deployment so in depth SharePoint. We do not have that fellow yet.

A

So let me actually start explore in this folder, so we actually can get it easily deployed. So, let's get in here in the SharePoint folder solution and that's my ex normal extension normal and there we go. We can say that it's a normal activation of the solution. Let's get that one deployed and now it's available to be installed on the side. No right now, at this point, I'm going to quickly create a new site, because this is the default extension. I haven't done any modification, so it's pretty annoying.

A

Actually, when you get it up and running, you'll see it in a second but let's create web cast. You know two sides: it's definitely hbi policy. This slide is getting created and the finish is getting widen up right, No excellent. So now, if we go on this side, so obviously the work- the tenant scoped web part is available on this side as well immediately which, which is a good thing but and the other web part isn't and the extension yet isn't.

A

So how do we get this extension because it was a normally deployed extension available and knock Tibetan on the site? Well, we can add an app and then in here we can say our extension application for solution. Let's select that one and that is now getting installed on the site. So there we go it's getting installed on the site and we can do an f5. This is really depends on on the speed of things.

A

So that was fast and we can say that I refresh the page solution is gonna install and my application customizer it's getting executed. So there's my application customers I, which, by the way super annoying customizer, because if I click OK and if I can now go to the home page, it's actually doing that again. So not necessarily something what you're gonna do. But.

B

So the future XML that that you created what does it do.

A

So what happened here was that, because we installed the solution to the site- and we activated this feature- which is automatically buckets inside of the SB pkt file- and this feature octave or executed this XML fragment- and this XML fragment essentially is saying for SharePoint that hey there is a user custom action which is an object collection in the web object and let's associate this client-side component ID, which is matching the manifest ID of our extension. So if I come in, here is matching actually on this one.

A

Let's associate that one to the user custom action collection of the web in this case- and let's give the this as the default parameterization and execution. So you can see that if I get back in here, it is actually saying test message, because our parameter station is saying that that is what it should be, showing right.

B

And because that an application customizer, you don't need to specify any additional info, such as field ID, correct, so.

A

If it would be a ListView cost, a common set customizer or if it would be a field customize that then this XML looks slightly different, but we do actually create that default setup for you as well nowadays in the in the bundling, which is all the scaffolding which is pretty cool now, okay. So this is again.

A

We need it to activate the solution in a site and that's not really an optimal thing, because if you have, let's say a self-service site collection creation story- and you want to have your extensions activated by default on those sides- and we don't have an API, how do how would we know this isn't doesn't feel right? So how do actually? How do we actually want to make this happen?

A

So, let's close this one, because it's the annoying site, which is prompting that alert all the time and let's go to our second fellow, which is the extensions in a tenon script. Now so next tenants script and let's do the CD there as well.

B

A

It's been a long week, it's.

B

A

Afternoon so.

B

While you door opening this and I think, can you still bring up the XML, because there's one thing I wanted to ask absolutely on the normal extension right? Yes, yes, yes correct! So when we add a webpart to the page, you can open the property and then you can specify parameters Christ, correct, yes, but because for extensions there is no UI to do it. We have we. We have the option and extensions. Allow us to use pump parameters right, so you you can build it once and then adapted to every single site.

B

You want to use it across correct truth underscore, but that's somewhere. You have to be able to actually specify the values for your parameters, correct, correct! Yes, so that's what we can do here as well, so not only an able it but also configure it. For this particular instance.

A

Yes and that's pretty much yeah client, side, como component properties here gosh and that's a super super important thing to realize as well, because that you can thrive the behavior of your extension based on this properties. Now, in this case, in that particular site, this extension has already been up and running. And, yes, you can use API, remote, API, REST, API system ApS to go and modify this properties if you need and then that can change the behavior of the of the extension in this case, it's it's just managing.

A

While it's going to be actually shown as message super simple extension, but it could be the behavioral things it could be. It could be almost whatever it's up to you. What your estimation is doing. That's the thing so in.

B

Other words whatever or the same approach that applies to web parts, whether you build a web part that do one specific thing or you make it more flexible and allow the user that adds it to the page two says head it up. Yeah, you can do exactly the same here. You can build affection who wants and I allow it to do different things, depending on how it's being set up on that particular instance, whether that's a site or a list or a field correct.

A

Absolutely absolutely now, let's get back on the ten scope deployment option on the extension, because.

B

A

This is super interesting for some of the some of the people who are trying to figure out how to make this happen as well, because, like mention right now, if you need it, if, if the comin with me that you need to always install the solution, decide to get your stuff enabled yeah.

B

A

Not really optimal, so how do we make this happen in that in a larger scale? So this is a tenant, scoped and deployed extension. So I can show you that in the package solution again we have that attribute called skip feature deployment. There goes true, so, even though the solution would have XML files, we would actually ignore them. This means that whenever the solution is getting installed on this application catalog, it is immediately available across all of the signs, but because its attention.

B

Coming as assuming that admin chose that it's, it's still a choice, absolutely.

A

Absolutely, and in this case, because we chose that this is a tenant scoped deployment, we did not find a fault, create you, the default XML, because there's no need for them, so our scaffolding engine is kind of clever enough to understand that you can still create them and modify this to be false if you need to afterwards as well, absolutely doable. No in this case, let me actually open up again an explorer here and let's get this fellow deployed to our app catalog, and what's my folder, that's my folder.

A

Let me actually refresh just in case that there's no pending UI things. Yes, oh yes, hello! Yes, let me click their complete refresh. There we go. This is my tenants go black station in the SharePoint folder solution by default we have extant unscoped. So let's actually get that from the point, and now the question again is slightly different than for the previous extension.

A

What for so and where we were asking that from the admin that okay do you want to have this extensions available Crisanta sites- and this is the final control from the tenant from the from the let's say, app catalog, administrator, technically tenant administrator can delegate responsibility of that catalog to anybody else, but ultimately it's not administrator who makes that decision now, let's click deploy now.

A

This does not mean that that application customizer is now activated across all of your site collections, because technically that would be insane, but you might have hundreds of thousands of site collections and most likely you want to have slightly more targeted way of providing that functionality or activating the functionality, or it might be that in some site collections you have multiple extensions, some site collections. You have subsets of vaccinations. So that's why we don't want this to get activated automatically across the whole term.

A

But then the question is: how do I actually make that happen now, in this case, like mention, let's actually create a new clean site and we can well technically reduce this one, but let's create a new site, so we can walk through the whole process. Let's create a site, it's called this demo webcast demo tree and definitely this is top secret because we don't want anybody in creating a site. Luckily it takes only few seconds and there we go clicking finish and there we go. There's our new sign.

A

So now how do I actually get on this site that tenant scoped extension available animation? It is already available to be used with InDesign, but we haven't associated that to the right objects and the easiest way to actually do that. It's well you could. You could run a rest of a P I, so you can run Caesar made the eyes or you can take. It run this, for example the PMPA provisioning engine to make that happen. So let me actually get in here and in my PowerShell.

A

So let me clear this one: let's actually go and connect EMP EMP online and let's connect to that site using PMA, PowerShell I'm.

B

A

First show an octave 8, X tension and, let's have a look on. How did we actually make that happen in a second, so we're using the PMP PowerShell super super valuable super increases productivity enormously for these kind of scenarios, because we're able to manipulate the slides directly in the context of the site and that's pretty enormous, because we can automate all of the stuff. Obviously you can automate the logins and credentials and everything else as well.

A

You can now, for example, do something: I had had the MPA list and our list item or list and well at a library yeah that EMP? What else client-side page there's multiple different things. What you can do mangas amount of things. First, we can actually whatever on the site. No in this case, we don't want to actually do it on. So let me slightly move to a new location. I do have an extensions XML on my site. It's a serialized BMP provisioning template, in which we can actually have a look as well.

A

So let's have a look on that one. So we're going to start again have a look on that one in the individuals to layer cut. This XML is using the PNP provisioning schema and the definition, and what we are doing here is that we're saying that whenever we are applying the template, a super simple template, because we removed everything else from the template. It might have lists and everything else. We activate or create a new user custom action which will have this particular ID.

A

It's a unique ID component ideas that one which is matching again the manifest ID of the component, which is now already deployed to their catalog, and then we are able to provide the parameterization. So in this case we cannot use updated message as the parametrization for that particular functionality and.

B

I guess that, with that, you can already see that it resembles a lot. The feature XML that that you had previously it's.

A

B

Identical truth,.

A

Absolutely- and this has been documented, there's game on there's examples: there's a schema files, everything else and people are quite nicely and using this lot anyway, to automate your stuff. So.

B

A

If I do apply and apply a PMP provisioning template, and we want to reference that file extension XML in here, we are already in the context of the site. The web custom entry sign I'm, going to execute that one this one technically. What it does is that it uses see some underneath or the remote API sees more rests underneath and it's gonna actually apply that configuration and to the side. That was super fast again, because we only had a one entry in the template, so it didn't take that one.

A

But now, if I go back on my website, web cast tree site, and if I refresh this, we can actually see that our tenant telescope at the point extension is available within a site. So now, if I scroll down, there's my message and it's using the updated message in the UI as well, but people difference here is that if I now click OK, we can still go to the site contents, and we can see that there's no solution since not on the site, because we took advantage of the telescope deployment option.

A

We just remotely configure the extension to be available within this particular sign, and the same could happen for your let's say: field customizers or the lists very common sets. In the same way, you can supplied up the extension as long as you have the Denon scoped option enabled and deployed in the catalog. You can light up the functionality just remotely accessing and setting the right properties in the site level right.

B

And I guess that the benefit for that is also that when you already use provisioning engine light like the one here, but I can imagine that that would work with also other engines that that just use either cc some arrests that you could make enabling the extensions a part of your deployment. When you create your site, you create libraries. You can make that complete by including extensions as as well absolutely.

A

Absolutely and like like, like you, said more like so you probably there's a lot of customers who invested on this automation on the provisioning and covenants automation as well. The BMP provisioning interns, just the one of the one sample it uses native out-of-the-box api's, to make all of that happening.

A

So it's just a convenient way of automating stuff on the sites as well, but could have quite long demo, but I think we went through the different options, the impact of the different options, and when do you need to deploy and how do you parameter sites those individual instances as well? And that was really the key point here as well as to understand how would I parameter science differently, for example, my application, customized or in certain site collections in certain site collections? Well, you would just run against, for example, for different.

A

You would use a different template, and so it's not just about the feature XML based deployment option.

B

Right and also dozen times, the one thing that we're gonna really talk about is that when you look at the template that we just had at the end with PMP, you can imagine that you can run that template against different sites and provide different values for each site. Correct.

A

B

That what if you wanted to achieve this, the same through XML, declarative, prompt or visioning, would you have to have feature for each case, yes site or how would you did the work that that's.

A

A that's, a pretty good question and I. Don't know how it would actually work, because for me that feels not as a suitable thing. So if you need to have a multiple different, let's say configurations based on your site, I would say that the remote provisioning promotes API way of configuring them. Absolutely the right way to do, because that gives you flexibility and then making that happen, plus deactivates the solution which you have deployed. What? What would?

A

What would it then mean your user custom actions then removed from a site, and then your behavior is different. Now that you used the tenon scope deployment option, you can control the behavior across the tenant much more efficiently right.

B

Right the fact that when you add solution to a site you actually install the package inside at that point, you're gonna choose which feature it gets enabled sure. So if you have five of them, one setting it to orange one to blue one to gray and so forth, you're gonna really choose which one is enabled so by default. They are all enabled correct, correct that.

A

Is correct? Yes,.

B

So then you would have to turn all of them off and then turn the only one you need on this. Wouldn't.

A

Really make any sense yeah that doesn't sound, try it absolutely mr. yeah.

B

And also, if you, if you need another way to set up your extensions, you would have to what update the package redeploy just because you want to edit add another choice right, so that doesn't really make sense either. That's.

A

True, absolutely absolutely cool I think good discussion, absolutely and hopefully you'll find the video useful. The whole point like mention, was trying to clarify what does the tenon scope mean for different component types and working through the different options? We'll get some of this stuff absolutely documented in the Docs that monster that comes last shipment sooner or later. But hopefully this is good reference for you as well, but thank you Mark for joining. Thank you, everybody for watching and welcome up with a new webcast sooner or later. Thank you. I.