Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Child class activity does not get called at runtime

SA-8132

Summary



Developer has created two activities p1 & p2 in parent class and tries to call p2 activity from p1 activity. Developer also creates another version of p2 activity in child class which is a specialized version. When child class flow is called activity p1 is run,  p2 activity from parent is called instead of specialized version present in child class.

Error Messages



No Error message.
Wrong version of activity is running at runtime.


Steps to Reproduce



1. Create two Activities Act1, Act2 in AAAA- class.
2. Create another activity in AAAA-BBBB class with name Act2 (specialized version of Act2 in AAAA- )
3. Call Act2 from Act1 using call method and do not use any step method.
4. Now run Act1 from AAAA-BBBB flow and observe which version of Act2 is calling at runtime.

 

Root Cause



The root cause of this problem is a defect in customer application code/rules.
Developer has not used any step page in Act1 for the step where there is a call to Act2. So as per PRPC rule resolution, Act2 present in AAAA- is called at runtime.

Resolution



This issue is resolved through the following Local-change:
There should be a step page in Act1 for the step where there is a call to Act2 and that step page must be present on clipboard and refer to AAAA-BBBB class at run time, then Act2 present in AAAA-BBBB class is called.
 

 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us