There is an external system from where we have to fetch records and create cases now how to handle the error like suppose if the case couldnt be created then how will we know that the case wasnt created for that particular record?
I presume the external system would be interacting with pega system through an api call or trying to create a case via an email. Keeping these in mind you can design something like at the end of the api call completion based on status of case creation, you can just send an email correspondence with case id or respective identifier for the case in the external system if it is an email case creation. If it is just an api call send a success / failure / some other response based on the implementation.
@Anantha Nag K The case creation is happening through an api call so how to send send a success / failure here?
Basically its a API call and integeration is getting involved so you can utilise the intergeration error handling given by pega . Like we can use the log messages inside activities while getting case data and creating case against that case data .
In case you are not caling activity then error handling tempelate might be useful with Datapage of error handling “Pxdatapagehaserror” . OOTB rules only you can utilise to find case got created or not .
- While using activity after the data fetch step you can keep a error handling step to handle exception and put a log message in case of failure and success for that step.
@Somil Shukla
Yes since it involves an app call like Somil mentioned you can send appropriate response using the service call. If that’s not an option as part service call if the service consumer can send an email address then you can send email at the end of app call completion.