There is an external service which runs at every 2 hours but when the service is down even after that whatever case details the user is saving that should be there in the service-how to do that
here is an external service which runs at every 2 hours but when the service is down even after that whatever case details the user is saving that should be there in the service-how to do that
For running the external service at every 2 hours we can have a JS but how to map the data entered by the user in it?As per the situation the user can enter data anytime even when the service is down
Accepted Solution
Updated: 14 Jun 2024 3:55 EDT
Eclatprime Digital Private Limited
IN
I don't think there is any OOTB rule Present here , in this case we need to play with queue processor logic of pega . Like when you go for delayed item queue it makes entry in DB table and then send the record for processing once system is Up
So let suppose you are trying to trigger your service from Activity , You will use error handling inside that activity for No response like to find service is down or not , If that service is down make a entry into Different database table (Like queue processor do it for delayed items). As you will make different entry write down one more step to execute that table when service would be up. So by this logic we can easily achieve the result Make an entry inside different table and then at last process records of those table via same service. It depend which error logic you will use let suppose error is 200 so you can use that as message and play with that error code and make a condition over activity step to save the record while error code comes and then process record if error code vanish or went away. Thanks | Somil
OCBC
SG
Have to include exception handling when service is down should make an entry into DB Table. Once the service is up should make a service call to update case details from entries in DB table to external service. Similar to how pega maintains the entries in Delayed queue when kafka is down.
Cognizant
IN
@Priyanka_Konda could please add some links for reference or any more details to this.Like in which DB it will make entry and what error handling approach to configure like connection problem or anything else ?
Accepted Solution
Updated: 14 Jun 2024 3:55 EDT
Eclatprime Digital Private Limited
IN
I don't think there is any OOTB rule Present here , in this case we need to play with queue processor logic of pega . Like when you go for delayed item queue it makes entry in DB table and then send the record for processing once system is Up
So let suppose you are trying to trigger your service from Activity , You will use error handling inside that activity for No response like to find service is down or not , If that service is down make a entry into Different database table (Like queue processor do it for delayed items). As you will make different entry write down one more step to execute that table when service would be up. So by this logic we can easily achieve the result Make an entry inside different table and then at last process records of those table via same service. It depend which error logic you will use let suppose error is 200 so you can use that as message and play with that error code and make a condition over activity step to save the record while error code comes and then process record if error code vanish or went away. Thanks | Somil