Question

WrongModeException with Property-Set and StringBuffer-Append

Hello, everyone.

I sometimes encountered WrongModeException when editing Activities, using Property-Set method or StringBuffer-Append method in Pega 7.3.1.

The message displayed is as following:
"com.pega.pegarules.pub.clipboard.WrongModeException: The property RH_1.pySteps(2).pyStepsCallParams.pyStepsParamUI was of mode String while com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.iterator() was expecting a List or Page mode. Details: (none)"

At first, I thought that something wrong occured with the parameter type of Property-Set or StringBuffer-Append.
However, when I look at the Clipboard, the parameters of Property-Set and StringBuffer-Append are stored in RH_1.pySteps(n).pyParamArray(m), not RH_1.pySteps(n).pyStepsCallParams.pyStepsParamUI.

(For other methods (such as Property-Map-DecisionTable, Log-Message, and so on), the parameters were stored in RH_1.pySteps (n) .pyStepsCallParams.pyStepsParamUI.)

Can anyone help me to clarify the following points ?
* Why does the program which raised the Exception check elements other than where the parameters are stored with Property-Set and StringBuffer-Append ?
* How can I avoid this Exception ?

Thanks in advance.

Correct Answer
May 8, 2019 - 4:22am

There is a known issue which can occurs after the passivation. If you don't have HFix-46352, I propose you to open a case and request this fix.

Regards

Simon

Comments

Keep up to date on this post and subscribe to comments

May 8, 2019 - 4:01am

Hello everyone,

Is there anyone who can help me ?
If you need more information for consideration, please let me know.

Best Regards,

Pega
May 8, 2019 - 4:22am
Response to YujiW777

There is a known issue which can occurs after the passivation. If you don't have HFix-46352, I propose you to open a case and request this fix.

Regards

Simon

May 8, 2019 - 5:30am
Response to chans3

Hello Simon,

Thank you for providing information.

As a result of investigation, HFix-46352 has not been applied to our system.
I will consider applying the hotfix.

Thank you very much.

May 22, 2019 - 2:09am

Hello Simon,

I considered with team members and decided to apply the hotfix in the future.
The application timing will be a little later to coincide with the application of other hotfixes.

I will close this issue as resolved.
Thank you very much.

Yuji

Mod
May 22, 2019 - 5:33am
Response to YujiW777

Thanks for the update! I have marked Simon's reply as the Correct Answer.

Lochana | Community Moderator | Pegasystems Inc.