approvals using Adobe Sign. Adobe Sign, an eSignature application like Docusign or Hellosign is designed to let people sign documents online instead of using the traditional pen and paper. In other words, when a signer signs an online document wilfully and intentionally it’s considered an eSignature. It constitutes the same as a handwritten or “wet” signature and is a system of agreement which is legally binding as recognised by the US, the UK, the European Union and many other countries in many other parts of the world. The value of having an eSignature app for your organisation is easily describable and typically follows a standard set of narratives such as time as in the ability to do business faster, geography as in the ability to sign from anywhere on any device, the environment or the elimination of manual costs as well as the use of paper, and security and compliance since data is encrypted and the apps are designed to meet industry standards such as SOC and ISO27001 (ISMS). It is a great type of app for our hub for teamwork, but some will no doubt ask - and it's a legitimate question, why use a third party app at all since we have the approvals application? Two reasons here. Number one is there may be times when you need something approved and recorded with more formal attestation, and adding signatures to the approval process is necessary. Secondly we return to the prior point of signing being something intentional and thought out instead of a button click. Now in time the approvals app will support several eSignature applications. For example it's pretty well known that DocuSign has been demoed in sessions run by Microsoft. Yet Adobe Sign is the only one integrated into Teams today and at the time of writing its currently within Public Preview meaning a user needs to be set up for the public preview in the Teams Admin Centre. Like the previous blog on templates, my good friend Vesa Nopanen did a blog on this a while back so I am very much doing this for completeness and pretty much in the event I ever need to jump in and do eSign during our Art of Approvals session which we running on the speaking circuit. I am going to take a slightly different tack from Vesa and do this end to end, from scratch. I'll certainly be using it in real life
With Microsoft Build in the books you would think it high time to decompress, let off some steam and take some time out especially after the madness that was Teams Nation. Unfortunately, we've arrived at that time of the year. The summer circuit is underway; and yesterday I had the privilege of speaking alongside Vesa Nopanen at SharePoint Saturday Cologne: one of my favourite events which is run by my community friends Raphael Kollner and Jennifer Eimertenbrink. Cologne - Köln - is the fourth largest city in Germany, the largest on the Rhine and famous for, amongst other things, the Kölner Dom and Kölsch beer. Having been to Düsseldorf earlier in my career on business but never having made it out of the city or the Bolkerstraße Cologne is definitely one of the places I am sure I will visit to speak when things open back up. But yesterday was all about virtual, and the session Vesku and I did was on Approvals in Microsoft Teams. Now, earlier in the year I did a few blogs on the Approvals app: a few were on Approval flows using Power Automate and Microsoft 365 apps such as one using Forms, Lists and Yammer. Another focussed on Parallel Approvals. Since our session featured it yesterday as part of a roadmap update on what's coming for the app, I thought I would just knock one out about Approval Templates which I think significantly adds to what it is rapidly becoming one of those really strong apps for Teams now it's broken out of Power Automate. Vesku wrote one earlier this month but I thought I would also do one - for completeness and the opportunity to get hands on and get into the nuts and bolts. Based on Microsoft Forms, I don't really need to articulate and evangelise the business value of templates too much simply because templates are templates: they are designed to save time, effort, execution is quicker, repeatable. They help inexperienced users and ensure consistency across an organisation that uses them
So Build is done. It's in the books. I just finished up my last session moderating which was one of those sessions at the back end of the conference. You know the ones. Less attendees, but every one of those attendees die-hards still asking awesome questions to get every last ounce of value out of the event. I remember the first time I was out in Vegas at Inspire. I was still there at the Mandalay doing sessions on the Friday morning when others were still in bed conferenced out or were checking in at the airport to go home. And you have to hand it to the speakers who still show so much passion at the end probably having just done the last few days on about 4 hours sleep a night. So signing out of Build, I wanted to complete a trio of blogs on the new Power Apps for Microsoft Teams which were announced at the conference. The first blog was on Perspectives. The second was on Boards. This one is on Profile+
Day two of Build. It's a good one. And I have the opportunity of following up yesterday's blog on Perspectives with one on Boards. This is the second of three blogs on the three new Power Apps Solutions introduced at Build, and which I think are really building (excuse the pun) on the success of others released over the past six months. I am talking about Bulletins, Milestones, Employee Ideas, Inspection and Issue Reporting. If you haven't used them yet, they are Power Apps within the Teams App store which you can install and which are deployed in Dataverse for Teams. The great thing about these apps is that you can go on and extend their functionality, you can widen their use in broad distribution scenarios, but what is also really cool is that they are straightforward and you can simply use them straight out of the box. They are designed for a specific purpose. So let's get to it for today
Today at Microsoft Build it was great to run a Table Talk with Vesku Nopanen, Reza Dorrani, Mar Llambi, Karoliina Kettukari and April Dunnum. Lots of people showed up. I think - and I say think - we answered most questions. The chat was moving so fast that Reza, Mar and I were leapfrogging each other trying to answer them in time. There's a lot of interest about Dataverse for Microsoft Teams - particularly the apps which can be installed in them and extended with by Fusion Teams - Teams which are mixes of citizen and professional developers. Now some of these apps you may already know and used, and some of them I have already written about: Bulletins and Employee Ideas. There's Milestones too and a few others. Today, at Microsoft Build, three more were announced. Profile Plus, Perspectives and Boards. Over the next few days I am going to write about all three and all three are available in preview. Today I am going to cover Perspectives.