Question

2
Replies
1050
Views
JoseB422 Member since 2016 1 post
Banco Colpatria
Posted: October 22, 2018
Last activity: November 5, 2018
Closed

Pega API [POST] is creating a case even if there was an error in the transaction

Pega API 7.2 is being used to create cases and sometimes the response is an error, however, case gets created. This behaviour is causing duplicated cases from the business side since when the error is returned, the external system recalls. Pega is deployed in a cluster and what we have noticed is that this error only occurs in cluster.

Error returned is: Pega_API_014: .pyCommitError: ** ** ORA-00001: unique constraint (DATAADM.PC_HISTORY_CCC_NN_YY_WORK_PK) violated

Is there any mechanism to avoid creating the case when an error is returned?

***Edited by Moderator: Pallavi to update platform capability tags***

Case Management
Moderation Team has archived post
Share this page LinkedIn