If we optimise a property then move it other environment like SIT etc,then why do we need to include Data-Admin-DB-Table instance in product rule?
If we optimise a property then move it other environment like SIT etc, then why do we need to include Data-Admin-DB-Table instance in product rule?cant we just include the pzinskey of the class in which this property is and the pzinskey of the database to which this properties class is mapped to?
***Edited by Moderator Rupashree S. to add Capability tags***
Accepted Solution
Updated: 11 Jun 2024 3:42 EDT
Eclatprime Digital Private Limited
AU
Hi @TanyaS58, pzInsKey will just move the property and the changes which you made in that but exposing a column in the table need to be done in the other environment as well right. So for this you need to send the Data-Admin-DB-Table instance to expose in the higher environment or you can execute an SQL to create the column in next environment. Hope this gives you answer. Thanks
OCBC
SG
While we are deploying product to next environment if we add Data-Admin-DB-Table instance in product rule, PEGA checks for DB schema changes and applies all the schema related changes in the next environment and also performs column population jobs if a property is optimized.
Accepted Solution
Updated: 11 Jun 2024 3:42 EDT
Eclatprime Digital Private Limited
AU
Hi @TanyaS58, pzInsKey will just move the property and the changes which you made in that but exposing a column in the table need to be done in the other environment as well right. So for this you need to send the Data-Admin-DB-Table instance to expose in the higher environment or you can execute an SQL to create the column in next environment. Hope this gives you answer. Thanks