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

Page-New method not setting the class



While using a SOAP connector to an external (non-Pega) system the activity that runs fails. 

The Page-New method is not using the class name defined in the Pages & Classes tab for the step page, so the activity call is using the applies to class of the activity instead of the class for the step page.

Error Messages

Could not find Rule-Connect-SOAP instance My-FWClass.MySoapService

Steps to Reproduce

Initiate the processing through a SOAP service.

Root Cause

After migrating a ruleset to a higher environment, the ruleset name was changed in the lower environment. 

​The ruleset was deleted and reimported with the correct name however the class was not properly moved.  The activity call was generated without the desired class rule present in the system, so the assembly of the calling activity defaulted to using the calling activity's applies to class, instead of the class on the step page of the activity.


Perform the following local-change:
  1. Import the class rule to the appropriate ruleset.
  2. Revalidate and save the calling activity.

Published March 12, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 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