Skip to main content

Requirement - select a relevant Service on the Create Request screen and have the Service Price Rule be applied to the Request instead of the Price Rule defined on the Contract Line. This works for SLAs but not for the Price Rule?

 

I have a Service defined with it’s own Price Rule set, see screenshot.

This Service is then added to the Services tab in my Contract. 

However, when I’m logging my Request, the SLA is being read from the Service ok (as expected) BUT my Price Rule is not being pulled into the Request like the SLA. Does anyone know why this might not be? 

 

I’ve done two tests: 

 

Test 1 - a Contract Line set to Invoice Plan (therefore no price rule at Contract Level). No Price Rule is triggered at Request level - completely ignoring my Service Price Rule.

 

Test 2 - a Contract Line with a Defined Price Rule (therefore not Invoice Plan). This pulls in the Contract Line’s Price rule therefore ignoring my Service’s price rule again.

 

 

Is this intended? If so what’s the point of defining a Price Rule at Service Level if it’s to be ignored? or have it not configured something correctly? 

 

Thanks in advance for any help! :) 

The Price Rule defined in the Service Catalog is used when you don’t use contracts. Price rules are mandatory on contract lines unless they are invoice plans, whereas SLA templates aren’t. 

Is there something you cannot achieve with the current logic?

Terms & ConditionsCookie settingsAccessibility statement