2019-05-16 aOS Luxembourg - 6 - Flow avancé astuces et bonnes pratiques avec Docteur Flow - Serge Luca

1. Flow avancé : astuces et bonnes pratiques avec
Doctor Flow
Serge Luca

2. Office Apps & services MVP
Business Applications MVP
O365 Architect
@sergeluca
ShareQL Brussels
Office365
Flow
Dev
Architecture
Bullshit
Doctor Flow aka “Serge Luca”

3. https://myignite.techcommunity.microsoft.com/sessions/66476

4. Key Questions
Any Flow showstopper ?
Do I need to use a third party tool ?
Robust ?
Very easy ? Expensive ?
Here is our experience after 3 years
and 9 enterprise flow projects…

5. Microsoft
flow and
citizen
developers

6. Demo:
Automatic timesheet

7. Microsoft
flow and
developers

8. Create REST
Services
(like Azure
functions)
Create
Custom
Connectors
Call REST
APIs from
Flow
Integrate
Flow in their
Applications
Developers
Activities
Requires P1Requires P1

9. Demo:
Calling
the Graph API
Requires P1

10. Demo:
Custom Connector
Requires P1

11. Patterns
and
limitations

12. State machine pattern or Controller patternNo State Machine
No custom task
forms
Max 5,000 iterations in Do until –> Create embedded
loops
Max 5,000 iterations in For each (100,000 in Plan 1)
Loops
Create nested flows or raise a ticket250 actions/flow
Flow Approval
duration : 30 days
Flow duration :
30 days
No guest access
Controller pattern
In the roadmap for Flow & PowerApps
ALM/devops
weak
I could tell you, but then I would have to kill you…
Custom approval actions
Cannot resume
flow
In the roadmap

13. Boss validates the final document
Secretary validates style
Advisors validate content
User Publishes a new “legal” document
Why State
Machine ?

14. State Machine and
> 30 days
« Flow Controller
Pattern »
Controller
Launcher flow
SecretaryAdvisor Boss
escalate
timeout
approved
rejected
in vacation
timeout
approved
rejected
redirect
in vacation
timeout
approved
rejected
escalate
Normal flow
Service flow

15. 3 Implementations Messages
(Service
Bus)
Database
(SQL Azure)
Http &
Request
(Requires
P1 license !)
Requires P1

16. Demo:
Approval escalation
Approval analytics
Controller pattern
Machine Learning

18. Started from
Excel
Started from SP
New Expense
from App
Trigger : Excel for a
selected row
Trigger :
SharePoint for a
selected row
Existing Expense
from App
Trigger :
SharePoint : when an item is
created
Proxy Flows
Service Flow

19. Requires P1

20. • the url might change, we want to use a stable vanity url like
https://flowdemo.azure-api.net
• you might need to protect it : authentication
• throttling
• restricting the callers to some specific network locations
• ….

21. Returns max
2048 records

22. Returns max
5000 records
or 100.000 if
P1 licence
$skiptoken=Page=TRUE%26p_ID=3000&top=5000

23. Demo:
Manage errors

24. Demo:
Manage parallelism

25. Adapt retry policy
Reduce flow concurrency
Use several connectors
Error HTTP 429 : « I’m too busy » come later (in 10 sec)
Flow throttled by the Service (like SharePoint) and by
the Connector (600 calls/min)

26. 202 ACCEPTED
The request has been accepted for
processing, but the processing has not been
completed.
Long Call Duration
Pattern
Requires P1

27. Demo:
Manage Long calls

28. Office 365
audit log
Webhook
1
2

29. Microsoft
flow and
PowerBI

30. FLOW
DATA ALERTS
DATA SOURCES
POWER BI
SCHEDULED REFRESH
STREAMING DATA
LIVE
POWERQUERY
Requires P1
Data On premises
REFRESH DATASET (april 2019)

31. Conclusions

32. Conclusions
You can, but it will be much much more expensive
Do I need to use a third party tool ?
Is it robust enough for enterprise business processes ?
Is Flow is very easy to use and not expensive (Office 365 license)
Easy : Yes but it sometimes requires “advanced” skills
Cheaper than anything else but be careful with P1
Very robust engine (Logic Apps) – we’ve tested it on thousands of
flows 24x24x365
Reliability depends on the connector and on your architecture
Error handling and Flow monitoring
Start with Flow in a first place, your prototype might survive

33. Conclusions
I ALWAYS define UML Use Cases
I often define UML Activity Diagrams
I often define RACI matrices (Responsibility assignments)

34. Merci à notre sponsor !