Meet Ken:Ken joined Pega way back in 1997 and has worked all over the product, though mostly in the areas of Case Management and Process Engine. Today he’s working on the next generation of product APIs which will facilitate componentization of the rules space.
Message from Ken:Hello! I am looking forward to answering all your questions around best practices for rules development, including how to properly componentize your rules and create APIs for your features, even without further product enhancements.
We implemented Pega about four years ago. We have about 10 different applications across our organization. We have recently begun implementing Pega Customer Service for a new application. We are finding that many of the legacy work types and controls will be needed in the Customer Service portal.
We are really interested to know how best to provide access to the legacy tools without agents needing to switch apps (in essence creating swivel-chair approaches within Pega itself).
Rebuilding all of the legacy functionality in Pega Customer Service would be very costly at this point. Unfortunately much of the legacy work was created in implementation layers. So my question is: would it be effective to create an API integration between Pega CS and our legacy applications in order provide the seamless experience our agents need? Can we retrofit Pega API on the legacy apps? Any rules of the road or potential pitfalls with this approach?
Posted: 5 years ago
Posted: 13 Jun 2017 13:52 EDT
Ken Marin (MARIK)
Fellow, Software Architect, Case Runtime