In Pega 7.4 version, We have a validation ( when rule ) in step 1 of "PegaAccel-Task-. pzCreateLocalDataStorage" activity not to use "PegaDATA" Database for Configuring source for Data types due to some Internal Constraints. It seems PEGA introduced the CustomerData database rule since PEGA 7.4 and when we create the Data Type rule, PEGA is by default adding px related properties. You can use "CustomerData" DB ( which is pointing to PegaDATA ) for Configuring source in Data types for System of Record.
What is the intended purpose of this new database / Schema? It seems to have customer database tables in it. I can see perhaps it may have been intended for some security or logical grouping but how does it then make sense to have the data types created in that?
Is there any update for the reason of this change?
We are not planning to store any customer data but we do need to create some for configuration information. Is there a possible override to this? (Manual script execution for the creation of table in PegaDATA schema?)
Also, when creating a product in 7.4 and trying to import in 7.3.1 an error is raised during import process about invalid CustomerData DB. Tried removing the DB-Name instance from package but did not help. Any idea how to work around this?
I would like to understand why though? Its not ideal just saying 'we have moved something' without the rationale. Customer data is quite a misleading schema name also especially if you are dealing with customer service applications.
FYI, Now Pega relaxed the restriction to select only CustomerData when creating local data storage for Datatypes. In 8.1.2, it is fixed and you can create local storage for Datatypes in PegaDATA schema.