There isn't a clear migration path from non-pega platform workflow tools into our applications. I would recommend you look at your legacy workflows and find the deltas between them and the out of the box Pega Customer Service application. Then, I'd customize the out of the box application to meet those needs. If your legacy workflows are not something that is going to be replaced by Customer Service, then I'd say that you probably want the applications to integrate with your CS application. Without knowing what integration options your existing apps have, it's hard to say exactly how best to do that, but the Pega Platform does offer a number of ways to pass data back and forth with third party applications.
Thanks for your response and suggesting one of the possible solution.
Probably you are correct - there is not a clear migration path.However I would like to know and try all the possible solutions.Please let me know if somebody has achieved the same in past and what approach is/was used - that would be a great help.
Posted: 6 years ago
Posted: 16 Sep 2015 14:08 EDT
Mike Townsend (MikeTownsend_GCS)
Director, Technical Support, Customer Service
Without knowing anything about the 3rd party legacy workflows, what they do, what their communications capabilities are, etc, it's hard to say. We've definitely had many customers rewrite their legacy applications on the Pega Platform with lots of success. Depending on the scale, that could be a complex project. We also regularly connect with various 3rd party systems and share data/drive work forward. The Pega Platform can work well as the glue that holds a patchwork of legacy systems together, but how it communicates to them is largely up to them and your specific business needs. If these legacy applications are home grown Java or .Net systems you'll probably need to talk to the development teams to see what access you have to their data and what sort of messaging they support for driving workflow. If they are products from some other company, you will want to review their documentation for the same. You might be able to get away with connecting directly to their databases or use SOAP or MQ or something else for messaging. I wish I could be more specific but at the moment there are still too many unknowns for me to provide anything concrete.
Posted: 6 years ago
Posted: 16 Sep 2015 14:48 EDT
Phani Sahukaru (sahup1)
Architect - Financial Services