Question
JP Morgan Chase
IN
Last activity: 1 Jul 2024 7:31 EDT
We have one issue. Same case we can see item created audit trail twice and performed by is different user. Case ID is unique, how an existing case ID is assigned while creating new case
a user created a case and proceeded the case. So in the case history we can see item created.
After few days we can see the case history has another Item created and performed by different user and all the case data added by previous user is overriden. This implies that pega assigned existing case ID for another case creation. Is it possible in pega to reuse same case ID by pega while creating case?
***Edited by Moderator Marije to add Support INC-B23117***
Accepted Solution
Updated: 1 Jul 2024 7:31 EDT
Pegasystems Inc.
GB
@AkshayKadam I can see that you logged INC-B23117 (PRPC is using existing case ID while using is creating new case)
------------------------------
Ticket Analysis/Summary:
The work around used by client : getdatauniqueid() will work fine, but performance wise very slow, so requested client that we have to investigate the issue, but can't proceed with investigation as client is unable provide logs from the day when the issue has occurred and unable reproduce the issue in their lower environment.
We have not identified the root of the issue to give prevention steps, but client should not modify pc_data_uniqueid table to resolve the issue related to getuniqueid().
Our engineering team informed you that the api getDataUniqueId will work perfectly and that is the robust solution but Pega recommends to use getUniqueId api since it is faster.
If you have questions about this update or about the case in general, please add a note to the case.
----------------------------------------------------------------------
If the issue is resolved, please update this PSC question and mark with 'Accept Solution'.
Pegasystems Inc.
GB
@AkshayKadam it is not possible for Pega to reuse the same case ID while creating a new case. Each case in Pega has a unique ID. The issue you're experiencing might be due to a configuration error or a system glitch. It's recommended to investigate the issue further with the help of Pega Support.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
User doesn't see same item ID's in case manager as another user
PEGA generated work-objet ID skipping sequence number. Any idea?
Accepted Solution
Updated: 1 Jul 2024 7:31 EDT
Pegasystems Inc.
GB
@AkshayKadam I can see that you logged INC-B23117 (PRPC is using existing case ID while using is creating new case)
------------------------------
Ticket Analysis/Summary:
The work around used by client : getdatauniqueid() will work fine, but performance wise very slow, so requested client that we have to investigate the issue, but can't proceed with investigation as client is unable provide logs from the day when the issue has occurred and unable reproduce the issue in their lower environment.
We have not identified the root of the issue to give prevention steps, but client should not modify pc_data_uniqueid table to resolve the issue related to getuniqueid().
Our engineering team informed you that the api getDataUniqueId will work perfectly and that is the robust solution but Pega recommends to use getUniqueId api since it is faster.
If you have questions about this update or about the case in general, please add a note to the case.
----------------------------------------------------------------------
If the issue is resolved, please update this PSC question and mark with 'Accept Solution'.