How Coaches of 8.0 are different from Coaches of previous versions ?

Coach in IBM BPM 8.0 is a improvement of Coach in previous versions which is now called as heritage coach. A concept of Coach view is introduced in 8.0, which makes it possible to reuse parts of coaches in different Human Services. A coach can consits of one or more Coach Views. Another Big difference in Coach of 8.0 is introduciton of client-side model to coaches to apply Web2.0 appearance and behaviour. The Coach has data on the client, which is available to all of the Coach Views. That is, fields in different Coach Views that are bound to the same data object update without requiring a full-page refresh.

Instead of the one-button mechanism of Heritage Coaches, Coach Views use named boundary events. Programmers use boundary events for actions such as data updates with the server and transitions to other Coaches or services. For example, a Coach can have multiple buttons. In the human service diagram, you can wire each button to a different event. Any Coach View can declare and fire a boundary event. You are not limited to using only buttons to do so although, of the stock controls, only the button stock control can fire a boundary event. Furthermore, the programming for Coach Views consists entirely of client-side JavaScript. There is no need for server-side JavaScript.

Coaches support collaboration while Heritage Coaches do not. More than one person can work on the
same Coach instance at the same time in their own browsers. For example, with collaboration, users can call on colleagues to help them complete a Coach instance. These users see which controls their colleagues are editing and the values that they are setting in those controls. Collaboration is available only if the service flow uses Coaches for its user interface. If the service flow contains one or more Heritage Coaches, collaboration is not available.

In IBM BPM, services use Coaches and Heritage Coaches for the user interface. A service flow can mix Coaches and Heritage Coaches so that one type can flow into the other. However, a Coach cannot contain Heritage Coach elements and Heritage Coaches cannot contain Coach Views. That is, a user interface must be a Coach or Heritage Coach and not a mix of the two.

The control ID of a view-based Coach is different from the control ID of a Heritage Coach. The control ID of a Heritage Coach is the div node ID. This is not the case in view-based Coaches because Coach Views are reusable and you can have multiple views in a Coach. In view-based Coaches, the control ID is the value of the data-viewid attribute of a <div></div> tag. By using the data-viewid attribute, View developers can locate the nested View because data-viewid is unique within its parent or enclosing view.


  1. Hi Pradeep.. Just a small correction... as per documentation on IBM site, heritage coaches support collaboration while as per your blog, coaches support collaboration... I am shring link below

  2. Hi Saloni, Thanks for taking time to inform me about this. But the link that you provided is listing differences between Heritage human services and client side human services but not Heritage coaches and coaches. This article is about Heritage coaches and coaches and what is mentioned in this article still holds good. Just for your information, this is a very old article and refers to BPM v8.0 where the concept of client side human service concept does not exist.