BPMN in Pegasystems PRPC Flow Rules

BPMN in PegasystemsPRPC Flow Rulesby Declan Chellar@AnalysisFu

Pega BPMN: the perceptionThere is a perception that Pegasystems PRPC can be used to create BPMN-compliant process models.** This slide deck is relevant up to PRPC version 6.2.2What the Pega Developers Network saysBPMN stencil By selecting a BPMN Visio stencil, you can create flow diagrams that closely match the appearance and notation used in Business Process Management Notation (BPMN) diagrams.** http://pdn.pega.com/Devnet/Announcements/Announce61/process.asp3What the Pega Developers Network saysBPMN stencil By selecting a BPMN Visio stencil, you can create flow diagrams that closely match the appearance and notation used in Business Process Management Notation (BPMN) diagrams.** http://pdn.pega.com/Devnet/Announcements/Announce61/process.aspNotice the words closely match.This is not the same as saying that Pegas BPMN stencil is BPMN-compliant.4What the Pega Developers Network saysBPMN stencil By selecting a BPMN Visio stencil, you can create flow diagrams that closely match the appearance and notation used in Business Process Management Notation (BPMN) diagrams.** http://pdn.pega.com/Devnet/Announcements/Announce61/process.aspNotice the words closely match.This is not the same as saying that Pegas BPMN stencil is BPMN-compliant.CAVEAT:Pega does not claim that Pega BPMN Flow Rules are BPMN-complaint.

5A sub-process expressed using BPMNThe next slide contains an example of a sub-process modelled using BPMN.This sub-process Review Leave Request is part of a higher-level workflow for handling leave requests.That workflow consists of three sub-processes:Request LeaveReview Leave RequestReview Rejected Leave Request.The level of modelling on this diagram calls out all the logical steps that need to take place in order to review a leave request.Details such as data requirements and business rules do not appear on the diagram, although steps where business rules get invoked are indicated.This is an example of a sub-process modelled using BPMN.This sub-process Review Leave Request is part of a higher-level workflow for handling leave requests.That workflow consists of three sub-processes: Request Leave, Review Leave Request and Review Rejected Leave Request.The level of modelling on this diagram calls out all the logical steps that need to take place in order to review a leave request.Details such as data requirements and business rules do not appear on the diagram, although steps where business rules are invoked are indicated.

6A sub-process expressed using BPMN

7The sub-process as implemented by a Flow Rule

Here we see how an initial draft of the PRPC Flow Rule for Review Leave Request might look.

This diagram shows Pega Standard shapes.8The same Flow Rule in Pegas version of BPMN

And here we see how the initial draft of the PRPC Flow Rule might look using Pegas version of BPMN shapes.This slide shows how the initial draft of the PRPC Flow Rule might look using Pegas version of BPMN shapes.9Compare the levels of visible detail

Compare the levels of visible detailBoth are supposed to be BPMN models of the sub-process

Compare the levels of visible detailPega Developers Network says: BPMN stencil By selecting a BPMN Visio stencil, you can create flow diagrams that closely match the appearance and notation used in Business Process Management Notation (BPMN) diagrams.

12Compare the levels of visible detailBPMN is a standard modelling notation maintained by the Object Management Group.

13Compare the levels of visible detailA BPMN modelling tool is either BPMN-compliant or it is not. Closely matching is not compliance.

14Compare the levels of visible detailMoreover, the diagram on the right does not closely match the one on the left.

15Compare the levels of visible detailBPMN-trained business stakeholders would understand the diagram on the left, but would be confused by the lack of BPMN-compliance in the Flow Rule on the right.

16Compare the levels of visible detailIt would be better to show business stakeholders a Pega Standard Flow Rule and get them used to the Pega Standard notation.

17Pega BPMN is just a way of re-decorating Flow Rules

The Pega Standard notation is on the left and Pega BPMN on the right.All Pega does is re-paint its Flow Rule shapes to look like BPMN shapes.This is not the same as BPMN-compliance.

18Pega BPMN is just a way of re-decorating Flow Rules

All Pega does is re-paint its Flow Rule shapes to look like BPMN shapes.This is not the same as BPMN-compliance.

19Pega BPMN is just a way of re-decorating Flow Rules

This is not the same as BPMN-compliance.20Pega BPMN is just a way of re-decorating Flow Rules

PRPC Flow Rules implement the business process and as design/implementation devices, they do not make all the necessary business steps explicit on the Flow.21Much of the logical detail is not explicit in the Flow Rule

This slide highlights business process steps which are unlikely to be explicit on the Flow Rule, even though they are handled by Rules behind the Flow.22Compare the levels of visible detailFrom a business stakeholder perspective , the Flow diagram does not fully represent the business process.

23Compare the levels of visible detailHowever, a Flow Rule is not meant to illustrate the business process, rather its implementation.

24Compare the levels of visible detailBut you should not try to use your Flow Rule to express something which it cannot.

25Pega BPMN is not BPMN compliant

This slide introduces the argument that Pegas version of BPMN is actually not BPMN at all.26

Pega BPMN is not BPMN compliantThe Integration shape that Pega uses on the BPMN view of the Flow is not part of the BPMN palette.27

Pega BPMN is not BPMN compliantIn BPMN diamond shapes are known as Gateways and serve only as visual aids in navigating the diagram. No processing takes place inside a Gateway.28

Pega BPMN is not BPMN compliantInstead, in BPMN, business rules are invoked and executed inside a task shape.29

Pega BPMN is not BPMN compliantIn PRPCs version of BPMN, there is behaviour going on inside diamond shapes, which breaks the rules of BPMN.30

Pega BPMN is not BPMN compliantAlthough it is correct from a PRPC perspective to hide process details behind Flow Rule shapes, from a BPMN perspective, this is not correct.31Further limitations to Pega BPMNPega BPMN cannot and should not include manual steps. BPMN can and should.Pega BPMN cannot and should not include steps and sub-processes executed in non PRPC systems. BPMN can and should.Pega BPMN cannot and should not include steps and sub-processes which are out of scope for the current software implementation. BPMN can and should.BPMN is technology-agnostic; Pega BPMN is technology-specific.This slide lists limitations to Pega BPMN which are allowed in BPMN.32ConclusionThe Pega BPMN stencil is not a tool for creating BPMN models within PRPC.It is a way of viewing PRPC Flow Rules using shapes reminiscent of BPMN.Pega BPMN is not BPMN-compliant.This non-compliance is likely to confuse stakeholders who are BPMN-trained.Better to get stakeholders used to Pega Standard Flow Rules.This slide lists limitations to Pega BPMN which are allowed in BPMN.33ConclusionIn golf, no matter how good your 3-iron is, you cant turn it into an 8-iron by scratching on the number.

This slide lists limitations to Pega BPMN which are allowed in BPMN.34www.chellar.com/AnalysisFu