Set PersonWantsOrg properties to mandatory for specific products

You haven't specified the version you are using. Your solution with the product parameters should work in 8.1 more easily, as the UI only shows each property once, regardless if it is coming by default or via a request property.

Hi Markus,

Thanks for the reply - this is on version 8.1.5

In this scenario we have created a request property mapping to the reason field, setting to mandatory and changing the title to "reason for access".

When the requestor raises the request, all looks good. They are prompted to populate the mandatory field and their PWO screen shows the single "reason for access" field.

However, then when the approver logs in, when they view the request to approve, they see 2 fields: 1 named "reason" and another named "reason for access", both containing the value the end user entered.

Hi Grant,

you are right. It was only solved for the request pages but not for the approval pages. I have created backlog entry VPR#34798 to add this behavior to the approval pages as well.

Hi Grant,

you are right. It was only solved for the request pages but not for the approval pages. I have created backlog entry VPR#34798 to add this behavior to the approval pages as well.