Support Article
Page-New method not setting the class
SA-20563
Summary
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.
Resolution
Perform the following local-change:
- Import the class rule to the appropriate ruleset.
- Revalidate and save the calling activity.
Published March 12, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.