Microsoft 365 Community PnP Webcasts, 31 Aug 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: PnP Webcast - Introduction to SharePoint Webhooks

Description

There's a newer version of this webcast recorded as part of the Webhook General Availability (GA) in January 2017. You can find updated web cast from https://www.youtube.com/watch?v=P4a1_EWokwM

In this PnP Web Cast we focus on the SharePoint WebHooks capability. WebHooks will provide more reliable remote event mechanism for operations happening at the SharePoint side. In the past you might have used server side event receivers or remote event receivers to achieve similar capability.

WebHooks are industry standard model for http based events, also used by multiple other services outside of Office 365. Currently WebHooks are already supported for OneDrive for Business and for Outlook. SharePoint support will be also gradually introduced, like explained in this web cast.

Presentation (https://doc.co/Jwbh8r) covers following topics:
- What are WebHooks?
- How to subscribe to a WebHook?
- Event notifications and processing
- GetChanges pattern
- Why to use WebHooks over Remote Event Receivers?

Web cast demo shows following details:
- SharePoint.WebHooks Visual Studio sample walk-through
- How to subscribe to WebHooks
- How to implement an asynchronous pattern with WebHooks using Azure Storage Queues and WebJobs

The sample used in the web cast will be available in the SharePoint Patterns and Practices samples repo once available. Check out the details over here: https://github.com/SharePoint/sp-dev-samples/tree/master/Samples/WebHooks.

Web cast presenters: Bert Jansen, Vesa Juvonen

Additional resources
See following resources around the WebHooks in general
- What are WebHooks? (http://culttt.com/2014/01/22/webhooks)
- Outlook Notification REST API reference (https://msdn.microsoft.com/office/office365/APi/notify-rest-operations)
- Outlook Notifications REST API (http://dev.office.com/patterns-and-practices-detail/7227)
- OneDrive: Adding a new subscription - OneDrive API documentation (https://dev.onedrive.com/webhooks/create-subscription.htm)
- OneDrive WebHooks ASP.NET Sample (https://github.com/OneDrive/onedrive-webhooks-aspnet)

Thanks for your interest on the PnP initiative!

A

Hello welcome everyone. Today's webcast we're going to talk about sharepoint web books, sharepoint web books is a really cool new feature. That's coming up in sharepoint, and we want to give you an early introduction to that. My name is Beth Johnson, I'm, a so Microsoft and with me today, I have a vessel Vernon, hey.

B

My name is Erin and I'm senior program manager in shape and engineering, so like a lot quickly on the on the carnauba timing and everything else at the webhooks right now. What we're going to show you guys today is something which is coming in summer, 2016 so oberstar, depending on when you're watching the video this might be available or it might not yet be available within your first released tenants, but we'll get a a plot posts out there. Whenever the things are available for you to reuse.

A

B

Huge some notes on the under on the SharePoint P and P site. So it's just the kind of a clarify the situation, the office 365. Balancing practices is well nowadays kind of a combined with SharePoint and patterns and practices from a prank perspective. So what we want to do around on messaging and within the webcast is that we kind of a differentiates all of the SharePoint related topics under the SharePoint P and P Prime, and then all of the non SharePoint related topic under the office. Traces to web developer, balance and practices sprang the initiative.

B

S is exactly the same. It's just matter of printing and printing the SharePoint in a spotlight as well related on SharePoint specific topics, so the SharePoint BMP, the same set up as an office raises to five PM p f--. We provide you code, samples, guidance, documentation, monthly community calls case studies and on the theming site or birthday in the future, will concentrate more and more on the shipment framework and all of this new goodies which are coming up in a SharePoint fee. Next, the SharePoint, adding model or Admiral or whatever.

B

We want to call that it's still completely valid in the future as well, and especially all the season based operations in the backend services is something what we will be using in the future as well been in the context of SharePoint a kms office. Def PNP is still the actress and most likely will do a SharePoint PMP, a kms Atris landing to that same page as well, so we kind of in the middle of transition. While we are recording this webcast, but I think that's for the introduction.

B

So, let's actually deep dive on the SharePoint web hooks Yellowbird, take it away. Web books.

A

What are web hooks web ebooks essentially is a way for you to be notified of a change or don't change. So if your application is interested in knowing when something changed, the web book is the universal model to do so. So in a sense, it is similar to remote event, receivers, which is also a push model so SharePoint reaching out to you. Instead of you, go to SharePoint and ask what has changed now, there's one little difference between Hewett when receivers and Web books is that web books do not support the synchronous model.

A

So a web book only happens fires after the change not before so the item adding or item updating events. Those are not there in in Web books. If you need them, you can still need to use remote event receivers, but there are several advantages of using Web books over them with different receivers which we'll talk about later on and in this deck now. Web ebooks is also something we're. Just not I think that Microsoft invented is not only for SharePoint or only for up to 65. No, it is more broadly used in the industry.

A

Companies like WordPress and github and MailChimp by using web hooks to allow their developers to integrate with their service and Microsoft. This is just implementing the same model for their services as well like we have today already for onedrive in Outlook and SharePoint is following so, and what you see here today is mention. My VESA is an early preview of what will be available in public preview as of summer 2016.

A

Now that coming slides will give you a view on and personal how to subscribe to a web hook and then how the notifications work so step one subscribing to a web hook. Your application needs to tell SharePoint. I won't have a web book on this particular object.

A

Currently we have support for lists web books. So, let's assume we're going to add a web hook to a SharePoint list which we'll do via post request a rest call using the post operation to HCP for API slash web slash lists. The idea is the glue it of your list that you want to have a subscription against and then slash subscriptions important content that you need to provide. While doing so is this notification URL essentially you're telling SharePoint like ok?

A

If an event happens on this list, please notify me on HTTPS, euro / or / / book / service this case or your endpoint. Another important thing is the expiration time. So when you create a web book, you can define like when will it expire and the maximum expiration window that you can define as six months. So, within six months you have to renew your web book subscription if you want to keep it, if not, it just expires and gets out of the system. So that's different compared to multi-vendor serious.

B

Sober tone that one actually actually test the Kannamma are thinking on that one. So couldn't we do something like automatic renewal of web codes within every single two months within our service side, so thinking out loud on the on the ALM of the web, poke? Yes,.

A

Absolutely so there are different veterans. I think the best partners were the one that you mentioned. Vesa is indeed keeping track of the web books that you created or just checking out and then automatically renewing them when they're about to expire like having a web job running a nagger that is scheduled to run each week and finds the web books that are about to expire and just renew them.

A

Another model, which is more lightweight, would be like whenever you get an web book notification, you check when you get that the web notification you also see when is about to expire, welcome.

B

A

Coming slides, if it's about to expire at that point, just a bit expiration date for another six months, so yeah models can work. Oh now, coming back to the slide, when you do the, when you want to add your subscription, your web book share points will go out to your notification endpoint. So this is different. I'm, your moat event, receiver. So we will go to your education endpoint that you specified in the subscription payload and we'll give you this random string. So a validation token, which essentially is.

A

Is it good what you need to do in your service endpoint? If you see the rotation token coming in, you need to reply with HP you understand and with the content of the message, the same string same GUI tacticals from SharePoint. This way you can confirm the SharePoint that your endpoint is running and available. If that doesn't it's not running, description will fail. So this all succeeds and you will be notified by SharePoint with an HTTP 201 being like the web book has been created and you get the additional data that you need.

A

So you get web book subscription ID. So this GUI is actually a unique identifier for your web book that you just created, if you later on, want to, for example, an extent expiration date of this web hook with this ID, you can tell share pornog extent web book with ID, a8, etc for another six months. So, if step one, then we have our web book in our system now. My next step is okay SharePoint. Let's say we added this web book to a list and I create an item in the list.

A

At that point, SharePoint will see you change and will notify us, so it will do a post to our source and point that we specified previously providing information about the change location, but no information about the actual change. So if you look at this this payload, this is what you get. You see the description, ID expiration date time, the talent, ID etcetera, but you don't see like item edit or which field was added. There is no context about the actual change, so that's different compared to the most event receivers.

A

Absolutely what you need to do, what your service and what needs to do is reply with HTTP 200 being acknowledge that you accepted the the notification. One big caveat, though here is like you need to respond in less than five seconds. Why? What.

B

Actually happens that they don't that's not an interesting thing.

A

Yeah, if you don't, then we will see this request as being failed, and you will retry to deliver this message to you again. Okay, if you keep on consistently responding later than five seconds eventually, we will not send the message to any more to you and the message will be lost, so it is a good pattern. The best practice in this model to be able to always respond in five seconds in each and every case, and the best way to do so is using an asynchronous patron.

A

So, let's dive into that one, let's move to the next slide and see how that then does work.

A

We have the right side, SharePoint, notifying your endpoint at the left side over here to get into an asynchronous state. There are different models that you can use, but something which is very common, a popular in the PNP community, is using storage queues and Azure, it's a few lines of code and you have an item in the queue. So let's do that. So we put the message that we got from SharePoint in the queue and then we talked SharePoint. Well then, we call it so this operation is super.

A

Super lightweight can be done in fraction of a second and then less than that 5 seconds over yeah, obviously less than 5 seconds. It should be like milliseconds to do such a thing, and at that point the message is in the queue and we can take the time to process the queue processing, a storage queue again different options, but the most common office option is using Azure web job, which is automatically monitoring particular queue. When I see some message in the queue picks up the message and then what then, like?

A

You saw before that the message you get only contains information about the change happened over there, that's it, so we need to do something with it.

A

The model that you have to apply is to use seesaw, so the system, if you get changes, api's to go to the particular list in this case and ask from the list like list. What changes that happen to you give me your changes, so you get one or more changes back from the list. At that point, you can process the changes.

A

So if you see like an item, was added, you get it back, as in from the ditch get changed scroll your code can then, let's say, do the same, update and another system, because you want to integrate those systems just thinking about something. So you need to do something with the changes you get back so.

B

Basically, berthed as part of that original post, the first request, which is coming from sharepoint, you are actually getting the the web ID and the list ID so you're able to then figure out which list you will apply to get change this to yes,.

A

You get so in the payload, you get, you get a resource property. The resource is actually this case. The list. If you have web hooks it will be the web ID. So you get a neat an ID, pointing to the to the right SharePoint object that you need to query for changes. Yeah.

B

Yeah and I know that within the first release we will be supporting list level back loops, so the additional stuff Moab is coming later on in the in the roadmap, but it's good to know how to actually get access on it and I think we have a demo on this one as well. Yep.

A

Yeah well show this later on, yeah there's one more slides and then we jump into demo. So the next slide, we're gonna, give you bit more context on how to successfully work with the gate changes, because you need to rush some things to be aware of so, let's jump into that slide and then, after that one we can do a little demo, an application when your application creates a web book like we did on the first slide.

A

It's all good book is created. You get the subscription ID back from SharePoint. Now, what's important at that point that you grab the current change docket from the list, so there's a current change. Token property on the list that you can use file system. Inquire SharePoint like give me the current change token off the list. Why is it important? Because you want to track here? What happens the list as of the moment that you created the subscription? So we need to have to change talking available, so you grab that one and this all this is.

A

It is in the demo code, so we can graph or later on, and you need to persist that opens somewhere. This case is secret, ledger database, but could be also another way to persist it. It needs to be persisted as eating later on. That could be like one week later, if nothing happened in your list. But let's say one week later: someone added an item to the list and SharePoint hits your notification endpoint, because there was a change, all goods you which, as shown previous light, we go asynchronous.

A

So we use a storage queue and a web job to do the work now the web job when it needs it, wasn't the changes it first will grab the latest change token from the database, which is the one we put in there when we subscribed the web book. So we we have that change token and we use the get changes. They give me all the changes as of this particular change token, so you get all the changes.

A

As of the subscription, you process all those changes at the end when you process the last change, you take the change token from the last change and save it back to the database so next time. Next event that happens if the same project Oh share Ponder's the post put a message in the queue web shop runs the web job. At that point, he grabs the change token from the last process, change and goes to share point with that changed okay.

A

So you only get the changes from the last process as of the last process, the change, so you don't get duplicate change events which.

B

Is a point on that on that one actually Burch has to clarify what you mention around change token, but that's actually a time. Isn't it so we're? Essentially what we're saying is that please we need to save the the previous time the webshop was executed and whenever we are requesting get changed as per saying, hey SharePoint. What has happened after this time, so we're carrying the times and it changes what has happened after that previous execution of the webshop yeah? It's essentially.

A

A time concept, although it is expressed a little bit different I think in the token, but it's a concept of need, give me the changes. As of this particular point in time, yeah yeah, right, yeah, this one one god sure that that you need to be very often, which we have clearly documented in the sample code- is that there that has deal with web book, so AB AB, AB job sorry behave.

A

So if your web shop is monitoring a queue and it sees two messages appearing in the queue at once or sitting in a queue, it will spin up to intercept so it will process both messages in parallel. So at that point you will have some concurrency issues of could have some concurrency issues which results in getting you're getting the same change twice. So at that point, is it best practice to have your web job running in a single instance mode? So it will process message my message, so you don't have that issue.

A

The issue will be limited, though, because we are also batching at our site. The messages we send so we're not sending you a notification for each individual change. So when, let's say sorry, oh you have a list and you at 100 items to the list that triggers 100 and turn all changes in SharePoint. But our web book eventing mobile inside SharePoint, which is time which are based, will kind of do a deduplication of the events. So after 100 additions to a list in say five seconds, you will only get one event in your notification service.

A

So only one message in the queue, so no risk on potential duplicate get changes being a pull down from SharePoint, but depending on on on the loads, it might be that difference from the service sent the same message. So you might see a duplicate now and then so, and this pattern gives you like a really safe way to deal with it. Yeah make.

B

A

Ok enough talking, let's try to show this in real life in action. Yep.

B

Code is always good, so how does it actually work and obviously this sample will be available in the PMP sample, Gerrit calorie whenever we are in the status where the capability is available within the tenants as well, because, right now, when we are recording this video, this is already too early. So right now, this is not available. In the first released announced it will be available there in summer 2016. So depending again, when you're watching the video, it might be there or might not. Yes,.

A

So so application itself, the demo is a SharePoint MVC application.

A

Like we have the web part and the actual shape and partner with some common classes, a common project with all the logic and then the actual web job. That is the work, so the isochrones part.

A

So let's first do the demo and then show a little bit of the code. So in the demo we have no, let's, let's just do slightly different I'm gonna, press, a5 and Ronan's. Just show you guys that there's a web book on a particular list and then we'll make a change to that list and see how that happens. So I press the 5, the application is being loaded from visual studio, so I'm in debug mode and SharePoint is working on it.

A

And here we are so what we see in the application is a list of all the web books for all the lists that you have in your site, so it will scan all the lists and we'll check like this.

A

Do you have web book is a no so and release those you can add a new web book, so I can go to the documents, library and say like I, want to create a web hook for documents, and at this point SharePoint you got the SharePoint sharepoint goes to your identification service service replies with the string it gets from. Sharepoint sharepoint goes back to you, saying, like ok, everything to see that you get an HTTP 201 message back from sharepoint and that's what just happened.

A

So we have a new web book on documents over here and it is listening to this particular endpoint. So this is my endpoints deployed in Azure and we have an expiration date. So there's nothing September! This workbook will be gone right. Let's delete this guy again, while this one is deleting we're. Gonna focus the next part of them on the on the countries list. So we already have a web book available on this list and let's go to this list. It's simple list showing some countries: Belgium Italy, Sweden, Finland and France.

A

Now I recently added France I made a mistake: I'm gonna drop France. So, let's say Italy to item okay, so at this point, France is deleted, and what will happen now is that SharePoint will see this change in a short moment. The internal timer job will fire we'll see we grab the changes, the duplicate and sent a message to to our endpoint, which will put the thing in a storage queue and will be processed so sometimes we're lucky, and that today we're lucky.

A

We see the message in the storage queue, so we clicked on the right time to refresh so it was there and it if my webshop is still running it will disappear. Let me very quickly check the web job that is still running. We can refresh it over here if it disappears.

B

You can you show the text in the mess. That's out of that, because that's the message text preview. Just out of curiosity, if you open up the message, so what are we actually getting so.

A

What you get is the subscription ID. We just do your workbook subscription, let's zoom in client state. We didn't talk about that, but you when you subscribe web book, you can also provider a string, client state, just a string for your information and we'll always pass back the string to you, which can contain some additional context for you to for your application. We have the expiration date time and then resource over here, so this guy. This actually is the list ID yeah.

A

Then we have our talent ID, the URL, so it's in the dev site and the idea of the web. This is what you get so no information about actual change, just the location of the change.

A

Alright, so I press, I refresh the queue message is gone, which meant it was picked up by the web job, which also means that we should have something in our UI now. The implementation of this demo is that we just have a we list. What happened? What changes we got? So we have a web book history list in here, and this list shows the changes we we had just creates a record for each change. It gets so before the demo before the webcast, I I, already added France, and now we deleted France.

A

So you see like oh and change of the type delete object happened in the list, countries for item with ID 32, and that happens to be a once record yeah.

A

But at you, when you create a web book at that point, you do something with a change you propagate it delete and all system, because you want to sync the data or you process it in different way that it's your business logic doesn't do something with the change we just for demo purposes, track changes in the list which reminds me like, if I put a red book on this, one I will get a nice circle of book. Yes,.

B

B

A

Bring people on crazy.

B

A

B

Just did it actually.

A

So the go: it's very quickly, a few pieces of codes, we're not going really deep in the codes leaders go faster for this webcast, but for sure we will have additional webcast or more details on web books in the future as well, so MVC application controls a web book servers are just a plain HTTP service, so you can use the API control of the greatest service. We have this or notification endpoint.

A

We respond to the post. Remember that you can get a validation token inside when you do the subscription. So if you had a rotation token, you simply, if you apply the foundation token back to SharePoint, if you don't get a validation token, it means it's the actual notification event, so the same endpoint is used for confirming and for actual notification. What we do over here is essentially deserialize the the contents and add it to a notification queue. We want to be a synchronous.

A

The notification queue is, then, let's jump to disk one, so it's actually just putting it in a storage queue. You've seen this piece of codes many times before revenue, q reference, adding it to the queue. That's actually.

B

A credit call when I think of it that's five lines of code yeah.

A

It's super easy oppression, yeah, absolutely yeah. The one thing with queues is you need to have lowercase, Q names always tend to forget it, and then I hits me but little side. Now it's reading a queue again. Is this even simpler? It's yes, one attribute saying like want to trigger whatever cute rate you're on this queue. So if something in this queue happens, this particular method fires. In this case we have every all logic, point kind of combined and change manager class. So with it we'll go to change, mentor class and save process notification.

A

If I jump in this guy, you see that we're getting back into the regular SharePoint codes that they did. The plane is called plane all season codes, but still super important in this model as well so see. Some is needed.

B

In the future, future.

A

As well, so we setting up or dedication manager using the PNP call library. In this case you can do whatever this world between you speed be call. So we get an app only a client context, because your endpoint, the disco go back to ship one. So it needs to be able to authenticate to SharePoint.

A

Then, if I scroll down a little bit in the code, we are preparing a change query for SharePoint, so we want to have the item changes in batches of 1000.

A

We grab a token from database when we finish least off the token. So we grab the last change, took it from the database and then scrolling down. Here is what actual the change query happens. So it's a break point so for our lists that we want that we are looking at. We call the gate, changes API, providing the change Kirby. This change query does have to change dock in it. So you only get the changes. As of that particular change. So again you get.

A

A batch of changes can be more than one keep that in mind and then you process the changes do work. In our case, we put something in a list, your case, you do whatever that you need to do with the change and, at the very end, it's important again.

B

A

That we say if the last use change token back to the database.

B

So that we don't actually process them that that changes again within that list, yeah that make sense yes,.

A

And there's also is it about updating expiration, so in this case, whenever you get in a book event, we're checking like okay, if you're about to expire in less than five days. If so, we update the web book, so this Center also has a web manager class which supports, adding updating and deleting and and listing all the web books. So everything is there for you to just reuse in your code once it gets available, yep.

B

And that's actually a pretty nice pattern, because then you don't have to do any additional wet jobs or anything else. It's part of the service itself that is checking the status. Obviously, if we add a web hook on the existing list- and there won't be any modern notifications within less than six months years, there would be a theoretical challenge so.

A

That's the point with with this one, so it's to list the steel for six months and your web book is gone so the other model with us. Would you just regularly going back and refresh into a book thing? That's a better one, but it's quite a bit more work depends a bit on your scenario. I think both can be followed, depending on your case yep.

A

Okay, a few more slides to wrap up this webcast. You might wonder like yeah, okay, we have this remote event receivers. We love them, I, don't think so, but yeah could be.

B

Somebody might.

A

Love them, so why should we use web books and with the some of the key reasons, why do you use Web books? One of them is there's a retry mechanism with incremental backup. So when your endpoint isn't responding, we try again if you're again not responding, we will increase the time between our attempts. At a certain point, we will say like okay, this one endpoint is completely that we're not doing this anymore yeah details around how long are frequent.

A

All of that is still to be finalized, so we can't share those yet, but this twisted mechanism in there.

B

On that one, by the way I'm going to think of it, we do for app installed or installing events. We do have the ridiculous and for remote event for service, but not for a normal list. Events directly.

A

And we only try four times and you have to respond to 30 seconds. So it's yes, there are some it's very. It is a requirement, but it's not some this. This will be better yeah. This we trained model web books are also less taxing for your endpoint. The payload is always is very small, small JSON message, plus we are matching deduplicating, the notifications, so 1,000 items being added to a list.

A

There's not generate 1000 calls to you so, which is a good thing and also good thing for us, because otherwise you would go 1,000 times back to rest, trance changes which doesn't make sense.

A

What books is also, in my view, more secure than regularly receive this, since we're not passing any information about the actual change about the changed item. So no informations passed that can be compromising environments, it's easier to consume by non SharePoint developers. What I mean is about by people that don't have a SharePoint developers, knowledge? Don't you are not used to write humor event receivers, all of that it's a more universal model which is becoming more more industry standard, so everyone that issues to do the standards can work with web books as well and.

B

At the same time, the SharePoint developers learn how to their stuff outside of the shipment as well. So that's that's. A win-win situation actually yep. Absolutely.

A

But like with the new SharePoint developer framework, the same way yeah yeah and finally, the remote event. Receivers were based on CC F endpoints, because that was the thing which was out there when these were envisioned.

A

Whereas for web book CK uses plain simple, regular HTTP endpoint, like we did with the Web API, which again is way more, is called friendly for the known or SharePoint developers out there.

A

Now you might wonder like all right, but if you want to add a web book, hey my endpoint needs to be available and it's be available for SharePoint. It means it needs to be publicly available. So how do I then debug it because it needs to be deployed somewhere, so it is a little bit of you need to think about how to really debug it and because you have to have something running before you can even subscribe to web book. So the model that I used is using mobile debugging in Azure.

A

So I made a very lightweight v1 of my web book. Push it to Azure, so I could do a subscription model and then I use later on the remote debugging and Azure to if something went wrong.

B

Yeah one approach that works really well in Visual Studio 2015. Yes,.

A

Yep perfectly and actually also pretty fast, so you don't even notice.

B

A

Doing every moiety begins another bad run. It's and this use using ng rocket as a platform and tool, is built a tunnel between your service endpoint and you essentially, what you're doing here is you tell SharePoint my hair and point? One location point is hosted on ng Rob comm, you install ng work the client locally and when the client is running, it will grab the messages to the ship, one sense to that public endpoint, oxidant, ng rock and we'll transfer them to your localhost endpoint.

A

So at that point you will get your local host debug environments, hitting the breakpoint very similar actually to the model we used with service bus and remote event receivers within this kind of roll around model.

A

So these things are today available and I think you are already very sufficient to deal with the buggy and yeah. Let's wrap up this webcast, so we have some resources for you guys, an article about Web books in general bit more agnostic article about why webs are important for the web and for future we already used it out of the onedrive as I mentioned. So it is a link documentation about this Web books in Outlook and onedrive, and also a link to a sample.

A

We have a PNP sample outlook and there's a link to a onedrive sample in the onedrive github organization, I. Think with that fessor, let's wrap up this webcast official topics. You want to share one on read: books.

B

No, no, not really I, think this is a cute webcast on getting kind of understanding what happens and what's what's coming up and how the web for web groups are actually working, and it's really important to understand the a synchronous way of handling those messages. So you don't hit those timelines as well and we'll do a probably much more detailed webcasts on the code level later on for later on. In the in the autumn, sister yep.

A

And we also share the code as soon as Web books are available. First, who leaves tenants who will get the code the code out there for you guys, so you can leverage to go. It is a lot of usable patterns in the code and even clauses that you just plug into your projects and start being very productive food web books, yeah.

B

Absolutely but I think that's it, then the expert for for this one and and will come up with to come up with a new web cast sooner or later, Thank.

A

You yep sooner or later, Oh bye, everyone.