BPM Patterns & Best Practices with OutSystems BPT

www.outsystems.com © 2010outsystems – all rights reserved

OutSystems Agile Platform

BPT Patterns & Best Practices

Gonçalo Borrêga - OutSystems


Agenda

•Mindset

•BPT vs. Rest of the World

•Simple techniques

•Advanced patterns

•Q&A


Background & Ground Rules

Mindset


MindsetBackground

Claims processing process• 708 Activities• 501 Decisions• >4.000.000

instances (>1.800.000 human)

• Processes that last from 2 minutes to 2 years

• Refactoring project


MindsetBackground – One of the “old” processes


MindsetGround rules

Know your process• Analyze early• Design deep• Top down

approach• Parallelize manual

activities• Guide your users


MindsetGround rules

Aim for simplicity• Show it to your

users• Use sub-processes• Consider

versioning• But…• Avoid refactoring


The things you really should take advantage

BPT vs. Rest of the World


BPT vs. Rest of the WorldThe things you really should take advantage

Impact analysis• Process upgrades

ARE possible• Plan deployment

wisely



The process is close to the data

• No data dictionaries

• TrueChangeTM built in

• Amazing event model



The process is close to the UI• Synchronous

closing and validation

• UI is easily controlled from the process

• UI can easily reflect the process


Small steps for you, big steps for your processes

Simple techniques


Simple techniquesSmall steps for you, big steps for your processes

Empower sub processes• Fork and Join• Use input

parameters to refine behaviour

• Use ouput parameters to control parent behaviour

• Do not forget reporting



Smart labeling• Hierarchical• Incremental• Relational



Cycles?• Sure, when they

belong to the process

• Never as procedural logic



Run again… with no impact• Implement

automatic activities considering they will be run several times

• Design the process so it can be “restarted”


Use and extend the model

Advanced patterns


Advanced patterns Use and extend the model

Process intercommunication

• Database/Event based

• Decouple from process specific actions

• “State machine”



States• Database flag-

based status• Allows easy

reporting• Easy process

lockers



BPT aware application• Single entry points• Session.ActivityId• Every action with

an activity



Custom inboxes• Contextual• Task oriented • Custom priorities


Advanced patterns Use and extend the model – Custom inboxes



Conditional starts• Supports ad hoc

processes• Auto launch

hidden by UI


Advanced patterns Use and extend the model – Conditional start



Activity Extension Entities• ActivityId as

identifier• Purge if required

on Close/Skip• Extend BPT model

– Foreign systems events

– Comments



Activity Behaviour• Static entity with

behaviours• Create entry on

Open (bound to user)

• Purge on Close/Skip

• Control UI• CheckBehaviour(

Entities.BEHAVIOUR.AcceptReject)



Metamodel Extension Entities

• ActivityDefinitionId as identifier

• If no record exists on OnCreate, create entry

• When change is frequent use SS_Key and allow BackOffice configuration


Advanced patternsUse and extend the model

Templates

• Gather your requirements

• Create Template processes

• Use process generic callbacks– User assignment,

SLAs, Group assignment


Questions?

[email protected]


Thank you for your attention and contribution!

BPM Patterns & Best Practices with OutSystems BPT

Technology

Transcript of BPM Patterns & Best Practices with OutSystems BPT