Example: There is not much difference in the Case life cycle of Case "A" , "B" and "C" except few section.I want to use "Specialization using Pattern Inheritance" to handle it. (Don't want circumstance)
I can withdraw case type rule in class A ,B and C, set pxObjClass to A,B or C based on a property value when I am on the New harness of Case S.
This way I can run the Case S flow and create Class A , B or C instances at run time.
Is this a acceptable solution? When i try to set pxObjClass in data transform, pega throws warning.
Any other option if i don't want to withdraw Case type rule? How i can trigger Case flow for S but still use custom section rules present in A, B and C?
Are there any specific reasons you don't want to consider circumstancing ?
Given you have some strong reasons, you probably don't need to withdraw the rules in Case A,B or C. You should be able to make use to rules in class S because of inheritance. The rules that are specific to A,B or C can be specialised in these . Specialised rules will be picked when case is initialised for class A,B or C