Issue with migrating embedded optimized properties
Developers notice that after they attempt to migrate optimized embedded properties to a system which has the embedded properties defined but not exposed, that the target system doesn't perform as if the property was exposed. They also notice that post migration the Rule-Obj-Class associated to the embedded properties doesn't have the properties defined on the External Mapping tab. The developers confirmed this behavior by reviewing the contents of the database field that they created to align against the exposed property(Null).
Steps to Reproduce
1. Optimize a Work Object(WO) embedded property
2. Generate a Rule-Admin-Product(RAP) and Migrate
3. Test creating instances of the WO on the higher environment and verify the embedded exposed property isn't mapped into the created column.
The root cause of this problem is a defect in Pegasystems’ code/rules. The activity pzOptimizeAproperty doesn't update the pxUpdateTime when saving the associated class instance.
This issue is scheduled to be resolved in Pega 7.1.8
100% found this useful