In PEGA PRPC for a work object is it required the underlying mapped work table to have PZINSKEY to be mandatory Primary key on table? Due to some oracle table partitioning limitations DBAs are asking if we can have it (PZINSKEY column on worktable) as “Unique Key” instead of Primary key. And still all the OOTB step methods obj-* function as it is?
I have completed the discussion with DataEngineConsulting team.
Having pzInsKey be the primary key is pretty fundamental to PegaRULES.
It's quite possible that most operations would work fine.But it's possible that certain more advanced functionality (such as those related to schema changes) might not work. It's also possible that upgrades would run into difficulties, or that in future versions of PegaRULES something could go wrong.
We can't recommend this considering the above risk, but you could try "at your own risk." If this is something which you thinks is very important, then please describe the use case and we will see what best we can do.