Mandating Request Type field when extending Resource Plans - avoid having 0 effort allocations

[PaulaaO]

Hi Community,

I am looking for some best practice advice in the following situation: we're facing some issues in resource plans not getting extended correctly, more precisely users are bypassing the value in the Request type which generates 0 effort records (requested allocations and then resource allocations if the Resource Manager doesn't pick up the mistake).

For this reason, I'm thinking that we need to mandate the Request type field to force end users to select a value for this field, but unsure what's the best way to go about it:

a. mandate the field from the Dictionary which means the field will always be mandated (when resource plan gets created, extended, etc.) ? OR
b. is there other component you advise to amend and enable the mandatory behaviour? Have found the following components which seem to drive the behaviour: ResourcePlanExtension (Script Include); request_for_resource_plan_extend (UI page) >>have I missed any?

If anybody had to do something similar, please share - any help appreciated 🙂

Many thanks,

Paula

[PaulaaO]

I have reached out to SN Support and they suggested to go with either:

a. amending the Dictionary associated to the field

b. creating an UI Policy and UI Policy action for this field

---------

LE: I've removed the solution as it doesn't work for the scenarios I needed.

The field is not being mandated with either solutions when Extend or Request Extension UI Actions are being used.