• State Suggested Answer
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 93 subscribers
  • Views 831 views
  • Users 0 members are here
Options
Related

Set PersonWantsOrg properties to mandatory for specific products

grant.kerwood
over 2 years ago

This seems like it should be straight forward, however I haven't been able to find a simple solution to the following:

There are a number of ootb fields on the PWO records which are used to capture details during the request - Reason, Valid From and Valid Util.

Is there a way of setting these fields to be mandatory for specific AccProducts?

IE product A requires Valid To field to be populated, product B this can remain optional.

We are able to create a request property which maps to the Valid Until field with the mandatory flag enabled.  This works for the end user, as they are prompted to complete the field on raising the request - however the approver then sees 2 Valid Until fields both containing the same information.

Any ideas?

Parents Reply Children
  • 0 over 2 years ago in reply to Markus Weiss-Ehlers

    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.

  • 0 over 2 years ago in reply to grant.kerwood

    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.