BPM Patterns & Best Practices with OutSystems BPT
Download as PPTX, PDF5 likes5,871 views
The document presents best practices and patterns for utilizing the OutSystems agile platform for business process technologies (BPT). It emphasizes strategies for process design, user guidance, and effective deployment, along with advanced patterns for process intercommunication and activity management. Key recommendations include simplification, using sub-processes, and leveraging automation while ensuring a close relationship between processes and data/UI.
BPM Patterns & Best Practices with OutSystems BPT
- 1. OutSystems Agile PlatformBPT Patterns & Best PracticesGonçalo Borrêga - OutSystems
- 3. BPT vs. Rest of the World
- 7. MindsetBackgroundClaims processing process708 Activities501 Decisions>4.000.000 instances (>1.800.000 human)Processes thatlastfrom 2 minutes to 2 yearsRefactoringproject
- 8. MindsetBackground – One of the “old” processes
- 9. MindsetGround rulesKnow your processAnalyze earlyDesign deepTop down approachParallelize manual activitiesGuideyourusers
- 10. MindsetGround rulesAim for simplicityShow it to yourusers
- 13. But…
- 14. AvoidrefactoringThe things you really should take advantageBPT vs. Rest of the World
- 15. BPT vs. Rest of the WorldThe things you really should take advantageImpactanalysisProcess upgrades ARE possiblePlandeploymentwisely
- 16. BPT vs. Rest of the WorldThe things you really should take advantageTheprocessisclose to the dataNo data dictionariesTrueChangeTM built inAmazing event model
- 17. BPT vs. Rest of the WorldThe things you really should take advantageTheprocessisclose to the UISynchronous closing and validationUI iseasilycontrolledfromtheprocessUI caneasilyreflecttheprocess
- 18. Smallsteps for you, bigsteps for your processesSimple techniques
- 19. Simple techniquesSmall steps for you, big steps for your processesEmpowersub processesForkandJoinUse input parameters to refine behaviourUse ouputparameters to controlparentbehaviourDo notforgetreporting
- 20. Simple techniquesSmall steps for you, big steps for your processesSmartlabelingHierarchicalIncrementalRelational
- 21. Simple techniquesSmall steps for you, big steps for your processesCycles?Sure, whentheybelong to theprocessNever as procedurallogic
- 22. Simple techniquesSmall steps for you, big steps for your processesRun again… with no impactImplementautomaticactivitiesconsideringtheywillberunseveraltimesDesign theprocesssoitcanbe “restarted”
- 23. Use and extend the modelAdvanced patterns
- 24. Advanced patterns Use and extend the modelProcessintercommunicationDatabase/EventbasedDecouplefromprocessspecificactions“Statemachine”
- 25. Advanced patterns Use and extend the modelStatesDatabaseflag-based statusAllowseasyreportingEasyprocesslockers
- 26. Advanced patterns Use and extend the modelBPT awareapplicationSingleentrypointsSession.ActivityIdEveryactionwithanactivity
- 27. Advanced patterns Use and extend the modelCustominboxesContextualTaskorientedCustompriorities
- 28. Advanced patterns Use and extend the model – Custom inboxes
- 29. Advanced patterns Use and extend the model – Custom inboxes
- 30. Advanced patterns Use and extend the modelConditionalstartsSupportsadhoc processesAuto launchhiddenby UI
- 31. Advanced patterns Use and extend the model – Conditional start
- 32. Advanced patterns Use and extend the modelActivityExtensionEntitiesActivityId as identifierPurgeifrequiredonClose/SkipExtend BPT modelForeignsystemseventsComments
- 33. Advanced patterns Use and extend the modelActivityBehaviourStaticentitywithbehavioursCreateentryonOpen (bound to user)PurgeonClose/SkipControl UICheckBehaviour(Entities.BEHAVIOUR.AcceptReject)
- 34. Advanced patterns Use and extend the modelMetamodelExtensionEntitiesActivityDefinitionId as identifierIf no recordexistsonOnCreate, createentryWhenchangeisfrequent use SS_Keyandallow BackOffice configuration
- 35. Advanced patternsUse and extend the modelTemplatesGatheryourrequirementsCreate Template processesUse processgenericcallbacksUserassignment, SLAs, Groupassignment
- 37. Thankyou for yourattention and contribution!
Editor's Notes
- #14: Demo: Claim Process -> Damage report
- #16: Demo: Cycle vsCycleOk
- #17: Demo: Claim process -> If liability determinedCycle Sub ->OrderLineStatus
- #19: Demo: Damage report -> Perform assessment -> Wait
- #25: Demo: Cancel claim; Cancel damage report -> Check on Wait
- #26: Demo: Cancel claim; Cancel damage report -> Check on Wait
- #27: Demo: Add a wait for WebService and a Comments structure
- #28: Demo: Screen controlled via behaviour
- #29: Demo: Custom SLA
- #30: Demo: show the template process