I’m looking at a requirement where I want to provide additional contextual information to users while they are working with a form - specifically on Read-Only fields (In Service cases or in Customer 360).
For example, in a UI Kit application, we used an information icon next to a field that users can click/hover to see additional details.
We can do this constellation, as well.
We need do it on form view.
Create a text property and go to advance tab of that property and scroll to bottum you see additional information and some times a pega create a paragraph rule along with property creation.
You can give the additional information you wanted to show on the “i” icon. Or create a paragraph with required text and configure that paragraph rule in that additional info field of advanced setting of that property.
use that property on the form view and enable tooltip in respective view settings for the property you gave.
Once UI loads you see an “i” icon and hovering on it you can see the text you gave on the paragraph.
please check this if you are trying get same behaviour.
At runtime, this renders the “i” icon next to the field and, upon click, it shows the additional information for the field. All OOTB using Constellation.
@NaganandShenoy additional information does not show for read only contexts. This is coming on the roadmap but in the mean time I would be trying to understand better what you need to show more information and context on and use one of the other available features (data reference / preview, field group instructions etc.)
Thanks @Will_Cho & @SivaramaSaimadhav72
Adding the additional information worked for read-only & Editable fields in both 25.1.3 & 26.
@MarcCheong We are working on the CSFS framework & currently in Pega 25.1.3.
My use case is that we want to show additional information on hover/click of an “i” icon on the Customer 360 (which is a full page view) for only a few specific fields that are not categorised under a field group. As shared in the screenshot below.
The above suggestions from Will & Sivarama worked for me for the Service cases under an Interaction case. But not for the fields in Customer 360 of an Interaction.
Please let me know if you need any additional information to understand the use case.
