Last activity: 16 Feb 2017 12:24 EST
Format Problem "&" --> "&amp;"
I have created a Radio button with several choices like "New & Additional Contract". The Radio Button is sourced by a Property which contains a prompt list. The prompt list has entries like Standard Value: S01 Prompt Value S01 ....
Prompt Value S01 is a field value rule. So Field Value S01 contains the string "New & Additional Contract".
Now if i starting the Portal the "&" sign of the string will be shown as "&"! It is curious because it works if i use a Label field instead of a Radio button. So my question is it not possible to use symbols within field values?
Thanks a lot
Can you please share us the PRPC version you are working on ?
it is PRPC 7.1.7 and I found something that i probably need an additional hotfix 22332 to solve this Problem
The Hotfix-22332 is for field values containing double quotes. Exact scenario is "When field values that contain quotes are used with controls like Radio buttons, checkbox and dropdown then these controls show encoded values of quotes."
I have tried the above mentioned design at my end. I am able to observe the same behavior at my end.
On running the usecase:
I will investigate the behavior at my end and will get back to you with more updates.
I have checked the behavior after installing the hotfix. The hotfix-22332 will help solve the behavior. There is an additional instruction that needs to be followed. After installing the hotfix, if the Field Values already contain encoded values then manually replace them with & and Resave the field values.
Please rasie an SR with GCS to obtain the hotfix.
Tata Consultancy Services
I have tried using this but the main problem is the values are present in the Clipboard pxResults and in the UI the row is still exists.
kindly help us on this.
Thank you very much Mounika. I will do that and let you know if it completely solves my Problem!
Please let us know here if you end up opening an SR!
Lochan | Online Community Moderator | Pegasystems Inc.
Is this issue resolved in Pega 7.1.8? I am facing same issue in my Application, which is built on Pega 7.1.8, but this Hfix is available for Pega 7.1.7
As per the BUG-203518 details the issue is fixed in 7.1.9 release. You can raise an SR with Support team for 7.1.8 fix.
Please let us know if you open up an SR by leaving a new reply with the SR number. This helps us to connect the SR with this post for context.
Marissa | Community Moderator | Pegasystems Inc.