Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Kuldeep Singh Hada (Karate) Optum
Optum
US
Karate Member since 2016 7 posts
Optum
Posted: Nov 27, 2019
Last activity: Nov 27, 2019
Posted: 27 Nov 2019 13:43 EST
Last activity: 27 Nov 2019 17:04 EST
Closed

Question about Specialization using Pattern Inheritance

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)

Org-Div-Work-S

Org-Div-Work-S-A

Org-Div-Work-S-B

Org-Div-Work-S-C

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?

To see attachments, please log in.
Case Management

  • Kumar Pushkar Venkat Punati Achalasri Kaza Venkata Nunna
Posted: 4 years ago
Posted: 27 Nov 2019 17:04 EST
Gurpreet Dhanoa (dhang) PEGA Principal System Architect
Pegasystems Inc.
AU
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
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice