Multiple Concrete Classes mapped to a single Database Table
In v6.3 I had faced a situation where two classes were mapped to a single database table. While performing a test connectivity on the classes, I used to get an error "External data table XYZ in database PegaRULES has more than one concrete class mapped to it ...". During runtime, the behaviour was pretty erratic. Either of the class instances used to have issues while save/commit. I dont remeber the exact error message that I used to get.
My question here is:
Is the above behaviour in Pega by design? If yes, why so? I think there might be situation when we might need more classes linked to a single table.
***Updated by moderator: Lochan to add Categories***