ECS19 - Dragan Panjkov - Connecting Enterprise Software With Flow
0 likes239 views
This document discusses how PowerApps, Microsoft Flow, and the Common Data Service work together to connect apps and data. It explains that PowerApps allows users to build apps that connect to various data sources through the Common Data Service. Microsoft Flow can then be used to automate workflows and integrate apps. The document provides examples of how custom connectors in Flow can integrate with third party systems like K2 to enable monitoring and processing workflows.
ECS19 - Dragan Panjkov - Connecting Enterprise Software With Flow
- 3. ♡ ♡
- 6. Data connectors Dynamics 365 Office 365 Mobile apps Web apps Common Data Service PowerAppsPower BI Flow
- 7. A is a wrapper around an API that allows the underlying service to talk to , and
- 8. Quickly generate and customize apps based on Excel files, SharePoint Online lists, Dynamics 365, Salesforce records and more. You can even connect custom APIs. Even connecting to data in your local systems through the common on premises data gateway. Your apps will be able to fully interact with underlying sources and will respect the permissions you’ve already established in them. Your product here!
- 36. On-premises data sources On-premises data gateway One gateway for multiple cloud services and experiences Files, SharePointSQL Server SQL Server Analysis Services Other data sources Cloud services PowerApps Microsoft FlowPower BI Azure Service Bus Application Gateway Data source connection credentials can only be decrypted by the gateway Gateway Cloud Service Data source connection credentials are encrypted Read access, scheduled refresh, live connection Live connection, CRUD support (create, read, update and delete) Azure Logic Apps
- 44. $$ $$
- 46. Flow custom connector portal Dev machine CLI PowerApps/Flow RP Code repository Flow custom connector portal PowerApps/Flow RP Development using portal Development using portal and CLI paconn login paconn download paconn create paconn update paconn validate (coming)
- 53. K2 AND FLOW SCENARIO 1 - CUSTOMER FEEDBACK Monitor and Process Flow – Trigger – Flow Template - Monitor twitter for #tags - Sentiment Analysis scoring - Translation - Start K2 for management K2 – Process – Customer Enquiry and Customer Complaint SmartStarters - Classification of request - Management, Action and Tracking and Reporting Flow - Monitor Customer Complaint Management Customer Enquiry K2 - Process
- 54. FLOW DESIGN
- 56. K2 AND FLOW SCENARIO 2 – CONTRACT MANAGEMENT Monitor and Process Flow – Trigger – Flow Template - Monitor Gmail for contracts - Extract Email Content - Start K2 for management K2 – Process – Contract Management - Classification of request - Manage contract creation, approvals (internal and external users (vendors) - Integrate with DocuSign for digital document signing Flow - Monitor Contact Management K2 - Process Digital Signatures
- 57. FLOW DESIGN – MONITOR EMAIL INBOX
- 58. K2 BUSINESS PROCESS – CLASSIFY AND ALLOCATE REQUEST
- 59. K2 BUSINESS PROCESS – CONTRACTS MANAGEMENT