IBM BPM Client Side Human Services vs Heritage Human Services

Nearly most of the IBM BPM projects exclusively depends on human services or coaches which leads to many of server performance issues and PMRs. Coaches are the user interfaces for human services. There are two varieties of user interfaces for human services: task completion and stand-alone service. To build either type of user interface for human services, you use coaches. And IBM took a smart move by introducing client side human service which reduces  the server load and pushing everything to client machine and browser. Server moves  forward all coaches in a single call to client browser and it is browser’s duty to load the coaches in organized manner, coach navigation and respond back to server after finishing. Coach performance and interpretation will differ according to end client machine configuration.

Difference Between Heritage Human Services  and Client-Side Human Services :

Using  heritage human services, you use current artifacts, such as coaches, heritage coaches, and stock controls, to generate user interfaces for business process management. You produce and amend heritage human services in the IBM Process Designer desktop editor, execute them on the server, and utilize them to supply user interfaces to web-based applications such as IBM Process Portal.

But When you use client-side human services, you can use web technology to develop human-service performance and supply support for case management and process management. You generate and amend client-side human services in the Process Designer web editor, run them on the client-side in the web browser, and use them to call the server for data when necessary.

Server side human service or Heritage Coaches :

Client and server communication of heritage coach.

Client side human service :

System pushes  all the coaches to client browser, once all coaches are finished and then browser pushes data reverse to server. It diminishes no of server calls and let the high end browser’s to do the job for you.

There are few confines, if you close the browser prior to reaching the end point then you may lose all the data. And we have an option to save the execution context upon each coach completion, but it will increase no of calls to server.

 Combination of Client side and heritage coaches :

Combination with save execution context scenario :