If Primary Key is changed how to move the existing cases?
in my opinion, that’s not recommended and not supported directly in Pega.
-
pzInsKey / pxInsNameis referenced across multiple tables (work, history, assignments, indexes, links, etc.) -
Changing it will break referential integrity and can corrupt data
If it’s absolutely mandatory:
-
It has to be done as a full data migration (offline approach)
-
You would need to update:
-
Work tables
-
Assignments
-
History tables
-
Index tables
-
Any exposed references / external systems
-
-
Typically done using DB scripts or ETL tools, not from Pega rules
Safer alternative (recommended):
-
Keep old cases as-is
-
Introduce a new business key and handle mapping
you could use alternative key? it will mean you can move to the new key for new records but still keep the primary key on the class?
I have no done this but in the Constellation world I commonly see this configuration underutilised.
