Is it a best practice to always map the concrete data class to the CustomerData schema?

General
, , ,
1

Is it a best practice to always map the concrete data class to the CustomerData schema? but what if the data type need to contain pega default columns like pxcreatedatetime.

CustomerData:

The Database schema in which all the table created will not have any pega default columns like pxcreatedatime, pxupdatedatetime etc… and no blob in it.

PegaData:

The Database schema in which all the table created will have few pega default columns like pxcreatedatime, pxupdatedatetime etc… and blob in it.

2

@Karthik Kummera

It’s generally best to map concrete data classes to the CustomerData schema to avoid unnecessary Pega-specific columns and blob. However, if your data type needs to include Pega default columns like pxcreatedatetime, pzInsKey etc you should use the PegaData schema