Using Coach Views and SPARK for Seamless Client-Side Human Service Migration

With the introduction of IBM BPM V8.5.5, user interfaces within BPMS web-based applications can be built using both heritage human services and client-side human services. A great article explaining the differences between client-side and heritage human services can be found on the IBM Knowledge center here. A large advantage to using a client-side human service is to provide a thin client user experience to only make calls to the server when necessary. The SPARK toolkit is also built with the thin client architecture in mind by providing asynchronous server side interaction using coach controls like the Service Call and Service Data Table. Migrating from the heritage human services to client-side human services can be made easy through a combination of coach views and SPARK. 

How to Use Coach Views in Migration

To migrate coaches from heritage human services to client-side human services without the use of coach views a developer would need to rebuild the entire coach in the web editor. Such an approach would be redundant and unnecessary. Instead the developer can utilize the re-usable and decoupling characteristics of coach views to accomplish the same thing.  

Create coach views of coach sections to provide reusable interfaces


Provide Configuration Options or Business Data of the business objects needed within the coach view

Drag and drop the coach view into a coach within a heritage human service or a client-side human service

Traditionally, at this point a developer would need to initialize the employee information data outside of the coach within a server script in heritage human services or a client-side script in client-side human services. This data would then be bound to the coach view to be displayed to the end user. With SPARK all data initialization can be done asynchronously within the coach view so no predetermined data needs to be known. 

How to use SPARK in Migration

To use SPARK within the coach view so only the data object variable needs to passed in, a developer needs to make use of the Service Call control. The Service Call control is a control that uses Ajax server calls within the client to return results from the server asynchronously to the coach when needed. To learn more about the Service Call control see our article here. In the following example, a Service Call control will be used to return employee information based on the selection they choose in the drop-down. 

Drag and Drop a Service Call into the coach view and bind the business data/configuration option variable to it

The Ajax service that is called when a selection happens can be found in the behavior option within the configuration tab

The Ajax service will be able to retrieve all data that will be needed with the coach view when executed (which can be done automatically or explicitly our case it's done explicitly in the Single Select onChange() event. Data can also be retrieved from a database in the Ajax service to provide SOR integration.

By binding the variable within the coaches of the heritage and client-side human services to the coach view the coach can retrieve data dynamically without the use of server or client-side scripts, making the human services simpler and cleaner. 


  • Author: Elliot Pytosky
  • Date Created: October 30, 2015
  • Date Modified: October 30, 2015
Was this article helpful?
0 out of 0 found this helpful