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

SOAP connect failing because rule is blank and can't be modified



There is a Connect-SOAP rule to invoke a WCC service from CSP PEGA. Where security profile is added. In PEGA 7.2.1 environment that rule is blank and user is not able to modify that rule as well. As a result the soap connect is failing. However, if the user logs in as an Administrator then the rule shows up fine and the user can even add/modify it.

Error Messages

Not Applicable

Steps to Reproduce

tried to open in internet exploer but issue still persists

Root Cause

An issue in the custom application code or rules .

This is a custom code for WS-Security rule wriiten by customer. Because in the OOB WS-Security ruke form , we can not see the "extended configuration" checkbox.


Explained user the above asked them to look into their code.

Suggest Edit

Published March 26, 2017 - 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