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

Service call is not working with some of the Japanese characters

SA-18473

Summary



User is trying to set property pyTempDataPage as "いただいた方がご入会" and in a Activity calling "Connect-SOAP" method.
While executing the "Connect-SOAP" method with mentioned Japanese content, user is getting an parser error from InvokeAxis Activity of "Rule-COnnect-SOAP" class.


Error Messages


problem accessing the parser. Parser already accessed!


Steps to Reproduce



1) Property set to pyTempDataPage as "いただいた方がご入会".
2) In a Activity call "Connect-SOAP" method.
3) While excuting the "Connect-SOAP"method with above japenese content user is getting an parser error from Ivoke axis activity of "Rule-Connect-Soap" class.


Root Cause



A defect or configuration issue in the operating environment, WS-Security Signature when enabled is not allowing the Unicoded characters in the request envelope and hence not reaching the server, so user is suggested to encode the unicoded characters in base64 format and send it in the request.

Resolution


 

User must handle the request parameters by encoding in base64 with the help of expression builder and store the encoded values in local variables to send the request, which does not destroy the actual state of the property value.
This is holding unicoded characters, user can still be able to view the unicoded characters from the actual properties.
 

Published January 26, 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