web app design workflow
so good afternoon, folks. i'm chris. >> i'm kerem. >> and so, this is an abbreviated, an infopath's folks version ofthe session we just delivered. if any of you were upstairs with us,there's gonna be an awful lot of repeated material there, so if youreally wanna go find bananas and smartfood, we will totallynot take issue with that. our goals with whatwe're trying to do
is make sure that we'representing the on-ramp for solutions that have been built ininfopath and sharepoint designer. and how that translates into thepowerapps and microsoft flow world. we just delivered a much deeper divesession upstairs in the ballroom on the state of business apps forsharepoint today and in the future. if you were not there,that session is recorded. so i really wanna redirect youto that deck and that material. a lot of great stuff there. extensive demos on how tobuild this material together.
so where are we with infopath andsharepoint designer? it's probably worth noting howwe've gotten to this point today. so infopath was introduced wellover ten years ago as an xml doc in form generator forsharepoint on-premises. and it's been there as the front endfor designing custom experiences on top of sharepoint lists anda number of scenarios for years. when we look at the stateof business applications built within infopath,built with sharepoint designer, we know that once they're in,they get sticky,
they become integral tothe way a business operates. and we recognize that if you look,and i'm a former mvp, and if you look at the history ofhow we've talked about this. when we talked about deprecatinginfopath two and a half years ago, we didn't give a clear roadmap forwhat you were supposed to do next. there were some technologieswe were researching. some we rolled out,some we rolled back. we're here today to really make surethat people understand where we are pointed moving forwardis to powerapps and flow.
there are some scenarios infopathexcels at, some of offline access, those rich xml documents scenariosyou should continue to use. we've extended infopathsupport three more years. so for infopath, there are nonew versions of infopath. but we are treating a sharepointserver release this year as if there had been from a support perspective. so, you have five more years ofsupport standard, five more years of support extended to take you out to2026 giving you the longest possible runway to liftoff to your nextgeneration biz app solutions.
powerapps itself can do many, many, many more things than were evergonna be possible with infopath as we're gonna show youhere momentarily. i think this is you. >> so we are recommending at thistime that new scenarios that you're creating for your businessapplications should use powerapps. this lets you create mobile-firstforms that can run on your users' phones and moreover youcan use the device capabilities to make sure that youcan use things like gps.
like digital ink and your locationand the camera on the device. so we can take a photo andupload it somewhere and then use that in your data entry. it also lets you easily connectto multiple data sources. if you can go back and watch thevideo of the session that we just finished, you will be able to seehow easy it is to just create all these different data connectionsto different systems and make an app that ties allof those things together. and i will try to show thatoff in the demo in a second.
you can also leverage thingslike azure functions or any other rest endpoint thatis available on the web, where you can use that as a customapi to pull data from very easily. we really want to emphasize thatwe as sharepoint, i'm part of the sharepoint team, and we atsharepoint are really committed to making powerapps and flow a firstclass data source for powerapps. this means making sure that we havesupport for all the sharepoint data types which has attachments,pictures and other sharepoint data types like taxonomy, which is iknow there are many fans of here.
make sure that those work perfectlywell inside powerapp and the flow. and we also are working on enablingthe embedding of powerapps into sharepoint ui so that you can havea powerapp run in a sharepoint list and in the model list that youhave seen across ignite this week. as well as, use it as the forms foryour sharepoint lists. also, let's speak a little bit aboutsharepoint designer and workflows. so just like with infopath,sharepoint designer is also, we did not issue a newversion of it for 2016. but we did extendthe support through 2026.
but we recommend that youstart to use flow for your business app workflow needs. there's a grow-up story, flow willcover the basics of workflows around the same area assharepoint designer. and then there's a developer grow-upstory using logic apps which runs on the same connector infrastructure. so new workflows, you should goahead and create it with flow and then we're hard at work tosupport document libraries, other types of list, as well as thefull range of sharepoint field types
in that area as well. and flow team, i know, they'renot here today presenting, but they have plenty of other sessions,and they're working on further governance capabilities, which isone of the first questions we get from office 365 users and it admins,like, well, how will i govern this? they're working on theirgovernance capabilities and that will be available inthe official release as well. >> so powerapps and floware definitely the successors and kerem's gonna walk youthrough powerapps,
i'm gonna walk you through flow. >> yeah, solet's briefly talk about powerapps. this is a tool that lets you connecteasily to your existing systems and data sources. you can build your app, you can build your forms, you canhave multiple screens in an app. so it's a very familiar ui and very easy to transition betweenthe different screens in your apps. and then you get to publishthese apps for mobile devices,
as well as for web. so your users can use them, either using your browser ontheir desktop or on their phone, or they can actually installthe app on their devices. and then make sure that they'reusing the full capabilities of their devices thatthey're running on. the main point we want to underlinehere is how easy it is to create a fully functioning appwithout writing any codes. the powerapps designer studio isthe thing that lets you do that.
it runs as a windows client, but it can also be invoked throughthe web and runs in a browser. so you can go to any web browser andthen launch the powerapp studio and make adjustments to your app,save it, and then within minutes, all the usersof that app that have been using the older version can startto use the new version. it lets you use drag anddrop ui for editing the app, it lets you use excel-likeexpressions for creating things like conditional formatting andfiltering your results.
so if you have writtenan if statement in excel, then you can easily writea conditional formatting statement that will changethe value of a field. and change a color of a fieldbased on the value that you have. it's easier than writing v lookup,let me tell you. and, you can take advantage ofdevice capabilities, as i mentioned. and you can also connectto various data sources and bring those together in a singleapp as we will see in a second. and then->> [crosstalk] can i get
the clicker?>> here's the clicker. and then you can also publishthe apps instantly for a web or mobile as i mentioned earlier. let's quickly talkabout how it works. at the bottom of this diagram, you have your data andthis can be sharepoint online, as well as it can be sharepoint2016 or 2013 on-premises. and connection to these ispossible through the on-premise's data gateway, which is a freedownload that you can download from
the powerapps site and then installon a machine in your network. and then that will act asthe gateway between the powerapps service that's running in the cloudand youroon-premises data. there's the connection,that is basically the piece that talks betweenpowerapps service and your data. and then you create yourpowerapp in the studio, you save it to powerapps cloud,and then it is available for you in the browser oron your mobile devices. how about flow?
>> so, flow is the closecousin to powerapps. so to build a business app, we want to have a greatinterface experience. we also know that data needs tomove around, things need to happen. and so flow is an automation toolthat lets an individual business user create a beautifulno-code experience around scenarios likebeing able to be alerted. or being able to move files from oneplace to another based on conditions that are out there.
if someone dropsan image off in box and you wanna bring it in tothe office 365 family, you can use a flow to do thatbeing able to organize data. so, if you have something thatlives in dynamic crm or google or something coming out of salesforceand it's been marked as a win and you want to bring that datainto an operations team that's using the powerof office 365 groups. you can do it as well as, one of themost common scenarios we know people have been using designer workflowsfor is approval.
flow and power apps and power biuse a common connector framework. so these are some of the dozens ofconnectors that are made available through powerapps and flow today,whether it's what you would expect. for people who are running office365, e1835, most of the commercially available plans,you're gonna have access to a range of consumer services like facebook,as well as what you would expect, sql, exchange, sharepoint, onedrive,on-premises or in the cloud. and when you build a flow, is we'regonna show you in demo here in just a minute, you don't evenhave to move to the designer.
we ship dozens of templates to takedown the most common scenarios of in context,if i'm working with sharepoint, do i wanna send an email or getan approval or pick information of it's coming from the web andbe able to write it to a list or get an approval ona document in the library? all of these templatesare available. you can browse what's thereat flow.microsoft.com. and if something wehave doesn't work for you, there is a flowdesigner that's available.
it works again. whoa! that would be interesting. a no-code solution that letsme quickly drag in actions and components where i wanna connect to. it shows me the properties of eachstep all the way on down the line. i can build in conditional logic, so if in the fist step i say thesale has to be more than $1,000 or $1 million, i can go downone branch for a large sale, a different branch for a small sale,and be able to do all of this,
again, without needingto write a lick of code. since i haven't written code in tenyears, this is a tool for me as well as for many of you and the businessusers that we all support. so we really see powerapps andflow as being the future of business apps today and tomorrow insharepoint and office 365. i also wanna make a clear comment. we think, in particular thingslike flow are taking over for sharepoint designerscenario as the successor. we also know we have a very richecosystem of partner solutions,
company's like nintex and k2 and agilepoint andlots of people are doing this, we are not intending to get intothose complex enterprise scenarios. if you're gonna investor in nintex,we love that. if you have an investment in k2,etc., we love that. we are trying to orchestratebusiness automation in a quick way to deal with many ofthe classic scenarios. so that said, this is the statementand we wanna make it very clear. we see this now as a successorof these scenarios,
we're very happy withwhat we're able to do, and that's why we want totake a look at modern lists. >> the modern list integrationis merely the beginning of this integration process we havewith powerapps and flow. like i said, we want to make surethat sharepoint is a first class data source for these things. and to prove this concept, we've started the integrationwith modern lists. modern lists is available today forour first release users.
and it has started toroll out the production. so within the month of october,we expect all of our production customers in sharepoint online toreceive the modern list update. but they will not stop there. what we will do is we willcontinue to weave flow and powerapps into otherparts of sharepoint. so document library isthe very logical next step. for your documents,you will be able to create flows, maybe even trigger an actionbased on a selected document.
maybe trigger an approval flow fora selected item and create these custom ui. talking a little bitabout modern list, we really really wanted tomake it very very easy for someone to easily starta flow using a modern list. we will show you ina second in the demo, but its literally one click,well, two clicks i think. if you>> one button. >> one button andthen you click the button and
then you click the other button>> okay. >> anyway, so it's about twoclicks to get to a flow that is fully functional foryou to create something for example like sending you an email when a newitem has been added to the list. we know that was one ofthe top scenarios for using sharepoint designer workflows. so we really wanted to makethat very, very easy and accessible to end userswithout having to figure out, activating the work flow feature andthen going
to the work flow settings, andthen figuring out a bunch of things. we just wanted to make that muchmore accessible for our users. similarly, if you wantto create an app for your list, which kind of doublesas a customized form because that governs how you access andadd information to that list. it is again, very, very easy. you click a button, you say iwant to create an app for this. it will take the list context,start up the powerapp studio, and then create that app for you.
and you can, it is fully functionalas soon as you hit that button. but you can also start to customizeit so that it's your business rules, your business needsare reflected in that app. your corporate brandingcan go in there, your conditional formattingrules can go in there. your filtering rules can go inthere so that you access that data. >> so kareem's gonna walk us througha demo, a fairly typical scenario. we know info path has been used forlots of things. accident reporting.
one of my favorite thingsto do is take a vacation. i actually don't know what they are, but i'm told thatthey're very enjoyable. and people have built infopath forms tied to a list. so kareem's gonna walk usthrough the process on screen of what a vacation request formlooks like when you've taken over. this is a list, the kind of list iwould have built an info path form years ago or even last week, but nowi can use a powerapp to be able to address that data and thatinteraction in that request process.
[crosstalk]>> this doesn't work so, i'll just. >> here, so here we are on the list. >> so, i will gonna use the iphoneto have a fully mobile demo, but my iphone is failingme at the moment. so, what i'm going to do isactually show you things working in the desktop. here we are in the list that i havecreated for my vacation request. and you can seethe powerapp button here which allows me to createan app using one click.
i won't do it at the moment. i will show you the appthat i've created. for details please,go see the 2051 session. and i go into a good 15,20 minutes and ran over time. [crosstalk]>> it was a great 15 or 20 minutes. >> thank you, thank you. so you can see the all the detailsof the steps that i went through to create an app very much likethe one that i'm about to show you. again, also we wanted to make itvery very easy to create the flow.
so here's the flow button and thecreate flow button that i push, and then out comes this panel and itgives me a number of suggestions of ready or ready created flows thatare available for a particular list. so you can easily createa customized email when a new sharepoint listitem has been created. or you can send an approval mailautomatically when this has been created, and so on. so, in a moment, i'm going to showyou the flow that we're using on this list, but first, let's switchover to the powerapp that i have.
this is basically something thatlets me make a vacation request using a customized app. so when you land on this app,you see that you're already seeing the items from that list,that i was just on. it's just formatteda little differently. we can see that i have my companycolors reflected instead of the vanilla blue that,i guess, vanilla's not blue, but you get the point. >> in the right lighting.
>> yeah right, that's right, soyou can see that this has been a customized app that showsme my vacation requests. it has some conditional formattingthat shows the stuff that was approved by my manager in green. things that are pending in blue and then things have been rejected inred so that it's very easy for the user to identifythe status of something. i have built in search andbuilt in sort, and i have my company logo up herewith a customized picture.
let me also point out that inaddition to the conditional formatting, if i clickon one of these items, i will, the icons renderkind of funny there. but i will be able to edit,or delete this item based on, because this is an item that isstill pending approval, so it has been added, but hasn't been approvedyet so i can make changes to it. but whereas if i go to an itemthat was approved by my manager, those buttons don't appear. because based on the data,i can show and
hide the controls that i show on thescreen so you can easily manipulate and change the experience for yourusers based on certain conditions. all right, let's see what thatvacation request might look like. so i click this button, i have mycustomize form that only shows me the relevant pieces ofthat vacation request. so i'm going to type in my theater session 2,number 1 was this morning. and let's say, let's get thatvacation this week of october here. i'm gonna add my start andend dates and then here's some,
i think i already used this joke,i deserve it. the other thing to point out to youis this little piece of information that was below, vacation days left. so all this information up top isgonna go into that sharepoint list. this was basically usingthe scheme of the list and the fields from the list. but that second pieceof information, i wrote a little azure function thatwill return me the number of days that person has on vacation.
so that's the second piece ofinformation that i'm pulling in from another source. so you can see how you can matchup different sources of data in a single app. it's not just your sharepoint data, you can also grab other pieces ofdata using any other data sources, and then bring themtogether in a single list. so i hit my button, and you cansee that my list now has been updated with this theater session,and it's pending approval.
all right, that's great. just to prove that it's not all->> refresh? >> there we are. >> there's our new one. >> our item has beenadded to the list. so what->> we're two minutes over already. >> no.>> yes. >> well, let's talk about theapproval side of this then, quickly. since i don't seeanyone kicking us out.
i will just go overa couple of notes. >> and craig's been working reallyhard, and we need him to get his vacation approved after the weekthat we've been having for ignite. >> that's right. so as you were watching my screen, this approval mailjust popped into view. you can see that it is a request formy input. it is actually goingto another user. it's going to this manager of theperson who was making the request,
and informs them that hewants to go on vacation. all the fields that i have typedin are now present here, and if i hit approve, that approval willget recorded, if my internet works. all right. >> what's funny is if you judgeit from that managers inbox, his entire job seems to besitting around waiting for vacation request to approve. which seems like a neat job. >> that's what they do.
and you can see that this used to bepending approval, and when i refresh my list, you will note that the itemis now approved by manager. so what magic made that happen? let me show you. it's something that looks like this. so you can see thatthere's a trigger here. this has been a flow that wascreated by clicking one of those buttons that you saw on the righthand outside of the screen there. when an item is created for
this list, what i'm going todo is i'm going use the e-mail of the person who created that item,and find their manager. and then, in the next step, i'm gonna take the output ofthat get manager command, and then use it as input to sendthe approval mail to that person. and you will see thatthe details kind of show that all of those different fieldsare appearing from that field. and then, finally,i have a condition here. if the selected option is approved,then i update the item.
i'm grabbing the idea ofthe item that was created, and then using it as input forthe next step here. and i can set that approvalstatus to be approved by manager. otherwise, i can takesome other action. and it's very, very easy for me to go ahead and add anotheraction here to do other things, like update an hr system througha custom api, or any other things. >> so, it's also workingon early days for flow. we're in preview in power appsin flow, going to ga soon.
we're not disclosing the date yet,but it is coming soon. there are many workflow capabilitiesthat we're not covering in flow. if you're looking for advancedvariable and parameter handling and state machines, and looping andconditionalities beyond what we've already shown you,there are other ways of solving it. this is intended tobe a light weight, scalable process automation thatmost users can plug into without it needing a ton of training. >> all right.>> so [crosstalk]
>> and finish it up. do you have the clicker? >> there it is. and just to kinda recapwhat you just saw. you wanna talk us through it? >> we have the power appsrunning on a phone, and then it was requesting data fromthe list, to show their vacation request as well as the custom datasource for the number of days. then we added a new one, and then itwent and updated the list data, and
we had a flow that waswatching the list for changes. when it detected there wasa new vacation request, it sent that approvalmail to the manager. the manager approved. and then it went back and updated that sharepoint listto complete the circle. >> so, we're over time. we're not resting on whatwe are already doing. there's a lot that's coming.
>> support for images, attachments, and multi-value fields, integrationwith document libraries, kicking off flows manually instead of waitingfor this automated request. give me a second andthen let's do the questions after. and then, embedding powerapps insharepoint and using them as forms are some of the things that we'reactively working on at the moment. they're on the roadmap. >> so in conclusion, we know there's an awful lot ofinfopath in many organizations.
i know enterprisesthat have hundreds if not thousands of the forms. two of the resourcesthat are available. first off, we publishguidance as to how to manage infopath moving forward,available at the link here. as well as understanding whenyou convert an infopath process, it's been tied to a sharepoint list,if there is code behind on that infopath page, we're notlooking at it in the conversion. all we're doing isconverting the data.
one of the ways that you can findwhat's out there in your environment is to use the sandbox tool thatwe've released through pnp to help discover info path forms that youhave in your environment, and is there code behind them. we know in many cases thosecode behinds, or samples, or things that are never called orexecuted, so it helps you spotlight the placeswhere there might be something so you can triage it, anddetermine is this still a business critical function orsomething that we can live with and
implement differentlyusing power apps and flow. so other sessions going on,most of these have already wrapped. we have two sessionstomorrow morning. one that i'm delivering on cloud bi. so we're actually starting withpower apps and flow to move to a data warehouse, bring it to powerbi and then back to sharepoint. along with a deeper dive on powerapps from the power apps team. most of this stuff is recorded. let's wrap it up.
yay fasttrack,yay tech community, yay and me. >> [applause]>> thank you. >> thank you very much. and we'll be hanging outhere if you have questions, unless they kick us out thenwe'll be hanging out over there. >> [inaudible] >> so, it will alreadywork with on-premises. so, if you use the data gateway,you can connect to 2013 and 2016 data sources, and havethe flow, execution, the power apps,
work with that data the same waythey work with it in the cloud. >> [inaudible]>> then, no. >> [inaudible]>> that is something that's under design. azure app service takesthe capability on is potentially available, but we have no moreinformation to share about that. in this model, if you sign up forpower apps in flow, the definition and execution lives in the cloudeven if you don't have office 365. so, if you have powerapps and flow,you can run them against on-premises
data sources with nothing butthe powerapps and flow subscription. yes? >> we're this close. >> like, a week? >> no, not like a week. but- >> [laugh] >> we're gonna be making another blog post on futuresin about a month's time. i have to go back to redman andwrite it.
but we expect late october we'llhave more information to share about timing. >> it's- >> it's coming. we know. yes? you're holding your hand up, butif you were just stretching, that's totally okay. it's a long day.>> [inaudible]?
>> yes, yes it->> [inaudible] >> it's handled for you. >> not yet. >> i'm a windows phone guy. so, working on it. >> yeah, i mean the onething i kinda struggle with, just the difference in the split. and i totally get the, why it'sseparated into a platform and everything like that.
but when you go to sharepoint andyou hit a list item or whatever and you still get defaultlistings experience. but then you still havethe customized form editing anything you've experienced throughpowerapps, or whatever, is there anywhere they'll bea notification, be able to say, hey this has got specialized experienceover here, or anything like that? >> yes.>> they'll be able to, cuz it sounds like there's kind oftwo splits of being able to use it. >> that's part of what's coming.
for sure and when we talk about[inaudible] that is the story that we want to build [inaudible]. today, we don't do a great jobof that, i [inaudible] it. but what we're gonna be doing movingforward is make sure that those capabilities are there and you can see the customized onerather the one that [inaudible]. and also make sure that we pointthat the powerapps are available. today, when you create the appfrom starting from a modern list, we actually create a view foryou in modern lists.
that is the handle to that powerapp. soon we will be usingthat more extensively. [crosstalk] right,i think you have a question? >> gonna make that visual to you andstuff. >> is powerapps gonna be availableas an add-in in the app store? >> not as an add-in in the app storeit is more intrinsic capability that's coming in to part of office. so when it releases you willautomatically be able to a, you'll have the license for it and e1, e3,e5, and most commercial tenants.
b, be able to say the same waythat i can say, you get email or you don't. powerapps' flow capability ifyou wanna turn it on and off for selective users you can. if you wanna add it at the app tilesto show it or not show it, you can. but it's not a separate add-in,it's an intrinsic service. >> the download is for yourdevices from the app stores, for your mobile devices->> for that, yes. >> you can also install [inaudible]
>> any other questions? >> [inaudible] about the price? >> so for e1, e3, e5, that versionof powerapps until you get there is the same as what you would get,that's what your paying for, e1, e3, e5 today. >> [crosstalk] charge isincluded in your e1 and e5, [inaudible] therewill be some capabilities that are only available tomore advanced licenses. for example, you talked aboutbeing able to connect to many data
sources, so you will getconnectivity with your office 365 license to offices 365properties plus sql. >> right.right and- >> if you want to connect to, say, sales force, full sap and i'm not fully up to dateon the fullness of the. those may be an extra charge on topof what you believe you can find. >> yeah, a lot of it, the teiringis gonna be driven largely by connectors and also a number ofexecutions of a flow per month
aggregated an intendent, soif you are, we're in atlanta, so if you're delta airlines, and you'rebuilding a vacation request process, it's gonna fire 25 times a day,you're gonna be fine. and then if you say, wow i want todo this, so every time a flight attendant is taking an orderseat-side on the plane. and i'm firing this offthousands of times an hour, you're gonna need to buy additionalcapacity to handle that. but for most business scenarios wethink that the licensing that you're gonna get automatically in office365 is gonna keep most scenarios
covered. yes. >> when you start supportingandroid, windows phones- >> we support android now. >> really? >> yes.>> powerapp? >> yes. >> so,it's designed once [inaudible]? >> yes.>> exactly.
>> one more [inaudible] on flow,you mentioned that the range of what you're gonna support,what is intended to do and proclaim, lightweight like that->> yes. >> are you including like creatingsites permission those kinds of levels of things in that category orthat? [inaudible] the next stepis [inaudible] i know there's a lot of[inaudible] like this, so [inaudible] andthen i suspect sites will come. it's a little furtherdown the list but
documents like this is really->> i'm just kinda wondering what the bar is, how do you definethat bar of lightweight stops. you kinda get a lot of what you dois you're looking up at another lists and your getting look ups and your doing different things thatinteracting with different stuff and copying those items anddoing all that stuff. >> so, let me make it clear. you build a flow, it belongs to you. other people it's attached,it's listening to a list.
if anyone else changes the datain the list flow fires but it belongs to you and you leavethe company, your flow goes away. that's gonna get fixed, i'm not saying, it's an issue,this is early days. how i copy a flow from one user toanother, share it around a group or deal with dev test prod. those are things thatwe're working on. we just haven't released. >> what's the best way forsupport for flow?
cuz i've built like two orthree and they don't work. i get http time out errorswhen connecting to crm. i get blank emails when i put inall the fill in properties from it, i get blank emails. just, is there,just use the community for it? >> yes, sothere's a forum on microsoft.com, there's a community link forsupport link. you can even get an exploration. i get those customer-generatedexplorations,
i look at them, i get back to them. we find bugs when you help us, because [inaudible]->> it's preview. >> but [inaudible] maybe [inaudible]>> sure. >> if that still happens,we're gonna take a look after it. >> maybe available to fetcha flow to [inaudible] >> there was some discussions about that we had. we're also doing some privatedesign sessions with some
focus groups this week. it definitely comes up being ableto use a flow and a content type. so we're thinking about it. and that's really all i could say. >> yeah. >> [laugh]>> i just mentioned list in my head, actually everyone knows,it's like a [inaudible] >> it's like a pieces that we keep you from [inaudible] yourself- and
from other stakeholder that might be [inaudible] justadjusting it to make sure that [inaudible]>> so, let me make this broad point. so, what i got,i used to be cto at quest and dell. when i got to quest i inheriteda software product that was designed to handle emailattachments inside outlook. and it was one of these, quick hit,let's, didn't take a lot of dev time, let's put it out, we'll seeif it takes off in the market. and if it takes off in the marketwe're gonna do more and
in software development, you canreally spot those products a mile away just sort of trial balloons,this is totally got one of those, there's like this a huge arsenalof developers and engineers and architects and managers working onwith a really rich backlog, and roadmap, andthis is a big bet for microsoft. it's a big bet for sharepoint andoffice, and when we say that we're working on it and thinking aboutit and coming, absolutely we're designing it and working on it,and planning to release it. >> yeah, we do want to makesharepoint [inaudible]
>> yep. one more question, we're gonna. let's take more questions. what do you have? >> in terms of flow,powerapps, logic apps, what's the relationshipin the ecosystem? >> so flow and powerapps, they're very close to each other. it's just that flow is more enduser, business user-friendly,
presentation of logic apps. logic apps is the thingthat runs under this, so when you create a flow thatactually underneath the covers, it creates a logic apps foryou and it runs that. logic apps gives you morecapabilities for extending that, it's more developer friendly,you can write some coding issues, studio and like that->> right. >> updates tool. it's a [inaudible] andmore developer-friendly.
flow is then more end-user friendlyrepresentation of logic apps. powerapps similarly is designed forthose power users who are creating these app solutions onthe forums and presentation sites. logic apps and flow more onthe automation sites, one for [inaudible]. power apps is kind ofthe ui that the users and direct [inaudible]>> if you built those data stores out and you really see that you'relooking beyond the frontier of what you can do througha powerapp's interface.
you probably gonna preservethe data stores but start looking at tools like xamarin. there's grow up stories right all ofthese but we're really intending to democratize, lower case d, thesetools so people can pick up on them. that's it? >> so if you wanna customize,can you do it in flow as well or you have to go to logic apps? >> no you can customize the flow. >> all the flows are customizable.
there's several actions that you canjust take and add, all of the flows, if they can be arbitrarily large. writing custom code. >> yeah.>> is not something you can do in the flow.
Tidak ada komentar:
Posting Komentar