Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Troubleshooting: RuleNotFound error in called activity with different class inheritance

Updated on September 13, 2021

Symptom

The following exception appeared during execution of an activity:

FUAInstance-RuleNotFound Rule-Obj-Activity Beta

This occurred under the conditions detailed below:

The application contains two classes that do not inherit from a common class:

  • PegaSample (descends from Work-)
  • MyCo-Data (descends from Data-)

Also defined are two activities:

  • Alpha, which is defined on PegaSample
  • Beta, which is defined on MyCo-Data

And a clipboard page:

  • BetaPage, which is of class MyCo-Data

The activity Alpha calls the activity Beta with step page BetaPage.

Because the Beta activity is in a class unrelated to that of its caller, the step page (BetaPage) passed to the BetaActivity must be defined on the Pages & Classes tab of Alpha to allow Alpha to find Beta at runtime.

Note that this step page in activity Alpha becomes the primary page of activity Beta. Rule assembly assumes that the primary page of an activity is of the same (or a descendent) class as the class in which the activity is defined.

The Alpha Activity saves without problems, but at runtime, the error occurs.

Solution

Explanation

Listing BetaPage on the Pages & Classes tab of activity Alpha with class MyCo-Data is sufficient to allow design-time validation of activity Beta. However, at run-time, the actual class of the step/primary page being passed to a called activity is used to locate the activity. Therefore, in order for activity Alpha to find activity Beta at run-time, the page specified as the step/primary page to be passed to activity Beta (the BetaPage of class MyCo-Data) must exist on the clipboard.

The step page of class MyCo-Data might have been created at a previous point in the processing, in which case the Activities run without error. If this step page does not exist on the clipboard, then at run-time, activity Alpha does not find activity Beta and an error occurs.

Resolution

There are two ways that Alpha can call Beta without error at runtime:

  • A step page of class MyCo-Data can be defined in a prior step in the Alpha Activity, so that Alpha can find Beta.
  • The call to Beta can be prefaced with the name of the class: MyCo-Data.Beta

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect Data Integration Low-Code App Development

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us