Skip to main content

 

You can turn ‘P.O. required’ flag on in Customer Center to make PO field in Service Order mandatory, but this will also make PO mandatory in Customer Contract.

 

 

This will create an issue when a customer provides PO only at the service order level.  When PO is mandatory in Customer Contract, PO field in a new service order gets a default PO value from a contract, so the system will not force the user to enter a PO value unique to the service order.

Is there any way to make PO field mandatory only in Service Order, but not in Customer Contract?

Hi Susie,

I would think you can use Customizer to make this field mandatory for the UI at least.  This will not enforce uniqueness (which should be based on customer + po number level) nor prevent logging calls via integrations.

Otherwise, unless someone else knows, I think this would be a customization change request.

Hi Susie,

Confirmed with R&D, there is no functionality to make PO mandatory for only the service order other than the Customizer UI changes I mentioned in the previous post.

And don’t forget to test mobile afterwards when making these kinds of mandatory field changes on the back-end application.  We don’t allow you to change the logic on the Customer PO field in the Mobile Customizer application since the logic is downloaded from the back-end application (so if possible try to use the Alliance Customizer to make it NOT MANDATORY in the Customer Contracts module instead of turning off that flag completely and just making it mandatory in the Service Order module in Alliance).

Thanks all for your comments.  I agree that this can be only done by IFS customization.  We can’t use customizer because this setting should be applied to only some customers.

Reply


Terms & ConditionsCookie settings