Instructions needed - "Importing external data" for Cases
Hello there,
We have a requirement of migrating our legacy system data from Lotus Notes to Pega Case management application development in progress. I am looking for guide or instructions for Data Import for cases specially how to take care of assignments, stages and steps in case lifecycle.
PEGA Documentation: https://docs-previous.pega.com/data-management-and-integration/87/importing-data-file
This only talks about 'Data' type migration from external system. I need help if migration can be done for cases considering following:
- Data type doesn't have unexposed columns, Case's properties can be unexposed.
- Will it work different stage and step setup in case lifecycle? If yes, how?
- How about assignment for inflight cases?
Please help us with instruction document for case type migration from external system. Thanks!
NCS Pte. Ltd
SG
Hi @Pankaj_C: I don't think there is a defined process for this type of migration (migrating legacy system to PEGA and create cases) because it purely depends on the business logic. You can create your own Job schedulers / Data flows / ETL logics / API to migrate the data and create case.
Thanks.
Updated: 20 Dec 2022 6:36 EST
Pegasystems Inc.
GB
@Pankaj_C I can see that you opened support ticket SR-124432 for this.
I believe that they already responded to you with the following information:
Unfortunately there don't appear to be any documents that have instructions on how to import cases from Lotus Notes into a Pega application.
At a high level, you would need to design a case type (or case types) including the steps and stages for the cases you'll be importing. You can create utilities for taking the data from the existing non-pega application and create cases which are then populated with that data. The specifics about how to do this would presumably depend upon the application design.
Assistance with designing such a utliity is outside the scope of work supported by our Global Client Support team. If you would rather have direct consulting assistance from Pega Consulting on your question, reaching out to your Account Executive is the best way to raise this request.
We can wait for other forum users to see if anyone can pitch in with suggestions here.
.
Navy Federal Credit Union
US
@MarijeSchillern Thanks for your response! Have we consulted the Pega-platform team responsible for 'Importing Exeternal data' wizard? I have seen a demo earlier from PegaAccel team doing import for cases before but with earlier version. Would love to see documented approach, because need to share this with our partners.
Thanks, Pankaj Chopra
Red Alpha, LLC
US
@Pankaj_CI've been able to import "cases" from a legacy system into a Pega application using the Import function (Import Wizard) on the Records tab of the Data Designer view of a Work class item (case type). There is significant data mapping effort involved prior to the import to map data from the legacy system into the proper case type properties, as well as Pega built-in fields (pyStatusWork, pxCreateOpName, etc). But importing via this process has shown success for me, especially when needing the data there for reporting purposes. I am not sure about assignments for in-flight cases. In our system, we had a clear delineation of all legacy cases being in a resolved state in the source/legacy system before export/import into Pega.