[Mike Fitzmaurice] Oddly enough, too many workflow solutions treat the process itself as an afterthought. Data and user interfaces are important, but when designing a process-based solution, the process should dictate what data you need and what your users need to see/do. Data-centric and process-centric apps each have their places, but their rules are different; this session will spell them out in terms of user interfaces, integration, compliance, and more. This is advice you can use whether you’re using Flow, SharePoint Designer, WebCon, K2, or Nintex.
13. If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
14. If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
15. If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
16. If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
If (x and y) then
do this
do that
End if
If (user is Bob) then
do this and that and the other thing
undo that
End if
If (x and y) then
do this
do that
End if
101. Rough taxonomy
Automations
• Triggered sets of
action
• Flow of data
• Focus:
move+transform
• Execute and exit
Workflows
• Sets of tasks
• Assign and wait
• Focus:
assign+wait+act
• Coordinate and
report
• Could be long-
lived
• Non-linear logic
Business Processes
• Sets of assets to
accomplish a goal
• Multiple workflows
• Multiple animations
• Cross-boundary
• Metric-intensive