Corrupted word in Flow when called from [Create Work] local action
I am getting a unreadable japanese value (corrupted) in a flow (pyStartCase) as a parameter value. It only happens when the japanese word passed to to flow by parameter, like FlowParameter <- param1.value if I pass japanese word directly to flow parameter , it does not happen. FlowParameter <- "こんにちは！"
Reproduce step:
1. Create a button on a section
2. Set [Create work] as action to the button above.
3. In Create work setting, set any case type and select pyStartCase Flow. ( pyStartCase Flow has one parameter , like Param1)
4. In the [Create work] setting area, set flow (pyStartCase) parameter Param1 <- paramT.value (paramT is a local parameter holds a japanese word)
Result:
1. In the Flow (.pyStartCase), getting an corrupted japanese word. Expect Japanese word value: こんにちは！ Actuall getting : ????????≪?????￣???
Does anyone know how to solve this? Thank you!
***Edited by Moderator: Pallavi to update platform capability tags, update Support Case details***
Accepted Solution
Updated: 25 Jun 2020 10:03 EDT
Pegasystems Inc.
JP
I've created an SR (INC-130596) and GCS said this is a bug. This will be fixed in the future release (exact version is unknown yet).
[Issue]
If you pass multibyte characters to pyStartCase, string gets scrambled.
[Solution]
Since the fix is not included in the current version, apply a local change - add below snippet in the "UserWorkForm" HTML Fragment.
I've created an SR (INC-130596) and GCS said this is a bug. This will be fixed in the future release (exact version is unknown yet).
[Issue]
If you pass multibyte characters to pyStartCase, string gets scrambled.
[Solution]
Since the fix is not included in the current version, apply a local change - add below snippet in the "UserWorkForm" HTML Fragment.
<script> function createNewWork(strClassName, harnessVersion, strFlowName, strFlowParams,contentID, dynamicContainerID, skipConflictCheck,configParams) { var flowParamsafterDecode = ""; if (strFlowParams && strFlowParams != '') { var oParams = strFlowParams.split("&"); for (var i = 0; i < oParams.length; i++) { if (oParams[i] != '') { var oParamNVPair = oParams[i].split("="); if(oParamNVPair != '') { flowParamsafterDecode += "&"+ oParamNVPair[0] + "=" + decodeURIComponent(oParamNVPair[1]); } } } if (flowParamsafterDecode && flowParamsafterDecode != '') strFlowParams = flowParamsafterDecode; } return pega.desktop.createNewWork(strClassName, harnessVersion, strFlowName, strFlowParams,contentID,dynamicContainerID, skipConflictCheck, configParams); } </script>
Now you should be able to see multibyte characters correctly.
Thanks,
Pegasystems Inc.
US
What is the Pega version?
I see a similar issue reported here and resolved by a hot fix in 7.4. The hot fix changes were included in the 8.1.1 and 8.2 releases so should already be there if you are on a later release.
Pegasystems Inc.
JP
Thank you for your reply.
My Pega version is ver. 8.4.1.
It seems like the same issue, but in my case, if I set Japanese character directly into Flow param (not by a property), this issue will not happen...
Accepted Solution
Updated: 25 Jun 2020 10:03 EDT
Pegasystems Inc.
JP
I've created an SR (INC-130596) and GCS said this is a bug. This will be fixed in the future release (exact version is unknown yet).
[Issue]
If you pass multibyte characters to pyStartCase, string gets scrambled.
[Solution]
Since the fix is not included in the current version, apply a local change - add below snippet in the "UserWorkForm" HTML Fragment.
I've created an SR (INC-130596) and GCS said this is a bug. This will be fixed in the future release (exact version is unknown yet).
[Issue]
If you pass multibyte characters to pyStartCase, string gets scrambled.
[Solution]
Since the fix is not included in the current version, apply a local change - add below snippet in the "UserWorkForm" HTML Fragment.
<script> function createNewWork(strClassName, harnessVersion, strFlowName, strFlowParams,contentID, dynamicContainerID, skipConflictCheck,configParams) { var flowParamsafterDecode = ""; if (strFlowParams && strFlowParams != '') { var oParams = strFlowParams.split("&"); for (var i = 0; i < oParams.length; i++) { if (oParams[i] != '') { var oParamNVPair = oParams[i].split("="); if(oParamNVPair != '') { flowParamsafterDecode += "&"+ oParamNVPair[0] + "=" + decodeURIComponent(oParamNVPair[1]); } } } if (flowParamsafterDecode && flowParamsafterDecode != '') strFlowParams = flowParamsafterDecode; } return pega.desktop.createNewWork(strClassName, harnessVersion, strFlowName, strFlowParams,contentID,dynamicContainerID, skipConflictCheck, configParams); } </script>
Now you should be able to see multibyte characters correctly.
Thanks,