Power Apps and Microsoft Flow for Business Users
Power. Apps and Microsoft Flow for Business Users ADIS JUGO, DIRECTOR PRODUCT TECHNOLOGY AT SKYBOW MICROSOFT MVP OFFICE SERVERS AND SERVICES MICROSOFT MVP OFFICE DEVELOPMENT Businesssolutions on Microsoft Share. Point skybow accelerates, standardizes and simplifies!
Adis Jugo § Director of Product Technology at skybow § Microsoft MVP Office Development § Office Servers and Services § http: //adisjugo. com § Twitter @adisjugo §
Why Power. Apps and Flow? Time Resources Price Data Maintenance
Why Power. Apps and Flow?
W h a t
Power. Apps background § § § Extension of Project Sienna Cloud-based apps for range of mobile devices and browsers Authentication through Azure Active Directory Built in connectors for some popular data sources Extensibility through custom managed APIs (Azure Functions, Azure API Apps…) and Microsoft Azure
Microsoft Flow § § § Workflows and task automation Data connections, connected services Actions Conditions Loops
What can I build with Power. Apps? § Apps based on data (Share. Point*, SQL, but also Drop. Box and Google Drive) § Onedimensional, form-based apps § Simple, single-task apps § Microphone, camera, GPS coordinates. Ink and pen support. § Multiple data sources in one app § Multiple screens
What it isn’t? § Info. Path replacement. It is a successor, not a replacement. Limited functionalities § List forms § Microsoft stated there will be no 1: 1 parity § § Share. Point-specific product Limited Share. Point support § Will get better § § Free
So, how does it work? Power. Apps basics
High-level architecture Saa. S apps mobile enterprise services tablet business systems browser
Data Sources and connections Power. Apps basics
Power. Apps, Flow and Connections
Data sources? Saa. S data sources • Excel on One. Drive • Excel on Dropbox • Excel on Google Drive • Office 365 • Share. Point Online lists • Google Sheets • Salesforce • Dynamics CRM
Demo 1 Power. Apps basics with Share. Point Online
Environments
Microsoft Common Data Model 19
Common Data Model 20 Secure Business database, comprising of standard business entities § Encrypted at rest. Built for scale –Service Fabric and elastic SQL. § Standard entities, Custom entities § Issues § No management capabilities § Multitenant databases Future § Some kind of Office 365 integration § 3 rd Party ISV Apps
Demo 2 Common Data Model
On Premises Data Gateway 22
And Flow? Microsoft Flow basics with demo
Microsoft Flow § Simple, data-driven actions, conditions and loops § Start from Power. Apps, by another services/events, or schedule § No write-back to Power. Apps
Security / Permissions AAD § Internal sharing § External users – still no info § Anonymous use – still no info §
Extensibility Overcoming Power. Apps and Flow limits
Expressions Actions and Conditions { C# } Azure API App, Azure Function Azure Service Bus
For your developers: Extending Power. Apps and Flow § http: //www. adisjugo. com § Adding custom data sources to Power. Apps and Flow § Extending Power. Apps language through Azure API Apps § Extending Power. Apps and Flow with Azure Functions § Exchanging data from Power. Apps and Flow with 3 rd party system using Azure Service Bus § Using Azure API Apps to create custom Flow Actions § …
Management, operations and governance
Managing Power. Apps & Flows § Limited management capabilities Basic export and import capability (”Save as”) § Automatised deployments are missing § No Power. Apps or Flows versioning § § Limited data and security governance capabilities through Environments § Limited authentication and sharing story § Rogue data sources along the enterprise-ready data sources § Custom entities throufgh Common Data Model No governance § No management § Multitennant SQL Azure §
Wrap. Up § Loosely coupled forms and flow engine. § NOT the Info. Path replacement you were waiting for, some scenarios covered (take a look at skybow Rich Forms – www. skybow. com) § Mixed enterprise and consumer oriented data sources, manage wisely § Limited expression language in Power. Apps § Extensibility options still pretty limited / undefined § Limited Share. Point support
WARNING 32 § Power. Apps are published as a Minimum Viable Product: things are changing. Prepare for change, and make your plans flexible. § First prove that feature you require is supported by Power. Apps, or is at least on the roadmap, to avoid dead-ends. § Don’t overpromise. Remember your lessons from Info. Path. § You might end up deploying hacks as workarounds
Info. Path replacement choice list 33 Power. Apps skybow Rich Forms +/- + Integrated security (no additional security layer, or unauthorized data sources should be allowed) - + 3 Powerful UI designer - + 4 Master-detail relations, and managing multiple lists and libraries inside a form - + 5 Field behaviors, calculation, validation + + 6 Code Behind (for complex calculations and from behaviors) - + 7 Acting on data changes +/- + 8 Custom form controls and actions (adding custom buttons with actions, and form loading actions) + + 9 Forms Business Logic – executing business logic within the forms 10 Easy deployment # Feature 1 Share. Point native (no 3 rd party technology has to be installed on the clients) 2 -/+ + +
THANK YOU QUESTIONS? Businesssolutions on Microsoft Share. Point skybow accelerates, standardizes and simplifies!
- Slides: 34