In my case I had to change:
getValue('ServiceCategoryFullPath')
to
getDisplay('ServiceCategoryFullPath')
But same applies e.g. for Description, and may also apply for other properties.
As the frontend-code does not know which properties might be translated (may change on version change, or by configuration...), I would suggest to always use getDisplay instead of getValue, except when explictly the technical value is necessary.
Hi folks,
I came up with this when checking why the sidesheet for service items (new product...) is showing the raw value for the service category fullpath, which is translated in my case. I found that in this case the ootb code is using getValue instead of getDisplay. But most values the users see may be translated, and usually you don't want users to see the technical values as they might be confusing... Example: https://github.com/OneIdentity/IdentityManager.Imx/blob/v92/imxweb/projects/qer/src/lib/new-request/new-request-product/product-details-sidesheet/product-details-sidesheet.component.html
In my case I had to change:
getValue('ServiceCategoryFullPath')
togetDisplay('ServiceCategoryFullPath')
But same applies e.g. for Description, and may also apply for other properties.
As the frontend-code does not know which properties might be translated (may change on version change, or by configuration...), I would suggest to always use getDisplay instead of getValue, except when explictly the technical value is necessary.
Best Regards
Andreas