Question
Bradesco Seguros
BR
Last activity: 18 Dec 2023 20:16 EST
Pulse - Error to Post - pc_work_social primary key violation
We identified a problem in our flow, where, in the last few days, it has not been possible to create or finalize our cases, as we are identifying an error in using the pulse ootb shape.
In our process, which in the attached document, I include evidence of how it is configured, when entering the case, it calls pulse through the ootb shape, to be able to post a message from the requester
The big point is that when he tries to create the message in pulse, we are receiving the following message:
ORA-00001: exclusive constraint (PC_WORK_SOCIAL_PK) - Violated
From what we assessed, when we use the ootb shape to generate a message on the pulse, it triggers an OOTB Internal and final pzPostSocial activity
and that generates a pyID case identifier to be able to handle each message, to be able to associate it with the case that is making the case post. (Class PegaSocial-Message)
What actions should we take to avoid this type of problem? Are there any internal control rules that we should re-evaluate?
Accepted Solution
Updated: 18 Dec 2023 20:16 EST
Bradesco Seguros
BR
I identified the root cause of the problem. As Pulse generates an identifier (pyid) for each post - for some reason, when they migrated from Pega 7.2.2 to version 8.6.x, they restarted the numbering of cases and with that Pulse when it is running - when activated , it triggers the GenerateID activity which ends up generating the same number that already exists in the table. Therefore, we will need to customize this id management, monitoring what the system is generating, comparing whether the value already exists and determining logic to define which case number to consider.
EvonSys
LK
Hi @GuiValino1984,
This incremental pyid is stored intance of class Data-UniqueID as property pyLastReservedID with condition set pyPrefix = <your prefix of pyID>. For these combination will return only one row and pyLastReservedID will have the last used number in it. If you override this number it will getting an error as PK violation.
Updated: 15 Dec 2023 15:32 EST
Bradesco Seguros
BR
One point I checked was that in the PDC it indicated a notification mechanism that was turned off and then immediately indicated a key violation.
Evidence attached.
Accepted Solution
Updated: 18 Dec 2023 20:16 EST
Bradesco Seguros
BR
I identified the root cause of the problem. As Pulse generates an identifier (pyid) for each post - for some reason, when they migrated from Pega 7.2.2 to version 8.6.x, they restarted the numbering of cases and with that Pulse when it is running - when activated , it triggers the GenerateID activity which ends up generating the same number that already exists in the table. Therefore, we will need to customize this id management, monitoring what the system is generating, comparing whether the value already exists and determining logic to define which case number to consider.