Posted: 11 Oct 2019 17:29 EDT Last activity: 28 Oct 2019 21:04 EDT
Advanced Tab Class Option - Propagate schema changes to child tables
On the advanced tab of the rule-obj-class ruleform, there is an option to "Propagate schema changes to child tables". This sets the .pyIsCoreClass property, which is referenced nowhere else in the system. There is no documentation around this option.
I've created a framework work class, and an implementation work class that direct inherits to it. On the framework class, I checked the "Propagate schema changes to child tables" checkbox. Then, I imported a product that triggered changes to the framework's db table. Nothing happened to the implementation work class's database table.
Does anyone know if this functionality is intended to work? It looks like it was added in 8.x. From what I can tell, the functionality is not yet fully flushed out. Does anyone know when it will be? The functionality would be very helpful if it works.
Do you think then that the purpose of the "Propagate schema changes to child tables" actually means "changes to the core tables...pr4_rule, pr_data, pc_work, and pc_history_work should be propagated to self/current class"? The wording of the checkbox label as it is today, feels like the intent is to make the current class's be considered a core table, and that changes to the current class's table would then be propagated to to its children.
Posted: 2 years ago
Updated: 2 years ago
Posted: 21 Oct 2019 0:29 EDT Updated: 21 Oct 2019 0:28 EDT
Vikash Ranjan Karn (Vikash Karn)
Senior Technical Solutions Engineer
When the new application wizard is run to extend the FW layer, it creates equivalent case types by "direct-inheriting" from case types in the FW layer. The new application wizard used to clone the tables that are mapped to the FW layer case-types.
This option is provided to clone all the exposed columns (optimized for reporting) to the newly created tables as previously it didnt used to clone these columns.
It would be really slick if the checkbox triggered the implementation class tables to create/update the new columns when imported product rules caused those sorts of changes on the framework class's tables.