Overview MSBizApps & MPP - Cork PBI UG
•Download as PPTX, PDF•
0 likes•101 views
This document provides an overview of Microsoft Business Applications and the Microsoft Power Platform presented by Clifton C. Lenne. It defines PowerApps and Microsoft Flow, explaining their uses and licensing. PowerApps is described as a low-code application development platform for citizen and professional developers to build apps of varying sophistication levels from simple forms to business critical solutions. Microsoft Flow is for automating workflows and processes by connecting services using triggers and actions. The document outlines the basic building blocks needed to start with examples and emphasizes following best practices, governance, and obtaining management backing.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Overview MSBizApps & MPP - Cork PBI UG
Similar to Overview MSBizApps & MPP - Cork PBI UG (20)
Recently uploaded
Recently uploaded (20)
Overview MSBizApps & MPP - Cork PBI UG
- 1. Cork Power BI User Group 15 Mei 2019 Clifton C. Lenne Overview Microsoft Business Applications and the Microsoft Power Platform
- 2. Clifton C. LenneMicrosoft Business Applications Solutions Specialist “Start Small, Think Big(ger)” E-mail: cclenne@yait-c.net Twitter: https://twitter/cclenne || #ThePAAdict LinkedIn: https://be.linkedin.com/in/cliftonclenne Blog: https://www.yait-c.net Functional Solution Consultant at Ordina www.ordina.be
- 8. What about every other need you and your business faces?
- 11. Definition What is PowerApps and why do we use it?
- 12. Low Code Application Development Platform tailored towards: • Citizen Developers (IT Pro, Business Analyst, Office Worker) • Professional Developers
- 13. Sophistication Levels From Simple Forms To Business Critical Solutions
- 14. Advanced LOB apps Mission critical LOB apps Horizontal, end-to-end apps Embedded forms C I T I Z E N D E V E L O P E R S P R O F E S S I O N A L D E V E L O P E R S Simple LOB apps
- 17. Building Blocks What do I need to start building an App?
- 18. License Browser Service Common Sense & Management Backing
- 19. Requirements Analysis Building Blocks • PowerApps License • Already assigned as part of Office 365 Subscription
- 20. PowerApps Licensing Advanced Features Basic Features Advanced Features for Personal Use
- 21. Consume Apps: Dynamics 365Manage Apps: PowerApps Office 365 Portal: https://www.office.com
- 22. PowerApps Portal • Create Apps • Manage Apps created by you (Edit, Update, Share, Delete) • Edit Apps shared with you (Only if Edit Permissions assigned)
- 23. Dynamics 365 Portal • Run Apps created by you • Run Apps created and shared by colleagues • Run Apps created and shared by your Internal IT department • Run Apps purchased at Third Parties
- 24. Requirements Analysis Building Blocks • Browser • Google Chrome • Opera • Microsoft Edge • Any Chrome based browser * No Internet Explorer or FireFox!
- 26. Requirements Analysis Building Blocks • Service: • Excel • OneDrive • SharePoint • Dynamics • Twitter • Azure Storage Table • Regular File Share • … and many more
- 27. May 2019: > 230 services Every month: Avg. +5 Connector not available? Create your own!
- 28. Start from Blank Start from Template May 2019 > 30 Templates
- 29. Requirements Analysis Building Blocks • Common Sense • Logical Thinking • Conceptual Excel Knowledge • Best Practice Guidelines • Basic Office Skills • Theming • Visualization Sense • Drag and Drop
- 30. PowerApps Canvas App Coding Standards and Guidelines https://powerapps.microsoft.com/en-us/blog/powerapps-canvas-app-coding- standards-and-guidelines/ PowerApps Canvas App Accessibility Guidelines https://powerapps.microsoft.com/en-us/blog/powerapps-canvas-app-accessibility- guidelines/ PowerApps and Microsoft Flow Governance and Deployment https://powerapps.microsoft.com/en-us/blog/powerapps-enterprise-deployment- whitepaper/ Power Platform Security & Governance: Deploying a Defense in Depth Strategy https://flow.microsoft.com/en-us/blog/security-governance-strategy/
- 31. Requirements Analysis Building Blocks • Management Backing • IT Policies • Culture • Mindshift • Business Case
- 32. Demo: Real World PowerApps Example
- 33. Definition What is Microsoft Flow and why do we use it?
- 34. Why? Why do we use Microsoft Flow?
- 37. Types of Flows
- 38. e.g. Instantaneously generate word document, convert to PDF and mail to recipients e.g. When a new item is added to list generate word document, convert to PDF and mail to recipients e.g. On every Wednesday generate word document, convert to PDF and mail to recipients e.g Gather information in specific order in Tender Process
- 39. May 2019: > 230 services Every month: Avg. +5 Connector not available? Create your own!
- 40. Start from Blank Start from Template June 2019 > 300 Templates
- 41. Microsoft Flow Licensing Advanced Features Basic Features
- 42. Demo: Real World Flow Example
- 43. Demo: Real World Power Platform Example
- 44. Key Takeaways By default everyone can create Apps & Flows Apps & Flows can be embedded in SharePoint, Teams, Power BI, Office and Dynamics 365 Applications Embedding natively into Windows alongside traditional Applications in the pipeline. Scenario decides sophistication level of the App & Flow. Uphold KISS principle at all times! PowerApps & Flow tailored towards Citizen Developers and Professional Developers Follow Best Practice Guidelines GOVERNANCE Management Backing!
- 45. Q & A
Editor's Notes
- Good afternoon everyone, Once again welcome at the inaugural edition of the Cork Power BI User Group. I’m quite honoured to be here today, and I would like to thank Jan, Mark and the User Group for having me today. In my presentation I will provide an overview of the Microsoft Business Applications Solutions Ecosystem and the position and role of the Microsoft Power Platform in this ecosystem So, hopefully after this presentation you have a better grasp of the Microsoft Power Platform and in extension the Microsoft Business Applications Solutions Ecosystem as a whole. (CLICK)
- Who am I, I am Clifton. I’m a Microsoft Business Applications Solutions Specialist, employed at Ordina as a Functional Solution Consultant. My daily work consists of assisting customers in maximizing the full capabilities of the Microsoft Power Platform. (CLICK)
- Let’s talk Data. Or better said: let’s talk about how we can make Data work better for us. And with “us” I mean the non-IT Pro: it’s about Jake the Accountant, Sarah the Secretary, and Dave the Business Analyst! (CLICK)
- As more organisations are digitizing their operations, the amount of Data grows exponentially. More Data means more opportunities, if done right! The Microsoft Cloud uses this Data as the foundation to support the 4 pillars of Digital Transformation. : It enables us to better engage with our customers She establishes opportunities to optimize Operations And we can rather quickly Transform our Services and Products All of this results in more productive employees This framework is known as the Digital Feedback Loop, and is the foundation of the Microsoft Business Applications Solutions Ecosystem. (CLICK)
- The Microsoft Cloud encompasses 3 components: Microsoft 365 Microsoft Dynamics 365 Microsoft Azure Let’s take an up-close look (CLICK)
- Here you see a detailed version of the three components from a BASE standpoint: Let’s take a closer look at these sub-components: Dynamics 365 is the integrated CRM/ERP solutions for organisations and business of all sizes. Office 365. This one doesn’t need an introduction LinkedIn, also doesn’t need an introduction Azure, the foundation of BASE, delivers more than 600 Services. Common Data Service is the central repository to store al kinds of data by using standard and custom entities based on the Common Data Model. CDS is built on top of Azure Data lake Gen 2, and can be positioned as the component to enable diverse systems and applications to share information with each other. So, one of the main benefits of CDS is the ability to integrate modern and legacy solutions, thereby resulting in an enormous costs benefit . No more months figuring out how to get “that solution to work with that system” And that’s how we arrive at the Power Platform. (CLICK)
- The Microsoft Power Platform consists of 3 components: Power BI for the Analyses and Visualisation of Data PowerApps for data entry Microsoft Flow to automate all kinds of tasks and processes And now the big question why do we use the Power Platform? (CLICK)
- Many organizations do not have the resources to develop custom solutions (KLIK) On the other hand commercial-of-the-shelf solutions aren’t always covering the unique needs (KLIK) And this is where the Microsoft Power Platform comes in: she enables us to deliver solutions, with a minimal set of resources, to fill the gaps. (KLIK)
- The Microsoft Power Platform, is know as an Application Platform as a Service, and is positioned as the Extensibility Framework, the so called glue between the Microsoft Cloud ecosystems.
- Lets take a look at an example of a company who maximized the full capability of the Microsoft Power Platform (Show Film) -> (Click)
- What is PowerApps and why do we use it?
- With PowerApps both Professional and Non-Professional Developers can relatively easily build all kinds of Apps with diverse sophistication levels. (KLIK)
- Talking about sophistication levels, let’s take a look! (KLIK)
- As stated earlier PowerApps Solutions can be quite diverse. From Simple Forms to End-2-End Business Critical Solutions In most cases the Citizen Developer, if willing, can build Embedded Forms, Simple Apps and Advanced Apps without too much of a hassle (KLIK) Mission Critical Apps and Horizontal en-2-end Apps are best left for the Professional Developers. As in these scenario’s quite often integration with systems which are not supported OOTB will be necessary. And that requires Pro Dev or at least Advanced IT knowledge. You can’t expect Sarah the Accountant to build an App which takes into account all the technical and functional aspects as expected in the case of an Enterprise Solution. (KLIK)
- When we build Apps we can make two types of Apps Canvas Apps Model Driven Apps (KLIK)
- In Canvas Apps we start by building the User Interface, adding controls, building the forms and finish by connecting to the Data source. (CLICK) In Model Driven Apps we start by building the Data Model. So, we define and customize the entities, build the Business Rules and other types of Automation and we finish by defining the UI layout. (CLICK)
- What do you actually need to start building an App? (KLIK)
- In fact you need 4 elements PowerApps License Recommended Browser Service To Connect or Integrate with Common Sense (KLIK)
- If I’m correct most of you already have a PowerApps License trough your Office 365 subscription. (KLIK)
- Although I won’t get too deep into the topic of licensing, because of the complexity, keep in mind that generally taken PowerApps knows three license types: (CLICK) First you have the ones included with your Office 365 and Dynamics 365 Subscription. This license provides you with the basic features to build Canvas Apps only. (CLICK) Then you have the P1 and P2 plans. These plans enable you to make use of CDS, Business Process Flows, Custom -and Premium connectors and other Premium features. (CLICK) And last but not least every user can enable his or her own Sandbox environment, which offers the same capability as the P1 and P2 plans, with One Major exception: you cannot share solutions with others. This environment is for personal use only. So, think of it as your own personal playground. In this environment you can freely explore preview features, try out capabilities etc..etc.. without impacting your Production Environment. Also keep in mind that all PowerApps licenses include Flow use rights as well. (CLICK)
- Once logged in, PowerApps is accessible via several menus, as depicted here. The Creator Portal simply know as PowerApps The Dynamics 365 Portal (KLIK)
- We use the PowerApps Portal to manage Apps. So, you go into this portal only when you need to build, modify, delete and share or unshare Apps (KLIK)
- Consumers of Apps access these via the Dynamics 365 Portal. These Apps can be official organizational Apps, Apps from colleagues or Apps from Third Parties So please, do not make the mistake to redirect your users to the PowerApps Portal when in fact they actually only need to Consume Apps. Believe it or not, but the bulk of the business users will not have a reason (or the motivation) to build their own Apps. When it comes to Flow, that’s an other story…. (KLIK)
- Browser compatibility. This is an important one! Any browser based on a Chrome Engine is good (KLIK)
- So, use Opera, use Chrome, Use Edge.. Anyone played with the Edge Chrome Edition Yet…? Well, I have and I have to say: It Love It! It feels like a marriage between Microsoft and Google. (KLIK)
- Before building your App you should know the kind of data you want to retrieve So, you need to ask yourself: Where is the Data allocated? What are the integration options of the Data within my App? What can I do with the Data: Read-Only or Read-Write? These are just some of the questions. (KLIK)
- As of now there are 230 services with which you can integrate OOTB. An average of 5 services are added each month. If the intended connector is not included, you can create custom connector. Which by the way, as stated earlier, requires at least a P1 License. If its is intended only for use in Microsoft Flow you’ll need a F2 license. More on that later. (KLIK)
- In PowerApps you can start from a blank template (CLICK) Or from a pre-build template At this moment there are about 30+ templates, which can be used as a starting point. For advanced features you will need to build your own Solution or customize an OOTB template to fit your specific needs. (CLICK)
- If there is one advise I can give, than it is Keep It Smart and Simple Do not make Applications unnecessarily complex. (KLIK)
- I have listed some useful links. Lookup these links to read up on recommended –and best practices. Here you can find information such as: Best practices regarding UI and UX design Security Administration Governance Guidelines (KLIK)
- This is an important one: You will not be able to make any useful progress if you do not have the backing of your Management. The Microsoft Power Platform is an Agile Data Driven Platform, thus requires an environment in which there is no place for outdated IT polices. This Platform enables the so called “Democratization of IT”. Thus requires a Cultural Change, a Mindshift. But this platform also has a dark site. Because of its flexibility, ill prepared organizations experience a chaotic emergence of all kinds of applications, Flows and Solutions. So please be sure to implement an adequate Governance Framework. Actually every Team -or Organization centric App or Solution needs a profound Business Case. If you don’t do that, you are literally building the foundation for Organized Chaos. I’m sure none of you wants to clean up the mess afterward…. (KLIK)
- So let’s look at some Real-World PowerApps Examples! PAUZE => DEMO TIME (KLIK)
- Now that we have a basic grasp of PowerApps, let’s Flow a little bit.
- So, why do we use Flow? We use flow to automate al kinds of tasks an processes. (KLIK)
- Let’s take for example a typical Onboarding process. Several tasks come into account: We need to notify his Manager Maybe we need to send a request to Operations to setup the new employee’s Desk and other peripherals At the same time we need to send a Welcome Email to the new colleague We also need to send an Work Order to Fleet Management to prepare the colleagues’ Lease Car Or when we look at graphically…. (CLICK)
- Flow is perfectly capable of automating these tasks, which in many organisations, believe or not I still being done manually. Optionally we can Visualise the result in Power BI. So in other words: PowerApps to fill in all kinds of forms, which Flow accepts as Input to automate these tasks. And the end result is a happy employee. The manager is also happy, as he can see the end result visualised in a Power BI report or dashboard. In other words, the Microsoft Power Platform in Full Swing! (CLICK)
- Microsoft Flow has several types of triggers (KLIK)
- Instant Flows also known as ‘On Demand’ Flows are executed instantaneously. These can be triggered form Excel, or by using Virtual or Physical buttons. (CLICK) Automated Flows. These are executed when a certain condition is fulfilled. For example send an email when stock reaches under 1000 pieces. Or push a row of data to a Dataset when a New Order is received. (CLICK) Use Scheduled Flows when u want to…..uhmm… Schedule your Flows. For example generate an Security Scan Report every Wednesday and mail this report to the Security Manager. (CLICK) And then you have Business Process Flows. We use these when we need to execute a set of tasks in a predefined order. For this feature, we require a P2 license however. Also I will not show you this one today, as this is a quite extensive topic. (CLICK)
- Just as is the case with PowerApps Flow offers more than 230 Out-Of-The-Box connectors. In fact these are the same connectors used by PowerApps. (CLICK)
- In Flow you can also start from a blank Template (CLICK) of from a Pre-Build Template. As of now there are more then 300 Templates. And just as is the case with PowerApps, you can use these as Starter Templates, or customize them to fit your specific needs. (CLICK)
- Flow Licensing follows a similar structure as PowerApps Licensing (CLICK) First you have the ones included with your Office 365 and Dynamics 365 Subscription. Jus as the PowerApps license, this license provides you with the all the basic features. (CLICK) Then you have the F1 and F2 plans. These plans enable you to make use of CDS, Business Process Flows, Custom -and Premium connectors and other Premium features. You guessed it, just as PowerApps. Flow does not have a dedicated Sandbox Offering. Sign up to the PowerApps Community Plan to experiment with Microsoft Flow’s features. Except of the Community Plan, Flow licenses do not offer PowerApps Capabilities. So, if there is a need for PowerApps capabilities you need to acquire a P1, P2, Office 365 or Dynamics 365 license. You also have the Free version of Microsoft Flow. Anyone can sign up to the Free version. But keep in mind that the Free version is quite limited in features. So, use this one only to create a reminder that you need to feed de dog and the cat, and buy another set of diapers for your new born, and to generate an alert that today it is your turn to prepare dinner. (CLICK)
- Ok. Enough talk. Let’s look at an example! PAUZE => DEMO TIME (KLIK)
- Now that we have a grasp of PowerApps and Flow, lets take a look at an example which makes use of all the Power Platform capabilities. PAUZE => DEMO TIME (KLIK)
- The Key Takeaways. (KLIK) By default everyone can build Apps and Flows. (KLIK) Apps & Flows can be integrated with SharePoint, Teams, Power BI, Dynamics, Office. And if I’m correct in the future natively into Windows. We’ll need to wait and see what Microsoft has in store for us. Because this part is still somewhat vague to me. (KLIK) Keep It Smart and Simple. You don’t want to Clean up the mess. (KLIK) Power Platform tailored toward Pros and Non-Pros. The situation’s requirements will decide sophistication level. (KLIK) Last but not least…… follow Best Practice Guidelines at all times, implement an adequate Governance Policy before starting with a companywide roll-out. And Management Backing is probably the most important. Without their backing your endeavor will surely fail. (KLIK)