Close popover
Joshua Guo (JoshuaG2)
The Bank of Nova Scotia

The Bank of Nova Scotia
JoshuaG2 Member since 2018 1 post
The Bank of Nova Scotia
Posted: January 16, 2019
Last activity: February 7, 2019

Case table separation | Update assignment keys in DB

Class xxx-Work <-- Is Classgroup, mapped to Table T1
Class xxx-Work-AA <-- belongs to above Classgroup
Class xxx-Work-BB <-- belongs to above Classgroup

Current we have an application in production with hundreds of in-flight cases mapping to each of the classes above Work-AA and Work-BB. The management want to decouple the 2 case types AA and BB, since they belong to different stakeholders now (there are some project history, but what's done is done).

In order to decouple the case tables at DB level:
1) I've asked the DBA to create new table T2 based on same definition as T1 above.
2) Updated class Work-BB to "is a classgroup", and created class group rule for Work-BB
3) Created DB-Admin-Table instance to map Work-BB class to new table T2

What I did above worked well for newly created cases. But I'm running into issue for in-flight cases. It seems there is a mismatch between
Assignment pxRefObjectKey and Case pzInsKey. I anticipated this of couse, so I also asked the DBA to update the following fields to make sure they reflect xxx-Work-BB (new table) instead of xxx-Work (old table).

Case Table T1:

pzInsKey, pxInsName, pxRefObjectKey

But after the DBA run the query I don't see the new values reflected in the assign_worklist table when I view the instance from Pega. I don't know why this is.
Also, what do you think of my approach?

***Edited by Moderator Marissa to update SR Details***

Enterprise Application Development Dev/Designer Studio Data Integration Support Case Exists
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.