Use case about how jBPM was used at SNS Bank

1. Full Scale STP with jBPM Use case about jBPM at SNS Bank Eric D. Schabell RedHat, Solution Architect Maurice de Château SNS IT, System Specialist (Java) jBPM Community Day – May 8th, Antwerp, Belgium

3. Current STP Products

4. How does jBPM fit in?

5. 'Legacy' tooling and way of working

6. Current improvements

7. Future directions

9. Origin in savings banks

10. Aims mainly at private individuals and small and medium-sized businesses

11. Financial conglomerate with REAAL Insurances since 1997

12. Several sublabels (ASN, BLG, ZwitserLeven)

14. 5 clicks to purchase new products (2010)

15. Central focus: customer experience

16. Transparent, quick and simple

17. Effective and efficient, eliminating handwork

18. Paperless (as much as legally possible)

20. Current STP Products

21. How does jBPM fit in?

22. 'Legacy' tooling and way of working

23. Current improvements

24. Future directions

26. Deposit accounts ( Depositosparen (interest per year or per month), Klimrente, Varivast, Rendementsparen )

27. Service processes ( among others Change of address, Change of contra account, Temporary increase of debit card limit, and many more to follow... )

29. Current STP Products

30. How does jBPM fit in?

31. 'Legacy' tooling and way of working

32. Current improvements

33. Future directions

34. Simplified System Overview jBPM Community Day – May 8th, Antwerp, Belgium . . . . . . Customer Administrator DB

36. No integrated rules engine

37. Some (prominent) back ends don't support transactionality/asynchronicity/events

38. And...

40. Current STP Products

41. How does jBPM fit in?

42. 'Legacy' tooling and way of working

43. Current improvements

44. Future directions

45. Tooling jBPM Community Day – May 8th, Antwerp, Belgium

46. Tooling jBPM Community Day – May 8th, Antwerp, Belgium

48. Decision

51. jBPM Community Day – May 8th, Antwerp, Belgium

52. Funny (?) Code Example (1) jBPM Community Day – May 8th, Antwerp, Belgium public class BackendExceptionHandler implements ActionHandler { public void execute(ExecutionContext context) throws Exception { Token token = context.getProcessInstance().getRootToken(); String originatingNode = token.getNode().getName(); if (!BackendExceptionHandler.BACKENDERROR_REDIRECTING_NODE.equals(originatingNode)) { ExecutionContextHelper.setVariable(context, BACKENDERROR_DROPOUT_NODE, token.getNode().getName()); } token.setNode(context.getProcessDefinition().getNode(BACKENDERROR_NODE_NAME)); token.signal(); throw new Exception("Functional error on back end."); } }

53. Funny (?) Code Example (2) jBPM Community Day – May 8th, Antwerp, Belgium public class SaveProcessInstanceHandler implements ActionHandler { public void execute(ExecutionContext context) throws Exception { context.getJbpmContext().getConnection().setAutoCommit( false ); context.getJbpmContext().getConnection().commit(); context.getJbpmContext().getConnection().setAutoCommit( true ); // Do something with context and changes will be saved, this call results // in an empty list Remark: not every call to context will result in a DB update. // This one does... context.getJbpmContext().getTaskList(); [further processing...] } }

55. Current STP Products

56. How does jBPM fit in?

57. 'Legacy' tooling and way of working

58. Current improvements

59. Future directions

62. Allows for the use of proper state nodes

64. Current STP Products

65. How does jBPM fit in?

66. 'Legacy' tooling and way of working

67. Current improvements

68. Future directions

70. Implementing multi-process solutions

71. Removal of the legacy tooling

72. Upgrade to jBPM 3.2.x

73. Proper use of swimlanes and the possibilities of tasks in the jBPM console

74. Questions? jBPM Community Day – May 8th, Antwerp, Belgium