Question
Capgemini
GB
Last activity: 24 Jan 2025 13:03 EST
How to enter OOTB annotation in a field in Constellation portal
Pega has many OOTB annotation and I want to display value of a field with one of these annotations
For example, I tried APPLICATION_DESC which is an @ENV annotation and I expected Pega to show the value of application description but its not working. See attached images.
HCA Healthcare
US
@SateeshB6784 To use an OOTB annotation like @ENV['APPLICATION_DESC'] in the Constellation portal, make sure the annotation is supported and properly configured. Check that the application description is set in App Studio > Application > Definition. In the field configuration, set the value as @ENV['APPLICATION_DESC']. If it doesn’t work, verify that the annotation is available in your Pega version and ensure the context where the field is rendered can access @ENV annotations. Test the annotation by temporarily displaying it in a field to check the output. Thanks
Updated: 23 Jan 2025 9:28 EST
Pegasystems Inc.
US
@SateeshB6784 Annotation is used in the pyHome page view to show the application description using @ENV APPLICATION_DESC.
Unfortunately annotations are not supported in the UX authoring UI - Entering @ENV APPLICATION_DESC in any input field will be considered as a label and be prefixed with the @L annotation and will not render correctly at runtime. Also only a fixed set of annotations is supported and you cannot extend or add other annotations. The recommended approach is to create a new property and populate it through a declare expression.
There is a way to use annotation by editing the view JSON manually and marking the view as custom - This is not a recommended setting and should be used rarely and only in limited circumstances since marking a view as custom might impact upgrade of your application.
Here is an example using USER_ID annotation for the pyHome page view
@SateeshB6784 Annotation is used in the pyHome page view to show the application description using @ENV APPLICATION_DESC.
Unfortunately annotations are not supported in the UX authoring UI - Entering @ENV APPLICATION_DESC in any input field will be considered as a label and be prefixed with the @L annotation and will not render correctly at runtime. Also only a fixed set of annotations is supported and you cannot extend or add other annotations. The recommended approach is to create a new property and populate it through a declare expression.
There is a way to use annotation by editing the view JSON manually and marking the view as custom - This is not a recommended setting and should be used rarely and only in limited circumstances since marking a view as custom might impact upgrade of your application.
Here is an example using USER_ID annotation for the pyHome page view
Here is the list of supported annotations - None of them are really useful outside of USER_NAME and APPLICATION_DESC
- APPLICATION_NAME
- ACCESS_GROUP
- USER_NAME
- USER_ID
- APPLICATION_DESC
- LOCALE
- TIMEZONE
- WORK_GROUP
Capgemini
GB
@RichardMarsot - Thank you Richard, very helpful. When we create a new portal, by default it is set to APPLICATION_DESC. One of my team member has changed it to a static value and I want to put it back. When I type APPLICATION_DESC its not working like it was before. Is there a way to fix this issue other than making the view as custom?
Pegasystems Inc.
US
@SateeshB6784 you need to recreate the portal - unfortunately. This should take no more than 1mn to fix since you reuse all your landing pages